Why is my network device or agentless server monitor classified incorrectly?
Topics covered in this doc:
How are devices classified?
Why is the device classified incorrectly and how do I fix it?
How are devices classified?
When a device is scheduled for discovery using an SNMP credential, we obtain the device identifier of the device or server and map it to the device identifier present in the generic or custom device template. If there is a match, the device is associated with the matching device template. If there isn't a match, the device is associated with a default template. The default template for a network device is a Custom SNMP Device, and for an agentless server, it's a Custom Server.
A device template can have multiple device identifiers, but the same device identifier cannot be used for different templates, i.e., the device identifiers must be unique.Why is the device classified incorrectly and how do I fix it?
When the identifier of the device being discovered is present in a different device template, then the device will be classified incorrectly. Let's consider the below two scenarios:
- A network device is classified as an agentless server.
A network device could be incorrectly classified as a Linux agentless server if the network device vendor uses the same SNMP agent as that of Linux (net-SNMP). This means the device will have the same device identifier as the Linux server.
To fix this, delete the agentless server monitor that was added and add the network device by specifying the correct device template during network discovery. Ensure that the device category and template names are correct.
- A network device is classified as a different type.
Consider a Cisco 3100 that is incorrectly associated with a Cisco 2600 template. You can fix this by re-associating the device to the Cisco 3100 template. To fix this permanently, you need to:
1. Edit the Cisco 2600 template and remove the device identifier that matches the device. Click Save.
2. Edit the Cisco 3100 template and add the device identifier to this template. Click Save.
This ensures that the new devices with the same device identifier are associated with the Cisco 3100 template during discovery.
Related Articles
How to set up alerts for network device data collection issues
When your network monitoring interfaces are not collecting data due to issues in the Network Module, you'll want to be alerted. To set up alerts, you need to add or edit the threshold and availability profile of the On-Premise Poller, which is used ...Troubleshooting false positive alerts in monitoring
Problem False positive alerts are being generated. Possible cause The monitoring system is down in some locations. The Website monitor might be configured for one location, such as Seattle, but may appear down when accessed from another location, ...Monitors that require On-Premise Pollers in Site24x7
Certain monitor types in Site24x7 require the use of On-Premise Pollers for data collection, especially when monitoring internal, firewall-restricted, or private resources. Depending on the type of monitoring, additional modules like the Network ...Amendments to Site24x7 Monitor Names
We've recently renamed a few of our Monitors to help keep in sync with the current IT and DevOps trends. The new monitor names are designed to correctly resonate with the IT & DevOps crowd. We've made necessary changes in the Web client, Help ...How to uninstall the Site24x7 Windows Server Monitoring Agent
Method 1: To uninstall the Site24x7 Windows Server Monitoring Agent, click the link below: https://staticdownloads.site24x7.com/server/Site24x7WindowsAgentUninstall.zip Unzip and execute the Uninstall.bat file in the Command Prompt as an ...