Appendix
E.
Verifying
Capacity
Upgrade
on
Demand
Processors
Capacity
Upgrade
on
Demand
data
is
stored
in
system
hardware.
If
a
system
failure
occurs
where
certain
hardware
must
be
replaced,
the
Capacity
Upgrade
on
Demand
data
may
be
lost.
Use
the
following
procedures
to
ensure
that
the
Capacity
Upgrade
on
Demand
data
is
restored
(if
necessary)
after
a
service
action.
Determining
Current
Configuration
Before
performing
any
other
actions,
use
this
procedure
to
determine
the
system
configuration:
1.
Log
in
to
the
system
as
root
user
or
as
a
user
with
system
group
privileges.
2.
Type
the
following
at
the
command
line:
chcod
3.
The
configured
Capacity
Upgrade
on
Demand
features
are
displayed.
Make
a
note
of
the
current
configuration.
Recovery
Procedures
Perform
any
required
service
actions
to
repair
the
system.
After
the
service
action
is
complete,
use
the
following
procedure
to
check
the
Capacity
Upgrade
on
Demand
information
and
if
necessary,
return
the
system
to
its
original
configuration.
1.
Log
in
to
the
system
as
root
user
or
as
a
user
with
system
group
privileges.
2.
Type
the
following
at
the
command
line:
chcod
3.
The
configured
Capacity
Upgrade
on
Demand
features
are
displayed.
Compare
the
current
configuration
with
the
configuration
you
recorded
earlier.
If
the
system
configurations
do
not
match,
use
the
procedures
beginning
with
“Installing
a
System
with
Capacity
Upgrade
on
Demand”
on
page
353
to
reinstall
the
Capacity
Upgrade
on
Demand
feature
and
reconfigure
the
hardware,
as
appropriate.
Capacity
Upgrade
on
Demand
Diagnostics
Capacity
Upgrade
on
Demand
monitors
its
resources.
Notification
of
the
number
of
enabled
devices
is
sent
to
the
CUoD
project
office
monthly
and
whenever
the
number
of
resources
change.
Unauthorized
devices
cannot
be
tested
by
AIX
diagnostics,
nor
do
they
appear
when
running
the
lscfg
command
on
the
NEW
RESOURCE
menu,
or
any
AIX
diagnostic
task.
For
example,
a
system
may
have
eight
processors
originally
installed,
but
only
six
of
the
eight
have
been
authorized
for
use.
Diagnostics
will
only
show
the
six
authorized
processors
in
the
diagnostic
test
list
or
NEW
RESOURCE
list.
The
two
unused
processors
cannot
be
tested
by
standalone
and
online
diagnostics,
and
will
not
display
in
the
diagnostic
test
list.
However,
they
are
tested
by
the
power-on
self-test
(POST),
and
if
a
processor
has
failed,
the
failure
is:
v
Logged
in
the
POST
error
log
v
Logged
in
the
AIX
error
log
v
Reported
at
boot
time
by
automatic
error
log
analysis
v
Reported
if
the
sysplanar0
diagnostics
are
run
System
Management
Services
and
service
processor
menus
are
not
affected
by
Capacity
Upgrade
on
Demand
and
all
processors
are
tested
at
boot
time.
If
one
processor
failed
at
IPL,
Capacity
Upgrade
on
Demand
still
enables
the
number
of
authorized
processors,
having
the
remaining
good
processors
marked
505
Summary of Contents for RS/6000 Enterprise Server M80
Page 1: ...RS 6000 Enterprise Server Model M80 Eserver pSeries 660 Model 6M1 Service Guide SA38 0571 01...
Page 10: ...x Service Guide...
Page 14: ...xiv Service Guide...
Page 16: ...xvi Service Guide...
Page 22: ...Data Flow 4 Service Guide...
Page 30: ...CEC Card Cage Rear of CEC drawer viewed from top cover removed 12 Service Guide...
Page 84: ...66 Service Guide...
Page 176: ...158 Service Guide...
Page 376: ...358 Service Guide...
Page 430: ...412 Service Guide...
Page 485: ...Chapter 11 Parts Information This chapter contains parts information for the system 467...
Page 486: ...CEC Drawer Card Assembly 9 468 Service Guide...
Page 488: ...CEC Drawer Backplane 5 2a 1 2 3 4 470 Service Guide...
Page 490: ...CEC Drawer Power Supplies 1 2 3 4 5 6 7 8 9 472 Service Guide...
Page 492: ...CEC Drawer Fan Assemblies 2 1 3 4 5 6 8 9 10 11 12 13 7 14 474 Service Guide...
Page 496: ...7 8 9 10 6 1 2 3 4 4 5 478 Service Guide...
Page 508: ...490 Service Guide...
Page 520: ...502 Service Guide...
Page 522: ...504 Service Guide...
Page 526: ...508 Service Guide...
Page 558: ...540 Service Guide...
Page 565: ......
