Table Of Contents
Integrating NAT with MPLS VPNs
Prerequisites for Integrating NAT with MPLS VPNs
Restrictions for Integrating NAT with MPLS VPNs
Information About Integrating NAT with MPLS VPNs
Benefits of NAT Integration with MPLS VPNs
Implementation Options for Integrating Nat with MPLS VPNs
Scenarios for Implementing NAT on the PE Router
How to Integrate NAT with MPLS VPNs
Configuring Inside Dynamic NAT with MPLS VPNs
Configuring Inside Static NAT with MPLS VPNs
Configuring Outside Dynamic NAT with MPLS VPNs
Configuring Outside Static NAT with MPLS VPNs
Configuration Examples for Integrating NAT with MPLS VPNs
Configuring Inside Dynamic NAT with MPLS VPNs: Example
Configuring Inside Static NAT with MPLS VPNs: Example
Configuring Outside Dynamic NAT with MPLS VPNs: Example
Configuring Outside Static NAT with MPLS VPNs: Example
Feature Information for Integrating NAT with MPLS VPNs
Integrating NAT with MPLS VPNs
First Published: May 2, 2005Last Updated: May 2, 2005Network Address Translation (NAT) Integration with MPLS VPNs feature allows multiple Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) to be configured on a single device to work together. NAT can differentiate which MPLS VPN it receives IP traffic from even if the MPLS VPNs are all using the same IP addressing scheme. This enhancement enables multiple MPLS VPN customers to share services while ensuring that each MPLS VPN is completely separate from the other.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Integrating NAT with MPLS VPNs" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Integrating NAT with MPLS VPNs
•
Restrictions for Integrating NAT with MPLS VPNs
•
Information About Integrating NAT with MPLS VPNs
•
How to Integrate NAT with MPLS VPNs
•
Configuration Examples for Integrating NAT with MPLS VPNs
•
Feature Information for Integrating NAT with MPLS VPNs
Prerequisites for Integrating NAT with MPLS VPNs
•
Before performing the tasks in this module, you should be familiar with the concepts described in the "Configuring NAT for IP Address Conservation" module.
•
All access lists required for use with the tasks in this module should be configured prior to beginning the configuration task. For information about how to configure an access list, see the IP Access List Sequence Numbering document at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fsaclseq.htm
Note
If you specify an access list to use with a NAT command, NAT does not support the commonly used permit ip any any command in the access list.
Restrictions for Integrating NAT with MPLS VPNs
Inside VPN to VPN with NAT is not supported.
Information About Integrating NAT with MPLS VPNs
To integrate NAT with MPLS VPNs, you should understand the following concepts:
•
Benefits of NAT Integration with MPLS VPNs
•
Implementation Options for Integrating Nat with MPLS VPNs
•
Scenarios for Implementing NAT on the PE Router
Benefits of NAT Integration with MPLS VPNs
MPLS service providers would like to provide value-added services such as Internet connectivity, domain name servers (DNS), and voice over IP (VoIP) service to their customers. The providers require that their customers; IP addresses be different when reaching the services. Because MPLS VPN allows customers to use overlapped IP addresses in their networks, NAT must be implemented to make the services possible.
Implementation Options for Integrating Nat with MPLS VPNs
There are two approaches to implementing NAT in the MPLS VPN network. NAT can be implemented on the customer edge (CE) router, which is already supported by NAT, or it can be implemented on a provider edge (PE) router. The NAT Integration with MPLS VPNs feature enables the implementation of NAT on a PE router in an MPLS cloud.
Scenarios for Implementing NAT on the PE Router
NAT could be implemented on the PE router in the following scenarios:
•
Service point—Shared access can be from a generic interface or from a VPN interface.
•
NAT point—NAT can be configured on the PE router that is directly connected to the shared access gateway, or on the PE router that is not directly connected to the shared access gateway.
•
NAT interface—The shared access gateway interface most often is configured as the outside interface of NAT. The inside interface of NAT can be either the PE-CE interface of a VPN, the interface to the MPLS backbone, or both. The shared access gateway interface can also be configured as the inside interface.
•
Routing type—Common service can be Internet connectivity or a common server. For Internet connectivity, a default route should be propagated to all the VPN customers that use the service. For common server access, a static or dynamically learned route should be propagated to the VPN customers.
•
NAT configuration—NAT can have different configurations: static, dynamic, pool/interface overloading, and route-map.
Figure 1 shows a typical NAT integration with MPLS VPNs. The PE router connected to the internet and centralized mail service is employed to do the address translation.
Figure 1 Typical NAT Integration with MPLS VPNs
How to Integrate NAT with MPLS VPNs
Perform one or more of the following tasks depending on the type of translation you wish to configure for your network:
•
Configuring Inside Dynamic NAT with MPLS VPNs (optional)
•
Configuring Inside Static NAT with MPLS VPNs (optional)
•
Configuring Outside Dynamic NAT with MPLS VPNs (optional)
•
Configuring Outside Static NAT with MPLS VPNs (optional)
Configuring Inside Dynamic NAT with MPLS VPNs
Perform this task to configure your NAT PE router for dynamic translations to integrate with MPLS VPNs.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip nat pool name start-ip end-ip netmask netmask
4.
ip nat [inside | outside] source [list {access-list-number | access-list-name} | route-map name] [interface type number | pool pool-name] vrf vrf-name [overload]
5.
Repeat Step 4 for all VPNs being configured.
6.
ip route vrf vrf-name prefix mask interface-type interface-number next-hop-address
7.
Repeat Step 6 for all VPNs being configured.
8.
exit
9.
show ip nat translations vrf vrf-name
DETAILED STEPS
Configuring Inside Static NAT with MPLS VPNs
Perform this task to configure your NAT PE router for static translations to integrate with MPLS VPNs.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip nat inside source {static {esp local-ip interface type number | local-ip global-ip}} [extendable | mapping-id map-id | no-alias | no-payload | redundancy group-name | route-map | vrf name]
4.
Repeat Step 3 for each VPN being configured.
5.
ip route vrf vrf-name prefix prefix mask next-hop-address global
6.
Repeat Step 5 for each VPN being configured.
7.
exit
8.
show ip nat translations vrf vrf-name
DETAILED STEPS
Configuring Outside Dynamic NAT with MPLS VPNs
Perform this step to configure your NAT PE router for dynamic outside translations to integrate with MPLS VPNs.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip nat pool outside global-ip local-ip netmask netmask
4.
ip nat inside source static local-ip global-ip vrf vrf-name
5.
Repeat Step 4 for each VRF being configured.
6.
ip nat outside source static global-ip local-ip vrf vrf-name
7.
exit
8.
show ip nat translations vrf vrf-name
DETAILED STEPS
Configuring Outside Static NAT with MPLS VPNs
Perform this task to configure your NAT PE router for static outside translations to integrate with MPLS VPNs.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip nat pool inside global-ip local-ip netmask netmask
4.
Repeat Step 3 for each pool being configured.
5.
ip nat inside source list access-list-number pool pool-name vrf vrf-name
6.
Repeat Step 5 for each pool being configured.
7.
ip nat outside source static global-ip local-ip vrf vrf-name
8.
Repeat Step 7 for all VPNs being configured.
9.
exit
10.
show ip nat translations vrf vrf-name
DETAILED STEPS
Configuration Examples for Integrating NAT with MPLS VPNs
This section provides the following configuration examples:
•
Configuring Inside Dynamic NAT with MPLS VPNs: Example
•
Configuring Outside Dynamic NAT with MPLS VPNs: Example
•
Configuring Inside Static NAT with MPLS VPNs: Example
•
Configuring Outside Static NAT with MPLS VPNs: Example
Configuring Inside Dynamic NAT with MPLS VPNs: Example
The following example shows configuring inside Dynamic NAT with MPLS VPNs.
!ip nat pool inside 2.2.2.10 2.2.2.10 netmask 255.255.255.0ip nat inside source list 1 pool inside vrf bank overloadip nat inside source list 1 pool inside vrf park overloadip nat inside source list 1 pool inside vrf shop overload!ip route vrf shop 0.0.0.0 0.0.0.0 Ethernet1/3 168.58.88.2ip route vrf bank 0.0.0.0 0.0.0.0 Ethernet1/3 168.58.88.2ip route vrf park 0.0.0.0 0.0.0.0 Ethernet1/3 168.58.88.2!access-list 1 permit 192.168.0.0 0.0.255.255Configuring Inside Static NAT with MPLS VPNs: Example
The following example shows configuring inside static NAT with MPLS VPNs.
!ip nat inside source static 192.168.121.113 2.2.2.1 vrf shopip nat inside source static 192.168.122.49 2.2.2.2 vrf shopip nat inside source static 192.168.121.113 2.2.2.3 vrf bankip nat inside source static 192.168.22.49 2.2.2.4 vrf bankip nat inside source static 192.168.121.113 2.2.2.5 vrf parkip nat inside source static 192.168.22.49 2.2.2.6 vrf parkip nat inside source static 192.168.11.1 2.2.2.11 vrf shopip nat inside source static 192.168.11.3 2.2.2.12 vrf shopip nat inside source static 140.48.5.20 2.2.2.13 vrf shop!ip route 2.2.2.1 255.255.255.255 Ethernet1/0 192.168.121.113ip route 2.2.2.2 255.255.255.255 Ethernet1/0 192.168.121.113ip route 2.2.2.3 255.255.255.255 Serial2/1.1 192.168.121.113ip route 2.2.2.4 255.255.255.255 Serial2/1.1 192.168.121.113ip route 2.2.2.5 255.255.255.255 FastEthernet0/0 192.168.121.113ip route 2.2.2.6 255.255.255.255 FastEthernet0/0 192.168.121.113ip route 2.2.2.11 255.255.255.255 Ethernet1/0 192.168.121.113ip route 2.2.2.12 255.255.255.255 Ethernet1/0 192.168.121.113ip route 2.2.2.13 255.255.255.255 Ethernet1/0 192.168.121.113Configuring Outside Dynamic NAT with MPLS VPNs: Example
The following example shows configuring outside dynamic NAT with MPLS VPNs.
!ip nat pool outside 4.4.4.1 4.4.4.254 netmask 255.255.255.0ip nat inside source static 192.168.121.113 2.2.2.1 vrf shopip nat inside source static 192.168.122.49 2.2.2.2 vrf shopip nat inside source static 192.168.121.113 2.2.2.3 vrf bankip nat inside source static 192.168.22.49 2.2.2.4 vrf bankip nat inside source static 192.168.121.113 2.2.2.5 vrf parkip nat inside source static 192.168.22.49 2.2.2.6 vrf parkip nat outside source list 1 pool outside!Configuring Outside Static NAT with MPLS VPNs: Example
The following example shows configuring outside static NAT with MPLS VPNs.
!ip default-gateway 10.1.15.1ip nat pool inside1 2.2.1.1 2.2.1.254 netmask 255.255.255.0ip nat pool inside2 2.2.2.1 2.2.2.254 netmask 255.255.255.0ip nat pool inside3 2.2.3.1 2.2.3.254 netmask 255.255.255.0ip nat inside source list 1 pool inside2 vrf bankip nat inside source list 1 pool inside3 vrf parkip nat inside source list 1 pool inside1 vrf shopip nat outside source static 168.58.88.2 4.4.4.1 vrf bankip nat outside source static 18.68.58.1 4.4.4.2 vrf parkip nat outside source static 168.58.88.1 4.4.4.3 vrf shopip classlessip route 192.170.10.0 255.255.255.0 Ethernet1/0 192.168.121.113ip route 192.170.11.0 255.255.255.0 Serial2/1.1 192.168.121.113ip route 192.170.12.0 255.255.255.0 FastEthernet0/0 192.168.121.113ip route vrf shop 0.0.0.0 0.0.0.0 168.58.88.2 globalip route vrf bank 0.0.0.0 0.0.0.0 168.58.88.2 globalip route vrf park 0.0.0.0 0.0.0.0 168.58.88.2 globalno ip http server!access-list 1 permit 192.168.0.0 0.0.255.255Where to Go Next
•
To learn about Network Address Translation and configure NAT for IP address conservation, see the "Configuring NAT for IP Address Conservation" module.
•
To verify, monitor, and maintain NAT, see the "Monitoring and Maintaining NAT" module.
•
To use NAT with application level gateways, see the "Using Application Level Gateways with NAT" module.
•
To configure NAT for high availability, see the "Configuring NAT for High Availability" module.
Additional References
Related Documents
Standards
MIBs
MIBs MIBs Link•
None
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
RFCs
Technical Assistance
Feature Information for Integrating NAT with MPLS VPNs
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Table 1 Feature Information for Integrating NAT with MPLS VPNs
Feature Name Releases Feature Configuration InformationNetwork Address Translation (NAT) Integration with MPLS VPNs feature
12.1(13)T
This feature allows multiple Multiprotocol Label Switching (MPLS) Virtual Private Networks (VPNs) to be configured on a single device to work together.
The following sections provide information about this feature:
•
"Information About Integrating NAT with MPLS VPNs" section
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2007 Cisco Systems, Inc. All rights reserved.

