Technical data

102 ServerIron ADX NAT64 Configuration Guide
53-1002288-02
Redundancy
6
DRAFT: BROCADE CONFIDENTIAL
• TCS — An ip policy must be defined. Without it, caching will not work.
Enabling IP NAT
When a ServerIron ADX is configured with Switch code, NAT is enabled globally but when it is
configured with Router Code, it is enabled per-interface.
NOTE
ServerIron ADX ADX does not support IP NAT inside and outside on the same physical interface.
Enabling IP NAT globally
The following command enables IP NAT globally.
ServerIronADX(config)# ip nat inside
Syntax: [no] ip nat inside
Enabling IP NAT per-interface
When enabled per-interface, IP NAT must be enabled exclusively “inside” or “outside” on a physical
or virtual interface as shown in the following example.
ServerIronADX(config)# interface ethernet 1/5
ServerIronADX(config-if-e1000-1/5) ip nat inside
Syntax: [no] ip nat [inside | outside]
The inside parameter configures the interface as an IP NAT inside interface.
The outside parameter configures the interface as an IP NAT outside interface.
Enabling static NAT redundancy
To enable static NAT redundancy, enter the ip nat inside source static command such as the
following.
ServerIronADX(config)# ip nat inside source static 10.10.10.10 63.32.23.1 2
Syntax: ip nat inside source static <ip-addr1> <ip-addr2> <priority-value>
The existing ip nat inside command has been extended to include a <priority-value>, which is used
to determine the owner of the NAT IP address.
The <priority-value> can be 1 or 2. 2 is the higher priority, and will be the owner of the NAT IP as
long as the system is up.
Enabling dynamic NAT redundancy
To enable dynamic NAT redundancy, enter commands such as the following.
ServerIronADX(config)# ip nat pool foo 63.23.1.2 63.23.1.4 prefix 24
ServerIronADX(config)# ip nat pool foo port-pool-range 2
Syntax: ip nat pool <pool-name> port-pool-range <priority-value>