Configure a secondary NIC to access ADM agent

March 11, 2024

Contributed by:

R C

You can configure two NICs on an ADM agent. Using the Dual NIC architecture, ADM agent will be able to:

Establish communication between ADM agent and ADC instances - You can use the first NIC to isolate the traffic that is received and sent through the NetScaler ADM and also to communicate between NetScaler ADM and its managed NetScaler instances in another network.
Establish communication between ADM agent and NetScaler ADM - You can use the second NIC to manage the NetScaler ADM that is on a network and perform administrative tasks

Note

You cannot interchange the functionality and configuration of both the NICs.

Block Diagram of Dual NIC Infrastructure

In this scenario, as an administrator, you can:

Configure IP address for the traffic between NetScaler ADM and its managed NetScaler instances.
Configure IP address for managing the NetScaler ADM software to perform all administrative tasks in the software.

Note

It is not mandatory to configure Dual NICs for an ADM agent. It is optional and is required only when traffic between ADM agent, NetScaler ADM and ADCs needs to be separated.

Modify the IPV4 NIC network addresses using CLI

Open an SSHconnection to the NetScaler agent console by using an SSH client, such as PuTTY.
Log in using the nsrecover/nsroot credentials and switch to the shell prompt.
Run the command ifconfig. You can see the details of the two NICs that you have configured -
- NIC 1 – For communication between ADM Agent to ADC Communication
- NIC 2 – For communication between ADM Agent to NetScaler ADM
Run the command networkconfig. A menu appears which allows you to set or modify the IPV4 network addresses.

Note

Second NIC Network address can take multiple IP values.
Select a menu item to modify. Save and quit the settings.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Configure a secondary NIC to access ADM agent

March 11, 2024

Contributed by:

R C

March 11, 2024

Contributed by:

R C

Configure a secondary NIC to access ADM agent

Modify the IPV4 NIC network addresses using CLI

In this article