[VPNSERVICE-39] Datapath not working for single ELAN in single DPN when binding VLAN interface as Trunk to ELAN port Created: 02/Feb/16 Updated: 30/Oct/17 Resolved: 08/Feb/16 |
|
| Status: | Verified |
| Project: | vpnservice |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | VINAY S | Assignee: | P Govinda Rajulu |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| Severity: | minor |
| External issue ID: | 5184 |
| Description |
|
Datapath not working for single ELAN in single DPN when binding VLAN interface as Trunk to ELAN port Binding trunk to ELAN port not working . { , { "enabled": "true", "description": "Vlan Interface s1-eth2", "name": "s1-eth2", "l2vlan-mode":"trunk", "odl-interface:parent-interface": "s1-eth2", "type": "iana-if-type:l2vlan" } ] { ] { , { "elan-instance-name": "elan1", "description": "string1", "name": "s1-eth2" } ] opendaylight-user@root>java.lang.NullPointerException http://localhost:8181/restconf/operational/ietf-interfaces:interfaces-state/ , , { "name": "s1", "phys-address": "FA:71:4E:11:6D:4E", "lower-layer-if": [ "openflow:1:LOCAL" ], "admin-status": "up", "oper-status": "up", "if-index": 2 } ] http://localhost:8181/restconf/operational/elan:elan-dpn-interfaces/ { ] http://localhost:8181/restconf/operational/elan:elan-interfaces/ ] http://localhost:8181/restconf/operational/elan:elan-tag-name-map/ { ] |
| Comments |
| Comment by VINAY S [ 02/Feb/16 ] |
|
Attachment log - Copy.rar has been added with description: logs |
| Comment by VINAY S [ 02/Feb/16 ] |
|
mininet> sh ovs-ofctl -O OpenFlow13 dump-flows s1 mininet> |
| Comment by Vishal Thapar [ 05/Feb/16 ] |