Skip Navigation Links
Exit Print View
| Oracle Solaris Cluster System Administration Guide Oracle Solaris Cluster 4.1

Search Scope:

- This Document
- Entire Library

## Administering the Cluster Interconnects

This section provides the procedures for reconfiguring cluster interconnects, such as cluster transport adapters and cluster transport cables. These procedures require that you install Oracle Solaris Cluster software.

Most of the time, you can use the `clsetup` utility to administer the cluster transport for the cluster interconnects. See the `clsetup`(1CL) man page for more information. All cluster interconnect commands must be run from a global-cluster node.

For cluster software installation procedures, see the Oracle Solaris Cluster Software Installation Guide. For procedures about servicing cluster hardware components, see the Oracle Solaris Cluster 4.1 Hardware Administration Manual.

Note - You can usually choose to use the default port name, where appropriate, during cluster interconnect procedures. The default port name is the same as the internal node ID number of the node that hosts the adapter end of the cable.

Table 7-1 Task List: Administering the Cluster Interconnect

Task | Instructions
--- | ---
Administer the cluster transport by using `clsetup`(1CL) | How to Access the Cluster Configuration Utilities
Check the status of the cluster interconnect by using `clinterconnect status` | How to Check the Status of the Cluster Interconnect
Add a cluster transport cable, transport adapter, or switch by using `clsetup` | How to Add Cluster Transport Cables, Transport Adapters, or Transport Switches
Remove a cluster transport cable, transport adapter, or transport switch by using `clsetup` | How to Remove Cluster Transport Cables, Transport Adapters, and Transport Switches
Enable a cluster transport cable by using `clsetup` | How to Enable a Cluster Transport Cable
Disable a cluster transport cable by using `clsetup` | How to Disable a Cluster Transport Cable
Determining an transport adapter's instance number | How to Determine a Transport Adapter's Instance Number
Changing the IP address or the address range of an existing cluster | How to Change the Private Network Address or Address Range of an Existing Cluster

### Dynamic Reconfiguration With Cluster Interconnects

You must consider a few issues when completing dynamic reconfiguration (DR) operations on cluster interconnects.

- All of the requirements, procedures, and restrictions that are documented for the Oracle Solaris DR feature also apply to Oracle Solaris Cluster DR support (except for the operating system quiescence operation). Therefore, review the documentation for the Oracle Solaris DR feature before using the DR feature with Oracle Solaris Cluster software. You should review in particular the issues that affect non-network IO devices during a DR detach operation.

- The Oracle Solaris Cluster software rejects DR remove-board operations performed on active private interconnect interfaces.

- You must completely remove an active adapter from the cluster in order to perform DR on an active cluster interconnect. Use the `clsetup` menu or the appropriate commands.

| Caution - Oracle Solaris Cluster software requires that each cluster node has at least one functioning path to every other cluster node. Do not disable a private interconnect interface that supports the last path to any cluster node.

Complete the following procedures in the order indicated when performing DR operations on public network interfaces.

Table 7-2 Task Map: Dynamic Reconfiguration with Public Network Interfaces

Task | Instructions
--- | ---
1. Disable and remove the interface from the active interconnect | Dynamic Reconfiguration With Public Network Interfaces
2. Perform the DR operation on the public network interface. |

## How to Check the Status of the Cluster Interconnect

The `phys-schost#` prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

You do not need to be logged in as the `root` role to perform this procedure.

1. Check the status of the cluster interconnect.

       % clinterconnect status

2. Refer to the following table for common status messages.

   Status Message | Description and Possible Action
   --- | ---
   `Path online` | The path is currently functioning correctly. No action is necessary.
   `Path waiting` | The path is currently being initialized. No action is necessary.
   `Faulted` | The path is not functioning. This can be a transient state when paths are going between the waiting and online state. If the message persists when `clinterconnect status` is rerun, take corrective action.

Example 7-1 Checking the Status of the Cluster Interconnect

