eGTP Service Configuration Mode Commands

The eGTP Service Configuration Mode is used to create and manage Evolved GPRS Tunneling Protocol (eGTP) interface types and associated parameters.


Mode:

Exec > Global Configuration > Context Configuration > eGTP Service Configuration

configure > context context_name > egtp-service service_name

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-egtp-service)#

IMPORTANT:

The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).

associate

Configures an association with a GTP-U service where parameters are applied to the GTP-U data flow. For an SGSN being configured for S4 functionality, this command associates a configured GTP-U service that will enable communication with the SGW over the S4 interface.

Product:

ePDG

P-GW

SAEGW

SGSN


Privilege:

Administrator


Mode:

Exec > Global Configuration > Context Configuration > eGTP Service Configuration

configure > context context_name > egtp-service service_name

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-egtp-service)#

Syntax
associate gtpu-service nameno associate gtpu-service
no

Removes the association to the configured GTP-U service from this service.

gtpu-service name

Associates a GTP-U service with this eGTP service. name must be an alphanumeric string of 1 through 63 characters.


Usage:

Use this command to associate a GTP-U service with this eGTP service.


Example:
The following command associates this eGTP service with a GTP-U service named gtpu3:
associate gtpu-service
gtpu3 
end

Exits the current configuration mode and returns to the Exec mode.

Product:

All


Privilege:

Security Administrator, Administrator


Syntax
end

Usage:

Use this command to return to the Exec mode.

exit

Exits the current mode and returns to the parent configuration mode.

Product:

All


Privilege:

Security Administrator, Administrator


Syntax
exit

Usage:

Use this command to return to the parent configuration mode.

gtpc

Configure the GPRS Tunneling Protocol Control (GTP-C) plane settings for this service.

Product:

ePDG

MME

P-GW

SAEGW

S-GW

SGSN


Privilege:

Administrator


Mode:

Exec > Global Configuration > Context Configuration > eGTP Service Configuration

configure > context context_name > egtp-service service_name

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-egtp-service)#

Syntax
gtpc { bind { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address ipv4_address ] } | echo-interval seconds [ dynamic [ smooth-factor multiplier ] ]  | echo-retransmission-timeout seconds | error-response-handling | ip qos-dscp { forwarding_type } | max-retransmissions num | node-feature { pgw-restart-notification } | path-failure
detection-policy echo | retransmission-timeout seconds | retransmission-timeout-ms milliseconds }no gtpc { bind { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address ipv4_address ] } | echo-interval | node-feature { pgw-restart-notification } | path-failure
detection-policy }default gtpc { echo-interval | echo-max-retransmissons | echo-retransmission-timeout | ip qos-dscp | max-retransmissions | node-feature { pgw-restart-notification } | path-failure
detection-policy | retransmission-timeout | retransmission-timeout-ms }
no

Disables or removes the configured GTP-C setting.

default

Resets the specified parameter to its default value.

bind { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address iv4p_address ] }

Binds the service to an interface with an IPv4 address, IPv6 address or both.

ipv4-address ipv4_address [ ipv6-address ipv6_address ]: Binds this service to the IPv4 address of a configured interface. Optionally, bind the service to a configured interface with an IPv6 address.

ipv4_address must be entered using IPv4 dotted-decimal notation.

ipv6_address must be entered using IPv6 colon-separated-hexadecimal notation.

ipv6-address ipv6_address [ ipv4-address ipv4_address ]: Binds this service to the IPv6 address of a configured interface. Optionally, bind the service to a configured interface with an IPv4 address.

ip6_address must be entered using IPv6 colon-separated-hexadecimal notation.

ipv4_address must be entered using IPv4 dotted-decimal notation.

IMPORTANT:

For binding GTP-C service on S2b interface; either IPv6 or IPv4 bind address shall be used; binding both v4 and v6 address is not supported on ePDG

The ipv6-address ipv6_address [ ipv4-address ipv4_address ] option is not currently supported on the SGSN.

echo-interval seconds [ dynamic [ smooth-factor multiplier ] ]

Configures the duration (in seconds) between the sending of echo request messages as an integer from 60 through 3600. Default: 60

dynamic: Enables the dynamic echo timer for the eGTP service. The dynamic echo timer uses a calculated round trip timer (RTT) to support variances in different paths to peer nodes.

smooth-factor multiplier: Introduces a multiplier into the dynamic echo timer as an integer from 1 through 5. Default: 2

echo-retransmission-timeout seconds

Default: 3

Configures the echo retransmission timeout, in seconds, for the eGTP service as an integer ranging from 1 to 20.

If dynamic echo is enabled (gtpc echo-interval dynamic) the value set in this command serves as the dynamic minimum (if the RTT multiplied by the smooth factor is less than the value set in this command, the service uses this value).

ip qos-dscp { forwarding_type }

Specifies the IP QoS DSCP per-hop behavior (PHB) to be marked on the outer header of signalling packets originating from the LTE component. This is a standards-based feature (RFC 2597 and RFC 2474).

