Cisco Cisco Packet Data Gateway (PDG)
SGTP Service Configuration Mode Commands
▀ disable-remote-restart-counter-verification
▄ Command Line Interface Reference, StarOS Release 17
8568
disable-remote-restart-counter-verification
This command disables the SGSN’s default behavior for verification of the remote peer’s (GGSN) restart counter
change values.
change values.
Product
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
[ default | no ] disable-remote-restart-counter-verification
default
Enables the default behavior for verification of the GGSN’s restart counter change values.
no
Disables the command configuration and enables the default behavior of verification.
Usage
This command disables the default behavior used to minimize PDP deactivations resulting from path failure
detection due to erroneous restart counter change messages.
With the execution of this command, the SGSN stops verifying restart counters received in Create PDP
Context Response or Update PDP Context Response or Update PDP Context Request (CPCR, CPCR, and
UPCQ) messages. When the SGSN detects GTP-C path failure between the SGSN and the GGSN, the SGSN
assumes PDP sessions at the GGSN are lost and the SGSN deactivates those PDP sessions towards the UE
with an indication that the UE should activate the PDP session again. Potentially, this scenario could cause
unnecessary traffic increases within the operator’s network.
The SGSN default behavior provides the ability to manage GTP-C path failures detected as a result of
spurious restart counter change value messages received from the GGSN. With the default behavior, path
failure detection is based on receipt of restart counter change values in CPCR, CPCR, and UPCQ messages.
The session manager informs the SGTPC manager about a changed restart counter value. The SGTPC
manager verifies the PDP context status by performing an echo request and echo response with the GGSN.
Only then is the path failure confirmed if the echo response contains a new restart counter value. Then the
SGTPC manager informs all session managers about the path failure and the session managers begin
deactivation of the PDP contexts.
Related commands:
detection due to erroneous restart counter change messages.
With the execution of this command, the SGSN stops verifying restart counters received in Create PDP
Context Response or Update PDP Context Response or Update PDP Context Request (CPCR, CPCR, and
UPCQ) messages. When the SGSN detects GTP-C path failure between the SGSN and the GGSN, the SGSN
assumes PDP sessions at the GGSN are lost and the SGSN deactivates those PDP sessions towards the UE
with an indication that the UE should activate the PDP session again. Potentially, this scenario could cause
unnecessary traffic increases within the operator’s network.
The SGSN default behavior provides the ability to manage GTP-C path failures detected as a result of
spurious restart counter change value messages received from the GGSN. With the default behavior, path
failure detection is based on receipt of restart counter change values in CPCR, CPCR, and UPCQ messages.
The session manager informs the SGTPC manager about a changed restart counter value. The SGTPC
manager verifies the PDP context status by performing an echo request and echo response with the GGSN.
Only then is the path failure confirmed if the echo response contains a new restart counter value. Then the
SGTPC manager informs all session managers about the path failure and the session managers begin
deactivation of the PDP contexts.
Related commands:
max-remote-restart-counter-change
, also part of the SGTP service configuration mode, allows
the operator to set a maximum variance between stored and received values for restart counter
changes coming from the GGSN.
changes coming from the GGSN.