Guidelines And Limitations For Static Nat - Cisco Nexus 3548 Configuration Manual

Configuring Static and Dynamic NAT Translation

Guidelines and Limitations for Static NAT

Static NAT has the following configuration guidelines and limitations:
• NAT supports up to 1024 translations which include both static and dynamic NAT.
• Cisco Nexus 3500 Series switches do not support static and dynamic NAT on vPC topology.
• The Cisco Nexus device supports NAT on the following interface types:
• NAT is supported for IPv4 Unicast only.
• The Cisco Nexus device does not support the following:
• Egress ACLs are applied to the original packets and not the NAT translated packets.
• By default, NAT can go up to 127 translations with 256 TCAM entries. If you need more NAT translations,
• HSRP and VRRP are supported on NAT inside address and not on NAT outside addresses.
• Warp mode latency performance is not supported on packets coming from the outside to the inside
• If an IP address is used for Static NAT or PAT translations, it cannot be used for any other purpose. For
• For Static NAT, the outside global IP address should be different from the outside interface IP address.
• If the translated IP is part of the outside interface subnet, then use the ip local-proxy-arp command on
• NAT statistics are not available.
• When configuring a large number of translations (more than 100), it is faster to configure the translations
• Only one of the following features can be enabled on an interface at a time. If more than one of these
• Switch Virtual Interfaces (SVIs)
• Routed ports
• Layer 3 port channels
• Application layer translation. Layer 4 and other embedded IPs are not translated, including FTP,
ICMP failures, IPSec, and HTTPs.
• NAT and VLAN Access Control Lists (VACLs) that are configured on an interface at the same
time.
• PAT translation of fragmented IP packets.
• NAT translation on software forwarded packets. For example, packets with IP-options are not NAT
translated.
you need to reduce the TCAM region allocation in other areas and then increase the NAT TCAM region
using the hardware profile tcam region nat command.
domain.
example, it cannot be assigned to an interface.
the NAT outside interface.
before configuring the NAT interfaces.
features is enabled on an interface, only the feature that is enabled last will work:
Cisco Nexus 3548 Switch NX-OS Interfaces Configuration Guide, Release 9x

Guidelines and Limitations for Static NAT

97