ADMINISTRATION PORTAL
Help Center User GuideGetting StartedFAQsRelease Notes
 
X
User Guide
Getting Started
FAQs
Release Notes
Contents  

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 Wireless LAN Controllers

User authentication failed.

This message is displayed when SNMP option is not enabled during the device discovery process.

Check whether the firewall is disabled on Junos Space Virtual Machine or the JA 1500 Appliance on port 8889 (outbound), if not, disable the firewall. Port 8889 is opened during Network Director installation, but in case of a failure, you must check whether this port is open or not.

Adapter mssos cannot manage the device - Either the Device is down or the port 8889 is not reachable.

This message is displayed when SNMP is enabled during the device discovery process.

Check whether port 8889 is open or not. You can check using the CLI command root@space# nmap <IP address of controller> -p 8889 from the Junos Space JA2500 Appliance or Junos Space Virtual Appliance.

Adapter mssos cannot manage the device-Can't manage Device, Wrong Credentials.

Check the credentials entered during the device discovery process. Always select the Enable Password credential for device discovery in Network Director.

Check if adapter is running or Platform can't connect to it.

Check whether the MSSOS adapter process is running on Junos Space JA2500 Appliance or the Junos Space Virtual Appliance. Verify using the CLI command root@space# ps -ef | grep mssos.

If no process is running, restart the adapter service by using the CLI command root@space# service mssosadapter start.

Device is not reachable.

If ping is enabled during device discovery, then check whether the controller is reachable using the CLI command ping.

Junos Space is unable to query the device information through SNMP. Check the SNMP settings on the device to verify SNMP is not blocked and the SNMP settings specified in Junos Space match the device SNMP settings.

If the SNMP option is enabled in Network Director during device discovery, then check and ensure that SNMP is enabled on the controller. Also, ensure that he SNMP settings on Network Director and Junos Space match with the SNMP settings on the controller.

Error Messages Displayed During Discovery of EX Series Switches

SSH connection failed. Device might not be reachable.

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.

User Authentication failed.

Check the read and write credentials used during device discovery.

Device is not reachable.

If ping is enabled during device discovery, then check whether the switch is reachable using the CLI command ping.

Junos Space is unable to query the device information through SNMP. Check the SNMP settings on the device to verify SNMP is not blocked and the SNMP settings specified in Junos Space match the device SNMP settings.

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

Device Failed to return System information.

This message is displayed if the switch is too busy to respond to operational commands. Try discovering the device again.

Failed to configure device, Check Device state.

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.

Device has been added, but failed to synchronize. Please try manual re-synchronization. Error while reading config from device: device_name, Detail - Fail while executing following RPC: <get-configuration database=committed><configuration></configuration></get-configuration>

Try to resynchronize the devices manually. For details, see Resynchronizing Device Configuration.

Error while reading config from device: device-name Failed while executing the following RPC: <get-hardware-inventory/>

Check the hardware details of the switch using the CLI command show chassis hardware detail.

If the output displays a message error: command is not valid, then the Junos OS image on the specified switch is corrupted and you need to upgrade to the latest version of Junos OS.

Related Documentation

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit