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

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

Chapter 8 Alternate Pathing 2.2 on the Sun Enterprise 3x00, 4x00, 5x00, and 6x00 Servers 127
c. Commit the network pathgroup entry in the database:
As shown above, you can verify the results of the
apdb(1M)
command by using
apconfig(1M)
.
d. Create the new
/etc/hostname.m
interface_name file to configure the network
when you reboot the server.
For example,
/etc/hostname.m
interface_name might contain
hmb
.
e. Remove the configuration files that correspond to the metanetwork interface:
5. If you plan to use a volume manager, such as Sun Enterprise Volume Manager™
(SEVM) or Solstice DiskSuite™ (SDS), configure the volume manager according
to the vendor’s instructions.
Caution –
Make sure that your volume manager is supported in the Solaris 7 11/99
operating environment (which is required for AP 2.2).
■
SEVM Issues
If you want to build your SEVM volumes on top of AP, you should configure your
volumes using AP metadisk paths rather than physical paths. SEVM recognizes and
properly installs existing AP metadevices with no special action required.
SEVM can encapsulate both nonboot disks and boot disks that are configured as AP
metadevices. SEVM can encapsulate AP databases without any impact on AP. Note,
however, that the standard SEVM requirements for encapsulation apply:
■
There must be an
s2
slice that represents the entire disk.
■
There must be a "small amount" of free disk space at the beginning or end of
the disk.
■
There must be two free partitions.
The partition requirement may necessitate giving up an AP database, which is
often placed in slice
s4
.
It is best to configure SEVM after you configure AP. It is beyond the scope of this
document to describe how to integrate AP with an existing SEVM configuration.
■
SDS Issues
# apdb -C
# apconfig -N
# rm -f /etc/hostname.
primary_interface_name
\
/etc/hostname.
alternate_interface_name