Two BMS on same VLAN, but different VN's on same TOR may have issues with bridge

Bug #1802683 reported by manishkn
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R5.0
New
Medium
Atul Moghe
Trunk
New
Medium
Atul Moghe

Bug Description

I have VN10 (vni 6) and VN11 (vni 7)
Created two BMS instance on same QFX with same vlan-id 10 then we are in trouble, because we try to match vlan and vni always.
Both the BMS interface goes inside same bridge domain, rather than two different bridge domain.

Can we assume that on same TOR, customer will use separate VLAN per VN ?

Configuration snippet when BMS1 (vlan 10 VNI-6) and BMS-2 (vlan 12 VNI-7) on same TOR

root@5c3-qfx3# show groups __contrail_overlay_evpn_access__
interfaces {
    ae123 {
        flexible-vlan-tagging;
        mtu 9192;
        encapsulation extended-vlan-bridge;
        unit 10 {
            vlan-id 10;
        }
    }
    ae126 {
        flexible-vlan-tagging;
        mtu 9192;
        encapsulation extended-vlan-bridge;
        unit 12 {
            vlan-id 12;
        }
    }
}
protocols {
    evpn {
        multicast-mode ingress-replication;
    }
}
switch-options {
    vrf-target {
        auto;
    }
}
vlans {
    bd-6 {
        vlan-id 10;
        interface ae123.10; >>>>This is good
        vxlan {
            vni 6;
        }
    }
    bd-7 {
        vlan-id 12;
        interface ae126.12;>>>>>This is good, both goes to separate BD
        vxlan {
            vni 7;
        }
    }
}

Now when BMS1 (vlan 10 VNI-6) and BMS-2 (vlan 10 VNI-7) on same TOR

root@5c3-qfx3# show groups __contrail_overlay_evpn_access__
interfaces {
    ae123 {
        flexible-vlan-tagging;
        mtu 9192;
        encapsulation extended-vlan-bridge;
        unit 10 {
            vlan-id 10;
        }
    }
    ae126 {
        flexible-vlan-tagging;
        mtu 9192;
        encapsulation extended-vlan-bridge;
        unit 10 {
            vlan-id 10;
        }
    }
}
protocols {
    evpn {
        multicast-mode ingress-replication;
    }
}
switch-options {
    vrf-target {
        auto;
    }
}
vlans {
    bd-6 {
        vlan-id 10;
        interface ae123.10;>>>>>>>This is a problem
        interface ae126.10;>>>>>>>>This is a problem,,both bms coming to same BD
        vxlan {
            vni 6;
        }
    }
}

manishkn (manishkn)
Changed in juniperopenstack:
importance: Undecided → Medium
Revision history for this message
Jeba Paulaiyan (jebap) wrote :

Notes:

VLAN tagged BMSes attached to same leaf node in a fabric, but under different virtual network must assume different VLANs

Jeba Paulaiyan (jebap)
information type: Proprietary → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.