Unified Load Balancer Configuration and Administration Guide, Release 2026.03

PDF

Unified Load Balancer Configuration and Administration Guide, Release 2026.03

GTP-C egress management policy custom resource

Updated: July 29, 2026

Want to summarize with AI?

Log in

Details GTP-C egress management policy custom resource for technical implementation and operations. It highlights key workflows, requirements, and expected outcomes.

Session level messages

apiVersion: lbs.cisco.com/v1alpha1
kind: EgressManagementPolicy
metadata:
  name: <gtpc-sess-emp-name>
spec:
  egressIPs:
  - <gtpc-service-IP>
  egressMode: bpf
  egressPort:
    stateful:
    - podName: <gtpc-sess-0-name>
      portRanges:
      - <port-range11...port-range1n>
    - podName: <gtpc-sess-1-name>
      portRanges:
      - <port-range21...port-range2n>
    - podName: <gtpc-sess-2-name>
      portRanges:
      - <port-range31...port-range3n>
    - podName: <gtpc-sess-3-name>
      portRanges:
      - <port-range41...port-range4n>
    - podName: <gtpc-sess-4-name>
      portRanges:
      - <port-range51...port-range5n>
  protocol: GTPC
  target:
    selectors:
      matchLabels:
        <label-key1>: <label-value1>
        <label-key2>: <label-value2>

Node level messages

For GTP-C Echo Request and Response messages, both the source and destination ports are typically set to 2123. If an application uses a different source-port range for these messages, an EMP CR can be configured for node-level traffic in the same way as the session-level EMP CR described above.

Limitations:

  1. ULB does not explicitly handle fragmented IPv4 packets or IPv6 extension-header chains.

  2. Rolling upgrades and downgrades are not supported in this release.

  3. GTPv1-C message handling is not supported in this release.

  4. Recovery from resiliency events, such as pod or node restarts, is not supported in this release.