Microsoft.SystemCenter.NetworkDevice.Custom
6.0.6278.0
Microsoft.SystemCenter.NetworkDevice.Custom
Microsoft.SystemCenter.NetworkDevice.Library
6.0.6278.0
31bf3856ad364e35
System.Health.Library
6.0.6278.0
31bf3856ad364e35
AvailabilityHealth
Error
true
Normal
MatchMonitorHealth
$Target/Property[Type="NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice"]/Name$
$Target/Property[Type="NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice"]/IPAddress$
120
false
$Target/Property[Type="NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice"]/IPAddress$
$Target/Property[Type="NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice"]/CommunityString$
$Target/Property[Type="NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice"]/Version$
.1.3.6.1.2.1.1.5.0
1
false
Network Device Customs
Microsoft System Center Network Device Customs: This Management Pack contains the definitions for custom monitoring that apply to Network Devices.
Device Status Check (Custom)
This monitor checks the state of a device.
Network device is down
Network device with name {0} and IP Address {1} is down.
Summary
The device currently being monitored is not responding to an SNMP GET for the System Name of the device.
Causes
This monitor is configured to get the System Name for this device is null. Below are the details of the Object Identifier (OID) that is queried via an SNMP GET
Symbolic Name
OID
Description
iso.org.dod.internet.mgmt.mib-2.system.sysName
.1.3.6.1.2.1.1.5.0
An administratively-assigned name for this managed node. By convention, this is the node's fully-qualified domain name.
This is defined in
RFC 1213
This can happen when:
The device is offline
The device is not responding to SNMP GET
The community string has changed and this Monitor has not been updated
Resolutions
Below are some basic troubleshooting steps to determine if the device is online
Ping the target device. If the device is not pingable, the device may be offline or there may be a firewall blocking ICMP communication.
If pinging the device was successful, try to ensure you have the correct community string for the device. You will have to contact the Network Administrator for the community string for this device.