CFM: BMS on a VN with multiple subnets not supported
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| Juniper Openstack | Status tracked in Trunk | |||||
| R5.0 |
Won't Fix
|
High
|
Unassigned | |||
| Trunk |
New
|
Critical
|
Atul Moghe | |||
Bug Description
VN1 (subnet1 40.1.1.0/24 and subnet2 30.1.1.0/24)
Expectation is once subnet1 is exhausted, use subnet 2 for same VN
This works for VM's
But when it comes to BMS, and bms in subnet1 want to talk to subnet2 (within same VN) , this needs a gateway to be configured on spine and this is failing to configure the g/w for subnet1 and subnet2 on spine
This is a must fix for 5.1 and release-note in 5.0.2
set groups __contrail_
address 30.1.1.4/24 virtual-
set groups __contrail_
address 40.1.1.3/24 virtual-
>>>>this is the config push on spine.....40.1.1.1 is the gateway for both subnet which is wrong.
| description: | updated |
| description: | updated |
| Jeba Paulaiyan (jebap) wrote | #1 |
| information type: | Proprietary → Public |
Notes:
When BMS are connected across different subnets that are part of same VN, the required gateway configuration is not pushed to the Spine by the device manager. To get the traffic flow between the BMS in such scenario, the workaround is to configure static ARP on the BMS.