When configuring multi-chassis redundancy, configuration must be performed on the two nodes that forms redundant-pair peer nodes. Each node points to its peer using the peer command.
When creating a multi-chassis LAG, the LAG must first be created under the config>lag lag-id context. Additionally, the LAG must be in access mode and LACP must be enabled (active or passive). Under the multi-chassis>peer>mc-lag context, the lag-id is the ID of the previously created LAG.
Use the following CLI syntax to configure multi-chassis redundancy features:
config>redundancy multi-chassis
peer ip-address
authentication-key [authentication-key | hash-key] [hash | hash2] description description-string
mc-lag
hold-on-neighbor-failure multiplier
keep-alive-interval interval
lag lag-id lacp-key admin-key system-id system-id [remote-lag lag-id] system-priority system-priority
no shutdown
source-address ip-address config>redundancy# config>redundancy# multi-chassis
config>redundancy>multi-chassis# peer 10.10.10.2 create
config>redundancy>multi-chassis>peer# description ‟Mc-Lag peer 10.10.10.2”
config>redundancy>multi-chassis>peer# mc-lag
config>redundancy>mc>peer>mc-lag# lag 1 lacp-key 32666 system-id 00:00:00:33:33:33 system-priority 32888
config>redundancy>mc>peer>mc-lag# no shutdown
config>redundancy>mc>peer>mc-lag# exit
config>redundancy>multi-chassis>peer# no shutdown
config>redundancy>multi-chassis>peer# exit
config>redundancy>multi-chassis# exit
config>redundancy#
The following displays the configuration:
A:7705:Dut-A>config>redundancy# info
----------------------------------------------
multi-chassis
peer 10.10.10.2 create
description "Mc-Lag peer 10.10.10.2"
mc-lag
lag 1 lacp-key 32666 system-id 00:00:00:33:33:33 system
priority 32888
no shutdown
exit
no shutdown
exit
exit
----------------------------------------------
A:7705:Dut-A>config>redundancy#