We have a setup where a pair of A99K boxes (IOS XR 7.1.3) are working as PE
routers, and on MLACP (active/standby) Bundle towards Metro Switch are
mixed L2/L3 subinterfaces.
When we try to configure static routes on standby node in customer VRF,
routes are advertised through both active and standby PoAs to the core
MPLS (it is advertised on both routers).
Is there any way on IOS-XR (7.1.3) that provides blocking of advertising
static routes on standby PoA in L3VPN MC-LAG environment.
Something tells me that this is not normal behavior (BUG maybe, or feature
XD )
I've found that on IOS-XE this works normal, feature is called:
Multichassis Link Aggregation Group for L3VPN
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l3_vpns/configuration/xe-16-9/mp-l3-vpns-xe-16-9-book/mc-lag-for_l3vpn.pdf
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
routers, and on MLACP (active/standby) Bundle towards Metro Switch are
mixed L2/L3 subinterfaces.
When we try to configure static routes on standby node in customer VRF,
routes are advertised through both active and standby PoAs to the core
MPLS (it is advertised on both routers).
Is there any way on IOS-XR (7.1.3) that provides blocking of advertising
static routes on standby PoA in L3VPN MC-LAG environment.
Something tells me that this is not normal behavior (BUG maybe, or feature
XD )
I've found that on IOS-XE this works normal, feature is called:
Multichassis Link Aggregation Group for L3VPN
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/mp_l3_vpns/configuration/xe-16-9/mp-l3-vpns-xe-16-9-book/mc-lag-for_l3vpn.pdf
_______________________________________________
cisco-nsp mailing list cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/