1
In the network shown in this figure, the packet travels from the host A (having the IP address 10.222.5.55)
in the public network to host B (having the IP address 5.5.5.2) in the private network. The public address
has to be mapped to the private address by NAT44 that is implemented in ISM.
2
The packet enters through the ingress port on the Gigabit Ethernet (GigE) interface at Slot 0.
3
Once the packet reaches the designated interface or VLAN on ASR9K, it is forwarded to the outside VRF
either through static routing or ACL-based forwarding (ABL).
4
The packet is forwarded by App SVI2 through a default static route. The destination address and the port
are mapped to the translated address.
5
The ISM applies NAT44 to the packet. The CGN determines the destination address from the FIB Look
Up. It pushes the packet to the egress port.
6
The packet is then forwarded to the egress port on the interface through App SVI2. Then the packet is sent
to the private network through the inside VRF.
7
The packets that do not need the address translation can bypass the App SVI and can be forwarded to the
destination through a different static route and a different egress port.
Implementing NAT 64 over ISM
This section explains how NAT64 is implemented over ISM. The figure illustrates the implementation of
NAT64 over ISM.
The components of this implementation are as follows:
Cisco IOS XR Carrier Grade NAT Configuration Guide for the Cisco CRS Router, Release 5.2.x
OL-32659-01 11
Implementing Carrier Grade NAT on Cisco IOS XR Software
Implementing NAT 64 over ISM
To Next Page
Loading...
Need help?
General
