# 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.

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.
Platform:

ASR 5000
Product:

P-GW
Privilege:

Administrator
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.
Platform:

ASR 5000
Product:

MME, P-GW, S-GW
Privilege:

Administrator
Syntax

    gtpc { bind { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address ipv4_address ] } | echo-interval seconds | echo-retransmission-timeout  | ip qos-dscp { forwarding_type } | max-retransmissions num  | retransmission-timeout seconds }no gtpc { bind { ipv4-address ipv4_address [ ipv6-address ipv6_address ] | ipv6-address ipv6_address [ ipv4-address ipv4_address ] } | echo-interval }default gtpc { echo-interval | ip qos-dscp | max-retransmissions | retransmission-timeout }

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.
echo-interval seconds

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

: 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.

multiplier: Introduces a multiplier into the dynamic echo timer as an integer from 1 through 5. Default: 2
ip qos-dscp { forwarding_type }

Specifies the IP QoS DSCP per-hop behavior to be marked on the outer header of signalling packets originating from the LTE component. This is a standards-based feature (RFC 2597). The following forwarding types are supported:

af11: Designates the use of Assured Forwarding 11 per-hop behavior. This is the default setting.

af12: Designates the use of Assured Forwarding 12 per-hop behavior.

af13: Designates the use of Assured Forwarding 13 per-hop behavior.

af21: Designates the use of Assured Forwarding 21 per-hop behavior.

af22: Designates the use of Assured Forwarding 22 per-hop behavior.

af23: Designates the use of Assured Forwarding 23 per-hop behavior.

af31: Designates the use of Assured Forwarding 31 per-hop behavior.

af32: Designates the use of Assured Forwarding 32 per-hop behavior.

af33: Designates the use of Assured Forwarding 33 per-hop behavior.

af41: Designates the use of Assured Forwarding 41 per-hop behavior.

af42: Designates the use of Assured Forwarding 42 per-hop behavior.

af43: Designates the use of Assured Forwarding 43 per-hop behavior.

be: Designates the use of Best Effort forwarding per-hop behavior.

ef: Designates the use of Expedited Forwarding per-hop behavior 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
retransmission-timeout seconds

Configures the control packet (non-echo) GTPv1 retransmission timeout in GTP (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.

Example:
The following command binds the service to a GTP-C interface with an IP address of 112.334.556.778:

    gtpc bind address 112.334.556.778

interface-type

Configures the interface type used by this service.
Platform:

ASR 5000
Product:

MME, P-GW, S-GW
Privilege:

Administrator
Syntax

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

{ interface-mme | interface-pgw-ingress | interface-sgsn | interface-sgw-egress | interface-sgw-ingress }

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.

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.
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

validation-mode

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

ASR 5000
Product:

P-GW
Privilege:

Administrator
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.
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 flowering command sets the validation mode for incoming messages to standard:

    validation-mode standard