There are a number of reasons why a topology map might not look right.
- SNMP is missing
- Devices aren’t appearing on the map
- Devices have incorrect connections
- Devices aren’t classified correctly
- Networks are missing
- WMI isn’t enabled
- VMware credentials are missing
- Auvik isn’t authorized to log into devices
- Cisco ASA is shunning the collector
- Dynamic IP is causing fluctuations in the data
This is what a good Auvik map looks like
This map has a mix of blue and black wires, which indicates Auvik is successfully reading data for Layers 1, 2, and 3. If you have managed Wi-Fi controllers and access points, you may also see dotted wires between APs and endpoints. The correct symbol is showing for most devices—a firewall is represented by flames, for example. And the map reflects the true shape of the network design.
This is a map with problems
This map has a lot of black wires. The network looks flat, fragmented, and incomplete.
Check SNMP status
Auvik relies on SNMP to gather data from key devices on your network, such as routers, firewalls, switches, and Wi-Fi infrastructure. If a device doesn’t have SNMP enabled or the credentials aren’t entered correctly in Auvik, the map might not render correctly.
Go to Discovery > Manage Devices in Auvik’s side navigation bar to see a list of devices and their current SNMP status.
How to enable SNMP
You’ll find many articles in the Auvik knowledge base to walk you through enabling SNMP on popular devices like Cisco, Juniper, and Dell. If your device isn’t on the list, search online for SNMP enablement instructions from the vendor or contact Auvik support.
If SNMP is enabled, then make sure you’ve correctly added the SNMP credentials in Auvik.
How to test whether SNMP is working
To test if SNMP works, you can use the Auvik collector to try an SNMPwalk on the device. This will tell you if SNMP is configured correctly and accepting SNMP queries from the Auvik collector. Please follow How do I debug using the Auvik collector to test if SNMP is working correctly.
Devices aren’t appearing on the map
Auvik uses ping (ICMP) to discover devices on your network. If a firewall or a router is blocking ICMP packets on a device, Auvik won’t be able to discover that device. To solve this issue, whitelist the Auvik collector’s IP address on your firewalls and routers.
To troubleshoot devices that aren’t appearing on the map, you can use the Auvik collector to perform a scan on a specified network. Devices that appear in the scan results should appear on the map.
If your device doesn’t reply, it may be in stealth mode and blocking pings (ICMP packets) from the Auvik collector. If so, add a policy to allow pings by the Auvik collector.
Devices have incorrect connections
Using the data collected through SNMP, Auvik tries to discover what each interface on a device connects to. Auvik also uses CDP and LLDP to determine connections. CDP (Cisco Discovery Protocol) and LLDP (Link Layer Discovery Protocol) are protocols that switches use to advertise their identities, capabilities, and neighbors.
If Auvik has mapped connections incorrectly, first ensure that CDP or LLDP is enabled on your switches. Most devices have the protocols enabled by default, but it’s always good to check.
You can link an IP to a specific device to help resolve mapping issues.
If enabling CDP or LLDP doesn’t correct the connection, you can manually change connections by editing the interface details.
Devices aren’t correctly classified
Auvik automatically classifies devices as they’re discovered. Auvik supports more than 7,300 devices from over 230 vendors. Still, there are times we encounter devices that aren’t on our list, which means we don’t have an object identifier record for that device.
If we do support the device, but it’s still classified incorrectly, you can manually reclassify it by editing the device details.
Networks are missing
Auvik discovers networks automatically and asks for permission to scan those discovered networks. Check to make sure that all networks you want scanned have been granted scanning permission.
WMI isn’t enabled
For Windows workstations and servers, Auvik uses >Windows Management Instrumentation (WMI) to gather information such as device bandwidth, interface information, uptime, and much more. Enabling WMI helps Auvik to determine where workstations are connected, which improves map accuracy.
There are two ways to enable WMI.
- If you’re using a domain controller, create a group policy to enable WMI on all workstations connected to your domain.
- Enable WMI on a single workstation.
Once you’ve enabled WMI and verified that it’s working properly, add the WMI credentials in Auvik.
VMware credentials are missing
Auvik can monitor your VMware ESXi hypervisor and the virtual machines being hosted. Auvik currently supports ESXi 5.0+.
For Auvik to properly manage your hypervisor and virtual machines, your ESXi host needs to be classified as a hypervisor. There are two ways you can accomplish this.
- Enable SNMP and add the proper VMware credentials into Auvik. Once SNMP is enabled, Auvik classifies the ESXi host as a hypervisor and the VMware credentials are used to authenticate.
- Manually classify the ESXi host as a hypervisor. See How to edit device details for more information.
Installing VMware Tools on your virtual machines also helps Auvik properly map your virtual machines.
Auvik isn’t authorized to log into devices
In addition to SNMP, Auvik uses SSH and Telnet to gather information on your network devices. (Some devices don’t give out enough information through SNMP so Auvik relies on SSH and Telnet to learn more.) Devices that are missing login credentials may not show up correctly on a network map.
If SSH or Telnet is already enabled, you may have to permit the Auvik collector to log into the device. Once you’ve verified that the Auvik collector is permitted to login, add the login credentials to Auvik.
If you can’t find your map issue on this list, or your map is still not displaying correctly after trying these fixes, contact Auvik support for further help.
Cisco ASA shunning the Auvik collector
If your Auvik collector is intermittently disconnecting from our servers or losing Internet connectivity altogether and you have a Cisco ASA on your network’s perimeter, the ASA may be >shunning> the Auvik collector as a result of aggressive threat detection. To stop the ASA from shunning the Auvik collector, see Known issue with Cisco ASA shunning Auvik collector.
Dynamic IP is causing fluctuations in the data
If the map is exhibiting odd behavior, redrawing itself, or displaying corrupted data, the Auvik collector may be getting its IP address using DHCP. To keep the data Auvik collects as consistent as possible, assign the virtual appliance a static IP or create a DHCP reservation.
Where to find more help
Didn’t find the answer you were looking for? Chat with us (see the window on the bottom right of your screen) or submit a support ticket for more help.