Is an error stopping you from adding new devices to OpManager? Here is a list of error messages and the corresponding reasons on why a particular error is triggered and solutions on how to resolve them.
Cause
When the device you are trying to add is not reachable from the OpManager server, this error is displayed. This error is triggered when you are attempting to add a device using its device name.
Solution
OpManager searches for the device using its device name. This error can be fixed by avoiding typos in the device name.
Note: When adding the device using its IP address, the device gets added even though it is not reachable, but the device status is classified as 'Device not Monitored'. OpManager periodically pings the device for availability and the status is updating accordingly.
Cause
This error is caused by one of the following reasons
Solution
Cause
This error is displayed when the network IP and device IP are the same.
Solution
Network IP turns out invalid when the IP that is standard to a network (.0) is configured for a device. Check for typos and make sure the correct value is entered. If the network IP is not configured for your network, enable the 'ADD_DEVICE_IP_ENDING_0' property as 'TRUE' in the discovery.properties file from the directory <OpManagerHome>\conf\OpManager and restart the service to use this IP (.0).
Also ensure that the device IP doesn't match the Network IP when it is fetched automatically.
Cause
This error is displayed when the broadcast IP and device IP are the same.
Solution
OpManager will not allow device addition, if the standard broadcast IP (ending with .255) is configured for a device. Proceed with device discovery once you confirm that the device IP and the broadcast IP is not identical. If the broadcast IP is not configured for your network, enable the 'ADD_DEVICE_IP_ENDING_255' property as 'TRUE' in the discovery.properties file from the directory <OpManagerHome>\conf\OpManager and restart the service to use this IP (.255).
Cause
Your device has run out of licensed devices that can be monitored. Here, {n} indicates the number of device that has exceeded the licensing limit.
Solution
Delete/Unmanage unwanted devices to make room for the new ones or purchase a license that can accommodate more devices.
Cause
This error is exclusive to SNMP devices. This error is triggered even though the device you are attempting to add is reachable from the OpManager server. This is because the Sysname turns up empty when trying to fetch the device details.
Solution
Sysname is a mandatory field. Make sure this field is populated before attempting to add the device. To verify the status of the Sysname, query the SNMP device to check if the Sysname (.1.3.6.1.2.1.1.5) returns a value.
Cause
The IP address of the device to be discovered may be available in OpManager as a subnet address.
Solution
In OpManager, an specific address cannot be used as both a IP address and Subnet. The required device can only be added if the device IP doesn't exist as a Subnet in OpManager or if the 'DNS Name' of the device is resolved.
Cause:
Solution:
Check whether the device is reachable from the OpManager server continuously and without any hindrance. Also ensure that there is no delay in the protocol response chosen for the corresponding credential that is associated with the device(SNMP, WMI, etc). In some cases, the device would have been added in OpManager, but not notified. Please check the Inventory after few minutes of discovery to make sure the device is added.
The message 'Device Discovery has been initiated' will be displayed when two or more devices are discovered at the same time (separated by comma) via 'Add Device'. In such cases, the mentioned devices will be added into OpManager without an additional message confirming the completion of the discovery process. These devices will be listed under Inventory once the discovery progress notification shows the completion status.
Thank you for your feedback!