peer-keepalive (optional)

Configures the keepalive session for the MCT cluster peer.

Syntax

peer-keepalive { auto } [ destination IP address |role primary/secondary]

no peer-keepalive { auto } [ destination IP address |role primary/secondary]

Command Default

The default is auto.

Parameters

auto: Destination and source IP will be automatically discovered and should not be configured.

destination ip-address source-interface interface: Manually configures the destination and source interface. Overrides the auto discovery default.

role primary/secondary: Configures the role of the node if the ICL goes down, but MCT peer remains up.

Modes

Cluster configuration mode.

Usage Guidelines

no peer-keepalive disables keep-alive session.

The default keepalilve session uses the management VRF and runs between the management IP addresses of the MCT nodes.

The primary node is responsible for forwarding all traffic when ICL goes down.

The Secondary node brings down all client interfaces and tunnels and isolates all client traffic.

By default, the node with lower IP is selected as primary and higher IP is selected as secondary. This behavior can be changed by configuring the role.

Examples

The following example automatically configures the peer-keepalive default destination IP, source interface, and primary/secondary roles.

device(config)# cluster MCT1
device(config-cluster-MCT1)# peer-keepalive
device(config-peer-keepalive)# auto 
device(config-peer-keepalive)#