Limitations
NAT support on the N4 interface has the following limitations:
-
Supports only NAT44 with many-to-one and on-demand modes.
-
All NAT pools are configured at respective User Plane in the destination context.
-
Does not support charging action with CLI action deny in fw-and-nat policy and flow-any-error charging action in active-charging-service.
-
Does not support access-rules which are configured with "dynamic-only" and "static-and-dynamic" rules from external servers.
-
Does not support multiple IPs from the same realm.
-
Does not support the next hop forwarding in NAT pool.
-
Does not support the port range in NAT pool.
-
Does not support the skip private IP check CLI.
-
Does not support RADIUS and Gy returned Fw-and-nat policy-based applying NAT policy.
-
Does not support the bearer-specific filters in access-ruledefs.
-
Access-rules do not support trigger open-port port range configuration in fw-and-nat policy.
-
Does not support the NAT port recovery (fw-and-nat action) after SR/ICSR.
-
Does not support the NAT reassembly timeout CLI in active-charging service. The generic context-level CLI on UP must be used instead.
-
Does not support the NAT fragmentation reassembly failure.
-
Does not support the NAT flow-mapping timer.
-
For N:M redundancy, the NAT IP pools to be configured from RCM done as part of interface configuration for each UP host and the pool name must be unique across all active user planes. It is mandatory to use NAT groups for all pools so that the same NAT realm referred in fw-and-nat policy can be applicable to all user planes.
-
In N:M redundancy, the total number of NAT IP pools collectively configured on all UPs through RCM must be as per the maximum limit (2000) of IP pools. The configuration in standby User Plane fails if the cumulative total of all active UPs exceeds the maximum value.