Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring GTP Services on the S5 Interface

    The following configuration specifies a separate address on which GTP packets (other than Create Session request) are received for a 3GPP S5 interface.

    The address you specify for an S5 interface must be the same address specified for the S8 interface although the VRF can be different. In addition, to allow mobility across 3G and Long Term Evolution (LTE), the S5 address must be the same as Gn and Gp addresses, optionally, with each interface in a different VRF, whether or not these addresses are specified explicitly or implicitly (through inheritance or from a higher level).

    To configure GTP services on an S5 interface for a broadband gateway configured as a GGSN/P-GW:

    1. Configure an IPv4 address on a loopback interface to specify the transport addresses on which GTP packets on the S5 interface are received.
      [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5]user@host# set interface lo0.1 v4-address 10.10.10.1
    2. For tunnel management, configure the maximum number of times that the gateway will attempt to send signaling-request messages to a peer (SGSN or S-GW).
      [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5]user@host# set n3-requests 6
    3. For tunnel management, configure the time that the gateway waits before resending a signaling-request message when a response to the request has not been received.
      [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5]user@host# set t3-response 8
    4. For path management, configure the maximum number of times that the gateway will attempt to send an echo-request message to a peer (SGSN or S-GW).
      [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5]user@host# set echo-n3-requests 6
    5. For path management, configure the time that the gateway waits before resending an echo-request message when an echo response to the echo request is not received.
      [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5]user@host# set echo-t3-response 4
    6. For path management, configure the number of seconds that the gateway waits before sending an echo-request message after an echo response is received from the peer.
      [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5]user@host# set echo-interval 65
    7. To configure a separate address on which GTP control packets are received for the S5 interface:
      1. Configure a loopback address to specify the address on which GTP control packets are received.
        [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5 control]user@host# set interface lo0.6 v4-address 10.10.10.2

        Note: The path management and tunnel management configuration you specified at the S5 interface level will also apply to GTP control packets unless you configure path management, or tunnel management, or both at the S5 control level.

      2. To interoperate with older gateways that support a GTP version with 16-bit sequence-number-length, configure the following option.
        [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5 control]user@host# set sequence-number-length16-bits
      3. Specify a forwarding class for outbound control packets.
        [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5 control]user@host# set forwarding-class assured-forwarding
      4. Specify a DSCP value in the IP packet header for outbound control packets.
        [edit unified-edge mobile gateways ggsn-pgw MBG1 gtp s5 control]user@host# set dscp-code-point 010110

    Published: 2011-11-17