Loading...
Loading...
Baseline issue which can affect ISSU with EVPN services configured.
ISSU load phase fails to complete because l2fib_mgr does not signal End of Initialization. As part of this, traffic loss will occur on affected services and will not recover until l2vpn_mgr restart.
IOS XR versions less than 25.4.1 EVPN services must be configured. In particular, there must be an EVPN Core Isolation Group configured with a Bundle interface specified as the core interface, whose group includes the access interfaces of an Ethernet Segment.
Unconfigure the core isolation group before ISSU, and re-configure the core isolation group after.
This issue is caused by a core interface in a core isolation group moving to the Down state during ISSU. The assumption in EVPN is that the ISSU operation should occur without traffic loss. As such, if an ES is undergoing core isolation, EVPN will not perform programming operations on that ES. When core isolation lifts, it is after the threshold where we perform critical programming during initialization which is impacted because of the initial interface down. This issue is indicative of another issue: the interface state moving to Down during ISSU. If this is hit, it is worth investigating whether some secondary issue is impacting the core interface state.
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.