How to Configure One-to-One Reverse Network Address Translation
Article ID: CTX121919
Updated On:
Description
This article describes how to configure a one-to-one Reverse Network Address Translation (RNAT) for a NetScaler appliance.
Requirements
NetScaler 9.0Pre-existing backend server
Background
A customer requested details on how to configure a one-to-one RNAT. In their scenario, they wanted to have precise control over which server got which address from the backend server and therefore could not use a typical RNAT configuration, which uses a range of addresses for outbound use. Other use cases could be: requirement to access external services that are expecting a specific address or to conform to routing requirements.Instructions
To configure one-to-one RNAT, complete the following procedure:-
Identify the outbound addresses of the servers. This address must conform to the existing network allocation and routing policies, must be owned by the NetScaler appliance, and must be a valid public IP address.
-
Run the following command from the command line interface to enable RNAT when the NAT IP address must be set to a Mapped IP address (MIP):
set rnat <ipaddress> <subnetmask>
Example:
set rnat 192.168.1.1 255.255.255.255
This automatically uses the configured MIP address as the NAT address. -
Run the following command to enable RNAT when the NAT IP address is set to a unique IP address:
Examples:
>set rnat <ipaddress> <subnetmask> -natip <natipaddress>>set rnat 192.168.250.52 255.255.255.255 –natip x.x.x.x
>set rnat 192.168.225.2 255.255.255.255 –natip y.y.y.y3 -
Run the following command to ensure that the one-to-one RNAT is working as expected:
>stat rnatip <natipaddress>Example:
> stat rnatip x.x.x.x
Rnatip x.x.x.x
Rate (/s) Total
Bytes Received 50 2675
Bytes Sent 24 11325
Packets Received 20 342
Packets Sent 45 697
Syn Sent 25 407
Current RNAT sessions 1 5
Done
Issue/Introduction
