| Sun Netra T5220 Server Administration Guide |    
|
| C H A P T E R 1 |
|
Configuring the System Console |
This chapter explains what the system console is, describes the different ways of configuring it on a Sun Netra T5220 server, and helps you understand the relationship between the system console and the service processor. This chapter contains the following sections:
| Note - For information about changing the hardware configuration of your server, or about running diagnostics, see the Sun Netra T5220 Server Service Manual. |
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 the 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 (SER 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. TABLE 1-1 lists these devices and where they are discussed in this document.
|
A terminal server attached to the serial management port (SER MGT) |
|||
|
An alphanumeric terminal or similar device attached to the serial management port (SER MGT) |
|||
|
Accessing the System Console Through an Alphanumeric Terminal |
|||
|
An Ethernet line connected to the network management port (NET MGT) |
|||
|
A local graphics monitor (graphics accelerator card, graphics monitor, mouse, and keyboard) |
Accessing the System Console Through a Local Graphics Monitor |
||
The system console displays status and error messages generated by firmware-based tests during system startup. After those tests 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, refer to the Sun Netra T5220 Server Service Manual for your server.
Once the operating system is booted, the system console displays UNIX system messages and accepts UNIX commands.
To use the system console, you need to attach an input/output device to the system. Initially, you might have to configure that hardware, and load and configure appropriate software as well.
You must also ensure that the system console is directed to the appropriate port on the server’s back panel. Generally, the one to which your hardware console device is attached (see FIGURE 1-1). You do this by setting the input-device and output-device OpenBoot configuration variables.
FIGURE 1-1 Directing the System Console Input and Output
On your server, the system console is preconfigured to allow input and output only by means of the service processor. The service processor must be accessed either through the serial management port (SER MGT) or the network management port (NET MGT). By default, the network management port is configured to retrieve network configuration using Dynamic Host Configuration Protocol (DHCP) and to allow connections using Secure Shell (SSH). You can modify the network management port configuration after connecting to ILOM through either the serial or network management ports.
Typically, you connect one of the following hardware devices to the serial management port:
These devices provide for secure access at the installation site.
FIGURE 1-2 Rear I/O Panel of the Sun Netra T5220 Chassis.
The service processor serial management port is the default console connection.
Using a Tip line enables you to use windowing and operating system features on the system making the connection to the server.
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 example, use the standard 9-pin serial port on the back panel of the Sun Netra T5220 server. The Oracle Solaris OS sees this port as ttya.
In the default configuration, service processor 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 a graphics card’s port.
The best practice is to leave the console port in its default configuration for the following reasons:
You change the system console configuration by setting OpenBoot configuration variables. See System Console OpenBoot Configuration Variable Settings.
The Sun Netra T5220 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 graphics accelerator card into a PCI slot, and attach a monitor, mouse, and keyboard to the appropriate front or rear USB 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 Accessing the System Console Through a Local Graphics Monitor.
| Note - POST diagnostics cannot display status and error messages to a local graphics monitor. |
The following sections describe methods of accessing the service processor.
This procedure assumes that the system console uses 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, you first access the ILOM service processor and its -> prompt. After connecting to the ILOM service processor, you can switch to the system console.
For more information about the ILOM service processor, refer to the ILOM user’s guide and the Integrated Lights Out Management 2.0 Supplement for the Sun Netra T5220 Server.
1. Ensure that the serial port on your connecting device is set to the following parameters:
2. Establish an ILOM service processor session.
See the ILOM user’s guide for instructions.
3. To connect to the system console, at the ILOM command prompt, type:
The start /SP/console command switches you to the system console.
4. To switch back to the -> prompt, type the #. (Hash-Period) escape sequence.
Characters are not echoed to the screen.
For instructions on how to use the ILOM service processor, refer to the ILOM user’s guide and the Integrated Lights Out Management 2.0 Supplement for the Sun Netra T5220 Server.
The network management port is configured by default to retrieve network settings using DHCP and allow connections using SSH. You might need to modify these settings for your network. If you are unable to use DHCP and SSH on your network, you must connect to the service processor using the serial management port to reconfigure the network management port. See Using the Serial Management Port.
You can assign the network management port a static IP address or you can configure the port to obtain an IP address using DHCP from another server. The network management port can be configured to accept connections from SSH clients.
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 ILOM service processor through the serial management port.
See the ILOM user’s guide for instructions.
3. Type one of the following commands:
| Note - If you have configured your server to use static IP addresses, but you wish to reset your network to use Dynamic Host Configuration Protocol (DHCP), type the following commands: |
-> set /SP/network pendingipdiscovery=dhcp Set ’pendingipdiscovery’ to ’dhcp’ -> set /SP/network commitpending=true Set ’commitpending’ to ’true’ -> |
4. Issue the following command to verify network settings:
To connect through the network management port, use ssh to the IP address you specified in Step 3.
The following procedure assumes that you are accessing the system console by connecting a terminal server to the serial management port (SER MGT) of your server.
1. Complete the physical connection from the serial management port to your terminal server.
The serial management port on the Sun Netra T5220 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 Netra T5220 server matches 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:
FIGURE 1-3 Patch Panel Connection Between a Terminal Server and a Sun Netra T5220 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 connects each pin on the Sun Netra T5220 server serial management port to the corresponding pin in the terminal server’s serial port.
TABLE 1-2 shows the crossovers that the cable must perform.
2. Open a terminal session on the connecting device, and type:
For example, for a Sun Netra T5220 server connected to port 10000 on a terminal server whose IP address is 192.20.30.10, you would type:
Use this procedure to access the Sun Netra T5220 server system console by connecting the serial management port (SER MGT) to the serial port of another system (FIGURE 1-4).
FIGURE 1-4 Tip Connection Between a Sun Netra T5220 Server and Another 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 system’s serial port (typically ttyb) and the serial management port on the back panel of the Sun Netra T5220 server.
2. Ensure that the /etc/remote file on the other system contains an entry for hardwire.
Most releases of Oracle Solaris OS software shipped since 1992 contain an /etc/remote file with the appropriate hardwire entry. However, if the system is running an older version of Oracle Solaris OS software, or if the /etc/remote file has been modified, you might need to edit the file. See Modifying the /etc/remote File for details.
3. In a shell tool window on the other system, type:
The system responds by displaying:
The shell tool is now a Tip window directed to the Sun Netra T5220 server through the system’s serial port. This connection is established and maintained even when the server is completely powered off or just starting up.
| Note - Use a shell tool or a terminal (such as dtterm), not a command tool. Some Tip commands might not work properly in a command tool window. |
This procedure might be necessary if you are accessing the Sun Netra T5220 server using a Tip connection from a system running an older version of the Oracle Solaris OS software. You might also need to perform this procedure if the /etc/remote file on the system has been altered and no longer contains an appropriate hardwire entry.
1. Log in as superuser to the system console of a system that you intend to use to establish a Tip connection to your server.
2. Determine the release level of Oracle Solaris OS software installed on the system. Type:
The system responds with a release number.
3. Take one of the following actions, depending on the number displayed.
The Oracle Solaris OS 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.
| Note - If you intend to use the system’s serial port A rather than serial port B, edit this entry by replacing /dev/term/b with /dev/term/a. |
Check the /etc/remote file and add the following entry, if it does not already exist.
| Note - If you intend to use the system’s serial port A rather than serial port B, edit this entry by replacing /dev/ttyb with /dev/ttya. |
The /etc/remote file is now properly configured. Continue establishing a Tip connection to the Sun Netra T5220 server system console. See Accessing the System Console Through 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 System Console OpenBoot Configuration Variable Settings.
Use this procedure when you are accessing the Sun Netra T5220 server system console by connecting the serial port of an alphanumeric terminal to the serial management port (SER MGT) of the 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. Connect this cable to the terminal’s serial port connector.
2. Attach the opposite end of the serial cable to the serial management port on the Sun Netra T5220 server.
3. Connect the alphanumeric terminal’s power cord to an AC/DC outlet.
4. Set the alphanumeric terminal to receive:
Refer to the documentation accompanying your terminal for information about how to configure the terminal.
You can now 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 ILOM service processor, refer to the ILOM guide and the ILOM supplement for your server.
Though it is not recommended, the system console can be redirected to the graphics frame buffer. 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 the following items:
|
|
1. Install the graphics card into an appropriate PCI slot.
Installation must be performed by a qualified service provider. For further information, refer to the service manual for your server 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/DC outlet.
4. Connect the USB keyboard cable to one USB port and the USB mouse cable to the other USB port on the Sun Netra T5220 server back panel (FIGURE 1-2).
For more information, see Procedures for Obtaining the ok Prompt.
6. Set OpenBoot configuration variables appropriately.
From the existing system console, type:
7. To cause the changes to take effect, type:
The system stores the parameter changes, and boots automatically when the OpenBoot configuration option auto-boot? is set to true (the default value).
| Note - To cause the parameter changes to take effect, you can also power cycle the system using the front panel Power button. |
You can now 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 System Console OpenBoot Configuration Variable Settings.
The service processor features two management ports, labeled SER 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 (the default configuration), these ports provide access to both the system console and the ILOM command-line interface (the ILOM service processor prompt), each on a separate channel (see FIGURE 1-5).
FIGURE 1-5 Separate System Console and Service Processor 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 ILOM command-line interface or the system console. You can switch between the ILOM service processor prompt and the system console at any time, but you cannot access both at the same time from a single terminal window or shell tool.
The prompt displayed on the terminal or shell tool tells you which channel you are accessing:
| Note - If no text or prompt appears, it might be because no console messages were recently generated by the system. Pressing the terminal’s Enter or Return key should produce a prompt. |
To reach the system console from the service processor, type the
start /SP/console command at the -> prompt.
To reach the service processor from the system console, type the service processor escape sequence. By default, the escape sequence is #. (Pound-Period).
For more information about communicating with the service processor and system console, see:
The ILOM service processor runs independently of the server and regardless of system power state. When you connect your server to AC/DC power, the ILOM service processor immediately starts up, and begins monitoring the system.
You can log in to the ILOM service processor at any time, regardless of system power state, as long as AC/DC power is connected to the system and you have a way of interacting with the system. You can also access the ILOM service processor prompt (->) from the OpenBoot ok prompt or from the Oracle Solaris # or % prompt, provided the system console is configured to be accessible through the serial management and network management ports.
The -> prompt indicates that you are interacting with the ILOM service processor directly. The -> prompt is the first prompt you see when you log in to the system through the serial management port or network management port, regardless of host’s power state.
| Note - When you access the ILOM service processor for the first time, the default username is root and the default password is changeme. |
For more information on navigating to or from the ILOM prompt, see the following:
Up to five ILOM sessions can be active concurrently, one session through the serial management port and up to four SSH sessions through the network management port. Users of each of these sessions can issue commands at the -> prompt. However, only one user at a time can access the system console, and then only if the system console is configured to be accessible through the serial and network management ports. For more information, see:
Any additional ILOM sessions afford passive views of system console activity, until the active user of the system console logs out.
There are several ways to obtain the -> prompt:
A Sun Netra T5220 server with the Oracle Solaris OS installed operates at different run levels. For a full description of run levels, refer to the Oracle Solaris system administration documentation.
Most of the time, you operate a Sun Netra T5220 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 Netra T5220 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 under which OpenBoot firmware control can occur.
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. Several ways to do this are outlined in Reaching the ok Prompt. For detailed instructions, see Procedures for Obtaining the ok Prompt.
ok Prompt Not Available After the Oracle Solaris OS StartsThe OpenBoot firmware is not available and might be removed from memory once the Oracle Solaris OS starts.
To reach the ok prompt from the Oracle Solaris OS, you must first halt the domain. Use the Oracle Solaris OS halt(1M) command to halt the domain.
There are several ways to reach the ok prompt, depending on the state of the system and the means by which you are accessing the system console. In decreasing order of desirability, the list is as follows:
| Note - To reach the ok prompt after a shutdown or reset of the server, the
auto-boot? option must be set to false. Also, you must shutdown or restart the Oracle Solaris OS to get to the ok prompt. You cannot reach the ok prompt from the Oracle Solaris OS (see OpenBoot ok Prompt Not Available After the Oracle Solaris OS Starts).
|
A discussion of each method follows. For step-by-step instructions, see Procedures for Obtaining the ok Prompt.
The preferred method of reaching the ok prompt is to shut down the operating system by issuing an appropriate command (for example, shutdown, init, or uadmin commands) as described in Oracle Solaris system administration documentation. The ILOM reset command also performs a graceful shutdown. However, when using the ILOM reset command, if a graceful shutdown is not possible, a forced shutdown is performed. 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 Oracle Solaris OS is running and the hardware has not experienced serious failure.
You can also perform a graceful system shutdown from the ILOM service processor command prompt using the stop /SYS command.
Use the ILOM reset command to gracefully reset the control domain and obtain the ok prompt. If a graceful shutdown is not possible, a forced shutdown is performed. To use this method to obtain the ok prompt, you must first set the control domain auto-boot? option to false.
Use the ILOM service processor reset /SYS command, or start /SYS and
stop /SYS commands, to reset the server. Reaching the ok prompt by performing a manual system reset or by power-cycling the system always first attempts a graceful shutdown. If a graceful shutdown is not possible, a forced shutdown is performed. A forced shutdown results in the loss of all system coherence and state information. A forced system reset could corrupt the server’s file systems, although the fsck command usually restores them.
|
Caution - Accessing the okprompt shuts down the Oracle Solaris OS. You cannot return to the Oracle Solaris OS without rebooting the OS, for example with the bootcommand. |
|
|
When it is impossible or impractical to shut down the system gracefully, you can get to the ok prompt, if you have an alphanumeric terminal attached to the Sun Netra T5220 server, by pressing the Break key.
The equivalent method uses the following pair of commands:
1. Type set /HOST send_break_action=break
This command forces a running Sun Netra T5220 server to drop to a menu. For example:
-> set /HOST send_break_action=break Set ‘send_break_action’ to ‘break’ -> start /SP/console Are you sure you want to start /SP/console (y/n)? y Serial console started. To stop, type #. |
3. Select r to reset the system and stop at the ok prompt if the autoboot? option is set to false.
Selecting c returns you to the Oracle Solaris prompt without reset.
Selecting s causes a core dump, a hard reset of the control domain (the host if no guest domains have been configured), then boots the Oracle Solaris OS.
| Note - After forcing the system into OpenBoot firmware control, be aware that typing certain OpenBoot commands (like probe-scsi, probe-scsi-all, or probe-ide) might hang the system. |
| Note - These methods of reaching the ok prompt will only work if the system console has been left in the default setting of virtual-console. For details, see System Console OpenBoot Configuration Variable Settings. |
If possible, back up system data before starting this procedure. Also exit or stop all applications, and warn users of the impending loss of service. For information about the appropriate backup and shutdown procedures, see Oracle Solaris system administration documentation.
|
1. Decide which procedure you need to use to reach the ok prompt.
See OpenBoot ok Prompt for details.
2. Follow the appropriate instructions in TABLE 1-3.
|
From a shell or command tool window, type an appropriate command (for example, the init 0 or uadmin 2 0 commands) as described in Oracle Solaris system administration documentation. |
|
|
Graceful reset of the control domain using the ILOM reset command |
From the -> prompt in the control domain, type: |
-> set /HOST/bootmode script="setenv auto-boot? false" |
|
|
From an alphanumeric terminal configured to access the system console, press the Break key. After the break, if a debugger is present the domain breaks to KMDB debugger prompt, which allows access to the c)continue, s)ync, r)eset? prompt. If a debugger is not present, the c)continue, s)ync, r)eset? prompt occurs:
See To Shutdown the Server Using the Break Key or the Equivalent Pair of ILOM Commands for instruction on using the equivalent ILOM break command pair. |
For more information about the OpenBoot firmware, refer to the OpenBoot 4.x Command Reference Manual. An online version of the manual is available at: http://docs.sun.com
On the Sun Netra T5220 server, the system console is directed to the serial management and network management ports (SER MGT and NET MGT) by default. However, you can redirect the system console 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 where system console input is taken from and where its output is directed. The table below shows how to set these variables in order to use either the serial management and network management ports, or a local graphics monitor, as the system console connection.
output-device |
virtual-console |
screen |
input-device |
virtual-console |
keyboard |
| Note - POST output will still be directed to the serial management port, as POST has no mechanism to direct its output to a graphics monitor. |
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 must connect it to ttya not to the serial management port.)
The -> prompt and POST messages are only available through the serial management port and network management port. The ILOM service processor start /SP/console command is ineffective when the system console is redirected to a local graphics monitor.
In addition to the OpenBoot configuration variables described in TABLE 1-4, there are other variables that affect and determine system behavior. These variables are discussed in more detail in Appendix A.
| Sun Netra T5220 Server Administration Guide | 820-3010-12 |
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
To Use the Serial Management Port
