Troubleshooting Device Discovery or Device Status
The table below shows the symptoms related to issues with device discovery or the device status. For each symptom that describes your problem, determine which possible causes apply and follow the corresponding solutions.
Symptoms |
Possible Cause |
Solution |
|
---|---|---|---|
A device discovery task fails. A device status changes to Unmanaged or Unreachable. |
Incorrect device credentials were provided. |
Reenter the username and password, and try discovering the device again. If you are attempting to discover CDP neighbors of the seed device, ensure that the credentials that you provide are valid on all devices that you want to discover. |
|
The SSH server is disabled on the device. | Reenable the SSH server on the device and try discovering the device again. | ||
The maximum number of SSH sessions that the device can support has been reached. | Check the number of user sessions on the device. Free at least one connection and try discovering the device again. | ||
CDP is disabled on the device or on the device interface that the DCNM-LAN server connects to. |
Ensure that CDP is enabled on the device globally and that it is enabled on the specific interface that the DCNM-LAN server connects to. |
||
The device interface that the DCNM-LAN server connects to is shut down. |
Ensure that the device interface that the DCNM-LAN server connects to is up. |
||
The device restarted or shut down before discovery could complete. |
Ensure that the device is running and try discovering the device again. |
||
The DCNM-LAN server cannot reach the device. |
Ensure that the network requirements for device management are met. |
||
Discrepancy in system log messages. |
Use the clear logging logfile command to clear the system log in the device and try to manually discover the device. |
||
Discrepancy in accounting log messages. |
Use the clear accounting log command to clear the accounting log messages in the device and try to manually discover the device.
|