Cisco Cisco Packet Data Interworking Function (PDIF)
DHCPv6 Service Configuration Mode Commands
detect-dead-server ▀
Command Line Interface Reference, StarOS Release 18 ▄
3523
detect-dead-server
Configures the number of consecutive communication failures that could occur before the system marks a DHCPv6
server as down.
server as down.
Product
GGSN
P-GW
SAEGW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > DHCPv6 Service Configuration
configure > context context_name > dhcpv6-service service_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-dhcpv6-service)#
Syntax
detect-dead-server consecutive-failures max_number
default detect-dead-server consecutive-failures
default
Returns the command to its default setting of 5.
consecutive-failures
max_number
Specifies the number of failures that could occur before marking a DHCPv6 server as down.
max_number
must be an integer from 1 through 1000.
Default: 5
Usage
This command works in conjunction with the
max-retransmissions
DHCPv6 client command to set a
limit to the number of communication failures that can occur with a configured DHCPv6 server.
The
The
max-retransmissions
DHCPv6 client parameter limits the number of attempts to communicate with
a server. Once that limit is reached, the system treats it as a single failure. This parameter limits the number
of consecutive failures that can occur before the system marks the server as down and communicate with the
server of next highest priority.
If all of the configured servers are down, the system ignores the
of consecutive failures that can occur before the system marks the server as down and communicate with the
server of next highest priority.
If all of the configured servers are down, the system ignores the
detect-dead-server
configuration and
attempts to communicate with the highest priority server again.
If the system receives a message from a DHCPv6 server that was previously marked as down, the system
immediately treats it as being active.
If the system receives a message from a DHCPv6 server that was previously marked as down, the system
immediately treats it as being active.
Example
The following command configures the system to allow
8
consecutive communication failures with a
DHCPv6 server before it marks it as down: