Uploaded image for project: 'vpnservice'
  1. vpnservice
  2. VPNSERVICE-33

Need vlan member support on same tap port with customized interface name support

    XMLWordPrintable

Details

    • Bug
    • Status: Verified
    • Resolution: Done
    • unspecified
    • None
    • General
    • None
    • Operating System: All
      Platform: All

    • critical
    • 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 .

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            k.faseela Faseela K
            vinay.s@ericsson.com VINAY S
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: