Behavior Change

Previous Behavior: The UDP proxy pod was used as an endpoint for the GTPC, PFCP, and RADIUS messages. If GTP default VIP, such as S11, S5, S5e, and S2b, was configured, the GTP endpoints started into the UDP proxy. Multiple protocol microservices depend on UDP proxy for UDP transport. Hence, UDP proxy was a scaling bottleneck. A surge of messages led to packet drops.

New Behavior: The UDP proxy functionality merges into the respective protocol microservice to mitigate the scaling bottleneck. The UDP proxy bypass improves the CPU usage by reducing one hop across microservices in the signaling path. With this new behavior:

  • If the GTP interface VIP is configured in the endpoint protocol, the GTP endpoints start into the UDP proxy.

  • If only the GTP default VIP is configured in the GTP endpoint and no VIP is configured in the endpoint protocol, then the GTP endpoints start into the GTPC endpoint.

Note

In this software release, you must deploy SMF in merged mode only. For more information on this mode, see the UCC SMF Configuration and Administration Guide and UCC cnSGWc Configuration and Administration Guide.