For
further
information
about
activating
and
deactivating
On/Off
Capacity
on
Demand
on
your
system,
refer
to
or
refer
to
the
IBM
Hardware
Management
Console
for
pSeries
Installation
and
Operations
Guide
that
was
delivered
with
your
hardware
management
console.
Trial
Capacity
on
Demand
Trial
Capacity
on
Demand
enables
CUoD
features
to
be
activated
one
time
for
a
period
of
30
consecutive
days.
If
your
system
was
ordered
with
CUoD
features
and
they
have
not
yet
been
activated,
you
can
turn
the
features
on
for
a
one-time
trial
period.
With
the
trial
capability,
you
can
gauge
how
much
capacity
you
might
need
in
the
future,
if
you
decide
to
permanently
activate
the
resources
you
need.
Alternatively,
the
Trial
Capacity
on
Demand
function
can
be
used
to
immediately
activate
resources
while
processing
an
order
for
a
permanent
activation
code.
For
further
information
about
using
Trial
Capacity
on
Demand,
refer
to
or
refer
to
the
IBM
Hardware
Management
Console
for
pSeries
Installation
and
Operations
Guide
that
was
delivered
with
your
hardware
management
console.
Capacity
Planning
If
you
are
doing
capacity
planning
for
models
with
CUoD
features,
plan
ahead
for
any
potentially
disruptive
actions
that
might
inhibit
your
using
fully
the
capacity
of
the
system.
Some
actions
you
may
want
to
take
prior
to
activating
any
CUoD
features
are
as
follows:
v
Perform
any
I/O
updates,
such
as
adding
adapters
necessary
to
increase
system
capacity
v
Perform
memory
upgrades
(CUoD)
or
standard
memory
features
v
Prepare
logical
partitions
By
planning
ahead,
you
can
accommodate
the
growth
of
existing
workloads,
as
well
as
handle
new
workloads
without
requiring
a
server
outage.
Each
component
of
a
server
affects
performance
and
overall
throughput
of
workloads.
By
planning
ahead
and
taking
into
account
the
complete
server
configuration,
you
can
help
ensure
that
you
get
the
full
benefit
of
CUoD
activations.
Note:
If
you
have
questions
about
capacity-planning
topics
not
covered
here,
contact
your
sales
representative
for
assistance.
Processor
CUoD
Ordering
Permanent
CUoD
capacity
can
be
activated
in
either
one
of
the
following
scenarios.
The
description
of
each
scenario
indicates
if
and
when
it
is
necessary
to
send
vital
product
data
(VPD)
to
IBM.
v
New
system
order
(new
footprint):
An
order
can
contain
a
number
of
CUoD-activation
features.
The
manufacturing
facility
fills
orders
directly
at
the
plant
of
manufacture,
before
the
server
is
delivered
to
the
customer.
v
Ordering
activation
features
for
an
installed
server:
After
you
have
determined
that
you
want
to
permanently
activate
some
or
all
of
your
CUoD
features,
contact
your
business
partner
or
sales
representative
to
place
an
order.
When
the
order
record
and
the
VPD
are
both
available
to
the
manufacturing
facility,
a
processor
CUoD
activation
code
unique
to
your
server
is
generated.
The
activation
code
is
mailed
to
you
and
posted
at
http://www.ibm.com/servers/eserver/pseries/cuod/index.html.
As
part
of
the
order
process,
VPD
collected
from
the
installed
server
is
combined
with
information
from
the
order
records
for
CUoD
activation
features.
This
combined
information
is
used
to
generate
a
CUoD
activation
code
specifically
for
your
server,
enabling
the
activation
of
the
appropriate
features.
Allow
some
time
for
the
order
processing
and
posting
of
the
processor
on
demand
activation
code
to
take
place.
Then
use
the
code
to
activate
the
processor
on
demand
features
directly
on
your
server.
If
you
need
to
activate
resources
immediately,
you
can
activate
features
using
the
Trial
Capacity
on
Demand
function.
This
allows
you
to
use
the
resources
immediately
while
the
permanent
activation
code
is
being
processed.
Chapter
1.
Reference
Information
11
Summary of Contents for eserver pSeries 690
Page 1: ...pSeries 690 Service Guide SA38 0589 05 ERserver...
Page 2: ......
Page 3: ...pSeries 690 Service Guide SA38 0589 05 ERserver...
Page 12: ...x Eserver pSeries 690 Service Guide...
Page 14: ...xii Eserver pSeries 690 Service Guide...
Page 228: ...Step 1527 5 Call your next level of support 212 Eserver pSeries 690 Service Guide...
Page 362: ...Step 1545 15 Call for support This ends the procedure 346 Eserver pSeries 690 Service Guide...
Page 381: ...Step 154A 14 Turn off the power Chapter 3 Maintenance Analysis Procedures 365...
Page 430: ...414 Eserver pSeries 690 Service Guide...
Page 798: ...782 Eserver pSeries 690 Service Guide...
Page 923: ...L3 Cache Shorts Test Step 4 Chapter 9 Removal and Replacement Procedures 907...
Page 924: ...L3 Cache Shorts Test Step 5 908 Eserver pSeries 690 Service Guide...
Page 926: ...L3 Cache Shorts Test Step 2 910 Eserver pSeries 690 Service Guide...
Page 928: ...L3 Cache Shorts Test Step 4 912 Eserver pSeries 690 Service Guide...
Page 929: ...L3 Cache Shorts Test Step 5 Chapter 9 Removal and Replacement Procedures 913...
Page 1055: ...7040 Model 681 Media Subsystem 1 2 3 4 5 6 7 8 9 10 Chapter 10 Parts Information 1039...
Page 1057: ...Power and SCSI Cables to the Media Subsystem 1 2 3 5 4 6 Chapter 10 Parts Information 1041...
Page 1061: ...Power Cabling Chapter 10 Parts Information 1045...
Page 1090: ...1074 Eserver pSeries 690 Service Guide...
Page 1094: ...1078 Eserver pSeries 690 Service Guide...
Page 1122: ...1106 Eserver pSeries 690 Service Guide...
Page 1124: ...1108 Eserver pSeries 690 Service Guide...
Page 1132: ...1116 Eserver pSeries 690 Service Guide...
Page 1133: ......
Page 1134: ...Printed in U S A February 2004 SA38 0589 05...