IBM JS20 Hardware Maintenance Manual - Page 78

Running, online, diagnostics, concurrent, standalone, management, server

Get IBM JS20 - BladeCenter - 8842 PDF manuals and user guides
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 78 highlights

v Under some conditions the system may stop, with instructions displayed on attached displays and terminals. Follow the instructions to select a console display. Running the online diagnostics in concurrent mode Use concurrent mode to run online diagnostics on some of the system resources while the system is running normal system activity. Because the system is running in normal operation, the following resources cannot be tested in concurrent mode: v Adapters connected to paging devices, or disk drive used for paging v Memory v Microprocessor Three levels of testing exist in concurrent mode: v The share-test level tests a resource while the resource is being shared by programs running in the normal operation. This testing is mostly limited to normal commands that test for the presence of a device or adapter. v The sub-test level tests a portion of a resource while the remaining part of the resource is being used in normal operation. For example, this test could test one port of a multiparty device while the other ports are being used in normal operation. v The full-test level requires the device not be assigned to or used by any other operation. This level of testing on a disk drive might require the use of the vary command. The diagnostics display menus to allow you to vary off the needed resource. Error log analysis is done in concurrent mode when you select the Problem Determination option on the Diagnostic Mode Selection menu. Error log analysis is done in concurrent mode when you select the Problem Determination option on the Diagnostic Mode Selection menu. Running standalone diagnostics from a management (NIM) server A client system connected to a network with a Network Installation Management (NIM) server is capable of booting the standalone diagnostics from the NIM server if the client system is registered on the NIM server, and if the NIM boot settings on both the NIM server and the client system are correct. Consider the following information when running standalone diagnostics from a NIM server: 1. For NIM clients that have adapters that would normally require that supplemental media be loaded when standalone diagnostics are run from CD-ROM, the support code for these adapters must be loaded into the directory pointed to by the NIM SPOT from which you wish to boot that client. Before running standalone diagnostics on these clients from the NIM server, the NIM server system administrator must ensure that any needed support for these devices is loaded onto the server. 2. Use one of the following methods to determine the amount of available system memory: v Run the Display Resource Attributes task for resource. v Use the Config option under System Management Services (see the system unit service guide). v Use the following AIX command: lsattr -E -l mem0 68 BladeCenter JS20 Type 8842: Hardware Maintenance Manual and Troubleshooting Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
v
Under
some
conditions
the
system
may
stop,
with
instructions
displayed
on
attached
displays
and
terminals.
Follow
the
instructions
to
select
a
console
display.
Running
the
online
diagnostics
in
concurrent
mode
Use
concurrent
mode
to
run
online
diagnostics
on
some
of
the
system
resources
while
the
system
is
running
normal
system
activity.
Because
the
system
is
running
in
normal
operation,
the
following
resources
cannot
be
tested
in
concurrent
mode:
v
Adapters
connected
to
paging
devices,
or
disk
drive
used
for
paging
v
Memory
v
Microprocessor
Three
levels
of
testing
exist
in
concurrent
mode:
v
The
share-test
level
tests
a
resource
while
the
resource
is
being
shared
by
programs
running
in
the
normal
operation.
This
testing
is
mostly
limited
to
normal
commands
that
test
for
the
presence
of
a
device
or
adapter.
v
The
sub-test
level
tests
a
portion
of
a
resource
while
the
remaining
part
of
the
resource
is
being
used
in
normal
operation.
For
example,
this
test
could
test
one
port
of
a
multiparty
device
while
the
other
ports
are
being
used
in
normal
operation.
v
The
full-test
level
requires
the
device
not
be
assigned
to
or
used
by
any
other
operation.
This
level
of
testing
on
a
disk
drive
might
require
the
use
of
the
vary
command.
The
diagnostics
display
menus
to
allow
you
to
vary
off
the
needed
resource.
Error
log
analysis
is
done
in
concurrent
mode
when
you
select
the
Problem
Determination
option
on
the
Diagnostic
Mode
Selection
menu.
Error
log
analysis
is
done
in
concurrent
mode
when
you
select
the
Problem
Determination
option
on
the
Diagnostic
Mode
Selection
menu.
Running
standalone
diagnostics
from
a
management
(NIM)
server
A
client
system
connected
to
a
network
with
a
Network
Installation
Management
(NIM)
server
is
capable
of
booting
the
standalone
diagnostics
from
the
NIM
server
if
the
client
system
is
registered
on
the
NIM
server,
and
if
the
NIM
boot
settings
on
both
the
NIM
server
and
the
client
system
are
correct.
Consider
the
following
information
when
running
standalone
diagnostics
from
a
NIM
server:
1.
For
NIM
clients
that
have
adapters
that
would
normally
require
that
supplemental
media
be
loaded
when
standalone
diagnostics
are
run
from
CD-ROM,
the
support
code
for
these
adapters
must
be
loaded
into
the
directory
pointed
to
by
the
NIM
SPOT
from
which
you
wish
to
boot
that
client.
Before
running
standalone
diagnostics
on
these
clients
from
the
NIM
server,
the
NIM
server
system
administrator
must
ensure
that
any
needed
support
for
these
devices
is
loaded
onto
the
server.
2.
Use
one
of
the
following
methods
to
determine
the
amount
of
available
system
memory:
v
Run
the
Display
Resource
Attributes
task
for
resource.
v
Use
the
Config
option
under
System
Management
Services
(see
the
system
unit
service
guide).
v
Use
the
following
AIX
command:
lsattr
-E
-l
mem0
68
BladeCenter
JS20
Type
8842:
Hardware
Maintenance
Manual
and
Troubleshooting
Guide