Cisco Cisco Packet Data Gateway (PDG) Documentation Roadmaps
Network Address Translation Overview
NAT Feature Overview ▀
Cisco ASR 5000 Series Product Overview ▄
OL-22937-01
ip subscriber-ip-address: The private IP address
radius-calling-station-id
radius-fa-nas-identifier
radius-fa-nas-ip-address
radius-user-name
sn-correlation-id: If available
sn-fa-correlation-id: If available
sn-nat-binding-timer: Optional
sn-nat-gmt-offset: Optional, GMT offset of the node generating this record. For example: -5.00, +5.30
sn-nat-ip
sn-nat-last-activity-time-gmt
sn-nat-port-block-end
sn-nat-port-block-start
sn-nat-port-chunk-alloc-dealloc-flag: 1: allocate; 0: deallocate
sn-nat-port-chunk-alloc-time-gmt: Sample time format: 03/11/2009 10:38:35
sn-nat-port-chunk-dealloc-time-gmt
sn-nat-realm-name: Optional
sn-nat-subscribers-per-ip-address: Optional
NAT Binding Updates
Whenever a NAT IP address or NAT port-chunk is allocated/deallocated to/from a subscriber, to update NAT binding
information for that subscriber in the AAA, a NAT Binding Update (NBU) can be sent to the AAA server.
information for that subscriber in the AAA, a NAT Binding Update (NBU) can be sent to the AAA server.
Important:
In the case of P-GW, NBUs is not applicable since it does not use RADIUS.
Since port-chunk allocation/deallocation happens on a per-call basis, this ensures that AAA messaging is reduced to a
great extent. NBUs are sent to the AAA server in accounting-interim messages. To send or not to send NBUs to the
AAA server is configurable in the NAT IP pool configuration.
great extent. NBUs are sent to the AAA server in accounting-interim messages. To send or not to send NBUs to the
AAA server is configurable in the NAT IP pool configuration.
NBUs are supported for both one-to-one and many-to-one NAT IP pools.
An NBU contains the following attributes:
Alloc-Flag
Binding-Timer
Correlation-Id
Loading-Factor
NAT-IP-Address