DM: Wrong encapsulation when physical interface added to MX
Bug #1486154 reported by
amit surana
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Juniper Openstack | Status tracked in Trunk | |||||
R2.20 |
Fix Committed
|
High
|
Suresh Balineni | |||
Trunk |
Fix Committed
|
High
|
Suresh Balineni |
Bug Description
cannot add VLAN sub-interfaces to physical router (MX). If user tries to add vlan 2001 to a physical interface, DM pushes this:
root@cmbu-tasman# show groups __contrail__ interfaces xe-2/3/2
encapsulation ethernet-bridge;
unit 2001 {
family bridge;
}
It should instead push this:
set groups __contrail__ interfaces xe-2/3/2 flexible-
set groups __contrail__ interfaces xe-2/3/2 encapsulation extended-
set groups __contrail__ interfaces xe-2/3/2 unit 2001 vlan-id 2001
information type: | Proprietary → Public |
To post a comment you must log in.
Let's fix this by not generating the IFD configuration from DM.
Since DM doesn't have knowledge of PICs/MICs and SW versions,
it will be best to leave the IFD configuration to the user. There
may different devices with slightly different capabilities in
different versions of code. Ideally, we want the user to be able
to use different IFLs on the same IFD for L2 or L3 e.g. unit 0 may
have family bridge while unit 1 has family inet and/or inet6.