Sun Fire V445 Server Administration Guide

This chapter explains what the system console is, describes the different ways of configuring it on a Sun Fire V445 server, and helps you understand its relation to the system controller.

Tasks covered in this chapter include:

• Entering the ok Prompt
• Using the Serial Management Port
• Activating the Network Management Port
• Accessing the System Console With a Terminal Server
• Accessing the System Console With a Tip Connection
• Modifying the /etc/remote File
• Accessing the System Console With an Alphanumeric Terminal
• To Verify Serial Port Settings on TTYB
• Accessing the System Console With a Local Graphics Monitor

Other information in this chapter includes:

• About Communicating With the System
• About the sc> Prompt
• About the ok Prompt
• About Switching Between the ALOM System Controller and the System Console
• Reference for System Console OpenBoot Configuration Variable Settings

---

About Communicating With the System

To install your system software or to diagnose problems, you need some way to interact at a low level with the system. The system console is Sun's facility for doing this. You use the system console to view messages and issue commands. There can be only one system console per computer.

The serial management port (SERIAL MGT) is the default port for accessing the system console upon initial system installation. After installation, you can configure the system console to accept input from and send output to different devices. See TABLE 2-1 for a summary.

---

About Using the System Console

The system console device can be either a standard alphanumeric terminal, terminal server, Tip connection from another Sun system, or a local graphics monitor. The default connection is through the serial management port (labeled SERIAL MGT) on the chassis back panel. You can also connect an alphanumeric terminal to the serial (DB-9) connector (as TTYB) on the system back panel. A local graphics monitor requires installation of a PCI graphics card, monitor, USB keyboard, and mouse. You can also access the system console through a network connection with the network management port.

The system console displays status and error messages generated by firmware-based tests during system startup. After those tests have been run, you can enter special commands that affect the firmware and alter system behavior. For more information about tests that run during the boot process, see Chapter 8 and Chapter 9.

Once the OS is booted, the system console displays UNIX system messages and accepts UNIX commands.

To use the system console, you need some means of getting data in to and out of the system, which means attaching some kind of hardware to the system. Initially, you might have to configure that hardware, and load and configure appropriate software as well.

You also must ensure that the system console is directed to the appropriate port on the Sun Fire V445 server's back panel - generally, the one to which your hardware console device is attached. (See FIGURE 2-1.) You do this by setting the input-deviceand output-deviceOpenBoot configuration variables.

FIGURE 2-1 Directing the System Console to Different Ports and Different Devices

The following subsections provide background information and references to instructions appropriate for the particular device you choose to access the system console. For instructions on attaching and configuring a device to access the system console, see:

• Using the Serial Management Port
• Activating the Network Management Port
• Accessing the System Console With a Terminal Server
• Accessing the System Console With a Tip Connection

Default System Console Connection Through the Serial Management and Network Management Ports

On Sun Fire V445 servers, the system console comes preconfigured to allow input and output only by means of hardware devices connected to the serial or network management ports. However, because the network management port is not available until network parameters are assigned, your first connection must be to the serial management port. The network can be configured once the system is connected to power and ALOM completes its self test.

Typically, you connect one of the following hardware devices to the serial management port:

• Terminal server
• Alphanumeric terminal or similar device
• A Tip line connected to another Sun computer

This provides for secure access at the installation site.

[ D ]

FIGURE 2-2 Serial Management Port (Default Console Connection)

Using a Tip line might be preferable to connecting an alphanumeric terminal, since the tip command allows you to use windowing and OS features on the machine being used to connect to the Sun Fire V445 server.

Although the Solaris OS sees the serial management port as TTYA, the serial management port is not a general-purpose serial port. If you want to use a general-purpose serial port with your server - to connect a serial printer, for instance - use the regular 9-pin serial port on the back panel of the Sun Fire V445. The Solaris OS sees this port as TTYB.

For instructions on accessing the system console through a terminal server, see Accessing the System Console With a Terminal Server.

