Troubleshooting Device Discovery Error Messages
While you are discovering devices by using Network Director, you might encounter some issues. Network Director enables you to detect the errors and provide solutions to the potential errors that you encounter.
Error Message |
Solution |
---|---|
Error Messages Displayed During Discovery of EX Series Switches | |
|
For EX Series switches, Network Director connects to port 22 (default port) on the JA2500 Appliance or the Junos Space Virtual Appliance by using SSH. Ensure that you have configured port 22 on the Space appliance through Administration > Applications in the Junos Space Plattform page. To do this, select Network Application Platform and click Actions > Modify Application Settings. Change SSH port for device connection field to 22. If port 22 is open on the Junos Space Appliance, and you still get the error, then check if port 22 is open on the switch and if the switch is accepting SSH connections on port 22. |
|
Check the read and write credentials used during device discovery. |
|
If ping is enabled during device discovery, then check
whether the switch is reachable using the CLI command |
|
If the SNMP option is enabled in Network Director during device discovery, check and ensure that SNMP is enabled on the switch. Also, check and ensure that the SNMP settings on Network Director and Junos Space match with the SNMP settings on the switch. |
General Error Messages | |
|
This message is displayed if the switch is too busy to respond to operational commands. Try discovering the device again. |
|
Check whether the Edit lock is open on the switch and close it if it is open. The configuration commit fails if the Edit lock is open. |
|
Try to resynchronize the devices manually. For details, see Resynchronizing Device Configuration. |
|
Check the hardware details of the switch using the CLI
command If the output displays a message |