Cisco Cisco Packet Data Gateway (PDG)
SGTP Service Configuration Mode Commands
max-remote-restart-counter-change ▀
Command Line Interface Reference, StarOS Release 17 ▄
8583
max-remote-restart-counter-change
Use this command to set a restart counter change window to avoid service deactivations and activations that could cause
large bursts of network traffic if the restart counter change messages from the GGSN are erroneous.
large bursts of network traffic if the restart counter change messages from the GGSN are erroneous.
Product
eWAG
SGSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > Context Configuration > SGTP Service Configuration
configure > context context_name > sgtp-service service_name
Entering the above command sequence results in the following prompt:
[context_name]host_name(config-sgtp-service)#
Syntax
max-remote-restart-counter-change variance
default max-remote-restart-counter-change
default
If this keyword is used or if a variance window is not configured, then the default value will be 255 and the
default behavior will be to detect a restart on any change.
default behavior will be to detect a restart on any change.
variance
Set a number (an 8-bit value) that will define the variance range for restart counter change values compared
between the gateway's stored value and the value received in messages from the GGSN. Valid entry is an
integer from 1 to 255; default is 255.
Value of 32 is recommended as it provides a sufficient window to allow the gateway to handle delayed
messages with old restart counters.
between the gateway's stored value and the value received in messages from the GGSN. Valid entry is an
integer from 1 to 255; default is 255.
Value of 32 is recommended as it provides a sufficient window to allow the gateway to handle delayed
messages with old restart counters.
Usage
When the gateway detects GTP-C path failure between the gateway and the GGSN, the gateway assumes
PDP sessions at the GGSN are lost and the gateway deactivates corresponding PDP sessions towards the UE
with an indication that the UE should activate the PDP session again. Detection is based on receipt of restart
counter change values in Create PDP Context Response or Update PDP Context Response or Update PDP
Context Request (CPCR/UPCR/UPCQ) messages. Potentially, this scenario can cause major traffic increases
within the operator's network. It is possible that the messages received from the GGSN are spurious.
The gateway default behavior provides the ability to verify possible GTP-C path failures detected as a result
of spurious restart counter change messages received from the GGSN. With the default behavior, the session
manager informs the SGTPC manager about a changed restart counter value. The SGTPC manager responds
by verifying the PDP context status by performing an Echo Request / Echo Response with the GGSN. If the
Echo Response includes a new restart counter change value, then the session manager considers the path
failure confirmed and begins the PDP context deactivation sequence.
PDP sessions at the GGSN are lost and the gateway deactivates corresponding PDP sessions towards the UE
with an indication that the UE should activate the PDP session again. Detection is based on receipt of restart
counter change values in Create PDP Context Response or Update PDP Context Response or Update PDP
Context Request (CPCR/UPCR/UPCQ) messages. Potentially, this scenario can cause major traffic increases
within the operator's network. It is possible that the messages received from the GGSN are spurious.
The gateway default behavior provides the ability to verify possible GTP-C path failures detected as a result
of spurious restart counter change messages received from the GGSN. With the default behavior, the session
manager informs the SGTPC manager about a changed restart counter value. The SGTPC manager responds
by verifying the PDP context status by performing an Echo Request / Echo Response with the GGSN. If the
Echo Response includes a new restart counter change value, then the session manager considers the path
failure confirmed and begins the PDP context deactivation sequence.