Cisco Cisco Packet Data Gateway (PDG)
Context Configuration Mode Commands E-H
gtpp detect-dead-server ▀
Command Line Interface Reference, StarOS Release 16 ▄
2385
gtpp detect-dead-server
Configures the number of consecutive communication failures that could occur before the system marks a Charging
Gateway Function (CGF) as down.
Gateway Function (CGF) as down.
Product
GGSN
P-GW
SAEGW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration
configure > context context_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
gtpp detect-dead-server consecutive-failures max_number
default gtpp detect-dead-server consecutive-failures
default
Configures this command with the default setting.
Default: 0
Default: 0
consecutive-failures
max_number
Specifies the number of failures that could occur before marking a CGF as down.
max_number
is an integer
from 0 through 1000.
Usage
This command works in conjunction with the
gtpp max-retries
parameter to set a limit to the number of
communication failures that can occur with a configured CGF.
The gtpp max-retries parameter limits the number of attempts to communicate with a CGF. Once that limit is
reached, the system treats it as a single failure. The gtpp detect-dead-server parameter limits the number of
consecutive failures that can occur before the system marks the CGF as down and communicate with the
CGF of next highest priority.
If all of the configured CGFs are down, the system ignores the detect-dead-server configuration and attempt
to communicate with highest priority CGF again.
If the system receives a GTPP Node Alive Request, Echo Request, or Echo Response message from a CGF
that was previously marked as down, the system immediately treats it as being active.
Refer to the
The gtpp max-retries parameter limits the number of attempts to communicate with a CGF. Once that limit is
reached, the system treats it as a single failure. The gtpp detect-dead-server parameter limits the number of
consecutive failures that can occur before the system marks the CGF as down and communicate with the
CGF of next highest priority.
If all of the configured CGFs are down, the system ignores the detect-dead-server configuration and attempt
to communicate with highest priority CGF again.
If the system receives a GTPP Node Alive Request, Echo Request, or Echo Response message from a CGF
that was previously marked as down, the system immediately treats it as being active.
Refer to the
gtpp max-retries
command for additional information.
Example
The following command configures the system to allow
8
consecutive communication failures with a CGF
before it marks it as down: