How it Works

This section describes how this feature works:

  • In SMF-Ops-Center , you can configure GTPC-EP Geo endpoints for each rack in IMS and data racks.

  • In SMF-Ops-Center CLI, you can configure GTPC-EP Geo endpoints for each rack in IMS and DATA racks.

    Note

    The optimization of GTPC messages can be applied to all four instances or a subset of instances of GTPC endpoints within these racks. A new element is added under the GTPC endpoints to configure a list of IP addresses where SMF and cnSGW-C service pods can route the GTPv2 messages over the IPC interface.

Upgrading and Enabling Inter-rack GTPC IPC

This section describes how to upgrade and enable the inter-rack GTPC IPC.

Before you configure, upgrade, and enable the GTPC IPC optimization on cnSGW-C and SMF interfaces, you must perform the following:

  • The inter-rack routing must be applied to the branched core network.

  • More configuration parameters such as GTPC, cnSGW-C, and SMF are enabled, when extra routes are added for supporting a new routable network across rack servers.

Note

The following are configuration-related points:

  • The SGW service pods for the S5 egress MBR request are used for IPC messages toward PGWc and SMF IP in the list.

  • The SMF service pods for S5 CBR, UBR, and DBR requests are used for IPC messages toward the cnSGW-C in the list.

  • IPC messages reuse the N3 or the T3 configuration for the respective interfaces to retry messages, whenever the timeout in the peer node occurs.