Sun Microsystems Solaris 7 11/99, Руководство по аппаратной платформе

Страница: 137 / 224

Chapter 8 Alternate Pathing 2.2 on the Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Servers 125
d. Rebuild the devices directories:
As shown above, you can verify the results of the
drvconfig(1M)
command by
listing the contents of
/devices/pseudo/ap_dmd*
.
e. Create symbolic links from the devices directory
/devices/pseudo
to the
special metadisk files in
/dev/ap/dsk
and
/dev/ap/rdsk
:
As shown above, you can verify the results of the
apconfig(1M)
command by
listing the contents of
/dev/ap/dsk
to view the symbolic links.
f. If you are placing the boot disk under AP control, use
apboot(1M)
to define
the new AP boot device:
The
apboot(1M)
command modifies the
/etc/vfstab
file and the
/etc/system
file. The metadisk_name must be in the form:
mcxtxdx
.
g. Modify any references that use a physical device node (that is, a path that
begins with
/dev/dsk
or
/dev/rdsk
) to use the corresponding metadisk
device node (that is, a path that begins with
/dev/ap/dsk
or
/dev/ap/rdsk
).
If a partition is mounted under a physical path, unmount and remount it under
the metadisk path.
Examine
/etc/vfstab
for any physical devices that should be changed to AP
metadevices. If necessary, edit
/etc/vfstab
to make the necessary
modifications.
Caution –
You must be a knowledgeable system administrator to edit the
/etc/vfstab
file. If you do not configure your file systems properly in
/etc/
vfstab
, it is possible that you will lose data the next time you boot the server.
3. Create AP metanetworks (for non-primary networks).
# drvconfig -i ap_dmd
# ls -l /devices/pseudo/ap_dmd*
...
# apconfig -R
# ls -l /dev/ap/dsk
...
# apboot
metadisk_name