Service Redundancy
Protocol Configuration Mode Commands
The Service Redundancy
Protocol Mode is used to configure properties for Interchassis Session
Recovery (ICSR) services.
IMPORTANT:
The commands or keywords/variables
that are available are dependent on platform type, product version,
and installed license(s).
bind
Binds the service
to the IP address of the local chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
bind address { ipv4 _address | ipv6_address }
no bind address
no
Removes the IP bind
address.
ipv4 _address | ipv6_address
Specifies the system
IP address using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal
notation.
IMPORTANT:
Both peers must be
using the same address family (IPv4 or IPv6) or the Service Redundancy Protocol
(SRP) connection will not be established.
Usage:
Defines the IP address
of the local chassis defined as part of the ICSR configuration.
Example:
The following example
binds the service to the IP address
10.1.1.1:
bind address 10.1.1.1
chassis-mode
Defines the chassis’s
operational mode - primary or backup - for ICSR.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
chassis-mode { backup | primary
}
default chassis-mode
default
Resets the chassis
mode to the default setting of backup.
backup
(Default) Configures
the system as the backup chassis operating in standby state.
primary
Configures the system
as the primary chassis operating in active state.
Usage:
Sets the chassis mode
(primary or backup) for the system within the framework of ICSR.
Example:
The following example
configures the system as the primary chassis operating in active
state
chassis-mode primary
checkpoint
Configures check pointing
for ICSR. With check pointing enabled, the system stores a snapshot
of the current application state use it for restarting the execution
in case of failure.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
checkpoint session
duration duration
default checkpoint
session duration
default
Resets the checkpoint
session duration to the default setting of 60 seconds.
duration
Specifies the amount
of time (in seconds) that a call must be active before it is check pointed. duration must
be an integer from 1 through 65535.
Default: 60
Usage:
Sets the amount of
time the chassis waits before check pointing an existing call session.
Example:
The following example
configures sets the checkpoint session duration to 6500 seconds:
checkpoint session duration 6500
configuration-interval
Defines the configuration
validation interval.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
configuration-interval interval
default configuration-interval
default
Resets the configuration
interval to the default setting of 3600 seconds.
interval
Specifies the amount
of time (number of seconds) between one configuration validation
and the next configuration validation.
interval must
be an integer from 1 through 65535.
Default: 3600
Usage:
This configures the
interval between configuration validations of the primary and backup chassis.
Example:
The following example
sets the configuration interval to 34 seconds:
configuration-interval 34
dead-interval
Defines the timeout
interval before a peer is determined to be down.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
dead-interval interval
default dead-interval
default
Resets the dead interval
to the default setting of 30 seconds.
interval
Specifies the amount
of time (in seconds) for the dead interval. interval must
be an integer from 1 through 65535.
Default: 30
Usage:
This command specifies
the amount of time that one chassis waits to receive a communication
from a peer before the listening chassis determines that the peer
chassis is down.
Example:
The following example
sets the dead interval to 65 seconds:
dead-interval 65
delay-interval
Configures the delay
time for starting the dead timer after configuration files are loaded.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
delay-interval
interval
default delay-interval
default
Sets or restores the
default value assigned for the specified parameter.
interval
Specifies the amount
of time (in seconds) for the delay interval. interval must
be an integer from 1 through 65535.
Usage:
This configures interval
for starting the dead timer after configuration files are loaded.
Example:
The following example
sets the delay interval to 65 seconds after the configuration files
are loaded:
delay interval 65
end
Exits the current
configuration mode and returns to the Exec mode.
Privilege:
Security Administrator,
Administrator
Usage:
Use this command to
return to the Exec mode.
exit
Exits the current
mode and returns to the parent configuration mode.
Privilege:
Security Administrator,
Administrator
Usage:
Use this command to
return to the parent configuration mode.
hello-interval
Defines the lapse
time between sending the hello message.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
hello-interval interval
default hello-interval
default
Resets the hello interval
to the default setting of 10 seconds.
interval
Specifies the lapse
time (in seconds) between sending the hello message. interval must
be an integer from 1 through 65535.
Default: 10
Usage:
This command configures
the hello interval - the amount of time that lapses between the sending
of each hello message. Each chassis sends the other chassis a hello
message at the expiration of every hello interval.
Example:
The following example
sets the hello interval to 35 seconds:
hello-interval 35
internal-switchover-retry-interval
Defines the interval
between internal switchover retries.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
internal-switchover-retry-interval interval
default internal-switchover-retry-interval
default
Resets the internal
switchover retry interval to the default setting of 60 seconds.
interval
Specifies the amount
of time (in seconds) between internal switchover retries. interval must
be an integer from 10 through 120.
Default: 60
Usage:
This configures the
interval between internal switchover retries. The system only initiates internal
switchovers if Service Redundancy Protocol (SRP) monitoring is configured.
IMPORTANT:
See the monitor authentication-probe, monitor bgp,
or monitor diameter commands
for more information on associated SRP monitoring.
Example:
The following example
sets the internal switchover retry interval to 34 seconds:
internal-switchover-retry-interval 34
monitor authentication-probe
Enables SRP monitoring
of the connection between the specified AAA server and the primary
chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] monitor
authentication-probe context context_name { ipv4_address | ipv6_address } [ port port_number ]
no
Turns off the monitoring.
context context_name
Identifies the context
being used.
context_name must
be an existing context expressed as an alphanumeric string of 1
through 79 characters.
ipv4 _address | ipv6_address
Defines the IP address
of the AAA server to be monitored, entered using IPv4 dotted-decimal
or IPv6 colon-separated-hexadecimal notation.
port port_number
Identifies a specific
port for the authentication probe. port_number must
be the port for the AAA server expressed as an integer from 1 through
65535.
Usage:
This command initiates
monitoring of the connection between the primary chassis and the specified
AAA server through the use of authentication probe packets. If the
connection drops, the standby chassis becomes active.
Example:
The following example
initiates the connection monitoring between the primary chassis
and AAA server
10.2.3.4 at
port
1025:
monitor authentication-probe
context test1 10.2.3.4 port 1025
monitor bfd
Enables SRP monitoring
of the connection between the specified Bidirectional Forwarding
Detection (BFD) neighbor and the primary chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] monitor
bfd context context_name { ipv4_address | ipv6_address } { chassis-to-chassis | chassis-to-router }
context context_name
Identifies the context
being used.
context_name must
be an existing context expressed as an alphanumeric string of 1
through 79 characters.
ipv4 _address | ipv6_address
Defines the IP address
of the BFD neighbor to be monitored, entered using IPv4 dotted-decimal
or IPv6 colon-separated-hexadecimal notation
chassis-to-chassis | chassis-to-router
chassis-to-chassis:
BFD runs between primary and backup chassis on non-SRP links.
chassis-to-router:
BFD runs between chassis and router.
Usage:
This command initiates
monitoring of the connection between the primary chassis and the specified
BFD neighbor in the specified context. If the connection drops,
the standby chassis becomes active.
IMPORTANT:
BFD monitoring must
run between chassis-to-chassis or chassis-to-router.
Example:
The following example
initiates the chassis-to-chassis connection monitoring between the primary
chassis and BFD neighbor
12.2.1.54:
monitor bfd context
test 12.2.1.54 chassis-to-chassis
monitor bgp
Enables SRP monitoring
of the connection between the specified Border Gateway Protocol
(BGP) peer and the primary chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] monitor
bgp context context_name { ipv4_address | ipv6_address } [ vrf vrf_name ]
context context_name
Identifies the context
being used.
context_name must
be an existing context expressed as an alphanumeric string of 1
through 79 characters.
ipv4 _address | ipv6_address
Defines the IP address
of the BGP peer to be monitored, entered using IPv4 dotted-decimal or
IPv6 colon-separated-hexadecimal notation
Defines the VPN Routing/Forwarding
instance.
Usage:
This command initiates
monitoring of the connection between the primary chassis and the specified
BGP peer in the specified context. If the connection drops, the
standby chassis becomes active.
Example:
The following example
initiates the connection monitoring between the primary chassis
and BGP peer
125.2.1.56:
monitor bgp context
test 125.2.1.56
monitor diameter
Enables SRP monitoring
of the connection between the specified Diameter server and the
primary chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] monitor
diameter context context_name endpoint endpoint_name [ fqdn fqdn | peer { ipv4_address | ipv6_address } ] [ port port_number ]
no
Turns off the monitoring.
context context_name
Identifies the context
being used.
context_name must
be an existing context expressed as an alphanumeric string of 1
through 79 characters.
endpoint endpoint_name
Identifies the endpoint
being used.
endpoint_name must
be for the Diameter server expressed as an alphanumeric string of
1 through 63 characters.
fqdn fqdn
Identifies a Fully
Qualified Domain Name (FQDN).
fqdn must
be for the Diameter server expressed an alphanumeric string of 1
through 127 characters.
peer { ipv4 _address | ipv6_address }
Defines the IP address
of the Diameter server to be monitored, entered using IPv4 dotted-decimal
or IPv6 colon-separated-hexadecimal notation.
port port_number
Identifies a specific
port to monitor.
port_number must
be the port for the Diameter server and an integer from 1 through
65535.
Usage:
This command initiates
monitoring of the connection between the primary chassis and the specified
Diameter server in the specified context. If the connection drops,
the standby chassis becomes active.
IMPORTANT:
Endpoint name, FQDN,
IP address, and port must all match the Diameter protocol configured
values for the peer state to be updated.
Example:
The following example
initiates the connection monitoring between the primary chassis
and the Diameter server on context
test1 and
endpoint
end2:
monitor diameter context
test1 10.6.7.8 endpoint end2
num-internal-switchover-retry
Defines the number
of times an internal switchover would be retried.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
num-internal-switchover-retry retries
default num-internal-switchover-retry
default
Resets the configuration
interval to the default setting of 3 retries.
retries
The number of times
an internal switchover would be retried in case of standby chassis. retries must
be an integer from 1 through 10.
Default: 3
Usage:
This configures the
number of times an internal switchover would be retried in case
of standby chassis failure to respond or become active.
Example:
The following example
sets the retry number to
5:
num-internal-switchover-retry 5
peer-ip-address
Specifies the IP address
for the peer chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
peer-ip-address { ipv4_address | ipv6_address }
no peer-ip-address
no
Removes the peer IP
address of the backup chassis.
ipv4_address | ipv6_address
Specifies the IP address
of the backup chassis, entered using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal
notation.
IMPORTANT:
Both peers must be
using the same address family (IPv4 or IPv6) or the Service Redundancy Protocol
(SRP) connection will not be established.
Usage:
This command is used
to identify the peer chassis in the ICSR configuration. From the primary’s
perspective, the peer is the backup and from the backup’s
perspective, the peer is the primary.
Example:
The following example
specifies
10.2.3.4 as
a backup peer system to the primary system:
peer-ip-address 10.2.3.4
priority
Sets the initial ICSR
priority of each peer chassis.
IMPORTANT:
priority takes
affect only during simultaneous initializing of all chassis in an
ICSR configuration, and only if a misconfiguration has both chassis
in the same mode (both Primary or both Backup).
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
priority priority_value
default priority
default
Resets the priority
to the default setting of 125.
priority_value
Specifies the priority
for the chassis.
priority_value must
be an integer from 1 through 255, where 1 is the highest priority.
Default: 125
Usage:
This command determines
which chassis transitions to the Active state when all chassis have
the same mode configuration. priority acts
as a tie breaker for the state determination only when all chassis
initialize simultaneously. The chassis with the higher priority
(lower number) becomes Active, while the chassis with the lower priority
(higher number) becomes Standby.
Once chassis become
operational (after initialization), if there is an event requiring
a chassis change of state, then each chassis returns to its previous
state (Active or Standby) after both chassis recover.
Example:
The following example
sets the priority value to
5:
priority 5
route-modifier
Sets the route modifier
for the peer chassis.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Syntax
route-modifier threshold threshold_value
default route-modifier
default
Resets the route modifier
to the default setting of 16.
threshold_value
Specifies the value
that causes the route-modifier counter to be reset to the initial
value. threshold_value must
be an integer from 2 through 32.
Default: 16
Usage:
This command is used
to determine when the route modifier should be reset to its initial value
to avoid rollover.
Example:
The following example
sets the route modifier threshold to
10:
route-modifier threshold 10