Skip to main content
All CollectionsProduct InfoMaps
Network Topology Mapping
Network Topology Mapping
Alex Patnick avatar
Written by Alex Patnick
Updated over a week ago

Faddom has the ability to map your physical devices, both routers, and switches. This map is static and it is recommended that when you wish to view it, you rerun the discovery which is done via SNMPv2. To read more about SNMP please see our blog post What is SNMP?

In order for Faddom to fully map the connections, the following MIBs need to be available. If they are not included in your device(s) then the full information cannot be captured,

RFC1213-MIB
IF-MIB
IP-MIB
IP-FORWARD-MIB
BRIDGE-MIB/Q-BRIDGE-MIB


For Cisco devices using SNMPv2 and community string indexing:
CISCO-VTP-MIB

To create the topology map please do the following -

  1. To access the screen go to Maps > Network Topology Map

    1.png
  2. Click on Settings


  3. Enter all the relevant details in the dialogue that appears

    SNMP Credentials

    A pop up will appear asking you to choose SNMPv2 or v3 and ask for the authentication details. By default Faddom will come with SNMPv2 credentials of Public and Priivate.

    SNMPv2



    SNMPv3



    ​SNMP Port - This is the port used for discovery. By default this is the standard SNMP port of 161
    SNMP Timeout - This is the amount of time to wait to receive a response from an SNMP device in seconds. Some devices, especially older ones, can take some time to respond so if you don't see the expected result try a higher timeout value.
    Scan Range - The range of IP addresses to scan for network devices. It is possible to enter a list of IP addresses or subnets in CIDR format (which can be divided by either spaces, commas or semicolons). If not specified, Faddom will use the default gateway defined for the server to start the discovery from
    Ping Scan - When selected, the network discovery will try to scan by pinging each IP address. This should reduce the time required to scan. In networks where ping is not available, this should be disabled
    Search Adjacent Devices - When selected, the network discovery will also attempt to scan devices that are detected to be communicating with each network device. Will increase scan time.
    Edit Schedule - This allows you to set up a daily or weekly scan of the network using the parameters defined
    Proxy - The proxy to use to perform the discovery if you are trying to run this on a remote site or DMZ and Faddom does not have direct access, you can use a Faddom proxy to perform the scan. If you do not have one, you can follow the guide How to Setup the Faddom Proxy


  4. Click on Run Discovery at the bottom

    nwktopology settigns.gif
  5. When the discovery scan has finished, you will get a map that looks similar to the one below

In the map, you can see the following information -

Device Name -this is the name used by the device to identify itself on the network

Numbers -each connection will show the interface number for the connection on each device

IP Address -This is the IP address identified via the scan of the device. Devices may have more than one IP address and you can view the device details..

View Device Details

To view more details on each device you can click left click. You will see details, as below, including the device name, software version, all IPs associated with the device, interfaces in use, and any configured routes.

Statuses

  • Up - The link is working and sending/receiving traffic

  • Down - The link is now working/not detected

  • Not Present - The interface has missing components preventing the detection of the status. Typically this is missing hardware.

Troubleshooting

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

  1. Make sure that the 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. Ensure Faddom is authorized on any ACLs

  5. If you are not seeing all your devices, try a higher timeout value. We recommend between 5 and 10 seconds as some older devices take time to respond.

  6. 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

Did this answer your question?