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

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

Chapter 9 Alternate Pathing 2.2 on the Sun Enterprise 10000 Server 145
c. Remove all direct usage of both members of the network pathgroups.
If the physical interface is currently plumbed, and it is not the interface that you
will be using as you run commands to configure the metanetwork, you can
unplumb the physical interface by using the
ifconfig(1M)
command.
d. Create an
/etc/hostname.m
network_interface_name file for any metanetworks
that you want to configure when the domain is rebooted.
4. Create the AP metanetwork for the primary network.
a. View the contents of the
/etc/nodename
and
/etc/hostname.
interface_name
files to verify that the interface name is the same.
b. Create the primary network pathgroup.
In this example,
-c
creates the new primary network pathgroup,
-p
designates
the primary network path, and
-a
designates the alternate path.
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 domain.
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).
# apnet -c -p
network_interface
-a
network_interface
# apdb -C
# apconfig -N
# rm -f /etc/hostname.
primary_interface_name
\
/etc/hostname.
alternate_interface_name