Technical Documentation

Configuring ICCP for MC-LAG

For Multi-Chassis Link Aggregation (MC-LAG), you must configure Internet Chassis Control (ICCP) to exchange information between two MC-LAG peers.

To enable ICCP, include the iccp statement at the [edit protocols] hierarchy level:

[edit protocols]iccp {authentication-key string;local-ip-addr ipv4-address;peer ip-address{authentication-key string;liveness-detection {detection-time {threshold milliseconds;}minimum-interval milliseconds;minimum-receive-interval milliseconds;multiplier number;no-adaptation;transmit-interval {minimum-interval milliseconds;threshold milliseconds;}version (1 | automatic);}local-ip-addr ipv4-address;redundancy-group-id-list [ redundancy-groups ];session-establishment-hold-time value;}session-establishment-hold-time value;traceoptions;}

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.

Published: 2010-07-14

Help
|
My Account
|
Log Out