[no] mc-lag
config>redundancy>multi-chassis>peer>mc-lag
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure multi-chassis LAG operations and related parameters.
The no form of this command administratively disables multi-chassis LAG. MC-LAG can only be issued only when mc-lag is shutdown.
hold-on-neighbor-failure multiplier
no hold-on-neighbor-failure
config>redundancy>multi-chassis>peer>mc-lag
Supported on all 7210 SAS platforms as described in this document
This command specifies the interval that the standby node will wait for packets from the active node before assuming a redundant-neighbor node failure. This delay in switch-over operation is required to accommodate different factors influencing node failure detection rate, such as IGP convergence, or HA switch-over times and to prevent the standby node to take action prematurely.
The no form of this command reverts to the default value.
3
Specifies the time interval that the standby node will wait for packets from the active node before assuming a redundant-neighbor node failure.
keep-alive-interval interval
no keep-alive-interval
config>redundancy>multi-chassis>peer>mc-lag
Supported on all 7210 SAS platforms as described in this document
This command sets the interval at which keep-alive messages are exchanged between two systems participating in MC-LAG. These keep-alive messages are used to determine remote-node failure and the interval is set in deciseconds.
The no form of this command reverts to the default value.
1s (10 hundreds of milliseconds means interval value of 10)
Specifies the time interval expressed in deciseconds.
lag lag-id lacp-key admin-key system-id system-id [remote-lag remote-lag-id] system-priority system-priority
lag lag-id [remote-lag remote-lag-id]
no lag lag-id
config>redundancy>multi-chassis>peer>mc-lag
Supported on all 7210 SAS platforms as described in this document
This command defines a LAG that is forming a redundant pair for MC-LAG with a LAG configured on the given peer. The same LAG group can be defined only in the scope of one peer.
The same lacp-key, system-id, and system-priority must be configured on both nodes of the redundant pair in order for MC-LAG to become operational. In order for MC-LAG to become operational, all of the parameters (lacp-key, system-id, system-priority) must be configured the same on both nodes of the same redundant pair.
The partner system (the system connected to all links forming MC-LAG) will consider all ports using the same lacp-key, system-id, and system-priority as the part of the same LAG. In order to achieve this in MC operation, both redundant-pair nodes have to be configured with the same values. In case of a mismatch, MC-LAG is kept operationally down.
Specifies the LAG identifier, expressed as a decimal integer. Specifying the lag-id allows the mismatch between lag-id on the redundant pair. If no lag-id is specified, it is assumed that the neighbor system uses the same lag-id as a part of the given MC-LAG. If no matching MC-LAG group can be found between neighbor systems, the individual LAGs will operate as usual (no MC-LAG operation is established).
Specifies a 16 bit key that needs to be configured in the same manner on both sides of the MC-LAG in order for the MC-LAG to come up.
Specifies a 6 byte value expressed in the same notation as MAC address.
Specifies the LAG ID on the remote system.
Specifies the system priority to be used in the context of the MC-LAG. The partner system will consider all ports using the same lacp-key, system-id, and system-priority as part of the same LAG.