Note that CS (class selector) mode options below are provided to support backward compatibility with the IP precedence field used by some network devides. CS maps one-to-one to IP precedence, where CS1 is IP precedence value 1. If a packet is received from a non-DSCP aware router that used IP precedence markings, then the DSCP router can still understand the encoding as a Class Selector code point.

The following forwarding types are supported:

  • af11: Designates the use of Assured Forwarding 11 PHB.
    This is the default setting.
  • af12: Designates the use of Assured Forwarding 12 PHB.
  • af13: Designates the use of Assured Forwarding 13 PHB.
  • af21: Designates the use of Assured Forwarding 21 PHB.
  • af22: Designates the use of Assured Forwarding 22 PHB.
  • af23: Designates the use of Assured Forwarding 23 PHB.
  • af31: Designates the use of Assured Forwarding 31 PHB.
  • af32: Designates the use of Assured Forwarding 32 PHB.
  • af33: Designates the use of Assured Forwarding 33 PHB.
  • af41: Designates the use of Assured Forwarding 41 PHB.
  • af42: Designates the use of Assured Forwarding 42 PHB.
  • af43: Designates the use of Assured Forwarding 43 PHB.
  • be: Designates the use of Best Effort forwarding PHB.
  • cs1: Designates the use of Class Selector code point “CS1”.
  • cs2: Designates the use of Class Selector code point “CS2".
  • cs3: Designates the use of Class Selector code point “CS3".
  • cs4: Designates the use of Class Selector code point “CS4".
  • cs5: Designates the use of Class Selector code point “CS5".
  • cs6: Designates the use of Class Selector code point “CS6".
  • cs7: Designates the use of Class Selector code point “CS7".
  • ef: Designates the use of Expedited Forwarding PHB typically dedicated to low-loss, low-latency traffic.

The assured forwarding behavior groups are listed in the table below.

. Class 1 Class 2 Class 3 Class 4

Low Drop

AF11

AF21

AF31

AF41

Medium Drop

AF12

AF22

AF32

AF42

High Drop

AF13

AF23

AF33

AF43



Traffic marked with a higher class is given priority during congestion periods. If congestion occurs to traffic with the same class, the packets with the higher AF value are dropped first.

max-retransmissions num

Configures the maximum number of retries for packets as an integer from 0 through 15. Default: 4

After max retransmissions is reached, the path is considered to be failed.

node-feature pgw-restart-notification

Enables P-GW Restart Notification functionality. Node will start announcement of new supported features to peer nodes in echo as soon as configuration is added.

Default: Disabled

path-failure detection-policy echo

Enables session cleanup upon path failure detected via ECHO timeout toward a peer.

Default: Enabled

If disabled, there is no session cleanup upon path failure detected via ECHO timeout toward a peer; however, SNMP trap/logs will continue to indicate path failure.

retransmission-timeout seconds

IMPORTANT:

In 17.3 and later releases, this option has been deprecated. Use retransmission-timeout-ms .

Configures GTPv2 control packets (non-echo) retransmission timeout (in seconds) as an integer from 1 through 20.

Default: 5


Usage:

Use this command to configure GTP-C settings for the current service.

This interface assumes the characteristics of an S11 reference point on the S-GW or MME.

For communication between the S4-SGSN and the LTE S-GW, the interface assumes the characteristics of an S4 reference point on the S4-SGSN. Before using the gtpc command on the S4-SGSN, a new or existing service must be created or entered using the egtp-service command in Context Configuration Mode. Once the eGTP service is configured, the service must be associated with the configured 2G and/or 3G services on the S4-SGSN using the associate command in SGSN Service Configuration Mode and/or GPRS Service Configuration Mode.

IMPORTANT:

For ePDG, IPv6 bind address should be used as ePDG supports IPv6 as transport on S2b interface.


Example:
The following command binds the service to a GTP-C interface with an IPv4 address of 112.104.215.177:
gtpc bind ipv4-address 112.104.215.177
interface-type

Configures the interface type used by this service.

Product:

ePDG

MME

P-GW

SAEGW

S-GW

SaMOG

SGSN

IMPORTANT:

Prior to release 16, the SGSN only supported this command on the ASR 5000 platform.


Privilege:

Administrator


Mode:

Exec > Global Configuration > Context Configuration > eGTP Service Configuration

configure > context context_name > egtp-service service_name

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-egtp-service)#

Syntax
interface-type { interface-cgw-egress | interface-epdg-egress | interface-mme | interface-pgw-ingress  | interface-sgsn | interface-sgw-egress | interface-sgw-ingress }
{ interface-cgw-egress | interface-epdg-egress | interface-mme | interface-pgw-ingress | interface-sgsn | interface-sgw-egress | interface-sgw-ingress }

interface-cgw-egress: Specifies the SaMOG Gateway's EGTP interface for egress.

interface-epdg-egress: Specifies that the interface has the characteristics of an ePDG's egress EGTP interface.

