How to Enable a Cluster Transport Cable
You can also accomplish this procedure by using the SunPlex Manager GUI. See the SunPlex Manager online help for more information.
This option is used to enable an already existing cluster transport cable.
Become superuser on any node in the cluster.
Enter the scsetup(1M) utility.
# scsetup
The Main Menu is displayed.
Access the Cluster Interconnect Menu by typing 2 (Cluster interconnect).
Enable the transport cable by typing 7 (Enable a transport cable).
Follow the instructions when prompted. You need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
Verify that the cable is enabled.
# scconf -p | grep cable
Example--Enabling a Cluster Transport Cable
This example shows how to enable a cluster transport cable on adapter qfe-1 located on the node phys-schost-2.
[Become superuser on any node.] [Enter the scsetup utility:] # scsetup Select Cluster interconnect>Enable a transport cable. Answer the questions when prompted. You will need the following information. You Will Need: Example: node names phys-schost-2 adapter names qfe1 junction names hub1 [Verify that the scconf command completed successfully:] scconf -c -m endpoint=phys-schost-2:qfe1,state=enabled Command completed successfully. Quit the scsetup Cluster Interconnect Menu and Main Menu. [Verify that the cable is enabled:] # scconf -p | grep cable Transport cable: phys-schost-2:qfe1@0 ethernet-1@2 Enabled Transport cable: phys-schost-3:qfe0@1 ethernet-1@3 Enabled Transport cable: phys-schost-1:qfe0@0 ethernet-1@1 Enabled |
How to Disable a Cluster Transport Cable
You can also accomplish this procedure by using the SunPlex Manager GUI. See the SunPlex Manager online help for more information.
You might need to disable a cluster transport cable to temporarily shut down a cluster interconnect path. This is useful when troubleshooting a cluster interconnect problem or when replacing cluster interconnect hardware.
When a cable is disabled, the two endpoints of the cable remain configured. An adapter cannot be removed if it is still in use as an endpoint in a transport cable.
Caution - Each cluster node needs at least one functioning transport
path to every other node in the cluster. No two nodes should be isolated from
one another. Always verify the status of a node's cluster interconnect before
disabling a cable. Only disable a cable connection after you have verified
that it is redundant; that is, that another connection is available. Disabling
a node's last remaining working cable takes the node out of cluster membership.
Become superuser on any node in the cluster.
Check the status of the cluster interconnect before disabling a cable.
# scstat -W
Caution - If you receive an error such as "path faulted"
while attempting to remove one node of a two-node cluster, investigate the
problem before continuing with this procedure. Such a problem could indicate
that a node path is unavailable. Removing the remaining good path takes the
node out of cluster membership and could result in a cluster reconfiguration.Enter the scsetup(1M) utility.
# scsetup
The Main Menu is displayed.
Access the Cluster Interconnect Menu by typing 3 (Cluster interconnect).
Disable the cable by typing 8 (Disable a transport cable).
Follow the instructions and enter the requested information. All of the components on this cluster interconnect will be disabled. You need to enter both the node and the adapter names of one of the endpoints of the cable you are trying to identify.
Verify that the cable is disabled.
# scconf -p | grep cable
Example--Disabling a Cluster Transport Cable
This example shows how to disable a cluster transport cable on adapter qfe-1 located on the node phys-schost-2.
[Become superuser on any node.] [Enter the scsetup utility:] # scsetup Select Cluster interconnect>Disable a transport cable. Answer the questions when prompted. You will need the following information. You Will Need: Example: node names phys-schost-2 adapter names qfe1 junction names hub1 [Verify that the scconf command completed successfully:] scconf -c -m endpoint=phys-schost-2:qfe1,state=disabled Command completed successfully. Quit the scsetup Cluster Interconnect Menu and Main Menu. [Verify that the cable is disabled:] # scconf -p | grep cable Transport cable: phys-schost-2:qfe1@0 ethernet-1@2 Disabled Transport cable: phys-schost-3:qfe0@1 ethernet-1@3 Enabled Transport cable: phys-schost-1:qfe0@0 ethernet-1@1 Enabled |
Administering the Public Network
Sun Cluster 3.1 supports the Solaris implementation of Internet Protocol (IP) Network Multipathing for public networks. Basic IP Network Multipathing administration is the same for both cluster and non-cluster environments. Multipathing administration is covered in the appropriate Solaris documentation. However, review the guidelines that follow before administering IP Network Multipathing in a Sun Cluster environment.
How to Administer IP Network Multipathing Groups in a Cluster
Before performing IP Network Multipathing procedures on a cluster, consider the guidelines below.
Each public network adapter must belong to a multipathing group.
The local-mac-address? variable must have a value of true for Ethernet adapters.
For multipathing groups that contain two or more adapters, you must configure a test IP address for each adapter in the group. If a multipathing group contains only one adapter, you do not need to configure a test IP address.
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.
There are no restrictions 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 scstat(1M) with the -i option.