more
information
on
the
Subsystem
Device
Driver
(SDD),
go
to
http://www-1.ibm.com/servers/storage/support/software/sdd.html.
For
information
about
running
MPIO
on
a
pSeries
host
system,
see
the
Interoperability
Matrix
at
http://www.ibm.com/servers/storage/disk/ds6000/interop.html.
Storage
unit
migration
issues
when
you
remove
the
AIX
5L
Version
5.2
with
the
5200-01
Recommended
Maintenance
package
support
This
section
discusses
the
migration
issues
when
removing
AIX
5L
version
5.2.
If
you
remove
AIX
5L
version
5.2
with
the
5200-01
Recommended
Maintenance
package
support
after
you
configure
devices
as
MPIO
other
FC
disks
,
consider
the
following
migration
issues.
Migration
back
to
the
other
FC
disk
configuration
can
occur
if
you
remove
the
MPIO
other
FC
disk
support.
In
this
case,
where
the
update
is
uninstalled
with
the
force
option,
the
AIX
version
5.2
release
of
MPIO
manages
the
migration.
If
the
system
reboots,
the
device
instance
is
in
the
defined
state.
During
migration,
the
device
instance
is
left
in
the
defined
state
and
a
new
other
FC
disk
instance
is
created.
If
the
system
does
not
reboot
and
the
device
instance
is
in
the
defined
state,
the
device
instance
remains
in
the
defined
state
and
a
new
other
FC
disk
instance
is
created.
If
the
system
does
not
reboot
and
the
device
instance
is
in
the
available
state,
the
device
instance
remains
unchanged.
There
might
also
be
other
FC
device
instances
that
are
created.
If
the
MPIO
other
FC
device
is
not
open,
an
other
FC
device
instance
is
created
for
each
path
where
the
device
is
detected.
If
the
MPIO
other
FC
device
instance
is
in
the
open
state,
no
further
other
FC
device
instances
are
created.
This
occurs
because
the
MPIO
other
FC
device
instance
would
have
already
issued
a
SCIOSTART
command
to
the
fibre-channel
adapter
for
each
of
the
paths.
The
fibre-channel
adapter
does
not
allow
two
devices
with
the
same
worldwide
name
and
worldwide
node
name
to
exist
in
its
internal
data
structures.
If
other
FC
device
instances
are
created,
sending
I/O
to
the
device
while
it
is
configured
as
both
MPIO
other
FC
and
other
FC
device
might
cause
indeterminate
device
behavior
or
data
corruption.
Recommendation:
Reboot
the
system
to
clear
this
condition.
Once
you
reboot
the
system,
the
MPIO
other
FC
device
instance
is
in
the
defined
state
and
you
can
remove
it
with
the
odmdelete
command.
You
cannot
remove
the
device
if
you
run
the
rmdev
command
due
to
missing
predefines.
For
information
about
running
MPIO
on
a
pSeries
host
system,
see
the
Interoperability
Matrix
at
http://www.ibm.com/servers/storage/disk/ds6000/interop.html.
88
DS6000
Host
Systems
Attachment
Guide
Содержание System storage DS6000 Series
Страница 1: ...IBM TotalStorage DS6000 Host Systems Attachment Guide GC26 7680 03...
Страница 2: ......
Страница 3: ...IBM TotalStorage DS6000 Host Systems Attachment Guide GC26 7680 03...
Страница 16: ...xiv DS6000 Host Systems Attachment Guide...
Страница 28: ...xxvi DS6000 Host Systems Attachment Guide...
Страница 30: ...xxviii DS6000 Host Systems Attachment Guide...
Страница 50: ...20 DS6000 Host Systems Attachment Guide...
Страница 84: ...54 DS6000 Host Systems Attachment Guide...
Страница 88: ...58 DS6000 Host Systems Attachment Guide...
Страница 164: ...134 DS6000 Host Systems Attachment Guide...
Страница 170: ...140 DS6000 Host Systems Attachment Guide...
Страница 174: ...144 DS6000 Host Systems Attachment Guide...
Страница 192: ...162 DS6000 Host Systems Attachment Guide...
Страница 212: ...182 DS6000 Host Systems Attachment Guide...
Страница 226: ...196 DS6000 Host Systems Attachment Guide...
Страница 240: ...210 DS6000 Host Systems Attachment Guide...
Страница 248: ...218 DS6000 Host Systems Attachment Guide...
Страница 250: ...220 DS6000 Host Systems Attachment Guide...
Страница 256: ...Taiwan class A compliance statement VS07171L 226 DS6000 Host Systems Attachment Guide...
Страница 297: ......
Страница 298: ...Printed in USA GC26 7680 03...