Nokia 7705 - 6.10.2.5 Configuring Multi-Chassis Redundancy

System Management
292
Basic System Configuration Guide
3HE 11010 AAAC TQZZA Edition: 01
Synchronization Information
===================================================
Synchronize Mode : Configuration
Synchronize Status : No synchronization
Last Config Sync Time : 2006/06/27 09:17:15
Last Boot Env Sync Time : 2006/06/24 07:16:37
===================================================
6.10.2.5 Configuring Multi-Chassis Redundancy
When configuring multi-chassis redundancy, configuration must be performed on the
two nodes that will form redundant-pair peer nodes. Each node will point 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 CLI syntax displayed below to configure multi-chassis redundancy features:
CLI Syntax: 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
Example: 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