Cisco Cisco ASR 5000
APN Profile Configuration Mode
gn-gtp-version ▀
Command Line Interface Reference, StarOS Release 18 ▄
1513
gn-gtp-version
This command enables the operator to prevent the SGSN from attempting GTPv0 Requests for GGSNs associated with
specified APNs so that the SGSN tries activation with the next available GGSN if the current GGSN does not respond
after the GTPv1 Request retries fail.
specified APNs so that the SGSN tries activation with the next available GGSN if the current GGSN does not respond
after the GTPv1 Request retries fail.
Product
SGSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration > APN Profile Configuration
configure > apn-profile profile_name
Entering the above command sequence results in the following prompt:
[local]host_name(apn-profile-profile_name)#
Syntax
[ remove ] gn-gtp-version v1-only
remove
Used with the command, this filter erases the previous GTPv1 configuration and returns the SGSN
configuration to the default value of both GTPv1 and GTPv0.
configuration to the default value of both GTPv1 and GTPv0.
v1-only
This extension must be included to complete the command. This extension disables GTPv0 fallback.
Usage
During activation, the SGSN sends GTPv1 PDP Requests a GGSN and if no response is available from the
GGSN after the maximum number of retransmissions and timeout, then before trying an alternate GGSN, the
SGSN attempts to create GTPv0 PDP Requests and retries are carried out. Only after GTPv0 retransmissions
and timeout would the SGSN try activation with the next available GGSN.
The SGSN supported GTPv0 fallback. After exhausting all configured retry attempts for GTPv1, the SGSN
would retry the GTP-C Request using GTPv0. This fallback is conditional and is done only when the GTP
version of a GGSN is unknown during the first attempt at activating a PDP context with the GGSN.
This command allows the operator to disable the GTPv0 fallback for GTP-C Requests to GGSNs
corresponding to a specific APN, thus reducing unnecessary signalling if all known GGSN support GTPv1
only. Hence, if more than one GGSN address is returned by the DNS server during activation, then the SGSN
more immediately attempts activation with the next GGSN after exhausting all the GTPv1 retry attempts. If
only one GGSN address is returned, then the SGSN rejects the activation after exhausting all the configured
GTPv1 retries.
GGSN after the maximum number of retransmissions and timeout, then before trying an alternate GGSN, the
SGSN attempts to create GTPv0 PDP Requests and retries are carried out. Only after GTPv0 retransmissions
and timeout would the SGSN try activation with the next available GGSN.
The SGSN supported GTPv0 fallback. After exhausting all configured retry attempts for GTPv1, the SGSN
would retry the GTP-C Request using GTPv0. This fallback is conditional and is done only when the GTP
version of a GGSN is unknown during the first attempt at activating a PDP context with the GGSN.
This command allows the operator to disable the GTPv0 fallback for GTP-C Requests to GGSNs
corresponding to a specific APN, thus reducing unnecessary signalling if all known GGSN support GTPv1
only. Hence, if more than one GGSN address is returned by the DNS server during activation, then the SGSN
more immediately attempts activation with the next GGSN after exhausting all the GTPv1 retry attempts. If
only one GGSN address is returned, then the SGSN rejects the activation after exhausting all the configured
GTPv1 retries.
Example
The following command disables GTPv0 fallback:
gn-gtp-version v1-only