Deploy the AutoDiscovery server
This topic explains how to deploy the AutoDiscovery server and move it between the Central Manager or a dedicated AutoDiscovery Remote Agent.
AutoDiscovery is typically installed on the Central Manager for a PoC environment; for a production environment, on a dedicated AutoDiscovery Remote Agent.
Note: When AutoDiscovery server is deployed on a dedicated AutoDiscovery Remote Agent in ASMS, the AutoDiscovery Remote Agent does not monitor devices.
Deploy the AutoDiscovery server on a Remote Agent
You can deploy the AutoDiscovery server on a new or repurposed Remote Agent.
Do the following:
-
Make sure the AutoDiscovery Remote Agent complies with the system requirements. For details, see AutoDiscovery server system requirements.
-
Both the CM and the machine that will be used as the AutoDiscovery Remote Agent must have the same build number installed.
If the Central Manager is not updated to the latest A32.10 build, update it now.Install the latest build A32.10 on the AutoDiscovery Remote Agent machine.
-
On the Central Manager, go to the algosec_conf menu, and select option 14 - Product configuration. Enter option 2 - AutoDiscovery configuration and then enter option 2 - Configure AutoDiscovery on Remote Agent.
- Enter the IP of the Remote Agent hosting the AutoDiscovery server. AutoDiscovery is installed on the Remote Agent.
-
Direct the NetFlow output to the IP address of the Remote Agent. We recommend you use port 2055.
- Connect to remote sensors, if any. See Define remote network sensors and subnets.
- Configure load balancers, if any. See Configure Load Balancers.
Deploy the AutoDiscovery server on the Central Manager
Do the following:
-
On the Central Manager, go to the algosec_conf menu, and select option 14 - Product configuration. Enter option 2 - AutoDiscovery configuration and then enter option 1 - Configure AutoDiscovery on local machine (POC). AutoDiscovery is installed on the Central Manager.
-
Direct the NetFlow output to the IP address of the Central Manager ( do not use 'localhost').
We recommend you use port 2055. - Connect to remote sensors, if any. See Define remote network sensors and subnets.
- Configure load balancers, if any. See Configure Load Balancers.
Move the AutoDiscovery server from the Central Manager to a Remote Agent
You can deploy the AutoDiscovery server on a new or repurposed Remote Agent. If your AutoDiscovery server is installed on the Central Manager, you can move the server to a dedicated AutoDiscovery Remote Agent as follows:
Do the following:
-
Make sure the AutoDiscovery Remote Agent complies with the system requirements. For details, see AutoDiscovery server system requirements.
-
If the Central Manager is not updated to the latest build, update it now.
Install the latest build A32.10 on the Remote Agent.
-
On the Central Manager, go to the algosec_conf menu, and select option 14 - Product configuration. Enter option 2 - AutoDiscovery configuration and then enter option 1 - Move AutoDiscovery from local Machine (Central Manager) to Remote Agent.
- Enter the IP of the Remote Agent hosting the AutoDiscovery server.
- Enter the password for user afa on the Remote Agent. The AutoDiscovery server (with local sensor) are moved to the AutoDiscovery Remote Agent.
-
Direct the NetFlow output to the new IP address of the AutoDiscovery machine. We recommend you use port 2055.
Move the AutoDiscovery server from the Remote Agent to the Central Manager
If your AutoDiscovery server is installed on a dedicated AutoDiscovery Remote Agent, you can move the server to the Central Manager as follows:
Do the following:
-
On the Central Manager, go to the algosec_conf menu, and select option 14 - Product configuration. Enter option 2 - AutoDiscovery configuration and then enter option 1 - Move AutoDiscovery from Remote Agent to local Machine (Central Manager).
- Enter the password for user afa on the Central Manager. The AutoDiscovery server (with local sensor) are moved to the Central Manager.
-
Direct the NetFlow output to the IP address of the Central Manager. We recommend you use port 2055.