ccep-up-delay

In an MCT configuration, places client cluster edge port (CCEP) dynamic LAGs in a blocking state for the specified time while Client Cluster Protocol (CCP) comes up. This allows for better traffic convergence.
Syntax
ccep-up-delay { value }
no ccep-up-delay { value }
Command Default

By default, the timer is disabled.

Parameters
value
Sets the timeout value in seconds. Available range is 0 thorugh 600. A setting of 0 (the default) disables the timer.
Modes

MCT cluster configuration sub-mode

Usage Guidelines

The no form of the command resets the configuration to the default, disabling the timer.

The recommended ccep-up-delay setting for most scenarios is 300 seconds.

Use of this timer is optional. It is recommended for MCT networks with scaled clients and MACs.

Whenever client cluster protocol (CCP) restarts, for example, following a reload, a re-deployment, an undeployments, or Inter-chassis link (ICL) flap, the timer keeps dynamic Client Cluster Edge Port (CCEP) LAGs on the peer in BLOCKING state. This allows MACs and mcache entries to sync properly, which prevents large drops or spikes in traffic.

Examples

The following example configures the timer on two MCT cluster peers to 300 seconds.

RUCKUS-1# configure terminal
RUCKUS-1(config)# cluster mct_stack 1000
RUCKUS-1(config-cluster-mct_stack)# ccep-up-delay 300
RUCKUS-1(config-cluster-mct_stack)# exit
RUCKUS-1(config)# 
RUCKUS-2# configure terminal
RUCKUS-2(config)# cluster mct_stack 1000
RUCKUS-2(config-cluster-mct_stack)# ccep-up-delay 300
RUCKUS-2(config-cluster-mct_stack)# exit
RUCKUS-2(config)#
History
Release version Command history
FastIron release 09.0.10 This command was introduced.
Parent topic: Commands C