Overview Of Cluster Eobc On L2 Channel With Topology; Restrictions Of Cluster Eobc On L2 Channel - Cisco ASR 9000 Series System Configuration Manual

Overview of Cluster EOBC on L2 Channel with Topology

4 Enhanced Cluster Convergence - Control plane convergence on a Cisco ASR 9001 nV Edge System can
be achieved in less than 5 seconds for node down conditions, from Cisco IOS XR Software Release 4.3.2.
or 5.1.0 onwards, based on these conditions:
• Both the control links(EOBC links) need to be connected across the cluster nodes
• FRR(Fast re-route) must be configured on the cluster node and the peer node to enable faster data path
• These FRR links must be connected to the peer, such that there is at least one link participating in an

Overview of Cluster EOBC on L2 Channel with Topology

The ASR 9K Ethernet Out-of-Band Channel (EOBC) packets use the internal MAC addressing system. This
restriction prevents the switching of EOBC packets on the L2 network and a dedicated topology is implemented
to route these packets to the destination node in the cluster system.
In a Cluster EOBC L2 network topology, all the Inter-Chassis Links (ICLs) connect to the P router ports that
can initiate Ethernet over Multi Protocol Label Switching PW (EoMPLS Pseudowire) on both sides. The PW
cannot be initiated from the cluster SFP+ ports. In other words, P router has end-to-end PW on it between P
routers at the cluster end ports. In this functionality, all the Inter-Chassis Links (ICLs) connect to the P router
ports that are capable of initiating EoMPLS PW on both sides. There is no configuration required on the
cluster system.

Restrictions of Cluster EOBC on L2 Channel

The following are some of the cluster EOBC-specific restrictions in the L2 environment:
• The SFP+ ports on the RSP front panel are not capable of initiating a PW.
• The UDLD packets that are sent through the links that implement the UDLD protocol are not punted to
• While this feature is designed for EOBC links, nothing precludes the IRL links from also being transported
• Only EoMPLS PW transport is recommended for EOBC links.
• The following EOBC link requirements must be supported:
• Quality of Service (QoS) is not supported on SFP+ ports.
• MAC address (01-00-cc-cc-cd-dd) cannot be used in the L2 cloud network because the MAC address
• Maximum packet delay of 10ms between the chassis.
Cisco ASR 9000 Series Aggregation Services Router nV System Configuration Guide, Release 5.3.x
138
switchover based on link down condition
FRR from each rack.
CPU of the switches that reside in between.
through the network in this fashion (as the recommendation specifies the use of an L2 tunnel).
• Message interval - 50 ms
• Timeout interval - 100 ms
change would result in network flapping and bring the ICLs and IRLs down. The MAC address can only
be changed to prevent the packets from being punted to the CPU of the switches that reside in between.
Configuring the nV Edge System on the Cisco ASR 9000 Series Router