Configuring ICCP for MC-LAG
For multichassis link aggregation (MC-LAG), you must configure Inter-Control Center Communications Protocol (ICCP) to exchange information between two MC-LAG peers.
To enable ICCP, include the iccp statement at the [edit protocols] hierarchy level:
The local-ip-address statement sets the source address. This could be a specified address or interface address. The session-establishment-hold-time statement determines whether a chassis takes over as the master at the ICCP session.
The authentication-key statement is provided by TCP Message Digest 5 (md5) option for an ICCP TCP session. The redundancy-group-id-list statement specifies the redundancy groups between ICCP peers and the liveness-detection hierarchy configures Bidirectional Forwarding Detection (BFD) protocol options.
 | Note: ICCP is based on TCP and it uses IP routes to reach the MC-LAG peer. To ensure that the ICCP session is as resilient as possible, we recommend that you configure alternative routes between the ICCP end-point IP addresses. Alternatively, configure a LAG interface that has two or more interfaces between the MC-LAG pairs to prevent session failure when there are no alternative routes. |
