![]() |
|||
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
![]() ![]() |
![]() |
| |||||
Chapter 11Replacing a CPU BoardFor information about how to replace a CPU board on a node, see the following sections: Replacing a Board on a NodeTo replace the board on a 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 Board on a Diskless Node With the DHCP Client ID Boot Policy.
|
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 |
A Netra T1 master-eligible node or dataless node has these OBP parameters:
ok> setenv local-mac-address? true ok> setenv auto-boot? true ok> setenv diag-switch? false ok> setenv boot-device disk net |
Reboot the node:
ok> boot |
Log into the node as superuser.
Verify that the node is configured correctly:
# nhadm check |
To replace the board on a diskless node that is using the DHCP client ID 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 Replacing 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 Replacing a Board on a Node.
![]() ![]() |