How to Change the Non-Global Zone Private Host Name

Use this procedure to change the private host name of a cluster non-global zone after installation has been completed.

Private host names are assigned during initial cluster installation. The private host name takes the form clusternode< nodeid>-priv, for example: clusternode3-priv . Change a private host name only if the name is already in use in the domain.

Do not attempt to assign IP addresses to new private host names. The clustering software assigns them.

This procedure provides the long forms of the Sun Cluster commands. Most commands also have short forms. Except for the long and short forms of the command names, the commands are identical. For a list of the commands and their short forms, see Appendix A, Sun Cluster Object-Oriented Commands.

1. Disable, on all nodes in the cluster, any data service resources or other applications that might cache private host names.

   # clresource disable resource1, resource2

   Include the following in the applications you disable.

   • HA-DNS and HA-NFS services, if configured

   • Any application that has been custom configured to use the private host name

   • Any application that is being used by clients over the private interconnect

   See the clresource(1CL) man page and the Sun Cluster Data Services Planning and Administration Guide for Solaris OS for information about using the clresource command.

2. Run the clsetup(1CL) utility to change the private host name of the appropriate non-global zone.

   You need to perform this step only from one of the nodes in the cluster.

   ---

   Note –

   When selecting a new private host name, ensure that the name is unique to the cluster.

   ---

3. Type the number that corresponds to the option for private host names and press the Return key.

4. Type the number that corresponds to the option for adding a zone private hostname and press the Return key.

   There is no default for a non-global zone private host name. You will need to provide a host name.

5. Type the number that corresponds to the option for changing a zone private hostname.

   Answer the questions when prompted. You are asked for the name of the non-global zone whose private host name is being changed (clusternode< nodeid>-priv), and the new private host name.

6. Flush the name service cache.

   Perform this step on each node in the cluster. Flushing prevents the cluster applications and data services from trying to access the old private host name.

   # nscd -i hosts

7. Enable all data service resources and other applications that were disabled in Step 1.