Verifying Network Address Translation (NAT) on a Cisco router requires inspecting both the static or dynamic rules committed to the running configuration and the real-time translation state maintained in memory. Even if your global NAT statements appear valid, missing interface direction commands, mismatched Access Control Lists (ACLs), or exhausted address pools can silently prevent traffic from translating. By following a structured command-line verification workflow across Cisco IOS and IOS XE platforms, you can quickly audit configured rules, inspect active translation tables, and pinpoint forwarding failures.
Table of Contents
Step-by-Step Guide to Checking NAT Configuration and Active Translations
Inspecting NAT on a Cisco router follows a four-step progression from static configuration review to live session monitoring. Execute these commands from privileged EXEC mode (Router#).
Step 1: Audit Global NAT Rules in the Running Configuration
Start by filtering the active configuration to view all global NAT statements, pool definitions, and ACL or route-map bindings:
Router# show running-config | include ip nat
ip nat pool PUBLIC_POOL 203.0.113.10 203.0.113.20 netmask 255.255.255.0
ip nat inside source list NAT_ACL pool PUBLIC_POOL overload
ip nat inside source static tcp 10.1.1.50 443 203.0.113.5 443 extendable
This command isolates your static mappings (ip nat inside source static), dynamic address pools (ip nat pool), and Port Address Translation (PAT) overload rules (overload) without scrolling through the entire configuration file.
Step 2: Verify Interface NAT Designations
Global translation rules will not trigger unless the router knows which interfaces face the internal network and which face the external network. Check the NAT directional assignments on your active interfaces:
Router# show ip interface | include line protocol|NAT
GigabitEthernet0/0 is up, line protocol is up
Network address translation is enabled, interface in domain outside
GigabitEthernet0/1 is up, line protocol is up
Network address translation is enabled, interface in domain inside
Alternatively, inspect a specific interface directly with show running-config interface GigabitEthernet0/0 to confirm the presence of ip nat inside, ip nat outside, or ip nat enable (used for NAT Virtual Interface configurations).
Step 3: Inspect the Active NAT Translation Table
Once configuration statements are confirmed, check the live translation table to see active mappings:
Router# show ip nat translations
Pro Inside global Inside local Outside local Outside global
tcp 203.0.113.5:443 10.1.1.50:443 --- ---
tcp 203.0.113.10:52411 10.1.1.102:52411 198.51.100.25:80 198.51.100.25:80
- Static NAT entries remain in the translation table permanently as long as the configuration is active, displaying
---under the Outside columns when idle. - Dynamic NAT and PAT entries populate only when matching traffic traverses the router and age out once the session closes or the translation timer expires.
- Append the
verbosekeyword (show ip nat translations verbose) to inspect how long an entry has been active, the remaining timeout counter, and internal translation flags.
Step 4: Check Global NAT Operational Statistics
To evaluate overall NAT health, pool capacity, and packet counters, run:
Router# show ip nat statistics
Total active translations: 2 (1 static, 1 dynamic; 1 extended)
Peak translations: 145, occurred 02:14:09 ago
Outside interfaces:
GigabitEthernet0/0
Inside interfaces:
GigabitEthernet0/1
Hits: 48290 Misses: 142
CEF Translated packets: 48148, CEF Punted packets: 142
Expired translations: 141
Dynamic mappings:
-- Inside Source
[Id: 1] access-list NAT_ACL pool PUBLIC_POOL refcount 1
pool PUBLIC_POOL: netmask 255.255.255.0
start 203.0.113.10 end 203.0.113.20
type generic, total addresses 11, allocated 1 (9%), misses 0
Section Takeaway: Always combine show running-config | include ip nat, show ip nat translations, and show ip nat statistics so you verify both the intended policy and whether packets are actively matching that policy in real time.
Interpreting NAT Output: Translation Columns and Operational Statistics
Running verification commands is only half the process; accurately reading the four-part address nomenclature in show ip nat translations and the counters in show ip nat statistics is essential for confirming that packets are translating to the expected IP addresses and ports.
NAT Translation Table Columns Explained
Cisco IOS categorizes every IP address in a NAT session based on whether the host is on the Inside or Outside of the router, and whether the IP address is viewed from the Local (private) or Global (public) network:
| Column Header | Network Perspective | Definition | Typical Value in Standard Outbound NAT/PAT |
|---|---|---|---|
| Pro | Protocol Layer | The Layer 4 transport protocol (or ICMP) associated with the translation entry. | tcp, udp, icmp, or --- (for protocol-independent static 1:1 entries) |
| Inside global | Public / External | The globally routable IP address (and port) representing an internal host to the outside network. | Your public WAN interface IP or an IP assigned from your public NAT pool (e.g., 203.0.113.10:52411) |
| Inside local | Private / Internal | The actual private IP address (and port) assigned to the host inside your enterprise LAN. | RFC 1918 private host IP address (e.g., 10.1.1.102:52411) |
| Outside local | Private / Internal | The IP address of the external destination host as it appears to the internal network. | Identical to the Outside global IP unless you are also performing destination/outside NAT |
| Outside global | Public / External | The actual globally routable IP address assigned to the remote host on the outside network. | The destination server’s public IP address (e.g., 198.51.100.25:80) |
Key Metrics in show ip nat statistics vs. show ip nat translations
| Metric / Field | Command Source | What It Measures | Operational Meaning |
|---|---|---|---|
| Hits | show ip nat statistics | Packets matching an already existing entry in the NAT translation table. | High and steadily increasing numbers indicate healthy, ongoing traffic flows using established translations. |
| Misses (Global) | show ip nat statistics | Packets requiring NAT that did not match an existing entry in the translation table. | A global miss is normal for the first packet of a new session, as it triggers the router to build a new dynamic translation. |
| Misses (Pool-Level) | show ip nat statistics | Failed attempts to allocate an IP address from a defined ip nat pool. | Non-zero pool misses indicate NAT pool exhaustion—no free global IPs or ports were available when a packet arrived. |
| Allocated (%) | show ip nat statistics | Percentage of total IP addresses in a dynamic NAT pool currently assigned. | Helps detect capacity bottlenecks before pool exhaustion drops new outbound connections. |
| CEF Translated vs. Punted | show ip nat statistics | Packets translated in hardware/Cisco Express Forwarding (CEF) vs. punted to the CPU. | The first packet of a flow or packets needing Application Layer Gateway (ALG) inspection are punted; subsequent packets should be CEF-translated. |
| Create / Use / Left Timers | show ip nat translations verbose | Timestamp of creation, time since last packet, and time remaining before expiration. | Identifies stale sessions consuming NAT table memory or premature timeouts breaking idle TCP connections. |
Section Takeaway: Distinguish between global Misses (which naturally increment whenever a new flow initiates a translation) and pool-specific misses (which indicate failed translations due to address exhaustion).
Checking VRF-Aware NAT Configurations on Cisco IOS XE Routers (FAQ)
In multi-tenant networks, MPLS VPN edge deployments, or SD-WAN environments running on Cisco IOS XE routers (such as Catalyst 8000, ISR 4000, or ASR 1000 series), NAT rules frequently operate across Virtual Routing and Forwarding (VRF) instances. Because VRFs maintain isolated routing and translation contexts, standard global checks must be adapted with VRF-specific parameters.
How do I filter active NAT translations for a specific VRF instance?
Append the vrf <vrf-name> keyword to the standard translation check command:
Router# show ip nat translations vrf CUSTOMER_A
Router# show ip nat translations vrf CUSTOMER_A verbose
This isolates the output to sessions belonging strictly to CUSTOMER_A, which is critical when multiple VRFs use overlapping RFC 1918 address spaces (for example, when two separate VRFs both use 10.5.5.0/24 internally).
What configuration keywords should I look for when auditing VRF-aware NAT rules?
When inspecting show running-config | include ip nat, check for two VRF-specific parameters depending on the traffic path:
1. VRF-to-Global NAT (vrf <name>): When traffic enters an inside interface belonging to a VRF and exits through a shared global outside interface, the NAT statement must include vrf <name> (e.g., ip nat inside source list ACL_10 pool SHARED_POOL vrf CUSTOMER_A overload).
2. Intra-VRF NAT (match-in-vrf): When both the inside interface and the outside interface belong to the same VRF, the NAT rule requires both the vrf <name> keyword and the match-in-vrf keyword at the end of the statement.
How do I verify inter-VRF NAT using VASI or NVI on Cisco IOS XE?
Depending on the platform generation and architecture, inter-VRF translation is inspected in one of three ways:
* VASI (VRF-Aware Software Infrastructure) Interfaces: On Cisco IOS XE routers performing inter-VRF routing and NAT, verify that paired virtual interfaces (vasileft1 and vasiright1) are up, assigned to their respective VRFs, and configured with ip nat inside / ip nat outside using show running-config interface vasileft1 and show running-config interface vasiright1.
* NAT Virtual Interface (NVI): If your router uses domainless ip nat enable interfaces instead of inside/outside domains, standard show ip nat translations will return empty output. You must include the nvi keyword: show ip nat nvi translations vrf <vrf-name> and show ip nat nvi statistics.
* IOS XE Hardware QFP Datapath: On Cisco IOS XE platforms with Quantum Flow Processors (QFP), verify that translations are properly programmed in the hardware forwarding plane using show platform hardware qfp active feature nat datapath stats and show platform hardware qfp active feature nat datapath map.
Section Takeaway: On VRF-segmented Cisco IOS XE routers, always verify the vrf and match-in-vrf keywords in the configuration and filter translation tables by VRF name (show ip nat translations vrf <name>) to avoid confusion over overlapping private subnets.
Troubleshooting Guide: Diagnosing and Fixing Cisco NAT Issues
When your verification commands reveal 0 Hits, missing translation entries, or intermittent connectivity drops, walk through this sequential diagnostic guide to resolve the root cause.
Step 1: Confirm ip nat inside and ip nat outside Interface Placement
The most frequent cause of a completely empty NAT table (0 Hits and 0 Misses) is omitting or reversing the ip nat inside and ip nat outside commands. Ensure that:
* Every internal LAN interface (including subinterfaces, BDI/SVI interfaces, or VRF customer links) that originates traffic has ip nat inside applied.
* The egress WAN interface has ip nat outside applied.
Step 2: Check ACL Match Counters and Order of Operations
If dynamic NAT or PAT fails to trigger for specific hosts, inspect the referenced Access Control List:
Router# show access-lists NAT_ACL
Extended IP access list NAT_ACL
10 permit ip 10.1.1.0 0.0.0.255 any (142 matches)
- If the ACL displays zero matches, verify that the source subnet mask/wildcard mask matches the actual host IP addresses.
- Respect Cisco IOS Order of Operations: For outbound traffic (Inside-to-Outside), the router checks Inbound Interface ACLs and the Routing Table before executing NAT. Ensure an inbound security ACL is not dropping the packet before it reaches the NAT engine, and verify the router has a valid route (such as a default route) toward the destination.
Step 3: Diagnose Pool Exhaustion and Missing overload
If a dynamic NAT pool serves multiple internal users without the overload keyword, the router performs 1:1 dynamic NAT. Once all IP addresses in the pool are assigned (shown as allocated 100% with incrementing pool misses in show ip nat statistics), additional hosts cannot connect. Fix this by appending the overload keyword to your ip nat inside source list statement to enable PAT.
Step 4: Verify Upstream Return Routing for Inside Global Addresses
Sometimes show ip nat translations proves that outbound packets are being translated properly, yet the client receives no reply. For return traffic to reach the router:
* If your Inside global address belongs to a dedicated NAT pool on a different subnet than the router’s WAN interface IP, the upstream router or ISP must have a static or dynamic route pointing that NAT pool subnet back to your router’s WAN IP.
* If the Inside global address is within the same subnet as the WAN interface, ensure the router wasn’t configured with the no-alias keyword unless another device is handling ARP replies for those addresses.
Step 5: Clear Stale or Stuck NAT Translations Safely
After modifying a NAT rule, ACL, or pool, existing dynamic entries in the translation table will continue using the old mapping until they time out. Rather than wiping the entire table in production with clear ip nat translation * (which drops all active user sessions), clear only the specific host or flow you are testing:
Router# clear ip nat translation inside 203.0.113.10 10.1.1.102
Router# clear ip nat translation tcp inside 203.0.113.10 52411 10.1.1.102 52411 outside 198.51.100.25 80 198.51.100.25 80
Step 6: Run Filtered Real-Time NAT Debugging Safely
Unfiltered debug ip nat on a busy production router can overwhelm the CPU if packets are punted or logged to the console. Always disable console logging, send debug output to the internal buffer, and restrict debugging with an ACL matching only your test host:
Router(config)# access-list 199 permit ip host 10.1.1.102 any
Router(config)# access-list 199 permit ip any host 10.1.1.102
Router(config)# logging buffered 64000 debugging
Router(config)# no logging console
Router(config)# end
Router# debug ip nat 199 detailed
Router# show logging | include NAT
Router# undebug all
Look for NAT*: s=10.1.1.102->203.0.113.10, d=198.51.100.25 (confirming outbound source translation) and NAT*: s=198.51.100.25, d=203.0.113.10->10.1.1.102 (confirming inbound return translation).
Section Takeaway: Most NAT failures trace back to missing interface direction statements, ACL mismatches, or missing return routes for the translated Inside Global pool—issues you can isolate safely using ACL-filtered debugs and targeted translation clears.
Cisco IOS and IOS XE NAT Verification CLI Cheat Sheet
Copy and adapt the following CLI command template for rapid NAT auditing, session filtering, hardware verification, and maintenance on Cisco IOS and IOS XE routers:
! ==========================================================
! 1. CONFIGURATION & INTERFACE AUDIT COMMANDS
! ==========================================================
show running-config | include ip nat
show running-config | section ip nat|interface|ip access-list
show ip interface | include line protocol|NAT
show access-lists <NAT_ACL_NAME_OR_NUMBER>
show route-map <NAT_ROUTE_MAP_NAME>
! ==========================================================
! 2. ACTIVE TRANSLATION TABLE & FILTERING COMMANDS
! ==========================================================
show ip nat translations
show ip nat translations verbose
show ip nat translations | include <INTERNAL_OR_PUBLIC_IP>
show ip nat translations vrf <VRF_NAME>
show ip nat translations vrf <VRF_NAME> verbose
show ip nat nvi translations
! ==========================================================
! 3. STATISTICS & IOS XE HARDWARE DATAPATH COMMANDS
! ==========================================================
show ip nat statistics
show ip nat nvi statistics
show platform hardware qfp active feature nat datapath stats
show platform hardware qfp active feature nat datapath map
show platform software nat fp active
! ==========================================================
! 4. TRANSLATION TABLE CLEARING COMMANDS
! ==========================================================
! Clear a single inside local/global mapping safely:
clear ip nat translation inside <INSIDE_GLOBAL_IP> <INSIDE_LOCAL_IP>
! Clear all dynamic UDP translations only:
clear ip nat translation udp
! Clear all dynamic translations globally (disruptive in production):
clear ip nat translation *
! ==========================================================
! 5. PRODUCTION-SAFE FILTERED NAT DEBUGGING TEMPLATE
! ==========================================================
configure terminal
ip access-list extended DEBUG_NAT_HOST
permit ip host <TEST_HOST_IP> any
permit ip any host <TEST_HOST_IP>
exit
logging buffered 128000 debugging
no logging console
end
debug ip nat DEBUG_NAT_HOST detailed
! --- Generate test traffic now, then inspect logs: ---
show logging | include NAT
! --- Turn off debugging immediately after testing: ---
undebug all
Section Takeaway: Keep this command reference on hand during change windows to audit configurations, filter large translation tables down to specific hosts, and execute non-disruptive troubleshooting.
Official Cisco Documentation and Command References
For platform-specific syntax variations, software release caveats, and architectural deep dives across Cisco IOS and Cisco IOS XE releases, consult the following official Cisco Systems technical publications:
- IP Addressing: NAT Configuration Guide (Cisco IOS XE 17.x): The primary architectural and configuration manual for Catalyst 8000, ISR 1000/4000, and ASR 1000 Series routers. Covers static/dynamic NAT, PAT overload, VRF-aware NAT, VASI inter-VRF NAT, and Carrier-Grade NAT (CGN).
- Cisco IOS IP Addressing Services Command Reference: Provides the complete syntax definition, command history, default timers, and output field descriptions for
show ip nat translations,show ip nat statistics,clear ip nat translation, anddebug ip nat. - Verify and Troubleshoot Basic NAT Operations (Cisco Support TechNote — Document ID: 6450): Official Cisco TAC troubleshooting workflow covering packet flow verification, routing dependencies, ARP behavior, and resolution steps for common connectivity failures in NAT environments.
- Configure VRF-Aware Software Infrastructure (VASI) NAT on IOS-XE (Cisco Support TechNote — Document ID: 200255): Details the official configuration and verification procedures for pairing
vasileftandvasirightinterfaces to translate traffic between separate VRF instances on Cisco IOS XE platforms. - Understand and Configure NAT Virtual Interface (NVI) (Cisco Support TechNote — Document ID: 71112): Explains domainless NAT operations (
ip nat enable) and the correspondingshow ip nat nviverification commands.
Section Takeaway: Match your router’s operating system train (show version) against the corresponding Cisco IOS or Cisco IOS XE Configuration Guide when verifying advanced features such as QFP hardware acceleration or VASI inter-VRF translation.
Checking NAT configuration on a Cisco router is most reliable when approached systematically: inspect the configured rules and interface directions in the running configuration, verify live session state in the translation table, and examine hit/miss counters in the NAT statistics. Whether you are managing a standard branch internet edge or a multi-VRF Cisco IOS XE router, combining these verification commands with targeted ACL checks and filtered debugging gives you full visibility into every address translation across your network.











Comments