Revision History

The Network Address Translation (NAT) is enhanced to introduce 5G MiFi device to the 5G network. With the enhancement, when more devices are connected to MiFi, the number of flows increases. The new 5G MiFi device allows up to a large number of devices through WiFi that requires the support of a large number of simultaneous IP flows in the P-GW NAT inline service in each single NAT pool. The NAT inline service is enhanced to support oversubscription and to keep a good utilization of NAT ports.

The min-port-chunk-per-user parameter added to the NAT ip-pool configuration guarantees new subscriber to have at least 1 (or n) port-chunks allocation. You can configure NAT pool for each subscriber port-chunk number, when it exceeds the calculated port-chunk number based on either (64k port) or napt-users-per-ip-addres .

Note

The min-port-chunk-per-user is only applicable to NAPT single-ip. min-port-chunk-per-user and port-chunk-threshold are mutually exclusive. Allows over subscription configuration. The number of port chunks per IP is reduced when you configure port-chunk size to a higher value. This is because the first 1024 ports are reserved.

For more information about Minimum Port-Chunks Reservation and configurations, refer the Minimum Port Chunks Reservation section in the NAT Configuration chapter of the NAT Administration Guide.

Use the following configuration commands to configure NAT IP pool.

configure 
   context context_name  
      ip pool min-port-chunk-per-user max_chunks_per_user  
      ip pool port-chunk-threshold 
      end 

NOTES:

• ip pool min-port-chunk-per-user : Specifies NAT Port minimum number of chunks per user for many-to-one NAT pool. max_chunks_per_user must be an integer from 1 through 100.

• ip pool port-chunk-threshold and ip pool min-port-chunk-per-user are mutually exclusive.