The following example shows the status of a functioning cluster interconnect.

    % clinterconnect status
    -- Cluster Transport Paths --
                        Endpoint             Endpoint             Status
                        --------             --------             ------
      Transport path:   phys-schost-1:net0   phys-schost-2:net0   Path online
      Transport path:   phys-schost-1:net4   phys-schost-2:net4   Path online
      Transport path:   phys-schost-1:net0   phys-schost-3:net0   Path online
      Transport path:   phys-schost-1:net4   phys-schost-3:net4   Path online
      Transport path:   phys-schost-2:net0   phys-schost-3:net0   Path online
      Transport path:   phys-schost-2:net4   phys-schost-3:net4   Path online

## How to Add Cluster Transport Cables, Transport Adapters, or Transport Switches

For information about the requirements for the cluster private transport, see Interconnect Requirements and Restrictions in Oracle Solaris Cluster 4.1 Hardware Administration Manual.

The `phys-schost#` prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

1. Ensure that the physical cluster transport cables are installed.

   For the procedure on installing a cluster transport cable, see the Oracle Solaris Cluster 4.1 Hardware Administration Manual.

2. Assume the `root` role on any node in the cluster.
3. Start the `clsetup` utility.

       # clsetup

   The Main Menu is displayed.

4. Type the number for the option for displaying the Cluster Interconnect Menu.
5. Type the number for the option for adding a transport cable.

   Follow the instructions and type the requested information.

6. Type the number for the option for adding the transport adapter to a node.

   Follow the instructions and type the requested information.

   If you plan to use any of the following adapters for the cluster interconnect, add the relevant entry to the `/etc/system` file on each cluster node. The entry becomes effective after the next system boot.

   Adapter | Entry
   --- | ---
   nge | set nge:nge_taskq_disable=1
   e1000g | set e1000g:e1000g_taskq_disable=1

7. Type the number for the option for adding the transport switch.

   Follow the instructions and type the requested information.

8. Verify that the cluster transport cable, transport adapter, or transport switch is added.

       # clinterconnect show node:adapter,adapternode
       # clinterconnect show node:adapter
       # clinterconnect show node:switch

Example 7-2 Adding a Cluster Transport Cable, Transport Adapter, or Transport Switch

