The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Performance Routing (PfR) introduced support for the control of traffic class routing using static routing in networks using NAT with the introduction of a new keyword to an existing NAT command. When PfR and NAT functionality are configured on the same router and PfR controls the routing for a traffic class using static routing, some applications may fail to operate due to dropped packets. This dropping of packets behavior is seen when static routing is used to connect to multiple ISPs from the same router, PfR uses static routing to control the traffic class routing, and one or more of the ISPs use Unicast Reverse Path Forwarding (Unicast RPF) filtering for security reasons. The Cisco IOS XE implementation of the PfR support for NAT is explained.
When the new keyword is configured, new NAT translations are given the source IP address of the interface that PfR has selected for the packet and PfR forces existing flows to be routed through the interface for which the NAT translation was created.
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 Performance Routing with NAT" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
•Prerequisites for Performance Routing with NAT
•Restrictions for Performance Routing with NAT
•Information About Performance Routing with NAT
•How to Configure Performance Routing with NAT
•Configuration Examples for Performance Routing with NAT
•Feature Information for Performance Routing with NAT
The Cisco ASR 1000 series aggregation services routers being used as PfR border routers must be running Cisco IOS XE Release 2.6.1, or a later release.
•On Cisco ASR 1000 Series Aggregation Services Routers running Cisco IOS XE Release 2.6.1, and later releases, the ability of PfR to control traffic class routing using static routing in networks using NAT does not support tunnels interfaces or DMVPN implementations.
•In Cisco IOS XE Release 2.6.1 support for using a Cisco ASR 1000 series router as a PfR border router was introduced. Only border router functionality is included in the Cisco IOS Release Cisco IOS XE Release 2.6.1 images; no master controller configuration is available. The master controller that communicates with the Cisco ASR 1000 series router being used as a border router must be a router running Cisco IOS Release 15.0(1)M, or a later 15.0M release.
To configure PfR with NAT, you should understand the following concepts:
•Network Address Translation (NAT)
•Inside Global Addresses Overloading
When PfR and NAT functionality are configured on the same router and PfR controls the routing for a traffic class using static routing, some applications may fail to operate due to dropped packets. This dropping of packets behavior is seen when static routing is used to connect to multiple ISPs from the same router, PfR uses static routing to control the traffic class routing, and one or more of the ISPs use Unicast Reverse Path Forwarding (Unicast RPF) filtering for security reasons. Packets are dropped at the ingress router performing Unicast RPF because PfR changes the route for an outgoing packet for a traffic class from one exit interface to another after the NAT translation from a private IP address to a public IP address is performed. When the packet is transmitted, Unicast RPF filtering at the ingress router (for example, an ISP router) will show a different source IP address from the source IP address pool assigned by NAT, and the packet is dropped. For example, Figure 1 shows how PfR works with NAT.
Figure 1 PfR with NAT
The NAT translation occurs at the router that is connected to the internal network, and this router can be a border router or a combined master controller and border router. If PfR changes routes to optimize traffic class performance and to perform load balancing, traffic from the border router in Figure 1 that was routed through the interface to ISP1 may be rerouted through the interface to ISP2 after the traffic performance is measured and policy thresholds are applied. The RPF check occurs at the ISP routers and any packets that are now routed through ISP2 will fail the RPF check at the ingress router for ISP2 because the IP address of the source interface has changed.
Note Only border router functionality is included in Cisco IOS XE Release 2.6.1 images; no master controller configuration is available. The master controller that communicates with the Cisco ASR 1000 series router being used as a border router must be a router running Cisco IOS Release 15.0(1)M, or a later 15.0M release. In Figure 1 the router is a border router, not a combined master controller and border router.
The solution involves a minimal configuration change with a new keyword, oer, that has been added to the ip nat inside source command. When the oer keyword is configured, new NAT translations are given the source IP address of the interface that PfR has selected for the packet and PfR forces existing flows to be routed through the interface for which the NAT translation was created. For example, PfR is configured to manage traffic on a border router with two interfaces, InterfaceA to ISP1 and InterfaceB to ISP2 in Figure 1. PfR is first configured to control a traffic class representing Web traffic and the NAT translation for this traffic already exists with the source IP address in the packets set to InterfaceA. PfR measures the traffic performance and determines that InterfaceB is currently the best exit for traffic flows, but PfR does not change the existing flow. When PfR is then configured to learn and measure a traffic class representing e-mail traffic, and the e-mail traffic starts, the NAT translation is done for InterfaceB. The PfR static routing NAT solution is a single box solution and configurations with interfaces on multiple routers using NAT and managed by PfR are not supported. Network configurations using NAT and devices such as PIX firewalls that do not run Cisco IOS XE software are not supported.
For details about configuring the PfR static routing NAT solution, see the "Configuring PfR to Control Traffic with Static Routing in Networks Using NAT" section.
NAT enables private IP internetworks that use nonregistered IP addresses to connect to the Internet. NAT operates on a router, usually connecting two networks together, and translates the private (not globally unique) address in the internal network into legal addresses before packets are forwarded onto another network. NAT can be configured to advertise only one address for the entire network to the outside world. This ability provides additional security, effectively hiding the entire internal network behind that one address.
NAT is also used at the Enterprise edge to allow internal users access to the Internet and to allow Internet access to internal devices such as mail servers.
For more details about NAT, see the "Configuring NAT for IP Address Conservation" chapter of the Cisco IOS IP Addressing Services Configuration Guide.
You can conserve addresses in the inside global address pool by allowing the router to use one global address for many local addresses. When this overloading is configured, the router maintains enough information from higher-level protocols (for example, TCP or UDP port numbers) to translate the global address back to the correct local address. When multiple local addresses map to one global address, the TCP or UDP port numbers of each inside host distinguish between the local addresses.
This section contains the following tasks:
•Configuring PfR to Control Traffic with Static Routing in Networks Using NAT
Perform this task to allow PfR to control traffic with static routing in a network using NAT. This task allows PfR to optimize traffic classes while permitting your internal users access to the internet.
When Cisco IOS PfR and NAT functionality are configured on the same router and PfR controls the routing for a traffic class using static routing, some applications may fail to operate due to dropped packets. This dropping of packets behavior is seen when static routing is used to connect to multiple ISPs from the same router, PfR uses static routing to control the traffic class routing, and one or more of the ISPs use Unicast Reverse Path Forwarding (Unicast RPF) filtering for security reasons.
In this task, the oer keyword is used with the ip nat inside source command. When the oer keyword is configured, new NAT translations are given the source IP address of the interface that PfR has selected for the packet and PfR forces existing flows to be routed through the interface where the NAT translation was created. This task uses a single IP address but an IP address pool can also be configured. For a configuration example using an IP address pool, see "Configuring PfR to Control Traffic with Static Routing in Networks Using NAT" section.
Note This configuration is performed on a master controller. Only border router functionality is included in Cisco IOS XE Release 2.6.1 images; no master controller configuration is available. The master controller that communicates with the Cisco ASR 1000 series router being used as a border router must be a router running Cisco IOS Release 15.0(1)M, or a later 15.0M release.
Note The PfR static routing NAT solution is a single box solution and configurations with interfaces on multiple routers using NAT and managed by PfR are not supported.
For more details about configuring NAT, see the "Configuring NAT for IP Address Conservation" chapter of the Cisco IOS IP Addressing Services Configuration Guide.
1. enable
2. configure terminal
3. access-list access-list-number {permit | deny} ip-address mask
4. route-map map-tag [permit | deny] [sequence-number]
5. match ip address {access-list access-list-number | prefix-list prefix-list-name}
6. match interface interface-type interface-number [...interface-type interface-number]
7. exit
8. Repeat Step 4 through Step 7 for more route map configurations, as required.
9. ip nat inside source {list {access-list-number | access-list-name} | route-map map-name} {interface type number | pool name} [mapping-id map-id | overload | reversible | vrf vrf-name] [oer]
10. interface type number
11. ip address ip-address mask
12. ip nat inside
13. exit
14. interface type number
15. ip address ip-address mask
16. ip nat outside
17. end
|
|
|
---|---|---|
Step 1 |
enable Router> enable |
Enables privileged EXEC mode. •Enter your password if prompted. |
Step 2 |
configure terminal Router# configure terminal |
Enters global configuration mode. |
Step 3 |
access-list access-list-number {permit | deny} ip-address mask Router(config)# access-list 1 permit 10.1.0.0 0.0.255.255 |
Defines a standard access list permitting the IP addresses that are to be translated. •The access list must permit only those addresses that are to be translated. (Remember that there is an implicit "deny all" at the end of each access list.) An access list that is too permissive can lead to unpredictable results. |
Step 4 |
route-map map-tag [permit | deny] [sequence-number] Router(config)# route-map isp-1 permit 10 |
Enters route-map configuration mode to configure a route map. •The example creates a route map named BGP. |
Step 5 |
match ip address {access-list access-list-name | prefix-list prefix-list-name} Router(config-route-map)# match ip address access-list 1 |
Creates an access list or prefix list match clause entry in a route map to identify traffic to be translated by NAT. •The example references the access list created in Step 3 that specifies the 10.1.0.0 0.0.255.255. prefix as match criteria. |
Step 6 |
match interface interface-type interface-number [...interface-type interface-number] Router(config-route-map)# match interface serial 1/0 |
Creates a match clause in a route map to distribute any routes that match out one of the interfaces specified. •The example creates a match clause to distribute routes that pass the match clause in Step 5 through serial interface 1/0. |
Step 7 |
exit Router(config-route-map)# exit |
Exits route-map configuration mode and returns to global configuration mode. |
Step 8 |
Repeat Step 4 through Step 7 for more route map configurations, as required. |
— |
Step 9 |
ip nat inside source {list {access-list-number | access-list-name} | route-map map-name} {interface type number | pool name} [mapping-id map-id | overload | reversible | vrf vrf-name] [oer] Router(config)# ip nat inside source interface GigabitEthernet 1/0/0 overload oer |
Establishes dynamic source translation with overloading, specifying the interface. •Use the interface keyword and type and number arguments to specify an interface. •Use the oer keyword to allow PfR to operate with NAT and control traffic class routing using static routing. |
Step 10 |
interface type number Router(config)# interface GigabitEthernet 1/0/0 |
Specifies an interface and enters interface configuration mode. |
Step 11 |
ip address ip-address mask Router(config-if)# ip address 10.114.11.8 255.255.255.0 |
Sets a primary IP address for the interface. |
Step 12 |
ip nat inside Router(config-if)# ip nat inside |
Marks the interface as connected to the inside. |
Step 13 |
exit Router(config-if)# exit |
Exits interface configuration mode and returns to configuration mode. |
Step 14 |
interface type number Router(config)# interface GigabitEthernet 1/1/0 |
Specifies a different interface and returns to interface configuration mode. |
Step 15 |
ip address ip-address mask Router(config-if)# ip address 172.17.233.208 255.255.255.0 |
Sets a primary IP address for the interface. |
Step 16 |
ip nat outside Router(config-if)# ip nat outside |
Marks the interface as connected to the outside. |
Step 17 |
end Router(config-if)# end |
Exits interface configuration mode and returns to privileged EXEC mode. |
The following example in this section shows a sample PfR link group configuration:
•Configuring PfR to Control Traffic with Static Routing in Networks Using NAT: Example
The following configuration example configures a master controller to allow PfR to control traffic with static routing in a network using NAT. This example shows how to use a pool of IP addresses for the NAT translation.
Note This configuration is performed on a master controller. Only border router functionality is included in Cisco IOS XE Release 2.6.1 images; no master controller configuration is available. The master controller that communicates with the Cisco ASR 1000 series router being used as a border router must be a router running Cisco IOS Release 15.0(1)M, or a later 15.0M release.
In this example, a border router is connected to the Internet through two different ISPs. The configuration below allows PfR to optimize traffic classes while permitting the internal users access to the internet. In this example the traffic classes to be translated using NAT are specified using an access list and a route map. The use of a pool of IP addresses for NAT translation is then configured and the oer keyword is added to the ip nat inside source command to configure PfR to keep existing traffic classes flowing through the interface that is the source address that was translated by NAT. New NAT translations can be given the IP address of the interface that PfR has selected for the packet.
Note The PfR static routing NAT solution is a single box solution and configurations with interfaces on multiple routers using NAT and managed by PfR are not supported.
Router(config)# access-list 1 permit 10.1.0.0 0.0.255.255
Router(config)# route-map isp-2 permit 10BGP permit 10
Router(config-route-map)# match ip address access-list 1
Router(config-route-map)# match interface serial 2/0
Router(config-route-map)# exit
Router(config)# ip nat pool ISP2 209.165.201.1 209.165.201.30 prefix-length 27
Router(config)# ip nat inside source route-map isp-2 pool ISP2 oer
Router(config)# interface GigabitEthernet 0/0/0
Router(config-if)# ip address 10.1.11.8 255.255.255.0
Router(config-if)# ip nat inside
Router(config-if)# exit
Router(config)# interface serial 1/0
Router(config-if)# ip address 192.168.3.1 255.255.255.0
Router(config-if)# ip nat outside
Router(config-if)# exit
Router(config)# interface serial 2/0
Router(config-if)# ip address 172.17.233.208 255.255.255.0
Router(config-if)# ip nat outside
Router(config-if)# end
For information about other Performance Routing features or general conceptual material, see the documents in the "Related Documents" section.
The following sections provide references related to the Performance Routing with NAT feature.
|
|
---|---|
Cisco IOS commands |
|
Cisco OER commands: complete command syntax, command mode, command history, defaults, usage guidelines and examples |
|
Basic PfR configuration in Cisco IOS XE releases |
|
Information and configuration for the border router only functionality for Cisco IOS XE releases |
"Performance Routing Border Router Only Functionality" module |
Advanced PfR configuration |
|
Concepts required to understand the Performance Routing operational phases |
|
Location of PfR features in Cisco IOS XE releases |
|
General information about NAT |
Table 1 lists the release history for this feature.
For information on a feature in this technology that is not documented here, see the "Cisco IOS XE Performance Routing Features Roadmap"
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE 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 Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
|
|
|
---|---|---|
Support for NAT and Static Routing1 |
Cisco IOS XE |
Support to allow PfR to control traffic class routing using static routing in networks using NAT. This feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. The following command was modified by this feature: ip nat inside source. |
1 This is a minor enhancement. Minor enhancements are not typically listed in Feature Navigator. |