How to troubleshoot connectivity issues between SecureShore and X-series.SecureShore NMS server cannot re-connect to a replaced CPM module on an X-series chassis. The Diagnostic reports following error message:
Unable to discover device 'NAME': java.rmi.RemoteException: The device has rejected a management request made by this server.
Please verify that the device has been configured to allow management by this server.
Tcpdump shows a short communication on TCP port 18085 between the CPM and SecureShore closed by the CPM.
Generic troubleshooting of SecureShore connectivity issues with an X-series device:
1. Verify in XOS configuration that web-server is enabled and management-server address is set to SecureShore NMS server IP address:
This specific case was caused by a missing configuration file /crossbeam/etc/nms.cf. This file should exist and contain the IP address of the SecureShore NMS server configured in the XOS CLI. The file likely wasn't properly created during the import of the XOS configuration on the replaced CPM. The file can be restored by refreshing the management-server statement in the XOS CLI:
CBS# configure no management-server 192.168.200.100
CBS# configure management-server 192.168.200.100
CBS# copy running-config startup-config
The content of the file can be verified in the Unix command line:
CBS# unix su
[[email protected] admin]# cat /crossbeam/etc/nms.cf
To activate the change, the cnmsd process needs to be restarted:
[[email protected] admin]# service cnmsd restart