For instructions on accessing the system console through an alphanumeric terminal, see Accessing the System Console With an Alphanumeric Terminal.

For instructions on accessing the system console with a Tip line, see To Access the System Console With a Tip Connection Throught the Serial Management Port.

Access Through the Network Management Port

Once you have configured the network management port, you can connect an Ethernet-capable device to the system console through your network. This connection provides for remote monitoring and control. In addition, up to four simultaneous connections to the system controller sc> prompt are available through the network management port. For more information, see Activating the Network Management Port.

For more information about the system console and the ALOM system controller, see:

• About the sc> Prompt
• About the ok Prompt

ALOM

ALOM software is preinstalled on the server's system controller (SC) and is enabled at the first power on. ALOM provides remote powering on and off, diagnostics capabilities, environmental control, and monitoring operations for the server. The primary functions of ALOM include the following:

• Operation of system indicators
• Fan speed monitoring and adjustment
• Temperature monitoring and alerts
• Power supply health monitoring and control
• USB overcurrent monitoring and alerts
• Hot-plug configuration change monitoring and alerts
• Dynamic FRU ID data transactions

For more information about ALOM software, see About the ALOM System Controller Card.

Alternative System Console Configuration

In the default configuration, system controller alerts and system console output appear interspersed in the same window. After initial system installation, you can redirect the system console to take its input from and send its output to the serial port TTYB, or to a graphics card's port.

A serial port and the PCI slots are located on the rear panel. Two USB ports are located on the front panel.

The chief advantage of redirecting the system console to another port is that it allows you to divide system controller alerts and system console output into two separate windows.

However, there are some serious disadvantages to alternative console configuration:

• POST output can only be directed to the serial management and network management ports. It cannot be directed to TTYB or to a graphics card's port.
• If you have directed the system console to TTYB, you cannot use this port for any other serial device.
• In a default configuration, the serial management and network management ports enable you to open up to four additional windows by which you can view, but not affect, system console activity. You cannot open these windows if the system console is redirected to TTYB or to a graphics card's port.
• In a default configuration, the serial management and network management ports enable you to switch between viewing system console and system controller output on the same device by typing a simple escape sequence or command. The escape sequence and commands do not work if the system console is redirected to TTYB or to a graphics card's port.
• The system controller keeps a log of console messages, but some messages are not logged if the system console is redirected to TTYB or to a graphic card's port. The omitted information could be important if you need to contact Sun customer service with a problem.

For all the preceding reasons, the best practice is to leave the system console in its default configuration.

You change the system console configuration by setting OpenBoot configuration variables. See Reference for System Console OpenBoot Configuration Variable Settings.

You can also set OpenBoot configuration variables using the ALOM system controller. For details, see the Sun Advanced Lights Out Manager (ALOM) Online Help.

Accessing the System Console Through a Graphics Monitor

The Sun Fire V445 server is shipped without a mouse, keyboard, monitor, or frame buffer for the display of bitmapped graphics. To install a graphics monitor on the server, you must install a frame buffer card into a PCI slot, and attach a monitor, mouse, and keyboard to the appropriate back panel ports.

After starting the system, you might need to install the correct software driver for the PCI card you have installed. For detailed hardware instructions, see To Access the System Console With a Local Graphics Monitor.

---

About the sc> Prompt

The ALOM system controller runs independently of the Sun Fire V445 server and regardless of system power state. When you connect a Sun Fire V445 server to AC power, the ALOM system controller immediately starts up, and begins monitoring the system.

You can log in to the ALOM system controller at any time, regardless of system power state, as long as AC power is connected to the system and you have a way of interacting with the system. You can also access the ALOM system controller prompt (sc>) from the ok prompt or from the Solaris prompt, provided the system console is configured to be accessible through the serial management and network management ports. For more information, see:

• Entering the ok Prompt
• About Switching Between the ALOM System Controller and the System Console

The sc> prompt indicates that you are interacting with the ALOM system controller directly. It is the first prompt you see when you log in to the system through the serial management port or network management port, regardless of system power state.

