This section contains procedures that relate to administering systems that support dynamic reconfiguration (DR).
This procedure explains how to replace a physical card on a system that supports DR. The procedure assumes the following conditions:
You assigned administratively chosen names to the data links over which you configured the IP interfaces. These interfaces are subitops0 and subitops1.
Both interfaces belong to the IPMP group, itops0.
The interface subitops0 contains a test address.
The interface subitops0 has failed, and you need to remove subitops0's underlying card, ce.
You are replacing the ce card with a bge card.
The configuration files correspond to the interfaces and use the interfaces' customized link names, thus /etc/hostname.subitops0 and /etc/hostname.subitops1.
The procedures for performing DR vary with the type of system. Therefore, make sure that you complete the following:
Ensure that your system supports DR.
Consult the appropriate manual that describes DR procedures on your system. For Sun hardware, all systems that support DR are servers. To locate current DR documentation on Sun systems, search for “dynamic reconfiguration” on http://docs.sun.com.
The steps in the following procedure refer only to aspects of DR that are specifically related to IPMP and the use of link names. The procedure does not contain the complete steps to perform DR. For example, some layers beyond the IP layer require manual configuration steps, such as for ATM and other services, if the configuration is not automated. Follow the appropriate DR documentation for your system.
On the system with the IPMP group configuration, assume the Primary Administrator role or become superuser.
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 System Administration Guide: Basic Administration.
Perform the appropriate DR steps to remove the failed NIC from the system.
If you are removing the card without intending to insert a replacement, then skip the rest of the steps after you remove the card.
If you are replacing a card, then proceed to the subsequent steps .
Make sure that the replacement NIC is not being referenced by other configurations in the system.
For example, the replacement NIC you install is bge0. If a /etc/hostname.bge0 file exists on the system, remove that file.
# rm /etc/hostname.bge0
Replace the default link name of the replacement NIC with the link name of the failed card.
By default, the link name of the bge card that replaces the failed ce card is bgen, where n is the instance number, such as bge0.
# dladm rename-link bge0 subitops0
This step transfers the network configuration of subitops0 to bge0.
Attach the replacement NIC to the system.
Complete the DR process by enabling the new NIC's resources to become available for use.
For example, you use the cfgadm command to perform this step. For more information, see the cfgadm(1M) man page.
After this step, the new interface is configured with the test address, added as an underlying interface of the IPMP group, and deployed either as an active or a standby interface, all depending on the configurations that are specified in /etc/hostname.subitops0. The kernel can then allocate data addresses to this new interface according to the contents of the /etc/hostname.ipmp-interface configuration file.
Certain systems might have the following configurations:
An IPMP group is configured with underlying IP interfaces
A /etc/hostname.interface file exists for one underlying IP interface.
The physical hardware that is associated with the /etc/hostname file is missing.
With the new IPMP implementation where data addresses belong to the IPMP interface, recovering the missing interface becomes automatic. During system boot, the boot script constructs a list of failed interfaces, including interfaces that are missing. Based on the /etc/hostname file of the IPMP interface as well as the hostname files of the underlying IP interfaces, the boot script can determine to which IPMP group an interface belongs. When the missing interface is subsequently dynamically reconfigured on the system, the script then automatically adds that interface to the appropriate IPMP group and the interface becomes immediately available for use.