interface-mme: Specifies that the interface has the characteristics of an eGTP MME S11 reference point to/from an S-GW or an eGTP MME Sv reference point to/from a Mobile Switching Center (MSC).

interface-pgw-ingress: Specifies that the interface has the characteristics of an eGTP P-GW S5/S8 reference point from an S-GW. The interface assumes the characteristics of either a GTP-C (control Plane) or GTP-U (user plane) reference point.

interface-sgsn: Specifies that the interface has the characteristics of an eGTP S-GW S4 reference point to/from an SGSN. On an S4-SGSN, this option specifies that the eGTP service is used for an S4-SGSN and gives the service the characteristics required for messaging towards an SGW (S4) / MME (S3) / S4-SGSN (S16).

interface-sgw-egress: Specifies that the interface has the characteristics of an eGTP S-GW S5/S8 reference point to an eGTP P-GW. The interface assumes the characteristics of either a GTP-C (control Plane) or GTP-U (user plane) reference point.

interface-sgw-ingress: Specifies that the interface has the characteristics of:
  • an eGTP-C S-GW S11 reference point from the MME.
  • an eGTP-U S-GW S1-U reference point from the eNodeB.

Usage:

Use this command to specify the type of interface this service uses. By configuring this command, the interface takes on the characteristics of the selected type.

Disable specific interface support for P-GW by entering the following command:
         interface-type
interface-pgw-ingress

Example:
The following command configures the interface bound to this service to maintain the characteristics of an eGTP-C S-GW S11 reference point from an MME:
interface-type interface-sgw-ingress

The following command accepts or rejects Create Session Request (CSR) on GTP based S2a interface.

interface-type interface-pgw-ingress s2a
pool

This command enables the default S4-SGSN functionality for (flex) pooling and enables inclusion of the configured pool hop-counter count in new SGSN context/identity request messages. This command supports S4-SGSN pooling across the S16 interface. The S16 interface provides a GTPv2 path to a peer S4-SGSN. Support for this interface is provided as part of the S4 interface license. This command sets the S4-SGSN as the default SGSN within a pool. If the default S4-SGSN receives an inbound SGSN context request, it forwards it to the right SGSN in the pool based on the NRI bits of the P-TMSI.

Product:

SGSN


Privilege:

Security Administrator, Administrator


Mode:

Exec > Global Configuration > Context Configuration > eGTP Service Configuration

configure > context context_name > egtp-service service_name

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-egtp-service)#

Syntax
pool { default-sgsn | hop-counter count }no pool  default-sgsn
 
no

Disables the default SGSN pooling functionality or removes the SGSN pool hop-counter IE from the GTP Identity/context requests.

default-sgsn

Enables default SGSN pooling functionality.

hop-counter count

Enables and configures the SGSN pool hop-counter to set the number of hops and to include the configured count in the new SGSN Context Requests or the new SGSN Identity Requests.

If default-sgsn is enabled, then any messages relayed will have the default value of 4 for the counter if the message does not include this hop-counter ID.

count: Enter an integer from 1 to 255.

Default: 4


Usage:

Use this command to enable the default flex functionality without exposing the pool (flex) structure. This functionality provides a means for SGSNs outside of the pool to reach a pooled SGSN on the basis of its NRI.

Once the pooling has been enabled. Repeat the command using the hop-counter keyword to enable inclusion of the hop-counter IE in SGSN context/identity request messages and to configure the count for the pooling hop-counter. If the SGSN is behaving as the ‘default SGSN’, this SGSN will forward (relay) requests with the hop-count included to the target SGSN.


Example:
Enable the default pooling functionality which allows an outside SGSN to reach a pooled SGSN:
pool default-sgsn
Set the hop-count to be included in messages to 25:
pool hop-count 
validation-mode

Configures the type of validation to be performed on messages received by this service.

Product:

ePDG

P-GW

SAEGW

SGSN

IMPORTANT:

The ePDG and SGSN are not currently supported on the ASR 5500 platform.


Privilege:

Administrator


Mode:

Exec > Global Configuration > Context Configuration > eGTP Service Configuration

configure > context context_name > egtp-service service_name

Entering the above command sequence results in the following prompt:

[context_name]host_name(config-egtp-service)#

Syntax
validation-mode { custom1 | standard }default validation-mode
default

Returns the command to the default setting of standard.

{ custom1 | standard }

custom1: Specifies that the message should be validated based on a vendor-specific set of mandatory elements.

standard: Specifies that the message should be validated based on the set of mandatory elements as defined in 3GPP 29.274. This is the default option on an S4-SGSN.


Usage:

Use this command to specify the type of validation performed on messages received by this service. The information elements contained in messages have mandatory elements and conditional elements. The standard set of elements, as defined by 3GPP 29.274 is checked if this command is set to “standard”. The custom1 setting is for a vendor-specific set of mandatory elements.


Example:
The following command sets the validation mode for incoming messages to standard:
validation-mode standard