sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
2. Chapter 10 # Adding a Node to a Cluster Created by the SMCT For information about how to add a node to a cluster created by the SMCT, see the following sections. Adding a Predefined Diskless Node to a Cluster Created by the SMCT Adding a Predefined Dataless Node to a Cluster Created by the SMCT Adding an Undefined Node to a Cluster Created by the SMCT ## Adding a Predefined Diskless Node to a Cluster Created by the SMCT ### To Add a Predefined Diskless Node to a Cluster Created by the SMCT Log in to a peer node as a superuser. Determine what nodes are currently running in the cluster:
       # nhcmmstat -c all
6. The `nhcmmstat` tool returns information about the nodes currently running in the cluster. This command does not provide information about nodes that are physically present in the cluster, but are down. Identify the node group and `nodeid` of the node that you want to add. Examine the `cluster.conf` file. The predefined node is present in the `cluster.conf` file, but not present in the output of Step 2. Verify that the configuration of the node that you want to add corresponds to that of the predefined node. Examine the `machine.conf` file to identify the type of board and network interface card for the predefined node: If the configuration in the `machine.conf` file corresponds to the configuration of the node that you want to add, go to Step 5. If the configuration in the `machine.conf` file does not correspond to the configuration of the node that you want to add, see Adding an Undefined Node to a Cluster Created by the SMCT. Connect the network interfaces (NIC0 and NIC1) of the new node to the switches. For information, see "Connecting the Cluster Hardware for SMCT Installation" in the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide. Access the console of the new node and obtain the `ok` prompt:
       # Control-]
       telnet> send brk
       Type  'go' to resume
       ok>
7. On the console of the new node, configure the OBP parameters:
       ok> setenv local-mac-address ? true
       ok> setenv auto-boot-retry? true
       ok> setenv diag-switch? false
       ok> setenv boot-device net:dhcp,,,,,5 net2:dhcp,,,,,5
   If the boot policy set in the `cluster.conf` file is `STATIC_CLIENT_ID_POLICY`, specify the client-ID. See To Configure DHCP Client ID Boot Policy for a Diskless Node.
       ok> setenv dhcp-clientid client-ID
8. Boot the new node:
       ok> boot
10. Become superuser on the new node. Verify that the node is configured correctly:
        # nhadm check
2. ## Adding a Predefined Dataless Node to a Cluster Created by the SMCT ### To Add a Predefined Dataless Node to a Cluster Created by the SMCT Log in to a peer node as superuser. Determine what nodes are currently running in the cluster:
       # nhcmmstat -c all
5. The `nhcmmstat` tool returns information about the nodes currently running in the cluster. This command does not provide information about nodes that are physically present in the cluster, but are down. Identify the node group and `nodeid` of the node that you want to add. Examine the `cluster.conf` file. The predefined node is present in the `cluster.conf` file, but not present in the output of Step 2. Verify that the configuration of the node that you want to add corresponds to that of the predefined node. Examine the `machine.conf` file to identify the type of board, disk, and network interface card for the predefined node. Configure the OBP parameters:
       ok> setenv local-mac-address ? true
       ok> setenv auto-boot-retry? true
       ok> setenv diag-switch? false
9. Verify that the installation server and the new node are on the same subnet and use the same netmask. Identify the network identity and netmask identity for the new node by examining the `network.conf` file. Identify the network identity and netmask identity for the installation server by examining the `install-server.conf` file. Compare the values found in Step a with those found in Step c. If the values are the same, the installation server and the new node are on the same subnet and use the same netmask. If the values are not the same, modify the content of the `install-server.conf` file. Then repeat stage 3 of the SMCT deployment process. For information, see Chapter 7, Configuration Stage 3: Configuring the Flash Archive for Deployment. Confirm that the hardware is correctly configured. For information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide. Check that the flash archive of the associated node group exists, and do one of the following: If your flash archive does not exist, rebuild the archive. For information, see Chapter 5, Configuration Stage 1: Creating a Generic Flash Archive. If your flash archive exists but the deployment parameters must be updated, see Chapter 7, Configuration Stage 3: Configuring the Flash Archive for Deployment. If your flash archive exists and the deployment parameters are correct, go to Step 8. Connect the two Ethernet interfaces (NIC0 and NIC1) of the node to the switches. For information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide. Access the console of the new node and obtain the `ok` prompt:
       # Control-]
       telnet> send brk
       Type  'go' to resume
       ok>
10. On the console of the new node, install the flash archive:
        ok> boot net - install
12. Become superuser on the new node. Verify that the node is configured correctly:
        # nhadm check
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems