Isolating
software
problems
Use
the
following
information
to
isolate
and
resolve
software
problems.
Operating-system
checks
Use
the
following
information
to
resolve
operating-system
checks:
Node
non-responsive
If
the
node
does
not
respond
to
ping
or
the
serial
console,
and
there
are
no
relevant
entries
in
the
syslog
or
hardware
logs,
refer
to
the
applicable
Linux
documentation
that
came
with
your
software
to
continue
with
the
problem
resolution
process.
Adapter
device
driver
not
configured
If
the
device
driver
is
not
configured,
and
there
are
no
adapter
hardware
problems
reported,
refer
to
the
applicable
Linux
documentation
that
came
with
your
software
and
continue
with
the
problem
resolution
process.
CSM
checks
Use
the
following
information
to
resolve
CSM
checks:
Events
not
logged
or
actions
not
taken
Using
the
ERRM
command
line
interface,
monitor
the
AnyNodeProcessorsIdleTime
condition
on
specific
managed
nodes
with
the
LogEventsAnyTime
response
while
causing
arm
and
rearm
events.
If
arm
and
rearm
events
are
not
observed
at
the
management
server,
this
is
configuration
or
network
problem.
Refer
to
the
applicable
documentation
that
came
with
CSM
and
complete
the
problem
resolution
process.
Differences
in
node
lists
Output
from
the
command
CT_CONTACT=<ManagedNodeName>
lsrsrc
IBM.[Host|FileSystem]
when
run
on
the
management
node
is
not
the
same
as
when
run
on
the
managed
node.
This
is
configuration
or
network
problem,
refer
to
the
applicable
documentation
that
came
with
CSM
and
complete
the
problem
resolution
process.
netstat
output
incomplete
The
command
netstat
-an
|
grep
rmc
on
the
management
server
does
not
show
ESTABLISHED
TCP
connections
for
each
managed
node
that
is
currently
turned
on.
This
is
configuration
or
network
problem,
refer
to
the
applicable
documentation
that
came
with
CSM
and
complete
the
problem
resolution
process.
RMC
not
running
The
command
lssrc
-ls
ctrmc
shows
that
RMC
is
not
running
on
the
management
server.
Refer
to
the
applicable
documentation
that
came
with
CSM
and
complete
the
problem
resolution
process.
lsrsrc
reports
errors
The
command
lsrsrc
-ab
IBM.[Host|FileSystem]’
which
checks
that
HostRM
and
FSRM
will
run
on
the
management
server
reports
errors.
Refer
to
the
applicable
documentation
that
came
with
CSM
and
complete
the
problem
resolution
process.
lsaudrec
reports
errors
The
command
lsaudrec
which
checks
that
AuditRM
will
run
on
the
management
server
reports
errors.
Refer
to
the
applicable
documentation
that
came
with
CSM
and
complete
the
problem
resolution
process.
48
IBM
Eserver
Cluster
1350
Installation
and
Service
Guide
Summary of Contents for eserver Cluster 1350
Page 1: ...IBM Eserver Cluster 1350 Installation and Service Guide ERserver...
Page 2: ......
Page 3: ...IBM Eserver Cluster 1350 Installation and Service Guide ERserver...
Page 26: ...10 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 82: ...66 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 86: ...70 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 88: ...72 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 90: ...74 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 94: ...78 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 98: ...82 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 104: ...88 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 114: ...98 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 120: ...104 IBM Eserver Cluster 1350 Installation and Service Guide...
Page 121: ......
Page 122: ...Part Number 25K8407 Printed in USA 1P P N 25K8407...