Part I TCP/IP Administration
1. Solaris TCPIP Protocol Suite (Overview)
2. Planning an IPv4 Addressing Scheme (Tasks
3. Planning an IPv6 Addressing Scheme (Overview)
4. Planning an IPv6 Network (Tasks)
5. Configuring TCP/IP Network Services and IPv4 Addressing (Tasks)
6. Administering Network Interfaces (Tasks)
7. Enabling IPv6 on a 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)
Part II DHCP
12. About Solaris DHCP (Overview)
13. Planning for DHCP Service (Tasks)
14. Configuring the DHCP Service (Tasks)
15. Administering DHCP (Tasks)
16. Configuring and Administering DHCP Clients
17. Troubleshooting DHCP (Reference)
18. DHCP Commands and Files (Reference)
Part III 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. Solaris IP Filter (Overview)
26. Solaris IP Filter (Tasks)
Part IV Mobile IP
27. Mobile IP (Overview)
28. Administering Mobile IP (Tasks)
29. Mobile IP Files and Commands (Reference)
Part V IPMP
30. Introducing IPMP (Overview)
31. Administering IPMP (Tasks)
Configuring IPMP (Task Maps)
Configuring IPMP Groups
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)
32. Introducing IPQoS (Overview)
33. Planning for an IPQoS-Enabled Network (Tasks)
34. Creating the IPQoS Configuration File (Tasks)
35. Starting and Maintaining IPQoS (Tasks)
36. Using Flow Accounting and Statistics Gathering (Tasks)
37. IPQoS in Detail (Reference)
Modifying the /etc/default/mpathd IPMP Configuration File
Use the IPMP configuration file /etc/default/mpathd to configure the following system-wide parameters for
These parameters apply to all IPMP groups that are created on an
How to Configure the /etc/default/mpathd File
- 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.
- Edit the /etc/default/mpathd file.
- (Optional) Type the new value for the FAILURE_DETECTION_TIME parameter.
where n is the amount of time in seconds for ICMP probes to
detect whether an interface failure has occurred. The default is 10 seconds.
- (Optional) Type the new value for the TRACK_INTERFACES_ONLY_WITH_GROUPS parameter.
TRACK_INTERFACES_ONLY_WITH_GROUPS=[yes | no]
yes- The yes value is the default behavior of IPMP. This parameter causes IPMP to ignore network interfaces that are not configured into an IPMP group.
no - The no value sets failure and repair detection for all network interfaces, regardless of whether they are configured into an IPMP group. However, when a failure or repair is detected on an interface that is not configured into an IPMP group, no failover or failback occurs. Therefore, theno value is only useful for reporting failures and does not directly improve network availability.
- (Optional) Type the new value for the FAILBACK parameter.
FAILBACK=[yes | no]
yes- The yes value is the default failback behavior of IPMP. When the repair of a failed interface is detected, network access fails back to the repaired interface, as described in IPMP Failure Detection and Recovery Features.
no - The no indicates that data traffic does not move back to a repaired interface. When a failed interfaces is detected as repaired, the INACTIVE flag of ifconfig is set. This flag indicates that the interface is currently not to be used for data traffic. The interface can still be used for probe traffic.
For example, suppose an IPMP group consists of two interfaces, ce0 and ce1. Then assume that the value FAILBACK=no is set in the mpathd file. If ce0 fails, its traffic fails over to ce1, as is the expected behavior of IPMP. However, when IPMP detects that ce0 is repaired, traffic does not fail back from ce1, due to the FAILBACK=no parameter in the mpathd file. ce0 retains its INACTIVE status and is not used for traffic unless the ce1 interface fails.
- Restart the in.mpathd daemon.
# pkill -HUP in.mpathd