IBM DR550, Руководство по диагностике и обслуживанию

Страница: 117 / 258

These scripts completely setup the environment so that hardware status events can
be received. The startcim script for example includes starting the CIM_diagd.
If there are problems with receiving hardware status events, it might help to restart
cimserver and cimlistener using the above scripts.
Possible reasons for an event not being displayed as hardware status:
1. Verify that error entry was added to AIX error log (while all the processes
above were active). If it was not added, make sure the errdemon is still
running:
ps -ef | grep errdemon
root 61504 1 0 Jul 15 - 0:00 /usr/lib/errdemon
If it is not running, start it with
/usr/lib/errdemon
.
2.
Verify that the above processes are still active.
3. If cimlistener doesn’t stay alive, it might help to turn tracing on (or off):
v vi /opt/freeware/cimom/pegasus/etc/cimlistener.conf
v Uncomment (or comment):traceComponents="LISTENER" traceLevel="4"
v
Restart cimlistener
4. Duplicate error entries are not passed on to Director. To find out if the error has
already been reported, run the diag command. For example, to check for
existing error entries for sysplanar0 run the following command which will
show similar output:
#diag -c -d sysplanar0
Starting diagnostics
Testing sysplanar0
Ending diagnostics.
A problem was detected. Run diagnostics.
The last line indicates that an error has been reported for sysplanar0 and is
pending. To resolve the problem, run the following:
#diag -c -d sysplanar0 -L complete
5. Verify that the agent has a DirectorConsumer subscription from the Director
server: /opt/ibm/icc/cimom/bin/cimsubscribe -lh | grep DirectorConsumer
/* should list something like */ Destination = http://localhost:6988/
CIMListener/DirectorConsumer/9.3.63.152 and 9.3.63.152 should be the ip
address of the IBM Director server you are expecting to show the event.
Chapter 11. IBM Director
89