[VPNSERVICE-33] Need vlan member support on same tap port with customized interface name support Created: 28/Jan/16  Updated: 08/Feb/16  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: Faseela K
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

Severity: critical
External issue ID: 5127

 Description   

Vlan-Interface creation:
===================
{
"interface": [

{ "enabled": "true", "description": "Vlan Interface s1-eth1-1000", "name": "s1-eth1-1000", "datapath-node-identifier": "1", "odl-interface:vlan-id": "1000", "parent-interface": "s1-eth1", "type": "iana-if-type:l2vlan" }

]
}

But I didn’t see vlan-interface creation in the Operation data-store of interface-state DS. Due to this At the time of elan-interface creation when we query vlan-interface from Interface-state operational Datastore no object is return and we not able to programmed flows and group(Elan-group).

Currently when interface name is provided other than the tap portname/switch port name . There is not Table 0,Table 52 etc not programmed .(Nothing other than default flows ) and ELAN group ( not programmed).

If we provided tap port name then everything gets programmed even for single vlan member .

Issue here is when interface name is anything else other than tap portname nothing gets programmed which has to be handled to test multiple vlan ports to same OF port .

Also operation datastore does not have lower level interface information .

 Comments   
Comment by Faseela K [ 29/Jan/16 ]

Issue has been fixed.
You have to use the json in below format :
http://localhost:8181/restconf/config/ietf-interfaces:interfaces/

{
"interface": [

{ "name": "s1-eth1", "type": "iana-if-type:l2vlan", "l2vlan-mode":"trunk", "enabled": "true" }

,

{ "name": "s1-eth2", "type": "iana-if-type:l2vlan", "l2vlan-mode":"trunk", "enabled": "true" }

]
}

http://localhost:8181/restconf/config/ietf-interfaces:interfaces/

{
"interface": [

{ "name": "s1-eth1-vlan1", "type": "iana-if-type:l2vlan", "l2vlan-mode":"native-tagged", "vlan-id":1000, "odl-interface:parent-interface": "s1-eth1", "enabled": "true" }

,

{ "name": "s1-eth1-vlan2", "type": "iana-if-type:l2vlan", "l2vlan-mode":"native-tagged", "vlan-id":2000, "odl-interface:parent-interface": "s1-eth1", "enabled": "true" }

,

{ "name": "s1-eth2-vlan1", "type": "iana-if-type:l2vlan", "l2vlan-mode":"native-tagged", "vlan-id":1000, "odl-interface:parent-interface": "s1-eth2", "enabled": "true" }

,

{ "name": "s1-eth2-vlan2", "type": "iana-if-type:l2vlan", "l2vlan-mode":"native-tagged", "vlan-id":2000, "odl-interface:parent-interface": "s1-eth2", "enabled": "true" }

]
}

Comment by VINAY S [ 08/Feb/16 ]

vERIFIED IN distribution-karaf-0.4.0-20160208.053726-3977

Generated at Wed Feb 07 20:47:09 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.