Network Topology

I cannot enable the Network Topology feature, or see the option to View Topology Copied

The Network Topology feature must be included in your subscription.

I cannot “View Topology” for a particular Collector Cluster Copied

There are two possible tooltips you might see if the “View Topology” button on the cluster menu is greyed out and cannot be interacted with:

Network Topology detection is running, but some Collector Clusters are being ignored Copied

There are a variety of reasons why a Collector Cluster maybe being ignored by Network Topology detection:

I can access the “View Topology” page for a Collector Cluster, but see “No Results found” displayed Copied

Your user may not be authorised to view the map. See Viewing Network Topology for more details. You may need to contact your Opsview Administrator to modify this for you.

I can access the “View Topology” page for a Collector Cluster, but see “No nodes detected” displayed Copied

Network Topology detection requires that you have set up one or more SNMP-enabled Hosts (v2c or v3 only) monitored by a Collector Cluster before you can build up a map of the network for that cluster. If there are no nodes detected, there may have been an error connecting to the SNMP-enabled Hosts on the cluster.

I can see a Network Topology map for my Collector Cluster, but some Opsview Hosts are not appearing where expected Copied

If you know that an Opsview Host is configured with an IP address, but it does not appear linked to the node for that IP address in the Network Topology map, it could be due to:

I can see a Network Topology map for my Collector Cluster, but some Opsview Hosts are missing Copied

Opsview Hosts monitored by a Collector Cluster will only be visible on the map if they are SNMP-enabled (v2c or v3 only) and the SNMP credentials are correct, or if they are a neighboring connection of an SNMP-enabled host. The ‘aes256’ and ‘aes256c’ SNMPv3 privacy protocols are not currently supported.

I can see a Network Topology map for my Collector Cluster, but some known devices are missing Copied

Network Topology detection relies on the LLDP or CDP protocols. At least one of these protocols must be enabled on network devices before they can be picked up as connections and displayed on the Network Topology map.

I can see a Network Topology map for my Collector Cluster, but some Opsview Hosts have no status (purple pills) Copied

This can occur for multiple reasons:

My Audit Log contains “Network Topology detection was requested, but was already in progress” messages Copied

These messages will be logged when a new detection is requested, but detection is already running. This could occur if a user manually triggers detection while one is in progress. If you see this message regularly then it is possible that your detection schedule is configured to run too often, and you should decrease the detection frequency.

My Map page displays incorrect translations Copied

For example, NETWORK_TOPOLOGY.CLUSTER_TITLE rather than the actual Collector Cluster details.

In Chrome, this issue can occur due to language preference ordering. Ensure that “English (United States)” has a higher preference than “English” in your Chrome settings.

["Opsview On-premises"] ["User Guide", "Troubleshooting"]

Was this topic helpful?