No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-How to resolve the problem of the deployment node status is abnormal before deploying the CSS

Publication Date:  2012-11-02 Views:  29 Downloads:  0
Issue Description
After the system information of the storage domain nodes in the CSS system, network information, and service information are all setting completely, the status of the deployment node is displaying as “ready and to be connecting” all the time, but the normal status is “establishment completed, to be configuring”.
Alarm Information
None
Handling Process
1. Login in the network management server via the “root” user.
2. Run the “service dhcpd status” command, and check the DHCP server’s status.
- If the DCHP server’s status is “running”, then execute the step 3.
- If the DCHP server’s status is “unused”, then run the “service dhcpd start” command, start the DHCP service on the network management server.
3. Login in the status abnormal node via the “root” user.
4. Run the “ps -ef | grep cm” command, check if there are deployment process and communication process.
-If the system displayed the following content, it illustrated the deployment process and communication process are existing, then execute the step 5.
xxxxx xx:xx:xx cm_deploy
xxxxx xx:xx:xx cm_msg_server
xxxxx xx:xx:xx cm_mmt
Where, “xxxxx” denotes the process name; “cm_deploy” denotes the deployment process; “cm_msg_server” and “cm_mmt” denote the communication process.
-If the system didn’t display the three processes or parts are un-displayed, it showed the device’s process was abnormal. Then run the “/OSM/cm/deploy/bin/xxxxx” command, start the process which the system hadn’t displayed.
Where, “xxxxx” denotes the process number; “cm_deploy” denotes the deployment process; “cm_msg_server” and “cm_mmt” denote the communication process.
5. Run the “/bin/clean.sh” command, confirm the password and clear up the device environment into the deployment initialization status (the default password: 123456).
6. After this node startup, login in the ISM to check the node’s status.
-If the node’s status displayed as “connected, to be configuring”, it indicates it’s normal.
-If the node’s status also displayed as “ready and to be connecting”, please ask the technology supporter for help.
Root Cause
Due to the deploying node and ISM hasn’t connected, the node status is displaying as “ready and to be connecting” all the time.
Suggestions
None

END