2.
Determine
which
storage
unit
volume
that
you
want
to
use
as
a
boot
or
dump
device
by
decoding
the
serial
number
as
described
in
“Tru64
UNIX
UDID
hexadecimal
representations”
on
page
34.
3.
Assign
a
unit
number
with
the
wwidmgr
-quickset
-item
i
-unit
u
command,
where
i
is
the
wwidmgr
item
number
and
u
is
the
unit
number
you
choose.
You
can
find
the
item
number
inside
the
square
brackets
of
the
output
from
the
wwidmgr
-show
wwid
command.
4.
Reinitialize
the
server
with
the
init
command.
When
you
make
changes
with
the
wwidmgr
command,
they
do
not
take
effect
until
the
next
system
initialization.
5.
Use
the
show
device
command
to
verify
that
the
system
displays
the
disk
as
console
device
DGAu
,
with
the
unit
number
that
you
defined.
After
the
initialization,
the
console
show
device
command
displays
each
fibre-channel
adapter
followed
by
the
paths
through
that
adapter
to
each
of
the
defined
fibre-channel
disks.
The
path-independent
OpenVMS
device
name
for
each
fibre-channel
disk
is
displayed
in
the
second
column.
6.
Set
the
default
boot
device
console
variable,
bootdef_dev
,
to
match
the
console
device
name
of
the
boot
disk.
In
a
multipath
environment,
use
the
asterisk
(
*
)
as
a
wildcard
to
make
all
boot
paths
available.
An
example
of
the
multipath
command
is
set
bootdef_dev
DGAu.*
,
where
u
is
the
unit
number
and
*
denotes
all
possible
paths.
Verifying
the
fibre-channel
attachment
of
the
storage
unit
volumes
to
Tru64
UNIX
This
section
contains
steps
you
must
perform
to
verify
the
fibre-channel
attachment
of
the
storage
unit
volumes
to
the
Tru64
UNIX
host
system.
For
Tru64
UNIX
5.
x
:
1.
Use
the
hwmgr
command
to
verify
the
attachment
of
the
storage
unit
volumes
for
Tru64
5.
x
.
Figure
15
shows
an
example
of
the
commands
you
can
use
to
verify
the
attachment
of
the
storage
unit
volumes.
#
hwmgr
-view
dev
-cat
disk
HWID:
Device
Name
Mfg
Model
Location
------------------------------------------------------------------------------
54:
/dev/disk/floppy0c
3.55in
floppy
fdi0-unit-0
60:
/dev/disk/dsk1c
DEC
RZ2DD-LS
(C)
DEC
bus-2-targ-0-lun-0
63:
/dev/disk/cdrom0c
COMPAQ
CDR-8435
bus-5-targ-0-lun-0
66:
/dev/disk/dsk5c
IBM
2105F20
bus-0-targ-253-lun-0
67:
/dev/disk/dsk6c
IBM
2105F20
bus-0-targ-253-lun-1
68:
/dev/disk/dsk7c
IBM
2105F20
bus-0-targ-253-lun-2
:
:
#
hwmgr
–get
attributes
–id
66
66:
name
=
SCSI-WWID:01000010:6000-1fe1-0000-2b10-0009-9010-0323-0046
category
=
disk
sub_category
=
generic
architecture
=
SCSI
:
:
Figure
15.
Example
of
the
hwmgr
command
to
verify
attachment
Chapter
4.
Attaching
to
a
Hewlett-Packard
AlphaServer
Tru64
UNIX
host
35
Summary of Contents for System storage DS6000 Series
Page 1: ...IBM TotalStorage DS6000 Host Systems Attachment Guide GC26 7680 03...
Page 2: ......
Page 3: ...IBM TotalStorage DS6000 Host Systems Attachment Guide GC26 7680 03...
Page 16: ...xiv DS6000 Host Systems Attachment Guide...
Page 28: ...xxvi DS6000 Host Systems Attachment Guide...
Page 30: ...xxviii DS6000 Host Systems Attachment Guide...
Page 50: ...20 DS6000 Host Systems Attachment Guide...
Page 84: ...54 DS6000 Host Systems Attachment Guide...
Page 88: ...58 DS6000 Host Systems Attachment Guide...
Page 164: ...134 DS6000 Host Systems Attachment Guide...
Page 170: ...140 DS6000 Host Systems Attachment Guide...
Page 174: ...144 DS6000 Host Systems Attachment Guide...
Page 192: ...162 DS6000 Host Systems Attachment Guide...
Page 212: ...182 DS6000 Host Systems Attachment Guide...
Page 226: ...196 DS6000 Host Systems Attachment Guide...
Page 240: ...210 DS6000 Host Systems Attachment Guide...
Page 248: ...218 DS6000 Host Systems Attachment Guide...
Page 250: ...220 DS6000 Host Systems Attachment Guide...
Page 256: ...Taiwan class A compliance statement VS07171L 226 DS6000 Host Systems Attachment Guide...
Page 297: ......
Page 298: ...Printed in USA GC26 7680 03...
