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

Can Not Manage S2600 By ISM

Publication Date:  2012-07-22 Views:  39 Downloads:  0
Issue Description
The system status of S2600 is normal and it can be managed through SSH tools, but can not be managed by ISM.
Alarm Information
None
Handling Process
1. Check the status of ISM service under the directory: /ISM/ism_cs/sbin.
It is running in the case below:
 
./Service.sh show
show lighttpd service...
root      4757     1  0 Nov08 ?        00:00:00 /ISM/ism_cs/sbin/lighttpd -f /ISM/ism_cs/sbin/lighttpd.conf
lighttpd service is running...
 
Use the command ./Service.sh start to start the service if it is not running.
 
2. Use the command ./show_agent.sh to check the status of ISM agent under the directory: /startup_disk/image/boot/ism_ap/agent/conf.
It is running in the case below:
 
root     19432     1  0 Nov08 pts/2    00:00:50 ./agent_common
root     19476     1  0 Nov08 ?        00:00:06 ./cimserver -D /startup_disk/image/boot/ism_ap/agent/conf/../../pegasus traceFilePath=/OSM/log/ismlog/cimserver.trc traceComponents=DiscardedData traceLevel=4
daemon   19466     1  0 Nov08 ?        00:00:00 ./slpd
root     19513     1  0 Nov08 pts/2    00:00:02 ./slpagent
root     19523     1  0 Nov08 pts/2    00:00:18 ./snmpapp
root     19423     1  0 Nov08 pts/2    00:00:02 sh monitorGuard.sh
root     19537     1  0 Nov08 pts/2    00:00:03 ./monitor
 
Use the command ./start_agent.sh to start the service if it is not running.
Root Cause
The system status of S2600 is normal and it can be managed through SSH tools, but can not be managed by ISM. How to restore it.
Suggestions
The S2600 can be managed by ISM again.

END