When configuring associated LAG ID parameters, the LAG must be in access mode and LACP must be enabled.
Use the CLI syntax shown below to configure multi-chassis redundancy features.
config>redundancy
— multi-chassis
— peer ip-address
— authentication-key [authentication-key | hash-key] [hash | hash2 |custom]
— description description-string
— mc-lag
— hold-on-neighbor-failure duration
— 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
— no shutdown
— source-address ip-address
— sync
— igmp
— igmp-snooping
— pim-snooping [sap]
— port [port-id | lag-id] [sync-tag sync-tag]
— range encap-range sync-tag sync-tag
— no shutdown
— srrp
— sub-mgmt
—
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 example shows the configuration:
A:ALA-48>config>redundancy# info
---------------------------------------------
multi-chassis
peer 10.10.10.2 create
description "Mc-Lag peer 10.10.10.2"
mc-lag
no shutdown
exit
no shutdown
exit
exit
---------------------------------------------
A:ALA-48>config>redundancy#