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
Troubleshooting steps if a device is not being added or the monitor shows Discovery in progress for more than five minutes
If a device is not being added: Check if the On-Premise Poller and the Network module are Up. Learn more. Check whether the device you’re trying to add is reachable from the machine the On-Premise Poller is installed on. Check if the device is ...Device types supported for Network Monitoring
Currently, Site24x7 Network Monitoring supports VPN Firewall Switch Router Load Balancer WAN Wireless UPS Printer Storage Cisco Meraki Switches Cisco Meraki Wireless Devices Cisco Meraki Security Appliances Cisco Meraki Cameras You can also monitor ...Comparison between Site24x7 VMware Monitoring and VM monitoring using Site24x7 server agent
Site24x7 VMware Monitoring capabilities Site24x7 VMware monitoring is agentless. An On-Premise Poller acts as a probe to collect data and sends it to Site24x7. With Site24x7 VMware Monitoring, you will be able to: Monitor vCenter Monitor VMware ...How are the metrics calculated in agentless server monitoring?
SNMP server monitoring Metrics such as CPU, Memory, and Disk utilization are collected via SNMP using the OIDs given below: Attribute OID CPU .1.3.6.1.2.1.25.3.3.1.2 Memory .1.3.6.1.2.1.25.5.1.1.2 Disk .1.3.6.1.2.1.25.2.3.1.6 Free Disk Space (MB) ...Security for Site24x7 Agentless Server Monitoring
How is performance data sent from the user environment to the Site24x7 Data Center? The On-Premise Poller uses a HTTPS connection to send performance data from the user environment to the Site24x7 Data Center. Do I need to whitelist any ...