| Netra™ High Availability Suite 3.0 1/08 Foundation Services Cluster Administration Guide | 
   |
| C H A P T E R 12 |
Follow these guidelines before replacing hardware in a cluster:
Before replacing hardware on the master node, perform a switchover and then replace the hardware on the vice-master node.
Replace hardware of one type with hardware of the same type, for the following reasons:
The vice-master node and master node must have the same hardware and software configuration.
If several nodes are running the same applications, the nodes might require the same hardware.
To replace hardware of one type with hardware of another type, you must reinstall the node with a configuration adapted to the new hardware type.
Perform one of the following procedures for each item of hardware that you change:
If you change one item of hardware, perform the procedure for that type of hardware. For example, if you replace a disk, perform only the procedure to change the disk.
If you change a board that contains Ethernet cards, perform the procedure to change the board and the procedure to change the Ethernet card.
If you change a board that contains Ethernet cards and a disk, perform the procedure to change the board, the procedure to change the Ethernet cards, and the procedure to change the disk.
The following table points to the procedures for replacing boards, Ethernet cards, and disks, for each type of node.
| Node Type | Hardware Type | For Information |
|---|---|---|
| Vice-master | CPU Board | Replacing a CPU Board on a Node |
| Ethernet Card | Replacing Ethernet Cards on a Vice-Master or Dataless Node | |
| Disk | Replacing the Disk on the Vice-Master Node | |
| Diskless | CPU Board | Replacing a CPU Board on a Node or Replacing a CPU Board on a Diskless Node |
| Ethernet Card | Replacing Ethernet Cards on a Diskless Node | |
| Disk | N/A | |
| Dataless | CPU Board | Replacing a CPU Board on a Node |
| Ethernet Card | Replacing Ethernet Cards on a Vice-Master or Dataless Node | |
| Disk | Replacing a Dataless Node Disk |
To replace the board on the vice-master node, a diskless node, or a dataless node, perform the following procedure. If the node is a diskless node that is using the DHCP client ID boot policy, perform the procedure in Replacing a CPU Board on a Diskless Node.
Verify that the new board is of the same type as the old board.
Replace the board using information in the hardware documentation at http://www.sun.com/products-n-solutions/hardware/docs/.
Configure the OpenBoot
PROM
parameters.
Note - For x64 platforms, refer to the hardware documentation for information about performing tasks that reference OpenBoot PROM commands and, therefore, apply only to the UltraSPARC architecture. |
The following examples show the OpenBoot PROM parameters for an UltraSPARC-based diskless node and an UltraSPARC®-based master-eligible node.
An UltraSPARC diskless node has the following OpenBoot PROM parameters:
ok> setenv local-mac-address? true ok> setenv auto-boot? true ok> setenv diag-switch? false ok> setenv boot-device net:dhcp,,,,,5 net2:dhcp,,,,,5 |
An UltraSPARC-based master-eligible node or dataless node has the following OpenBoot PROM parameters:
ok> setenv local-mac-address? true ok> setenv auto-boot? true ok> setenv diag-switch? false ok> setenv boot-device disk net |
Note - If the auto-boot-retry variable exists on your system, it must be set to true; if it does not exist on your system, disregard references to it in the preceding examples. |
ok> boot |
Verify that the node is configured correctly:
# nhadm check |
To replace the board on a diskless node that is using the DHCP static boot policy, perform the following procedure.
|
This procedure is an example of how to replace a board on a diskless node in a Netra CT 410, Netra CT 810 configuration. For information specific to your hardware configuration, see the hardware documentation.
Retrieve the client identifier in ASCII format, for the diskless node.
If the node is running, you can retrieve the client identifier for the diskless node, as follows.
Perform Step 1 to Step 5 of To Replace a Board on a Node.
Define the client identifier for the new diskless node:
ok> setenv dhcp-clientid client-id-name |
Perform Step 6 to Step 8 of To Replace a Board on a Node.
Identify the IP address (the Ethernet address couplet for the diskless nodes that are to be replaced).
Replace the diskless nodes using information in the hardware documentation at http://www.sun.com/products-n-solutions/hardware/docs/.
Record the Ethernet addresses of the new network interfaces on the new diskless nodes.
To find the Ethernet addresses of the network cards, perform the following steps:
Identify the Ethernet address of NIC0:
ok> banner |
The Ethernet address of NIC0 is provided in the output.
The Ethernet address of NIC1 is derived as follows:
NIC0 + 0x1 |
For example, if the output of the banner command is this:
Netra CP3010, No Keyboard Copyright 2005 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.21.0, 2048 MB memory installed, Serial #64803169. Ethernet address 0:3:ba:dc:d1:61, Host ID: 83dcd161. |
The Ethernet address of NIC0 is 8:0:20:fa:2a:6e, and the Ethernet address of NIC1 is 8:0:20:fa:2a:6f.
Ethernet address 8:0:20:f9:b3:60, Host ID: 80f9b360 |
In the DHCP configuration files, the Ethernet addresses of NIC0 and NIC1 are given as 01080020FA2A6E and 01080020FA2A6F, respectively.
For another example, the output of the banner command is as follows:
In the DHCP configuration files in the /SUNWcgha/remote/var/dhcp/ directory, the Ethernet addresses of NIC0 and NIC1 are given as 01080020F9B360 and 01080020F9B361, respectively.
Modify the DHCP configuration for NIC0:
# pntadm -M NIC0IP-address -i newEthernet-address \-f 'PERMANENT+MANUAL' -m NIC0IP-address subnet1 |
The parameters of this command are as follows:
| NIC0IP-address | is the IP address of the NIC0 interface |
| newEthernet-address | is the Ethernet address of the NIC0 interface in DHCP configuration format |
| subnet1 | is the subnet connecting the NIC0 interfaces |
Modify the DHCP configuration for NIC1:
# pntadm -M NIC1IP-address -i newEthernet-address \-f 'PERMANENT+MANUAL' -m NIC1IP-address subnet2 |
The parameters of this command are as follows:
| NIC1IP-address | is the IP address of the NIC1 interface |
| newEthernet-address | is the Ethernet address of the NIC1 interface in DHCP configuration format |
| subnet2 | is the subnet connecting the NIC1 interfaces |
Refresh the DHCP configuration on the master node:
# pkill -1 in.dhcpd1 |
ok> boot |
Verify that the node is configured correctly:
# nhadm checkm |
To replace the Ethernet cards on the vice-master node or a dataless node, perform the following procedure.
|
Verify that the new Ethernet cards are of the same type as the old Ethernet cards.
Replace the Ethernet cards using information in the hardware documentation at http://www.sun.com/products-n-solutions/hardware/docs/.
Verify that the node is configured correctly:
# nhadm check |
To replace the Ethernet cards on diskless nodes with the DHCP dynamic boot policy or the DHCP client ID boot policy, perform the procedure in Replacing Ethernet Cards on a Vice-Master or Dataless Node. To replace the Ethernet cards on diskless nodes with the DHCP static boot policy, perform the following procedure.
|
Verify that the new Ethernet cards are of the same type as the old Ethernet cards.
Identify the IP address - Ethernet address couplet for the network interface cards that are to be replaced.
Replace the Ethernet cards by using the hardware documentation at http://www.sun.com/products-n-solutions/hardware/docs/.
Record the Ethernet addresses of the new network cards.
To find the Ethernet addresses of the network cards, perform the following step:
Identify the Ethernet address of NIC0:
ok> banner |
The Ethernet address of NIC0 is provided in the output.
The Ethernet address of NIC1 is derived as follows:
NIC0 + 0x1
For example, if the output of the banner command is this:
Ethernet address 8:0:20:fa:2a:6e, Host ID: 80fa2a6e
The Ethernet address of NIC0 is 8:0:20:fa:2a:6e, and the Ethernet address of NIC1 is 8:0:20:fa:2a:6f.
In the DHCP configuration files, the Ethernet addresses of NIC0 and NIC1 are given as 01080020FA2A6E and 01080020FA2A6F, respectively.
For another example, the output of the banner command is as follows:
Ethernet address 8:0:20:f9:b3:60, Host ID: 80f9b360
In the DHCP configuration files in the /SUNWcgha/remote/var/dhcp/ directory, the Ethernet addresses of NIC0 and NIC1 are given as 01080020F9B360 and 01080020F9B361, respectively.
Modify the DHCP configuration for NIC0:
# pntadm -M NIC0IP-address -i newEthernet-address \-f 'PERMANENT+MANUAL' -m NIC0IP-address subnet1 |
The parameters of this command are as follows:
| NIC0IP-address | is the IP address of the NIC0 interface |
| newEthernet-address | is the Ethernet address of the NIC0 interface in DHCP configuration format |
| subnet1 | is the subnet connecting the NIC0 interfaces |
Modify the DHCP configuration for NIC1:
# pntadm -M NIC1IP-address -i newEthernet-address \-f 'PERMANENT+MANUAL' -m NIC1IP-address subnet2 |
The parameters of this command are as follows:
| NIC1IP-address | is the IP address of the NIC1 interface |
| newEthernet-address | is the Ethernet address of the NIC1 interface in DHCP configuration format |
| subnet2 | is the subnet connecting the NIC1 interfaces |
Refresh the DHCP configuration on the master node:
# pkill -1 in.dhcpd |
ok> boot |
Verify that the node is configured correctly:
# nhadm check |
This section describes how to replace the disk on the vice-master node.
|
Verify that the new disk is the same hardware type and can have the same disk partition configuration as the old disk.
Replace the hardware by using the hardware documentation at http://www.sun.com/products-n-solutions/hardware/docs/.
Install the Solaris OS on the vice-master node. Keep the original partitioning configuration (reformat the new disk by recreating the format of the old disk).
Install the Netra HA Suite software on the vice-master node.
For information, see the Netra High Availability Suite 3.0 1/08 Foundation Services Manual Installation Guide for the Solaris OS.
If logical partitioning or IDE disks are used, follow this step and then jump to Step 9. Otherwise, go to Step 6.
| # nhcrfsadm -f all |
Power on the vice-master node.
The master node will resynchronize the vice-master disk automatically.
If SCSI disks are used and logical partitioning is not used, follow this step and the rest of the procedure.
Power on the vice-master node. The master node detects that the vice-master node is not synchronized. A message is displayed in the system log file, asking whether you want to restart the replication.
# nhcrfsadm -a |
(All configurations, IDE or SCSI) Verify that the synchronization is complete:
For versions earlier than the Solaris 10 OS:
# /usr/opt/SUNWesm/sbin/scmadm -S -M |
For the Solaris 10 OS and later:
# /usr/sbin/dsstat 1 |
While the synchronization is taking place, the sync label is displayed. When the synchronization is complete, the sync label is replaced by the replicating label.
Verify that the node is configured correctly:
# nhadm check |
|
Clusters using shared disk are supported only on the Solaris OS. The information presented in this section does not apply to Linux clusters.
Replace the hardware by using the hardware documentation at http://www.sun.com/products-n-solutions/hardware/docs/.
Reformat the new disk by recreating the format of the old disk.
Restore the disk configuration.
Install the Solaris Operating System on the vice-master node.
Install the Netra HA Suite software on the vice-master node.
For information, see the Netra High Availability Suite 3.0 1/08 Foundation Services Manual Installation Guide for the Solaris OS.
Create the database replicas on the dedicated partition:
| # metadb -a -c 3 -f /dev/rdsk/c0t0d0s7 |
Reboot the node in cluster mode.
The vice-master node joins the cluster.
Note - Reliable NFS will not notice that the disksets on the vice master have not yet been recreated, so a switchover or failover is prohibited. |
Remove the vice-master node from the diskset node names:
| # metaset -s nhas_diskset -d -h netraMEN2-cgtp |
Re-add the vice-master node to the diskset node names:
| # metaset -s nhas_diskset -a -h netraMEN2-cgtp |
Disks in master-eligible nodes can be replaced without fully shutting down a cluster. The new disks may have different geometry than the old disks, however, the new disk in one node must be identical to the new disk in the other node, and the disks must be replaced sequentially in both nodes. When you replace disks as described in this section, the cluster is not single-fault tolerant.
This section describes how to replace disks on both master-eligible nodes without fully shutting down the cluster.
|
Note - For this release of the Netra HA Suite product, this procedure is supported for only master-eligible nodes that are running the Solaris OS. |
Replace the disk in the vice-master node using the procedure described in the hardware documentation at:
Install the Solaris OS on the vice-master node. Keep the original partitioning configuration as much as possible (reformat the new disk by recreating the format of the old disk). The following conditions must be met:
Device names of the new replicated and bitmap slices/partitions must be preserved.
New replicated slices/partitions must not be smaller than the original slices/partitions.
The new bitmap partitions must be at least 1 Kbyte + 4 Kbytes per Gbyte of data in the associated new replicated slice/partition.
Install the Netra HA Suite software on the vice-master node.
For information, see the Netra High Availability Suite 3.0 1/08 Foundation Services Manual Installation Guide for the Solaris OS.
If logical partitioning or IDE disks are used, follow this step and then jump to Step 11. Otherwise, go to Step 9.
On the master node, force a full synchronization:
| master# nhcrfsadm -f all |
Start the vice-master node with the Foundation Services.
Remove the /etc/opt/SUNWcgha/not_configured file, which was created automatically during the installation process and reboot the vice-master node. The master node will resynchronize the vice-master disk automatically.
If SCSI disks are used and logical partitioning is not used, follow this step and the rest of the procedure.
Start the vice-master node with the Foundation Services. Remove the /etc/opt/SUNWcgha/not_configured file, which was created automatically during the installation process and reboot the vice-master node. The master node detects that the vice-master node is not synchronized. A message is displayed in the system log file, asking whether you want to restart the replication.
Accept a replication restart by running the following command on the master node:
master# nhcrfsadm -a |
(All configurations, IDE or SCSI) On the master node, verify that the synchronization is complete:
For versions earlier than the Solaris 10 OS:
master# /usr/opt/SUNWesm/sbin/scmadm -S -M |
For the Solaris 10 OS and later:
master# /usr/sbin/dsstat 1 |
While the synchronization is taking place, the sync label is displayed. When the synchronization is complete, the sync label is replaced by the replicating label.
Verify that the vice-master node is configured correctly by running the following command on the vice-master node:
vice-master# nhadm check |
Abruptly terminate the master node by running the following command on the master node:
master# uadmin 1 0 |
Running this command will halt the CPU(s) immediately and failover will occur. The first node with an upgraded disk will take the mastership and the master role. Switchover should not be used, as the vice-master with old disk might be rejected because of insufficient disk space for replication.
Repeat steps Step 1 through Step 12 to finish the upgrade of the second node.
This section describes how to replace a dataless node disk.
Verify that the new disk is of the same hardware type as the old disk.
Replace the hardware by referring to information in the hardware documentation on http://www.sun.com/products-n-solutions/hardware/docs/
Reformat the new disk by recreating the format of the old disk.
Use the disk backup to restore the file system on the new disk.
For example, if the backup was created on the Solaris OS using the ufsdump command, use the ufsrestore command to restore the file system. If the backup was created on Linux using the dump command, use the restore command to restore the file system.
Verify that the node is configured correctly:
# nhadm check |
| Netra™ High Availability Suite 3.0 1/08 Foundation Services Cluster Administration Guide | 819-5235-13 |
|
Copyright © 2008, Sun Microsystems, Inc. All rights reserved.
To Replace a Board on a Node