Connecting To Node Board Consoles From The Distributed Management Card - Sun Microsystems Netra CT 820 Administration Manual

Hide thumbs Also See for Netra CT 820:
Table of Contents

Advertisement

4. Form the three-part client ID by using the system part number, the system serial
number, and the slot number, separated by colons. Then, convert the client ID to
ASCII.
For example, if the output from the showfru commands in
part number) and 000001 (Sun serial number), and you want to form the client ID for
the node board in slot 4, the client ID is: 3754335:000001:04.
Translate the client ID to its ASCII equivalent. For example:
Client ID part
3754335
:
000001
:
04
Thus, the example client ID in ASCII is:
33 37 35 34 33 33 35 3A 30 30 30 30 30 31 3A 30 34.
5. Configure the DHCP server.
Refer to the Solaris DHCP Administration Guide on the web site docs.sun.com for
information on how to configure the DHCP server for remote boot and diskless boot
clients.
The client ID is retained across a node board power cycle, reboot, or reset; the
distributed management card updates the client ID during a first-time power on or a
hot swap of a node board. In the event of a distributed management card fault, a
node board reboot or reset will retrieve the previously written client ID.
Connecting to Node Board Consoles
from the Distributed Management Card
The Netra CT system provides the capability to connect to node boards and open
console sessions from the active distributed management card.
54
Netra CT 820 Server System Administration Guide • March 2004
ASCII Representation
33 37 35 34 33 33 35
3A
30 30 30 30 30 31
3A
30 34
Step 3
is 375-4335 (Sun

Advertisement

Table of Contents
loading

Table of Contents