Go to main content

Administering an Oracle® Solaris Cluster 4.4 Configuration

Exit Print View

Updated: November 2019
 
 

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. To perform this task by using the command line, see the cluster(8CL) man page.

Before You Begin

Ensure that remote shell (rsh(1)) 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 the root role or a role that provides solaris.cluster.admin 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