Faddom Help Center

Deploying Faddom Network Device Mapping on Windows

Prerequisites

Hardware

  Minimum requirements Recommended requirements
CPU Dual CPU/Dual-core CPU 8 CPUs/cores
Memory (RAM) 4GB RAM 16GB RAM
Disk 10GB free disk space 40GB free disk space

 

Software

To install Faddom on a Windows server, Windows 2012 Server or higher is required.

Everything needed to run Faddom on the server is included and installed by the Windows installer.

 

Permissions

A user with administrative access to the Windows server that you are installing on is required for running of the Windows installer.

 

Firewall Rules

Faddom will need to access your network devices over SNMP so port 161 UDP should be allowed from the Faddom server to your network devices.

Also, in order to allow users to access the UI, port 443 TCP should be opened to the Faddom server.

 

Installation

To install the Faddom server on Window, run the installer. You will just need to accept the license agreement, choose an installation folder, and wait for the installation to complete.

 

Configuration

Login

After installing, you should be able to access the Faddom UI using the IP address of the server.

The user that will initially have administrative access to Faddom is the user that performed the installation. Additional users can be created later from the UI under Settings -> Access Control.

 

License Activation

After logging in, you will need to activate your license. See here for details: Activate Your License

 

Network Device Mapping

After activating your license, you should see the Network Topology mapping screen.

mceclip0.png

Here you should click on Run Network Discovery to access the network mapping configuration. Enter all the relevant community strings for your environment, optionally specify a gateway to start the discovery from, and click on Run Discovery. The map should start to appear as the discovery progresses.

 

Troubleshooting

If you do not see any results in the network map, check the following:

  1. Make sure that the gateway address that is used responds to SNMP requests
  2. Check the firewall rules to make sure that the Faddom server can send SNMP requests to the gateway
  3. Check that the correct community strings are entered
  4. On some devices, the Faddom server needs to be added to a "whitelist" so that they will respond to SNMP requests from it.

For any other questions, please contact us at support@faddom.com

 

Was this article helpful?
0 out of 0 found this helpful

Comments