Troubleshooting

This chapter provides a listing of problems or common error messages that you might see when using the Device Manager and provides actions that you can take to resolve the issues.

This chapter addresses the following topics:

Certificate Errors

“What should I do when I see the following errors?”

Causes:

  • Certificate Error
  • Failed to create cert file
  • Failed to parse cert file
  • Failed to read client cert
  • Failed to open client cert
  • Invalid client cert
  • Key Error
  • Missing Certificate

Resolution: Verify that the Device Manager has a valid certificate. (See Certificate Installation.)

“How do I check to see if the certificate is installed?”

See Certificate Installation page 2-5.

Connection Errors

“After I click Connect, I received a connection error message”

Resolution:

  • For an Ethernet connection: Verify that an IP address is defined for the interface, and verify that you can ping this IP address from the Device Manager laptop.
  • For an Auto-Detect connection: Ensure that the Ethernet port on the Device Manager has a direct connection to the CGR 1000 router and that the router interface is configured with ipv6 address use-link-local-only.
  • For a WiFi connection:

– Verify that the WiFi parameters (SSID and passphrase) match the WiFi configuration on the router.

– Ensure that there is no third-party wireless client tool controlling the WiFi interface. For example, if you are using a third-party client tool (such as Intel PROSet Wireless Client Tool), change the settings from that tool to enable Windows to manage the WiFi interface.

“I cannot log in to Device Manager”

Cause: This message appears when the application cannot find a valid certificate. When this condition occurs, the Certificate Configuration page opens to display the currently installed certificate.

Resolution :

Verify that the clock is set to the correct time, otherwise the certificate will not be honored.

See Certificate Installation for details on installing certificates.

 

 

“Connectivity: Windows failed to join WLAN”

Cause: The Device Manager cannot create a WiFi profile on the laptop on which it resides because third-party software has control of the laptop WiFi adapter. Additionally, the Device Manager cannot control WiFi through Windows API.

Resolution: Disable the third-party software and enable Windows to manage the WiFi interface.

“Cannot detect peer’s IPv6 address”

Cause: IPv6 peer was not found.

Resolution: Enable the IPv6 link local address on the CGR 1000 so that it will respond to an Auto-Discovery from the Device Manager.

See Cisco 1000 Series Connected Grid Routers Unicast Routing Software Configuration Guide.

“Connection Refused” and “Connection Timeout”

Causes:

  • IP HTTP server is not enabled on the CGR 1000
  • IP HTTP server port is not set up on the CGR 1000
  • Target port for the CGR 1000 and the Device Manager do not match
  • IP HTTP server crashed

Resolution: Check the IP HTTP server settings noted above.

“Valid work authorization is required to connect”

Cause: The work authorization does not fall within the expected time, serial, and role requirements.

Resolution: Contact the CG-NMS admin to resubmit the work order.

“SSL handshake failed”

Causes:

  • Certificates for the Device Manager and CGR 1000 do not match
  • Inaccurate System time on the Device Manager or CGR 1000

Resolution: Verify that the certificates for the Device Manager and CGR 1000 match and check the System time setting on the Device Manager and CGR 1000.

“Unable to connect to the CGR 1000 over WiFi”

Causes:

  • WiFi is not up
  • Incorrect Passphrase entered in the Connect to the Router page of the Device Manager

Resolution:

  • Attempt to connect to the CGR 1000 router over Ethernet.
  • Recheck the WiFi Passphrase provided by your admin and reenter the value on the Connect to the Router page.
  • Check the status of the WiFi connection.