Access Through Multiple Controller Sessions

Up to five ALOM system controller sessions can be active concurrently, one session through the serial management port and up to four sessions through the network management port.

Users of each of these sessions can issue commands at the sc> prompt, but only one user session can have write-access to the system console at anytime. The other sessions accessing the system console will have read-only capability.

For more information, see:

• Using the Serial Management Port
• Activating the Network Management Port.

Any additional ALOM system controller sessions afford passive views of system console activity, until the active user of the system console logs out. However, the console -f command, if you enable it, allows users to seize access to the system console from one another. For more information, see the Sun Advanced Lights Out Manager (ALOM) Online Help.

Ways of Reaching the sc> Prompt

There are several ways to get to the sc> prompt. These are:

• If the system console is directed to the serial management and network management ports, you can type the ALOM system controller escape sequence (#.).

• You can log in directly to the ALOM system controller from a device connected to the serial management port. See Using the Serial Management Port.
• You can log in directly to the ALOM system controller using a connection through the network management port. See Activating the Network Management Port.

---

About the ok Prompt

A Sun Fire V445 server with the Solaris OS installed is capable of operating at different run levels. A synopsis of run levels follows. For a full description, see the Solaris system administration documentation.

Most of the time, you operate a Sun Fire V445 server at run level 2 or run level 3, which are multiuser states with access to full system and network resources. Occasionally, you might operate the system at run level 1, which is a single-user administrative state. However, the lowest operational state is run level 0. At this state, it is safe to turn off power to the system.

When a Sun Fire V445 server is at run level 0, the ok prompt appears. This prompt indicates that the OpenBoot firmware is in control of the system.

There are a number of scenarios in which OpenBoot firmware control can happen.

• By default, the system powers up to OpenBoot firmware control before the OS is installed.
• The system boots to the ok prompt when the auto-boot? OpenBoot configuration variable is set to false.
• The system transitions to run level 0 in an orderly way when the OS is halted.
• The system reverts to OpenBoot firmware control when the OS crashes.
• When a serious hardware problem develops while the system is running, the OS transitions smoothly to run level 0.
• You deliberately place the server under firmware control in order to execute firmware-based commands or to run diagnostic tests.

It is the last of these scenarios that most often concerns you as an administrator, since there will be times when you need to reach the ok prompt. The several ways to do this are outlined in Entering the ok Prompt. For detailed instructions, see Entering the ok Prompt.

Entering the ok Prompt

There are several ways to enter the ok prompt, depending on the state of the system and the means by which you are accessing the system console. In order of desirability, these are:

• Graceful shutdown
• ALOM system controller break or console command
• L1-A (Stop-A) keys or Break key
• Externally initiated reset (XIR)
• Manual system reset

A description of each method follows. For instructions, see Entering the ok Prompt.

Graceful Shutdown

The preferred method of reaching the ok prompt is to shut down the OS by issuing an appropriate command (for example, the shutdown, init, or uadmin command) as described in Solaris system administration documentation. You can also use the system Power button to initiate a graceful system shutdown.

Gracefully shutting down the system prevents data loss, enables you to warn users beforehand, and causes minimal disruption. You can usually perform a graceful shutdown, provided the Solaris OS is running and the hardware has not experienced serious failure.

You can also perform a graceful system shutdown from the ALOM system controller command prompt.

For more information, see:

• Powering Off the Server Locally
• Powering Off the System Remotely

ALOM System Controller break or console Command

Typing break from the sc> prompt forces a running Sun Fire V445 server to move to OpenBoot firmware control. If the OS is already halted, you can use the console command instead of break to reach the ok prompt.

If you issue a break at the SC you will remain in an SC prompt. To use the OpenBoot prompt, enter the console command. For example:

hostname> #. [characters are not echoed to the screen]
sc> break -y [break on its own will generate a confirmation prompt]
sc> console
ok 

After forcing the system into OpenBoot firmware control, be aware that issuing certain OpenBoot commands (like probe-scsi, probe-scsi-all, or probe-ide) might hang the system.

L1-A (Stop-A) Keys or Break Key

When it is impossible or impractical to shut down the system gracefully, you can get to the ok prompt by typing the L1-A (Stop-A) key sequence from a Sun keyboard, or, if you have an alphanumeric terminal attached to the Sun Fire V445 server, by pressing the Break key.

After forcing the system into OpenBoot firmware control, be aware that issuing certain OpenBoot commands (like probe-scsi, probe-scsi-all, or probe-ide) might hang the system.

Externally Initiated Reset (XIR)

Use the ALOM system controller reset -x command to execute an externally initiated reset (XIR). Forcing an XIR might be effective in breaking the deadlock that is hanging up the system. However, an XIR also precludes the orderly shutdown of applications, and so it is not the preferred method of reaching the ok prompt, unless you are troubleshooting these types of system hangs. Generating an XIR has the advantage of allowing you to issue the sync command to produce a dump file of the current system state for diagnostic purposes.

For more information, see:

• Chapter 8 and Chapter 9
• Sun Advanced Lights Out Manager (ALOM) Online Help

Caution - Because an XIR precludes an orderly shutdown of applications, it should only be attempted if previously described methods do not work.

Manual System Reset

Use the ALOM system controller reset command, or poweron and poweroff commands, to reset the server. Reaching the ok prompt by performing a manual system reset or by power-cycling the system should be the method of last resort. Doing this results in the loss of all system coherence and state information. A manual system reset could corrupt the server's file systems, although the fsck command usually restores them.

Caution - Forcing a manual system reset results in loss of system state data, and should be attempted only as a last resort. After a manual system reset, all state information is lost, which inhibits troubleshooting the cause of the problem until the problem reoccurs.

Caution - When you access the okprompt from a functioning Sun Fire V445 server, you are suspending the Solaris OS and placing the system under firmware control. Any processes that were running under the OS are also suspended, and the state of such processes might not be recoverable.

The commands you run from the ok prompt have the potential to affect the state of the system. This means that it is not always possible to resume execution of the OS from the point at which it was suspended. The diagnostic tests you run from the ok prompt will affect the state of the system. This means that it is not possible to resume execution of the OS from the point at which it was suspended.

Although the go command will resume execution in most circumstances, in general, each time you force the system down to the ok prompt, you should expect to have to reboot the system to get back to the OS.

As a rule, before suspending the OS, you should back up files, warn users of the impending shutdown, and halt the system in an orderly manner. However, it is not always possible to take such precautions, especially if the system is malfunctioning.

For more information about the OpenBoot firmware, see the OpenBoot 4.x Command Reference Manual. An online version of the manual is included with the OpenBoot Collection AnswerBook that ships with Solaris software.

---

About Switching Between the ALOM System Controller and the System Console

The Sun Fire V445 server features two management ports, labeled SERIAL MGT and NET MGT, located on the server's back panel. If the system console is directed to use the serial management and network management ports (its default configuration), these ports provide access to both the system console and the ALOM system controller, each on separate channels (FIGURE 2-3).

FIGURE 2-3 Separate System Console and System Controller Channels

If the system console is configured to be accessible from the serial management and network management ports, when you connect through one of these ports you can access either the ALOM command-line interface or the system console. You can switch between the ALOM system controller and the system console at any time, but you cannot access both at the same time from a single terminal or shell tool.

The prompt displayed on the terminal or shell tool tells you which channel you are accessing:

• The # or % prompt indicates that you are at the system console and that the Solaris OS is running.
• The ok prompt indicates that you are at the system console and that the server is running under OpenBoot firmware control.
• The sc> prompt indicates that you are at the ALOM system controller.

To reach the system console from the ALOM system controller, type the console command at the sc> prompt. To reach the ALOM system controller from the system console, type the system controller escape sequence, which by default is #. (pound period).

For more information, see:

• About Communicating With the System
• About the sc> Prompt
• About the ok Prompt
• Using the Serial Management Port
• Sun Advanced Lights Out Manager (ALOM) Online Help

---

Entering the ok Prompt

This procedure provides several ways of reaching the ok prompt. The methods are not equally desirable. For details about when to use each method, see About the ok Prompt.

Caution - Dropping the Sun Fire V445 server to the okprompt suspends all application and OS software. After you issue firmware commands and run firmware-based tests from the okprompt, the system might not be able to resume where it left off.

1. If at all possible, back up system data before starting this procedure.

For information about the appropriate backup and shutdown procedures, refer to Solaris system administration documentation.

2. Exit or stop all applications and warn users of the impending loss of service.

3. Decide which method you need to use to reach the ok prompt.

See About the ok Prompt for details.

4. Refer to TABLE 2-3 for instructions.

---

Using the Serial Management Port

This procedure assumes that the system console is directed to use the serial management and network management ports (the default configuration).

When you are accessing the system console using a device connected to the serial management port, your first point of access is the ALOM system controller and its sc> prompt. After connecting to the ALOM system controller, you can switch to the system console itself.

For more information about the ALOM system controller card, see:

• About the ALOM System Controller Card
• Sun Advanced Lights Out Manager (ALOM) Online Help

Ensure that the serial port on your connecting device is set to the following parameters:

• 9600 baud
• 8 bits
• No parity
• 1 stop bit
• No handshaking

1. Establish an ALOM system controller session.

See Sun Advanced Lights Out Manager (ALOM) Online Help for instructions.

2. To connect to the system console, at the ALOM system controller command prompt, type:

sc> console

The console command switches you to the system console.

3. To switch back to the sc> prompt, type the #. escape sequence.

ok #. [characters are not echoed to the screen]

For instructions on how to use the ALOM system controller, see:

• Sun Advanced Lights Out Manager (ALOM) Online Help

---

Activating the Network Management Port

You must assign an Internet Protocol (IP) address to the network management port before you can use it. If you are configuring the network management port for the first time, you must first connect to the ALOM system controller using the serial management port and assign an IP address to the network management port. You can either assign an IP address manually, or you can configure the port to obtain an IP address using the Dynamic Host Configuration Protocol (DHCP) from another server.

Data centers frequently devote a separate subnet to system management. If your data center has such a configuration, connect the network management port to this subnet.

1. Connect an Ethernet cable to the network management port.

2. Log in to the ALOM system controller through the serial management port.

For more information about connecting to the serial management port, see Using the Serial Management Port.

3. Assign IP addresses by typing one of the following commands:

• If your network uses static IP addresses, type:


TABLE 2-5
sc> setsc if_network true sc> setsc netsc_ipaddr ip-address sc> setsc netsc_ipnetmask ip-address sc> setsc netsc_ipgateway ip-address

• If your network uses Dynamic Host Configuration Protocol (DHCP), type:


TABLE 2-6
sc> setsc netsc_dhcp

4. Select the communications protocol, either Telnet, SSH, or none, type:

sc> setsc if_connection none|ssh|telnet

5. To verify the network settings, type:

sc> shownetwork

6. Log out of the ALOM system controller session.

To connect through the network management port, use the telnet command to the IP address you specified in Step 3 of the preceding procedure.

---

Accessing the System Console With a Terminal Server

The following procedure assumes that you are accessing the system console by connecting a terminal server to the serial management port (SERIAL MGT) of the Sun Fire V445 server.

1. Complete the physical connection from the serial management port to your terminal server.

The serial management port on the Sun Fire V445 server is a data terminal equipment (DTE) port. The pinouts for the serial management port correspond with the pinouts for the RJ-45 ports on the Serial Interface Breakout Cable supplied by Cisco for use with the Cisco AS2511-RJ terminal server. If you use a terminal server made by another manufacturer, check that the serial port pinouts of the Sun Fire V445 server match those of the terminal server you plan to use.

If the pinouts for the server serial ports correspond with the pinouts for the RJ-45 ports on the terminal server, you have two connection options:

• Connect a serial interface breakout cable directly to the Sun Fire V445 server. See Using the Serial Management Port.
• Connect a serial interface breakout cable to a patch panel and use the straight-through patch cable (supplied by Sun) to connect the patch panel to the server.

FIGURE 2-4 Patch Panel Connection Between a Terminal Server and a Sun Fire V445 Server

If the pinouts for the serial management port do not correspond with the pinouts for the RJ-45 ports on the terminal server, you need to make a crossover cable that takes each pin on the Sun Fire V445 server serial management port to the corresponding pin in the terminal server's serial port.

TABLE 2-9 shows the crossovers that the cable must perform.

2. Open a terminal session on the connecting device, and type:

% telnet IP-address-of-terminal-server port-number

For example, for a Sun Fire V445 server connected to port 10000 on a terminal server whose IP address is 192.20.30.10, you would type:

% telnet 192.20.30.10 10000

1. Redirect the system console by changing OpenBoot configuration variables.

At the ok prompt, type:

ok setenv input-device ttyb
ok setenv output-device ttyb

2. To cause the changes to take effect, power off the system. Type:

ok power-off

The system permanently stores the parameter changes and powers off.

3. Connect the null modem serial cable to the TTYB port on the Sun Fire V445 server.

If required, use the DB-9 or DB-25 cable adapter supplied with the server.

4. Power on the system.

See Chapter 3 for power-on procedures.

What Next

Continue with your installation or diagnostic test session as appropriate. When you are finished, end your session by typing the terminal server's escape sequence and exit the window.

For more information about connecting to and using the ALOM system controller, see:

• Sun Advanced Lights Out Manager (ALOM) Online Help

If you have redirected the system console to TTYB and want to change the system console settings back to use the serial management and network management ports, see:

• Reference for System Console OpenBoot Configuration Variable Settings

---

Accessing the System Console With a Tip Connection

This procedure assumes that you are accessing the Sun Fire V445 server system console by connecting the serial port of another Sun system to the serial management port (SERIAL MGT) of the Sun Fire V445 server (FIGURE 2-7).

FIGURE 2-7 Tip Connection Between a Sun Fire V445 Server and Another Sun System

1. Connect the RJ-45 serial cable and, if required, the DB-9 or DB-25 adapter provided.

The cable and adapter connect between another Sun system's serial port (typically TTYB) and the serial management port on the back panel of the Sun Fire V445 server. Pinouts, part numbers, and other details about the serial cable and adapter are provided in the Sun Fire V445 Server Parts Installation and Removal Guide.

2. Ensure that the /etc/remote file on the Sun system contains an entry for hardwire.

Most releases of Solaris OS software shipped since 1992 contain an /etc/remote file with the appropriate hardwire entry. However, if the Sun system is running an older version of Solaris OS software, or if the /etc/remote file has been modified, you might need to edit it. See Modifying the /etc/remote File for details.

3. In a shell tool window on the Sun system, type:

% tip hardwire 

The Sun system responds by displaying:

connected 

The shell tool is now a Tip window directed to the Sun Fire V445 server through the Sun system's serial port. This connection is established and maintained even when the Sun Fire V445 server is completely powered off or just starting up.

1. Redirect the system console by changing the OpenBoot configuration variables.

At the ok prompt on the Sun Fire V445 server, type:

ok setenv input-device ttyb
ok setenv output-device ttyb

2. To cause the changes to take effect, power off the system. Type:

ok power-off

The system permanently stores the parameter changes and powers off.

3. Connect the null modem serial cable to the TTYB port on the Sun Fire V445 server.

If required, use the DB-9 or DB-25 cable adapter supplied with the server.

4. Power on the system.

See Chapter 3 for power-on procedures.

Continue with your installation or diagnostic test session as appropriate. When you are finished using the tip window, end your Tip session by typing ~. (the tilde symbol followed by a period) and exit the window. For more information about tip commands, see the tip man page.

For more information about connecting to and using the ALOM system controller, see:

• Sun Advanced Lights Out Manager (ALOM) Online Help

If you have redirected the system console to TTYB and want to change the system console settings back to use the serial management and network management ports, see:

• Reference for System Console OpenBoot Configuration Variable Settings

---

Modifying the /etc/remote File

This procedure might be necessary if you are accessing the Sun Fire V445 server using a Tip connection from a Sun system running an older version of the Solaris OS software. You might also need to perform this procedure if the /etc/remote file on the Sun system has been altered and no longer contains an appropriate hardwire entry.

This procedure assumes that you are logged in as superuser to the system console of a Sun system that you intend to use to establish a tip connection to the Sun Fire V445 server.

1. Determine the release level of Solaris OS software installed on the Sun system. Type:

# uname -r

The system responds with a release number.

2. Do one of the following, depending on the number displayed.

• If the number displayed by the uname -r command is 5.0 or higher:

The Solaris software shipped with an appropriate entry for hardwire in the /etc/remote file. If you have reason to suspect that this file was altered and the hardwire entry modified or deleted, check the entry against the following example, and edit it as needed.

hardwire:\   
	:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

• If the number displayed by the uname -r command is less than 5.0:

Check the /etc/remote file and add the following entry, if it does not already exist.

hardwire:\   
	:dv=/dev/ttyb:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

The /etc/remote file is now properly configured. Continue establishing a Tip connection to the Sun Fire V445 server system console. See:

• Accessing the System Console With a Tip Connection

If you have redirected the system console to TTYB and want to change the system console settings back to use the serial management and network management ports, see:

• Reference for System Console OpenBoot Configuration Variable Settings

---

Accessing the System Console With an Alphanumeric Terminal

This procedure assumes that you are accessing the Sun Fire V445 server system console by connecting the serial port of an alphanumeric terminal to the serial management port (SERIAL MGT) of the Sun Fire V445 server.

1. Attach one end of the serial cable to the alphanumeric terminal's serial port.

Use a null modem serial cable or an RJ-45 serial cable and null modem adapter. Plug this cable in to the terminal's serial port connector.

2. Attach the opposite end of the serial cable to the serial management port on the Sun Fire V445 server.

3. Connect the alphanumeric terminal's power cord to an AC outlet.

4. Set the alphanumeric terminal to receive:

• 9600 baud
• 8 bits
• No parity
• 1 stop bit
• No handshake protocol

See the documentation accompanying your terminal for information about how to configure it.

1. Redirect the system console by changing the OpenBoot configuration variables.

At the ok prompt, type:

ok setenv input-device ttyb
ok setenv output-device ttyb

2. To cause the changes to take effect, power off the system. Type:

ok power-off

The system permanently stores the parameter changes and powers off.

3. Connect the null modem serial cable to the TTYB port on the Sun Fire V445 server.

If required, use the DB-9 or DB-25 cable adapter supplied with the server.

4. Power on the system.

See Chapter 3 for power-on procedures.

You can issue system commands and view system messages using the alphanumeric terminal. Continue with your installation or diagnostic procedure, as needed. When you are finished, type the alphanumeric terminal's escape sequence.

For more information about connecting to and using the ALOM system controller, see:

• Sun Advanced Lights Out Manager (ALOM) Online Help

If you have redirected the system console to TTYB and want to change the system console settings back to use the serial management and network management ports, see:

• Reference for System Console OpenBoot Configuration Variable Settings

---

Verifying Serial Port Settings on TTYB

This procedure enables you to verify the baud rate and other serial port settings used by the Sun Fire V445 server to communicate with a device attached to its TTYB port.

You must be logged in to the Sun Fire V445 server, and the server must be running Solaris OS software.

1. Open a shell tool window.

2. Type:

# eeprom | grep ttyb-mode

3. Look for the following output:

ttyb-mode = 9600,8,n,1,-

This line indicates that the Sun Fire V445 server's serial port TTYB is configured for:

• 9600 baud
• 8 bits
• No parity
• 1 stop bit
• No handshake protocol

For more information about serial port settings, see the eeprom man page. For more information about the TTYB-mode OpenBoot configuration variable, see Appendix C.

---

Accessing the System Console With a Local Graphics Monitor

After initial system installation, you can install a local graphics monitor and configure it to access the system console. You cannot use a local graphics monitor to perform initial system installation, nor can you use a local graphics monitor to view power-on self-test (POST) messages.

To install a local graphics monitor, you must have:

• A supported PCI-based graphics frame buffer card and software driver.
  An 8/24-Bit Color Graphics PCI adapter frame buffer card (Sun part number X3768A or X3769A is currently supported)
• A monitor with appropriate resolution to support the frame buffer
• A Sun-compatible USB keyboard (Sun USB Type-6 keyboard)
• A Sun-compatible USB mouse (Sun USB mouse) and mouse pad

1. Install the graphics card into an appropriate PCI slot.

Installation must be performed by a qualified service provider. For further information, see the Sun Fire V445 Server Installation Guide or contact your qualified service provider.

2. Attach the monitor's video cable to the graphics card's video port.

Tighten the thumbscrews to secure the connection.

3. Connect the monitor's power cord to an AC outlet.

4. Connect the USB keyboard cable to any USB port on the Sun Fire V445 server front panel.

5. Connect the USB mouse cable to any USB port on the Sun Fire V445 server front panel.

6. Obtain the ok prompt.

For more information, see Entering the ok Prompt.

7. Set OpenBoot configuration variables appropriately.

From the existing system console, type:

ok setenv input-device keyboard
ok setenv output-device screen

8. To cause the changes to take effect, type:

ok reset-all

The system stores the parameter changes, and boots automatically when the OpenBoot configuration variable auto-boot? is set to true (its default value).

You can issue system commands and view system messages using your local graphics monitor. Continue with your installation or diagnostic procedure, as needed.

If you want to redirect the system console back to the serial management and network management ports, see:

• Reference for System Console OpenBoot Configuration Variable Settings.

---

Reference for System Console OpenBoot Configuration Variable Settings

The Sun Fire V445 system console is directed to the serial management and network management ports (SERIAL MGT and NET MGT) by default. However, you can redirect the system console to the serial DB-9 port (TTYB), or to a local graphics monitor, keyboard, and mouse. You can also redirect the system console back to the serial management and network management ports.

Certain OpenBoot configuration variables control from where system console input is taken and to where its output is directed. The table below shows how to set these variables in order to use the serial management and network management ports, TTYB, or a local graphics monitor as the system console connection.

output-device    

ttya

ttyb

screen

input-device 

ttya

ttyb

keyboard

The serial management port and network management port are present in the OpenBoot configuration variables as ttya. However, the serial management port does not function as a standard serial connection. If you want to connect a conventional serial device (such as a printer) to the system, you need to connect it to TTYB, not the serial management port. See About the Serial Ports for more information.

The sc> prompt and POST messages are only available through the serial management port and network management port. In addition, the ALOM system controller console command is ineffective when the system console is redirected to TTYB or a local graphics monitor.

In addition to the OpenBoot configuration variables described in TABLE 2-20, there are other variables that affect and determine system behavior. These variables are created during system configuration and stored on a ROM chip.

^{1 (TableFootnote) After initial system installation, you can redirect the system console to take its input from and send its output to the serial port TTYB.}

^{2 (TableFootnote) Requires the OpenBoot configuration variable input-device=keyboard. For more information, see Accessing the System Console With a Local Graphics Monitor and Reference for System Console OpenBoot Configuration Variable Settings.}

Sun Fire V445 Server Administration Guide

819-3741-13

Copyright © 2007, Sun Microsystems, Inc. All Rights Reserved.