Symptom
FaultDiagnosis
1. Possible cause 1: The management IP addressis switching to another node due to a node restart or network exception.
2. Wait about 1 minute until the management IPaddress finishes switching to another node and then try to log in again.
If yes, no further operations are required.
If no,go to cause 2.
3. Possible cause 2: The DeviceManager softwarefails.
a. Use PuTTY to log in as user omuserto theOceanStor 9000 management IP address. Run the su command and input the password of user root as prompted to switch to user root.
If yes, go to c.
If no,go to d.
c. Run ps -ef |grep httpd tocheck whether the DeviceManager software process is normal (if there are records, the process isnormal; otherwise, the process is abnormal).
If yes, go to cause 3.
If no,go to d.
d. Restart the DeviceManager. Run cd/opt/deviceManager/bin to go to the /bin directory.Then, run sh restart.sh.
e. Check whether you can successfully log into the DeviceManager.
Ifyes, no further operations are required.
If no,go to cause 3.
4. Possible cause 3: The CM fails.
a. Log in to the node.
b. Run ps -ef |grep snas_cm tocheck whether the CM process is normal (if there are records, the CM process is normal; otherwise,the CM process is abnormal).
If yes, contact technical support engineers.
If no,go to c.
c. Restart the CM.
i. Run ps -ef |grep cm tocheck the CM process number. The CM process number includes snas_cm.
ii. Run kill -9 process number to end the CM process. The daemon will automatically start the CM process.
d. Restart the DeviceManager. Run cd/opt/deviceManager/bin to go to the /bin directory.Then, run sh restart.sh.
e. Check whether you can successfully log into the DeviceManager.
If yes, no further operations are required.
If no, contacttechnical support engineers.
END
