How to Remove Transport Cables and Transport Junctions
This section contains the procedure about how to remove an unused transport cable or transport junction (switch) from a node in a running cluster.
If Virtual Local Area Networks (VLANs) are configured, more than one cluster might be impacted by removing a transport junction. Ensure that all clusters are prepared for the removal of a transport junction.
Caution - You must maintain at least one cluster interconnect between the nodes of a cluster. The cluster does not function without a working cluster interconnect.
Check to see whether the transport cable, transport junction, or transport cable and transport junction that you are removing appears in the Sun Cluster configuration.
If the interconnect component that you want to remove appears in the Sun Cluster configuration, remove the interconnect component from the Sun Cluster configuration. To remove an interconnect component, follow the interconnect administration procedures in your Sun Cluster system administration documentation before going to Step 2.
If the interconnect component that you want to remove does not appear in the Sun Cluster configuration, go to Step 2.
Shut down the node that is connected to the transport cable, transport junction, or transport cable and transport junction that you are removing.
For the procedure about how to shut down a node, see your Sun Cluster system administration documentation.
Disconnect the transport cable, transport junction, or transport cable and transport junction from the other cluster devices.
For the procedure about how to disconnect cables from transport adapters, see the documentation that shipped with your host adapter and node.
Perform a reconfiguration boot to create the new Solaris device files and links.
Maintaining Sun Fire Link Interconnect Hardware in a Running Cluster
This section contains the procedure about how to maintain Sun Fire Link interconnect hardware.
How to Replace Sun Fire Link Interconnect Hardware
Use this procedure to replace any component of the Sun Fire Link interconnect. This procedure requires you to switch data path loads before you replace interconnect hardware.
Caution - You must maintain at least one cluster interconnect between the nodes of a cluster. The cluster does not function without a working cluster interconnect. You can check the status of the interconnect with the command. scstat --W. For more details on checking the status
of the cluster interconnect, see your Sun Cluster system administration documentation.
Determine whether your node is enabled with the Solaris dynamic reconfiguration (DR) feature.
If your node is enabled with DR, go to Step 2.
If your node does not have DR enabled, shutdown the node.
For the full procedure about how to shut down a node, see your Sun Cluster system administration documentation.
Disconnect the data path component from the other cluster devices.
For the procedure about how to disconnect Sun Fire Link components, see the Sun Fire Link Service Manual.
Connect the new data path component to the other cluster devices.
For the procedure about how to connect Sun Fire Link components, see your Sun Fire Link Service Manual.
If you shut down the node in Step 1, boot the node (otherwise, skip this step).
For more information, see your Sun Cluster system administration documentation.
Configuring VLANs as Private Interconnect Networks
Sun Cluster software supports the use of private interconnect networks over switch-based virtual local area networks (VLAN). In a switch-based VLAN environment, Sun Cluster software enables multiple clusters and nonclustered systems to share Ethernet transport junction (switch) in two different configurations.
The implementation of switch-based VLAN environments is vendor-specific. Since each switch manufacturer implements VLAN differently, the following guidelines address Sun Cluster software requirements about how to configure VLANs with cluster interconnects.
You must understand your capacity needs before you set up a VLAN configuration. You must know the minimum bandwidth necessary for your interconnect and application traffic.
For the best results, set the Quality of Service (QOS) level for each VLAN to accommodate basic cluster traffic plus the desired application traffic. Ensure that the bandwidth allocated to each VLAN extends from node to node.
To determine the basic cluster traffic requirements, use the following equation. In this equation, n equals the number of nodes in the configuration, and s equals the number of switches per VLAN.
n (s-1) x 10Mb
Interconnect traffic must be placed in the highest priority queue.
All ports must be equally serviced, similar to a round robin or first in first out model.
You must verify that you have properly configured your VLANs to prevent path timeouts.
The first VLAN configuration enables nodes from multiple clusters to send interconnect traffic across one pair of Ethernet transport junctions. Sun Cluster software requires the use of at least two transport junctions to eliminate a single point of failure. The following figure is an example of the first VLAN configuration in a two-node cluster. VLAN configurations are not limited to two-node clusters.
Figure 3-5 First VLAN configuration
The second VLAN configuration also uses the same transport junctions for the interconnect traffic of multiple clusters. However, the second VLAN configuration requires two pairs of transport junctions that are connected by links. This configuration allows VLANs to be supported in a campus cluster configuration with the same restrictions as other campus cluster configurations. The following figure illustrates the second VLAN configuration.
Figure 3-6 Second VLAN configuration
