|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris Administration: IP Services Oracle Solaris 10 1/13 Information Library|
Note - The following procedure pertains only to IP layers that are configured by using the ifconfig command. Layers before or after the IP layer, such as ATM or other services, require specific manual steps if the layers are not automated. The specific steps in the next procedure are used to unconfigure interfaces during predetachment and to configure interfaces after postattachment.
Recovery after dynamic reconfiguration is automatic for an interface that is part of the I/O board on a Sun Fire™ platform. If the NIC is a Sun Crypto Accelerator I - cPCI board, the recovery is also automatic. Consequently, the following steps are not required for an interface that is coming back as part of a DR operation. For more information on the Sun Fire x800 and Sun Fire 15000 systems, see the cfgadm_sbd(1M) man page. The physical interface fails back to the configuration that is specified in the /etc/hostname.interface file. See Using IPMP Groups For High Availability for details on how to configure interfaces to preserve the configuration across reboots.
Note - On Sun Fire legacy (Exx00) systems, DR detachments are still subject to manual procedures. However, DR attachments are automated.
You must complete the following procedure before you recover a physical interface that was not present at system boot. The example in this procedure has the following configuration:
Physical interfaces hme0 and hme1 are the interfaces.
Both interfaces are in the same IPMP group.
hme0 was not installed at system boot.
Note - The failback of IP addresses during the recovery of a failed physical interface takes up to three minutes. This time might vary, depending on network traffic. The time also depends on the stability of the incoming interface to fail back the failed-over interfaces by the in.mpathd daemon.
The Primary Administrator role includes the Primary Administrator profile. To create the role and assign the role to a user, see Chapter 2, Working With the Solaris Management Console (Tasks), in Oracle Solaris Administration: Basic Administration.
See the syslog(3C)man page. The error message might be similar to the following:
moving addresses from failed IPv4 interfaces: hme1 (moved to hme0)
This message indicates that the IPv4 addresses on the failed interface hme1 have failed over to the hme0 interface.
Alternatively, you might receive the following similar message:
moving addresses from failed IPv4 interfaces: hme1 (couldn't move, no alternative interface)
This message indicates that no active interface could be found in the same group as failed interface hme1. Therefore, the IPv4 addresses on hme1 could not fail over.
Refer to the following for instructions on how to replace the physical interface:
cfgadm(1M) man page
Sun Enterprise 10000 DR Configuration Guide
Sun Enterprise 6x00, 5x00, 4x00, and 3x00 Systems Dynamic Reconfiguration User's Guide
# ifconfig moved-to-interface removeif moved-ip-address
Note - Failover addresses are marked with the failover parameter, or are not marked with the -failover parameter. You do not need to unplumb IP addresses that are marked -failover.
For example, assume that the contents of the /etc/hostname.hme0 file contains the following lines:
inet 10.0.0.4 -failover up group one addif 10.0.0.5 failover up addif 10.0.0.6 failover up
To unplumb each failover IP address, you would type the following commands:
# ifconfig hme0 removeif 10.0.0.5 # ifconfig hme0 removeif 10.0.0.6
# ifconfig removed-from-NIC <parameters>
For example, you would type the following commands:
# ifconfig hme1 inet plumb # ifconfig hme1 inet 10.0.0.4 -failover up group one # ifconfig hme1 addif 10.0.0.5 failover up # ifconfig hme1 addif 10.0.0.6 failover up