RNAT IP Test
With ‘Reverse Network Address Translation’ (RNAT), the ADC replaces the source IP addresses in the packets generated by hosts in the configured subnet with the configured, NAT IP address(es). Typically, RNAT is used to allow servers configured with private non-routable IP addresses to initiate connections to the Internet.
In the event of an overload, the RNAT test will enable you to determine whether/not the RNAT sessions are imposing excessive load on the ADC appliance. If so, then, you can use the RNAT IP test to isolate the client IP address that is generating maximum load.
Target of the test : An ADC VPX/MPX
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each client IP address that initiates RNAT sessions to the ADC appliance being monitored.
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The IP address of the host for which the test is being configured. |
|
NetScaler Username and NetScaler Password |
To monitor a ADC device, the eG agent should be configured with the credentials of a user with read-only privileges to the target ADC device. Specify the credentials of such a user in the NetScaler Username and NetScaler Password text boxes. |
|
Confirm Password |
Confirm the ADC Password by retyping it here. |
|
SSL |
The eG agent collects performance metrics by invoking NITRO (ADC Interface Through Restful interfaces and Objects) APIs on the target ADC device. Typically, the NITRO APIs can be invoked through the HTTP or the HTTPS mode. By default, the eG agent invokes the NITRO APIs using the HTTPS mode. This is why, the SSL flag is set to Yes by default. If the target ADC device is not SSL-enabled, then the NITRO APIs can be accessed through the HTTP mode only. In this case, set the SSL flag to No. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Active sessions |
Indicates the number of current RNAT active sessions originating from this client IP address. |
Number |
This is a good indicator of the RNAT session load generated by a client IP address on the ADC appliance. Compare the value of this measure across IP addresses to identify the client that is generating the maximum session load. |
|
Request for connections sent |
Indicates the number of requests for connections that were sent during the RNAT sessions that originated from this client IP address since the last measurement period. |
Number |
|
|
Data received |
Indicates the number of bytes that were received during RNAT sessions that originated from this client IP address since the last measurement period. |
MB |
These measures are good indicators of the load imposed by RNAT sessions started by a client IP address on the ADC appliance. By comparing the value of these measures across IP addresses, you can quickly and accurately isolate the IP address that is responsible for the maximum data load. |
|
Data transmitted |
Indicates the number of bytes that were transmitted during RNAT sessions that originated from this client IP address since the last measurement period. |
MB |
|
|
Packets received |
Indicates the number of packets that were received during RNAT sessions that originated from this client IP address since the last measurement period. |
Number |
These measures are good indicators of the load imposed by RNAT sessions started by a client IP address on the ADC appliance. By comparing the value of these measures across IP addresses, you can quickly and accurately isolate the IP address that is responsible for the maximum packet load. |
|
Packets transmitted |
Indicates the number of packets that were sent during RNAT sessions that originated from this client IP address since the last measurement period. |
Number |
