Study guide
7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload
Cisco ENCOR 350-401 CCNP Enterprise Core
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 Cisco 350-401 ENCOR Exam Logistics, Blueprint Structure, and Certification Paths 0.2 Preparation Strategy, Lab Environment Setup, and Practical Test Pacing
2 Enterprise Campus Architecture and High Availability
1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures 1.2 High Availability Architecture: Device Redundancy, FHRPs, and Stateful Switchover (SSO) 1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation
3 Cisco Software-Defined Architecture: SD-WAN and SD-Access
2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes 2.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles 2.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric
4 Device and Network Virtualization Technologies
3.1 Device Virtualization: Type 1/2 Hypervisors, Virtual Machines, and Virtual Switching 3.2 Data Path Virtualization: VRF-Lite, GRE Tunneling, and IPsec VPN Fundamentals 3.3 Network Virtualization Overlays: LISP and VXLAN Encapsulation Mechanics
5 Layer 2 Infrastructure: Trunking, EtherChannel, and Spanning Tree
4.1 802.1Q Trunking, Native VLAN, and Dynamic Trunking Protocol Troubleshooting 4.2 EtherChannel Bundling: Static, LACP, and PAgP Implementation and Verification 4.3 Spanning Tree Architecture: RSTP, MST, and STP Protection Mechanisms
6 Layer 3 Routing: OSPF Multi-Area and Protocol Comparison
5.1 Enterprise Routing Principles: Distance Vector vs. Link-State, EIGRP, and OSPF 5.2 OSPFv2 and OSPFv3 Multi-Area Architecture: LSAs, Area Types, and Summarization 5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps
7 Exterior Routing: BGP Peering and Path Selection
6.1 External BGP (eBGP) Peering, States, Neighbor Adjacencies, and Timers 6.2 BGP Path Attributes and the Step-by-Step Best Path Selection Algorithm
8 IP Services and First-Hop Redundancy
7.1 Time Synchronization: Network Time Protocol (NTP) and Precision Time Protocol (PTP) 7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload 7.3 First Hop Redundancy Protocols: HSRP and VRRP Implementation and Failover
9 IP Multicast Architecture and Protocols
8.1 Multicast Addressing, IGMPv2/v3 Host Membership, and the RPF Check 8.2 Protocol Independent Multicast Sparse Mode (PIM-SM) and Rendezvous Point Discovery 8.3 Anycast RP with MSDP, Source-Specific Multicast (SSM), and Bidirectional PIM
10 Network Diagnostics, Monitoring, and Telemetry
9.1 Network Diagnostic Tools: Conditional Debugging, Traceroute, SNMPv3, and Syslog Logging 9.2 Flexible NetFlow (FNF) Architecture: Flow Records, Exporters, and Monitors 9.3 Switched Port Analyzer: Local SPAN, Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN)
11 Performance Monitoring and Model-Driven Assurance
10.1 IP Service Level Agreements (IP SLA) Probes, Responder, and Route Tracking 10.2 Cisco Catalyst Center: Assurance Dashboards, AI Analytics, and Machine Reasoning Workflows 10.3 Model-Driven Telemetry and Programmable Interfaces: NETCONF and RESTCONF Verification
12 Device Access Control and AAA Architecture
11.1 Device Line Protection: Console, Aux, VTY, Local Authentication, and Privilege Levels 11.2 AAA Architecture: Comparing RADIUS vs. TACACS+ and Method List Configuration
13 Infrastructure Security: ACLs, CoPP, and API Security
12.1 IPv4 and IPv6 Access Control Lists (ACLs): Standard, Extended, and Named Rules 12.2 Control Plane Policing (CoPP): Protecting the Route Processor with MQC 12.3 REST API Security: Token Authentication, TLS Transport, and Rate Limiting
14 Enterprise Network Security Design: ISE, TrustSec, and MACsec
13.1 Endpoint Security Architecture: 802.1X, Cisco ISE Posture, and Profiling 13.2 Next-Generation Firewalls (FTD) and Enterprise Threat Defense Design 13.3 Cisco TrustSec (Security Group Tags) and MACsec (802.1AE) Layer 2 Encryption
15 Network Automation Fundamentals: Python, JSON, and YANG
14.1 Python Fundamentals for Network Engineers: Data Types, Control Flow, and Libraries 14.2 JSON Data Encoding: Syntax, Formatting Rules, and Python Serialization 14.3 YANG Data Modeling: Modules, Tree Structures, and Data Representation
16 Controller REST APIs and RESTCONF Implementation
15.1 Cisco Catalyst Center Intent APIs and Authentication Workflows 15.2 Cisco Catalyst SD-WAN Manager (vManage) REST APIs and Device Interaction 15.3 RESTCONF Protocol Operations: HTTP Verbs, Datastores, and Response Codes
17 Event-Driven Automation and Infrastructure Orchestration
16.1 Cisco Embedded Event Manager (EEM) Applet Architecture and Event Detectors 16.2 Configuration Management: Comparing Ansible, Puppet, Chef, and SaltStack 16.3 Infrastructure as Code (IaC) Principles with Terraform in Enterprise Networks
7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload
Key Takeaways Explain This Topic AI
Cisco NAT terminology describes addresses from four perspectives: Inside Local (private host IP), Inside Global (public IP representing inside host), Outside Local (external IP viewed internally), and Outside Global (registered public destination IP).
Static NAT creates an immutable, bidirectional 1:1 address binding between an Inside Local and Inside Global address, permitting inbound session initiation for DMZ public services.
Dynamic NAT maps private inside hosts to an available pool of public IP addresses on demand; translations preserve port numbers but fail once the available pool is depleted.
Port Address Translation (PAT / NAT Overload) multiplexes tens of thousands of concurrent client sessions onto a single public IP address by tracking unique Layer 4 TCP and UDP port numbers.
IPsec Encapsulating Security Payload (ESP) lacks Layer 4 port numbers, preventing PAT multiplexing; NAT Traversal (NAT-T / RFC 3948) resolves this by encapsulating ESP inside UDP port 4500.
Last updated: October 2026
Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload
Network Address Translation (NAT), defined in RFC 2663 , was introduced as an interim mechanism to slow IPv4 address exhaustion by enabling private IP networks (governed by RFC 1918 ) to communicate across the public Internet. Today, NAT remains an essential architectural component in enterprise edge routing, demilitarized zone (DMZ) security design, multi-tenant cloud segmentation, and business-to-business extranet integrations where overlapping address spaces collide.
Cisco NAT Address Terminology
Understanding NAT requires analyzing packets from two perspectives: the location of the host ( Inside vs. Outside ) and the perspective of the network viewing the address ( Local vs. Global ). +------------------------------------+ +------------------------------------+
- | INSIDE NETWORK (Private) | | OUTSIDE NETWORK (Public) |
- | Inside Local Inside Global | ROUTER | Outside Local Outside Global |
- | [10.10.1.50] --> [198.51.100.25] |==[NAT]==>| [203.0.113.10] <-- [203.0.113.10] |
- +------------------------------------+ +------------------------------------+
- The Four NAT Address Classifications
Inside Local (IL): The IP address assigned to an internal host residing on the private enterprise network. This address is typically drawn from RFC 1918 private space ( 10.0.0.0/8 , 172.16.0.0/12 , or 192.168.0.0/16 ) and is non-routable across the public Internet.
Inside Global (IG): The globally routable, public IPv4 address that represents the internal host to the external world. The NAT router translates the Inside Local source address into the Inside Global address on outbound transit.
Outside Local (OL): The IP address of an external host as it appears to internal endpoints on the inside network. In standard NAT deployments, the Outside Local address is identical to the Outside Global address. However, in advanced scenarios involving outside NAT or overlapping subnets, the router rewrites the external destination IP to an internal local address.
Outside Global (OG): The globally routable public IPv4 address assigned by the service provider or registered owner to the destination host on the outside network.
NAT Address Type Matrix
Address Category Physical Location Network Perspective Packet Direction & Header Modification Concrete Enterprise Example
Inside Local (IL) Inside Enterprise Viewed from Inside Source IP on outbound packet before translation 10.10.1.50 (Internal Web App Server)
Inside Global (IG) Inside Enterprise Viewed from Outside Source IP on outbound packet after translation 198.51.100.25 (Public NAT Address)
Outside Local (OL) Outside Internet Viewed from Inside Destination IP on outbound packet before translation 203.0.113.10 (Cloud SaaS Endpoint)
Outside Global (OG) Outside Internet Viewed from Outside Destination IP on outbound packet after translation 203.0.113.10 (Public Destination Server)
Packet Header Transformation Walkthrough
Consider an internal host ( 10.10.1.50 ) transmitting an HTTP request to an external web server ( 203.0.113.10 ):
Outbound Ingress (LAN to WAN):
Original packet received on the inside interface: Source: 10.10.1.50:51234 ⟶ \longrightarrow ⟶ Destination: 203.0.113.10:80 .
NAT lookup occurs. The router translates the Source IP from Inside Local ( 10.10.1.50 ) to Inside Global ( 198.51.100.25 ).
Egress packet transmitted out the outside interface: Source: 198.51.100.25:51234 ⟶ \longrightarrow ⟶ Destination: 203.0.113.10:80 .
Inbound Return (WAN to LAN):
Return packet received on the outside interface: Source: 203.0.113.10:80 ⟶ \longrightarrow ⟶ Destination: 198.51.100.25:51234 .
NAT state lookup matches the active session. The router translates the Destination IP from Inside Global ( 198.51.100.25 ) back to Inside Local ( 10.10.1.50 ).
Egress packet delivered to the inside host: Source: 203.0.113.10:80 ⟶ \longrightarrow ⟶ Destination: 10.10.1.50:51234 .
- The Three Flavors of NAT NAT ARCHITECTURES
- |
- +---------------------------+---------------------------+
- | |
- STATIC NAT DYNAMIC NAT
- (1:1 Fixed Mapping) |
- Inbound & Outbound Initiation +----------+----------+
- Ideal for DMZ Public Servers | |
- DYNAMIC POOL PAT / OVERLOAD
- (1:1 Dynamic Lease) (M:1 Port Multiplexing)
- No Port Rewriting 65,000+ Flows per IP
- Pool Depletion Risk Outbound Initiation
- 1. Static NAT (One-to-One Permanent Translation)
Static NAT configures a fixed, persistent mapping between an Inside Local address and an Inside Global address. The relationship is permanent and bidirectional: outside clients can initiate incoming sessions directly to the Inside Global address, which the router translates to the server's private Inside Local IP. Static NAT is standard for hosting enterprise DMZ services (such as HTTPS portals, SMTP relays, or external DNS servers).
2. Dynamic NAT (Many-to-Many Dynamic Allocation)
Dynamic NAT defines a pool of public Inside Global addresses. When an internal client initiates an outbound connection, the router dynamically assigns an unused IP from the pool. Key characteristics include:
Translations are temporary and stateful, expiring after inactivity.
Transport Layer port numbers are not modified ; the client retains its original Layer 4 source port.
Pool Depletion: If the pool contains ten public IPs, only ten internal hosts can establish external sessions concurrently. The eleventh host is dropped until an existing translation expires or is manually cleared.
3. Port Address Translation (PAT / NAT Overload)
PAT multiplexes thousands of private internal IP addresses onto a single public IP (or a small pool) by modifying both the Layer 3 source IP and the Layer 4 TCP/UDP source port . PAT tracks flows using a stateful 5-tuple: (Protocol, Source IP, Source Port, Destination IP, Destination Port) .
Port Multiplexing Capacity: Because TCP and UDP headers allocate 16 bits for port numbers, a single public IP theoretically supports up to 65,536 concurrent connections per protocol. In practice, Cisco routers allocate ports from three pools: 0–511, 512–1023, and 1024–65535. If multiple inside hosts transmit from the same source port (e.g., port 1024), PAT preserves the source port for the first host and re-marks subsequent hosts to unused ports in the same range.
Comparison of NAT Implementations
Feature / Metric Static NAT Dynamic NAT Port Address Translation (PAT / Overload)
Mapping Ratio 1 Inside Local : 1 Inside Global 1 Inside Local : 1 Inside Global (dynamic) Many Inside Local : 1 Inside Global
Layer 4 Port Translation No (Preserves original port) No (Preserves original port) Yes (Rewrites source port when needed)
Session Initiation Bidirectional (Inbound and Outbound) Outbound only (Inbound requires existing state) Outbound only (Inbound requires port forwarding)
Public IP Scalability Low (Requires 1 public IP per host) Low (Requires public IP per concurrent host) High (~65,000 concurrent sessions per IP)
Primary Use Case Public DMZ web/mail/API servers Rare legacy integrations without port changes Standard enterprise campus Internet access
Cisco IOS-XE Configuration and Implementation
NAT configuration on Cisco IOS-XE requires three distinct steps: defining boundary interfaces, selecting traffic via an Access Control List (ACL), and applying the translation rule. ! Step 1: Designate interface roles
- interface GigabitEthernet0/0/0
- description Internal Corporate LAN
- ip nat inside
!
- interface GigabitEthernet0/0/1
- description Primary ISP Uplink
- ip nat outside
!
- ! Step 2: Define traffic matching access list
- ip access-list standard ACL_CORP_INTERNAL
- permit 10.10.0.0 0.0.255.255
!
- ! Step 3a: Static NAT Configuration (DMZ Server)
- ip nat inside source static 10.10.50.10 198.51.100.50 extendable
!
- ! Step 3b: Dynamic NAT Pool Configuration
- ip nat pool POOL_PUBLIC 198.51.100.10 198.51.100.20 netmask 255.255.255.224
- ip nat inside source list ACL_CORP_INTERNAL pool POOL_PUBLIC
!
- ! Step 3c: PAT / Overload on Egress Interface (Standard Enterprise Model)
- ip nat inside source list ACL_CORP_INTERNAL interface GigabitEthernet0/0/1 overload
The extendable keyword in static NAT allows the network engineer to configure multiple translations referencing the same global IP (such as port forwarding different TCP ports to distinct internal servers) or apply the same rule across multiple VRF instances.
Operational Behavior, Timeouts, and Troubleshooting
Cisco IOS-XE maintains active translation sessions in the NAT table. These sessions are aged out according to configurable timers:
TCP Session Timeout: Defaults to 86,400 seconds (24 hours) for fully established connections.
TCP FIN / RST Timeout: Defaults to 60 seconds after observing TCP termination flags, freeing memory quickly.
UDP Timeout: Defaults to 300 seconds (5 minutes) because UDP lacks connection-teardown signaling.
ICMP Timeout: Defaults to 60 seconds , aging out ping translations rapidly.
- Verifying NAT Operations Router# show ip nat translations
- Pro Inside global Inside local Outside local Outside global
- tcp 198.51.100.1:1024 10.10.1.50:1024 203.0.113.10:443 203.0.113.10:443
- tcp 198.51.100.1:1025 10.10.1.51:1024 203.0.113.10:443 203.0.113.10:443
- -- 198.51.100.50 10.10.50.10 --- ---
- Router# show ip nat statistics
- Total active translations: 3 (1 static, 2 dynamic; 2 extended)
Outside interfaces:
GigabitEthernet0/0/1
Inside interfaces:
- GigabitEthernet0/0/0
- Hits: 1482932 Misses: 24
- Expired translations: 1482905
Dynamic mappings:
- - Inside Source
- [Id: 1] access-list ACL_CORP_INTERNAL interface GigabitEthernet0/0/1 ref count 2
In show ip nat statistics , Hits indicate packets matched against existing translations, while Misses indicate packets requiring a new entry in the translation table. A high miss rate accompanied by dropped packets indicates pool depletion under Dynamic NAT.
- To clear dynamic entries without disrupting static mappings: Router# clear ip nat translation *
- Router# clear ip nat translation inside 10.10.1.50 198.51.100.1
- NAT and IPsec Interaction: NAT Traversal (NAT-T / RFC 3948)
Deploying IPsec Virtual Private Networks (VPNs) across intermediate NAT routers introduces two major technical obstacles:
Authentication Header (AH / IP Protocol 51) Incompatibility: AH calculates an Integrity Check Value (ICV) across immutable fields of the IP packet, including the source and destination IP addresses. When an intermediate router performs NAT, it rewrites the IP address, causing the receiving IPsec peer to recalculate a mismatched ICV and drop the packet. AH is fundamentally incompatible with NAT.
Encapsulating Security Payload (ESP / IP Protocol 50) PAT Incompatibility: Standard ESP encrypts the transport-layer payload and operates directly over IP (protocol 50) without a TCP or UDP header. Because standard ESP lacks Layer 4 port fields, a PAT router cannot multiplex multiple outbound ESP tunnels over a single public IP address.
The NAT-T Solution
NAT Traversal (NAT-T) , standardized in RFC 3948 , resolves this conflict seamlessly: [Standard ESP Packet - Fails PAT]
- +-----------+-----------+-------------------------+
- | IP Header | ESP (50) | Encrypted Payload + Auth|
- +-----------+-----------+-------------------------+
- [NAT-T Encapsulated Packet - Traverses PAT]
- +-----------+------------+-----------+-------------------------+
- | IP Header | UDP 4500 | ESP (50) | Encrypted Payload + Auth|
- +-----------+------------+-----------+-------------------------+
NAT Discovery: During Internet Key Exchange (IKE) Phase 1 negotiation over UDP port 500 , peers transmit MD5/SHA hashes of their source and destination IP addresses. If the receiver calculates a different hash, it detects the presence of a NAT device along the transit path.
Port Floating to UDP 4500: Once NAT is detected, both peers dynamically shift communication from UDP port 500 to UDP port 4500 .
UDP Encapsulation: The router encapsulates outbound ESP packets inside a standard UDP header with source and destination ports set to 4500. Intermediate PAT routers can now modify the outer UDP port numbers without corrupting the inner encrypted ESP packet.
NAT-T Keepalives: Because intermediate PAT routers age out UDP translation entries after 300 seconds of inactivity, IPsec peers transmit lightweight UDP 4500 keepalive packets (typically every 20 seconds) to maintain active NAT state.