Sun Cluster 3.1 4/04, Sun Cluster 3.1 8/05, and Sun Cluster 3.2 support the Solaris software implementation of Internet Protocol (IP) Network Multipathing for public networks. Basic IP Network Multipathing administration is the same for both cluster and noncluster environments. Multipathing administration is covered in the appropriate Solaris OS documentation. However, review the guidelines that follow before administering IP Network Multipathing in a Sun Cluster environment.
Before performing IP Network Multipathing procedures on a cluster, consider the following guidelines.
Each public network adapter must belong to a multipathing group.
The local-mac-address? variable must have a value of true for Ethernet adapters.
You must configure a test IP address for each adapter in the following kinds of multipathing groups:
All multiple-adapter multipathing groups in a cluster that runs on the Solaris 9 or Solaris 10 OS. Single-adapter multipathing groups on the Solaris 9 or Solaris 10 OS do not require test IP addresses.
Test IP addresses for all adapters in the same multipathing group must belong to a single IP subnet.
Test IP addresses must not be used by normal applications because they are not highly available.
No restrictions are placed on multipathing group naming. However, when configuring a resource group, the netiflist naming convention is any multipathing name followed by either the nodeID number or the node name. For example, given a multipathing group named sc_ipmp0 , the netiflist naming could be either sc_ipmp0@1 or sc_ipmp0@phys-schost-1, where the adapter is on the node phys-schost-1, which has the nodeID of 1.
Avoid unconfiguring (unplumbing) or bringing down an adapter of an IP Network Multipathing group without first switching over the IP addresses from the adapter to be removed to an alternate adapter in the group, using the if_mpadm(1M) command.
Avoid rewiring adapters to different subnets without first removing them from their respective multipathing groups.
Logical adapter operations can be done on an adapter even if monitoring is on for the multipathing group.
You must maintain at least one public network connection for each node in the cluster. The cluster is inaccessible without a public network connection.
To view the status of IP Network Multipathing groups on a cluster, use the command.clinterconnect status command
For more information about IP Network Multipathing, see the appropriate documentation in the Solaris OS system administration documentation set.
Table 7–3 Task Map: Administering the Public Network
Solaris Operating System Release |
Instructions |
---|---|
SPARC: Solaris 9 Operating System |
“IP Network Multipathing Topics” in System Administration Guide: IP Services |
Solaris 10 Operating System |
“IP Network Multipathing Topics” in System Administration Guide: IP Services |
For cluster software installation procedures, see the Sun Cluster Software Installation Guide for Solaris OS. For procedures about servicing public networking hardware components, see the Sun Cluster 3.1 - 3.2 Hardware Administration Manual for Solaris OS.
You must consider a few issues when completing dynamic reconfiguration (DR) operations on public network interfaces in a cluster.
All of the requirements, procedures, and restrictions that are documented for the Solaris DR feature also apply to Sun Cluster DR support (except for the operating system quiescence operation). Therefore, review the documentation for the Solaris DR feature before using the DR feature with Sun Cluster software. You should review in particular the issues that affect nonnetwork IO devices during a DR detach operation.
DR remove-board operations can succeed only when public network interfaces are not active. Before removing an active public network interface, switch the IP addresses from the adapter to be removed to another adapter in the multipathing group, using the if_mpadm(1M) command.
If you try to remove a public network interface card without having properly disabled it as an active network interface, Sun Cluster rejects the operation and identifies the interface that would be affected by the operation.
For multipathing groups with two adapters, if the remaining network adapter fails while you are performing the DR remove operation on the disabled network adapter, availability is impacted. The remaining adapter has no place to fail over for the duration of the DR operation.
Complete the following procedures in the order indicated when performing DR operations on public network interfaces.
Table 7–4 Task Map: Dynamic Reconfiguration With Public Network Interfaces
Task |
Instructions |
---|---|
1. Switch the IP addresses from the adapter to be removed to another adapter in the multipathing group, using the if_mpadm |
if_mpadm(1M) man page. The appropriate Solaris OS documentation: Solaris 9: “IP Network Multipathing Topics” in System Administration Guide: IP Services Solaris 10:Part VI, IPMP, in System Administration Guide: IP Services |
2. Remove the adapter from the multipathing group by using the ifconfig command |
The appropriate Solaris documentation: Solaris 9: “IP Network Multipathing Topics” in System Administration Guide: IP Services ifconfig(1M) man page Solaris 10: Part VI, IPMP, in System Administration Guide: IP Services |
3. Perform the DR operation on the public network interface |
Sun Enterprise 10000 DR Configuration Guide and the Sun Enterprise 10000 Dynamic Reconfiguration Reference Manual (from the Solaris 9 on Sun Hardware, and Solaris 10 on Sun Hardware collections) |