I cannot enable the Network Topology feature, or see the option to “View Topology” for a Collector Cluster
The Network Topology feature must be included in your subscription.
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:
- “Enable Network Topology feature in cluster configuration“ - you must enable Network Topology for this specific Collector Cluster after clicking the “Features Enabled” option in the cluster menu.
- “Awaiting successful Network Topology detection results“ - Network Topology detection is enabled for this specific cluster, but the map cannot be viewed until detection runs successfully. Normally, you just need to wait until the regular scheduled detection is triggered before this will be present. If the detection has already been triggered and no map is available, this could indicate that detection is unable to run due to an underlying issue. To verify whether detection has run, you can check
Configuration > Audit Logfor the ACTION “Network Topology detection for all activated clusters triggered” by the SYSTEM user.
There are a variety of reasons why a Collector Cluster maybe being ignored by Network Topology detection:
- The cluster must be in the “activated” state (configurable via the “Edit” menu for each cluster within the Clusters tab on the
Configuration > Monitoring Collectorspage)
- The cluster must have active Collectors
- The cluster must be itself enabled for Network Topology (configurable via the “Features Enabled” menu for each cluster within the Clusters tab on the
Configuration > Monitoring Collectorspage)
- The cluster must be monitoring one or more SNMP-enabled hosts (v2c or v3 only)
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
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
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:
- The Opsview Hosts being monitored by a different Collector Cluster.
- Your user may not be authorised for the Host Group containing the Opsview Hosts in question. See Viewing Network Topology for more details. You may need to contact your Opsview Administrator to modify this for you.
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, from Opsview 6.6.7.
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)
This can occur for multiple reasons:
- If the Opsview Hosts in question have been deleted since the Network Topology map was generated, then they will appear with no status information.
- If your User Role has the VIEWALL permission set, but is not authorised to for the Host Group containing the Opsview Hosts in question. See Viewing Network Topology for more details. You may need to contact your Opsview Administrator to modify this for you. Additionally, your User Role may need to have "All Service Groups" ticked in the "Status Objects" tab of the Role permissions configuration.
My Audit Log contains “Network Topology detection was requested, but was already in progress” messages
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 (e.g. "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.
Updated over 1 year ago