Comment 0 for bug 1803465

VN1 (subnet1 40.1.1.0/24 and subnet2 30.1.1.0/24)
Expectation is once subnet1 is exhausted, use subnet 2

This works for VM's

But when it comes to BMS, and bms is subnet1 want to talk to subnet2, 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_overlay_evpn_gateway__ interfaces irb unit 10 family inet
address 30.1.1.4/24 virtual-gateway-address 40.1.1.1
set groups __contrail_overlay_evpn_gateway__ interfaces irb unit 10 family inet
address 40.1.1.3/24 virtual-gateway-address 40.1.1.1

>>>>this is the config push on spine.....40.1.1.1 is the gateway for both subnet which is wrong.