JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Administration: IP Services     Oracle Solaris 10 1/13 Information Library
search filter icon
search icon

Document Information


Part I Introducing System Administration: IP Services

1.  Oracle Solaris TCP/IP Protocol Suite (Overview)

Part II TCP/IP Administration

2.  Planning Your TCP/IP Network (Tasks)

3.  Introducing IPv6 (Overview)

4.  Planning an IPv6 Network (Tasks)

5.  Configuring TCP/IP Network Services and IPv4 Addressing (Tasks)

6.  Administering Network Interfaces (Tasks)

7.  Configuring an IPv6 Network (Tasks)

8.  Administering a TCP/IP Network (Tasks)

9.  Troubleshooting Network Problems (Tasks)

10.  TCP/IP and IPv4 in Depth (Reference)

11.  IPv6 in Depth (Reference)


12.  About DHCP (Overview)

13.  Planning for DHCP Service (Tasks)

14.  Configuring the DHCP Service (Tasks)

15.  Administering DHCP (Tasks)

16.  Configuring and Administering the DHCP Client

17.  Troubleshooting DHCP (Reference)

18.  DHCP Commands and Files (Reference)

Part IV IP Security

19.  IP Security Architecture (Overview)

20.  Configuring IPsec (Tasks)

21.  IP Security Architecture (Reference)

22.  Internet Key Exchange (Overview)

23.  Configuring IKE (Tasks)

24.  Internet Key Exchange (Reference)

25.  IP Filter in Oracle Solaris (Overview)

26.  IP Filter (Tasks)


27.  Introducing IPMP (Overview)

28.  Administering IPMP (Tasks)

Configuring IPMP (Task Maps)

Configuring and Administering IPMP Groups (Task Map)

Administering IPMP on Interfaces That Support Dynamic Reconfiguration (Task Map)

Using IPMP Groups For High Availability

Planning for an IPMP Group

How to Plan for an IPMP Group

Configuring IPMP Groups

How to Configure an IPMP Group With Multiple Interfaces

Configuring Target Systems

Configuring Standby Interfaces

Configuring IPMP Groups With a Single Physical Interface

How to Configure a Single Interface IPMP Group

Maintaining IPMP Groups

How to Display the IPMP Group Membership of an Interface

How to Add an Interface to an IPMP Group

How to Remove an Interface From an IPMP Group

How to Move an Interface From One IPMP Group to Another Group

Replacing a Failed Physical Interface on Systems That Support Dynamic Reconfiguration

How to Remove a Physical Interface That Has Failed (DR-Detach)

How to Replace a Physical Interface That Has Failed (DR-Attach)

Recovering a Physical Interface That Was Not Present at System Boot

How to Recover a Physical Interface That Was Not Present at System Boot

Modifying IPMP Configurations

How to Configure the /etc/default/mpathd File

Part VI IP Quality of Service (IPQoS)

29.  Introducing IPQoS (Overview)

30.  Planning for an IPQoS-Enabled Network (Tasks)

31.  Creating the IPQoS Configuration File (Tasks)

32.  Starting and Maintaining IPQoS (Tasks)

33.  Using Flow Accounting and Statistics Gathering (Tasks)

34.  IPQoS in Detail (Reference)



Recovering a Physical Interface That Was Not Present at System Boot

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.

How to Recover a Physical Interface That Was Not Present at System Boot

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:

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.

  1. 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 Oracle Solaris Administration: Basic Administration.

  2. Retrieve the failed network information from the failure error message of the console log.

    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.

  3. Attach the physical interface to the system.

    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

  4. Refer to the message content from Step 2. If the addresses could not be moved, go to Step 6. If the addresses were moved, continue to Step 5.
  5. Unplumb the logical interfaces that were configured as part of the failover process.
    1. Review the contents of the /etc/hostname.moved-from-interface file to determine what logical interfaces were configured as part of the failover process.
    2. Unplumb each failover IP address.
      # 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 -failover up group one
      addif failover up
      addif failover up

      To unplumb each failover IP address, you would type the following commands:

      # ifconfig hme0 removeif
      # ifconfig hme0 removeif
  6. Reconfigure the IPv4 information for the replaced physical interface by typing the following command for each interface that was removed:
    # ifconfig removed-from-NIC <parameters>

    For example, you would type the following commands:

    # ifconfig hme1 inet plumb
    # ifconfig hme1 inet -failover up group one
    # ifconfig hme1 addif failover up
    # ifconfig hme1 addif failover up