The following example shows how to add a transport cable, transport adapter, or transport switch to a node by using the `clsetup` utility.

    [Ensure that the physical cable is installed.]
    [Start the clsetup utility:]
    # clsetup
    [Select Cluster interconnect]

    [Select either Add a transport cable,
    Add a transport adapter to a node,
    or Add a transport switch.}
    [Answer the questions when prompted.]
       [You Will Need:  ]
    [Information:       Example:[
       node names             phys-schost-1
       adapter names          net5
       switch names           hub2
       transport type         dlpi
    [Verify that the clinterconnect
     command completed successfully:]Command completed successfully.
    Quit the clsetup Cluster Interconnect Menu and Main Menu.
    [Verify that the cable, adapter, and switch are added:]
    # clinterconnect show phys-schost-1:net5,hub2
      ===Transport Cables ===
    Transport Cable:              phys-schost-1:net5@0,hub2
      Endpoint1:                  phys-schost-2:net4@0
      Endpoint2:                  hub2@2
      State:                      Enabled

    # clinterconnect show phys-schost-1:net5
    === Transport Adepters for net5
    Transport Adapter:                             net5
      Adapter State:                                 Enabled
      Adapter Transport Type:                        dlpi
      Adapter Property (device_name):                net6
      Adapter Property (device_instance):            0
      Adapter Property (lazy_free):                  1
      Adapter Property (dlpi_heartbeat_timeout):     10000
      Adpater Property (dlpi_heartbeat_quantum):     1000
      Adapter Property (nw_bandwidth):               80
      Adapter Property (bandwidth):                  70
      Adapter Property (ip_address):                 172.16.0.129
      Adapter Property (netmask):                    255.255.255.128
      Adapter Port Names:                            0
      Adapter Port STate (0):                        Enabled

    # clinterconnect show phys-schost-1:hub2

    === Transport Switches ===
    Transport Switch:                              hub2
      Switch State:                                  Enabled
      Switch Type:                                   switch
      Switch Port Names:                             1 2
      Switch Port State(1):                          Enabled
      Switch Port State(2):                          Enabled

Next Steps

To check the interconnect status of your cluster transport cable see How to Check the Status of the Cluster Interconnect.

## How to Remove Cluster Transport Cables, Transport Adapters, and Transport Switches

Use the following procedure to remove cluster transport cables, transport adapters, and transport switches from a node configuration. 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 on 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, ensure that another connection is available. Disabling a node's last remaining working cable takes the node out of cluster membership.

The `phys-schost#` prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

1. Assume the `root` role on any node in the cluster.
2. Check the status of the remaining cluster transport path.

       # clinterconnect status

   | 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 operational path takes the node out of cluster membership and could result in a cluster reconfiguration.

3. Start the `clsetup` utility.

       # clsetup

   The Main Menu is displayed.

4. Type the number for the option for accessing the Cluster Interconnect menu.
5. Type the number for the option for disabling the transport cable.

   Follow the instructions and type the requested information. You need to know the applicable node names, adapter names, and switch names.

6. Type the number for the option for removing the transport cable.

   Follow the instructions and type the requested information. You need to know the applicable node names, adapter names, and switch names.

   Note - If you are removing a physical cable, disconnect the cable between the port and the destination device.

7. Type the number for the option for removing the transport adapter from a node.

   Follow the instructions and type the requested information. You need to know the applicable node names, adapter names, and switch names.

   If you are removing a physical adapter from a node, see the Oracle Solaris Cluster 4.1 Hardware Administration Manual for hardware service procedures.

8. Type the number for the option for removing a transport switch.

   Follow the instructions and type the requested information. You need to know the applicable node names, adapter names, and switch names.

   Note - A switch cannot be removed if any of the ports are still in use as endpoints on any transport cables.

9. Verify that the cable, adapter, or switch has been removed.

       # clinterconnect show node:adapter,adapternode
       # clinterconnect show  node:adapter
       # clinterconnect show  node:switch

   The transport cable or adapter removed from the respective node should not appear in the output from this command.

Example 7-3 Removing a Transport Cable, Transport Adapter, or Transport Switch

The following example shows how to remove a transport cable, transport adapter, or transport switch by using the `clsetup` command.

    [Assume the root role on any node in the cluster.]
    [Start the utility:]
    # clsetup
    [Select Cluster interconnect.[
    [Select either Remove a transport cable,
    Remove a transport adapter to a node,
    or Remove a transport switch.[
    [Answer the questions when prompted.[
       You Will Need:
       Information            Example:
       node names             phys-schost-1
       adapter names          net0
       switch names           hub1
    [Verify that the clinterconnect
     command was completed successfully:]
    Command completed successfully.
    [Quit the clsetup utility Cluster Interconnect Menu and Main Menu.]
    [Verify that the cable, adapter, or switch is removed:]
    # clinterconnect show phys-schost-1:net5,hub2@0
     ===Transport Cables ===
    Transport Cable:                        phys-schost-1:net5,hub2@0
      Endpoint1:                            phys-schost-1:net5
      Endpoint2:                            hub2@0
      State:                                Enabled

    # clinterconnect show phys-schost-1:net5
    === Transport Adepters for net5
    Transport Adapter:                             net5
      Adapter State:                                 Enabled
      Adapter Transport Type:                        dlpi
      Adapter Property (device_name):                net6
      Adapter Property (device_instance):            0
      Adapter Property (lazy_free):                  1
      Adapter Property (dlpi_heartbeat_timeout):     10000
      Adpater Property (dlpi_heartbeat_quantum):     1000
      Adapter Property (nw_bandwidth):               80
      Adapter Property (bandwidth):                  70
      Adapter Property (ip_address):                 172.16.0.129
      Adapter Property (netmask):                    255.255.255.128
      Adapter Port Names:                            0
      Adapter Port State (0):                        Enabled

    # clinterconnect show hub2
    === Transport Switches ===
    Transport Switch:                                hub2
      State:                                            Enabled
      Type:                                             switch
      Port Names:                                       1 2
      Port State(1):                                    Enabled
      Port State(2):                                    Enabled

## How to Enable a Cluster Transport Cable

This option is used to enable an already existing cluster transport cable.

The `phys-schost#` prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

1. Assume the `root` role on any node in the cluster.
2. Start the clsetup utility.

       # clsetup

   The Main Menu is displayed.

3. Type the number for the option for accessing the Cluster Interconnect menu and press the Return key.
4. Type the number for the option for enabling the transport cable and press the Return key.

   Follow the instructions when prompted. You need to provide both the node and the adapter names of one of the endpoints of the cable that you are trying to identify.

5. Verify that the cable is enabled.

       # clinterconnect show  node:adapter,adapternode

Example 7-4 Enabling a Cluster Transport Cable

This example shows how to enable a cluster transport cable on adapter `net0`, located on the node `phys-schost-2`.

    [Assume the root role on any node.]
    [Start the clsetup utility:]
    # clsetup
    [Select Cluster interconnect>Enable a transport cable.[

    [Answer the questions when prompted.[
    [You will need the following information.[
       You Will Need:
    Information: Example:
       node names             phys-schost-2
       adapter names          net0
       switch names           hub1
    [Verify that the scinterconnect
     command was completed successfully:]

    clinterconnect  enable phys-schost-2:net0

    Command completed successfully.
    [Quit the clsetup Cluster Interconnect Menu and Main Menu.]
    [Verify that the cable is enabled:]
    # clinterconnect show  phys-schost-1:net5,hub2
      Transport cable:   phys-schost-2:net0@0 ethernet-1@2    Enabled
      Transport cable:   phys-schost-3:net5@1 ethernet-1@3    Enabled
      Transport cable:   phys-schost-1:net5@0 ethernet-1@1    Enabled

## How to Disable a Cluster Transport Cable

You might need to disable a cluster transport cable to temporarily shut down a cluster interconnect path. A temporary shutdown 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, ensure that another connection is available. Disabling a node's last remaining working cable takes the node out of cluster membership.

The `phys-schost#` prompt reflects a global-cluster prompt. Perform this procedure on a global cluster.

This procedure provides the long forms of the Oracle Solaris Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical.

1. Assume the `root` role on any node in the cluster.
2. Check the status of the cluster interconnect before disabling a cable.

       # clinterconnect status

   | 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 operational path takes the node out of cluster membership and could result in a cluster reconfiguration.

3. Start the `clsetup` utility.

       # clsetup

   The Main Menu is displayed.

4. Type the number for the option for accessing the Cluster Interconnect Menu and press the Return key.
5. Type the number for the option for disabling the transport cable and press the Return key.

   Follow the instructions and provide the requested information. All of the components on this cluster interconnect will be disabled. You need to provide both the node and the adapter names of one of the endpoints of the cable that you are trying to identify.

6. Verify that the cable is disabled.

       # clinterconnect show  node:adapter,adapternode

Example 7-5 Disabling a Cluster Transport Cable

This example shows how to disable a cluster transport cable on adapter `net0`, located on the node `phys-schost-2`.

    [Assume the root role on any node.]
    [Start the clsetup utility:]
    # clsetup
    [Select Cluster interconnect>Disable a transport cable.]

    [Answer the questions when prompted.]
    [You will need the following information.]
      [ You Will Need:]
    Information: Example:
       node names             phys-schost-2
       adapter names          net0
       switch names           hub1
    [Verify that the clinterconnect
     command was completed successfully:]
     Command completed successfully.
    [Quit the clsetup Cluster Interconnect Menu and Main Menu.]
    [Verify that the cable is disabled:]
    # clinterconnect show  -p phys-schost-1:net5,hub2
      Transport cable:   phys-schost-2:net0@0 ethernet-1@2    Disabled
      Transport cable:   phys-schost-3:net5@1 ethernet-1@3    Enabled
      Transport cable:   phys-schost-1:net5@0 ethernet-1@1    Enabled

## How to Determine a Transport Adapter's Instance Number

You need to determine a transport adapter's instance number to ensure that you add and remove the correct transport adapter through the `clsetup` command. The adapter name is a combination of the type of the adapter and the adapter's instance number.

1. Based on the slot number, find the adapter's name.

   The following screen is an example and might not reflect your hardware.

       # prtdiag
       ...
       ========================= IO Cards =========================
                                Bus  Max
        IO  Port Bus      Freq Bus  Dev,
       Type     ID  Side Slot MHz  Freq Func State Name Model
       ---- ---- ---- ---- ---- ---- ---- ----- --------------------------------
       XYZ   8    B    2    33   33  2,0  ok    xyz11c8,0-xyz11c8,d665.11c8.0.0
       XYZ   8    B    3    33   33  3,0  ok    xyz11c8,0-xyz11c8,d665.11c8.0.0
       ...

2. Using the adapter's path, find the adapter's instance number.

   The following screen is an example and might not reflect your hardware.

       # grep sci /etc/path_to_inst
       "/xyz@1f,400/pci11c8,o@2" 0 "ttt"
       "/xyz@1f,4000.pci11c8,0@4 "ttt"

3. Using the adapter's name and slot number, find the adapter's instance number.

   The following screen is an example and might not reflect your hardware.

       # prtconf
       ...
       xyz, instance #0
                    xyz11c8,0, instance #0
                   xyz11c8,0, instance #1
       ...

## How to Change the Private Network Address or Address Range of an Existing Cluster

Use this procedure to change a private network address or the range of network addresses used or both.

Before You Begin

Ensure that remote shell (`rsh`(1M)) or secure shell (`ssh`(1)) access for the `root` role is enabled to all cluster nodes.

1. Reboot all cluster nodes into noncluster mode by performing the following substeps on each cluster node:
   1. Assume a role that provides `solaris.cluster.admin` RBAC authorization on the cluster node to be started in noncluster mode.
   2. Shut down the node by using the `clnode evacuate` and `cluster shutdown` commands.

      The `clnode evacuate` command switches over all device groups from the specified node to the next-preferred node. The command also switches all resource groups from the specified node to the next-preferred node.

          # clnode evacuate  node
          # cluster shutdown -g0 -y

2. From one node, start the `clsetup` utility.

   When run in noncluster mode, the `clsetup` utility displays the Main Menu for noncluster-mode operations.

3. Choose the Change Network Addressing and Ranges for the Cluster Transport menu item.

   The `clsetup` utility displays the current private network configuration, then asks if you would like to change this configuration.

4. To change either the private network IP address or the IP address range, type `yes` and press the Return key.

   The `clsetup` utility displays the default private network IP address, `172.16.0.0`, and asks if it is okay to accept this default.

5. Change or accept the private-network IP address.
   - To accept the default private network IP address and proceed to changing the IP address range, type `yes` and press the Return key.
   - To change the default private network IP address:
     1. Type `no` in response to the `clsetup` utility question about whether it is okay to accept the default address, then press the Return key.

        The `clsetup` utility will prompt for the new private-network IP address.

     2. Type the new IP address and press the Return key.

        The `clsetup` utility displays the default netmask and then asks if it is okay to accept the default netmask.

6. Change or accept the default private network IP address range.

   The default netmask is `255.255.240.0`. This default IP address range supports up to 64 nodes, 12 zone clusters, and 10 private networks in the cluster.

   - To accept the default IP address range, type `yes` and press the Return key.
   - To change the IP address range:
     1. Type `no` in response to the `clsetup` utility's question about whether it is okay to accept the default address range, then press the Return key.

        When you decline the default netmask, the `clsetup` utility prompts you for the number of nodes and private networks, and zone clusters that you expect to configure in the cluster.

     2. Provide the number of nodes, private networks, and zone clusters that you expect to configure in the cluster.

        From these numbers, the `clsetup` utility calculates two proposed netmasks:

        - The first netmask is the minimum netmask to support the number of nodes, private networks, and zone clusters that you specified.

        - The second netmask supports twice the number of nodes, private networks, and zone clusters that you specified, to accommodate possible future growth.

     3. Specify either of the calculated netmasks, or specify a different netmask that supports the expected number of nodes, private networks, and zone clusters.
7. Type `yes` in response to the `clsetup` utility's question about proceeding with the update.
8. When finished, exit the `clsetup` utility.
9. Reboot each cluster node back into cluster mode by completing the following substeps for each cluster node:
   1. Boot the node.

      - On SPARC based systems, run the following command.

            ok boot

      - On x86 based systems, run the following commands.

        When the GRUB menu is displayed, select the appropriate Oracle Solaris entry and press Enter.

10. Verify that the node has booted without error, and is online.

        # cluster status -t node

Copyright © 2000, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |