| Sun Netra T5440 Server | 
   |
| C H A P T E R 1 |
This chapter explains what the system console is, describes the different ways of configuring it on Oracle’s Sun Netra T5440 server, and helps you understand the relationship between the system console and the service processor. This chapter contains the following sections:
Switching Between the Service Processor and the System Console
System Console OpenBoot Configuration Variable Settings
Note - For information about changing the hardware configuration of your server, or about running diagnostics, see the Sun Netra T5440 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.
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 T5440 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.
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 Legend
1 PCI Slots 0-3: left to right: PCI-X Slot 0 (25 W maximum load), PCI-X Slot 1 (25 W maximum load), PCIe Slot 2 (25 W maximum load), PCIe Slot 3 (25 W maximum load)
2 PCI (or XAUI) Slots 4-9: left to right: PCIe or XAUI Slot 4 (15 W maximum load), PCIe or XAUI Slot 5 (15 W maximum load), PCIe Slot 6 (15 W maximum load), PCIe Slot 7 (15 W maximum load), PCIe Slot 8 (15 W maximum load), PCIe Slot 9 (15 W maximum load)
3 Service Processor Serial Management Port
4 Service Processor Network Management Port
5 Gigabit Ethernet Ports left to right: NET0, NET1, NET2, NET3
6 Power Supply 0 LEDs top to bottom: Output On LED (green), Service Required LED (yellow), Input Power OK LED (green)
7 Power Supplies (PSs): left to right: PS 0, PS 1, PS 2, PS 3
8 USB ports left to right: USB2, USB3
9 TTYA Serial Port
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 T5440 server. The Solaris OS sees this port as ttya.
For instructions on accessing the system console through a terminal server, see Accessing the System Console Through a Terminal Server.
For instructions on accessing the system console through an alphanumeric terminal, see Accessing the System Console Through an Alphanumeric Terminal.
For instructions on accessing the system console through a Tip line, see Accessing the System Console Through a Tip Connection.
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:
In a default configuration, the serial management and network management ports enable you to open up to eight additional windows through which you can view, but not affect, system console activity. You cannot open these connections if the system console is redirected 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 service processor output on the same device by typing a simple escape sequence or command. The escape sequence and command do not work if the system console is redirected to a graphics card’s port.
The service processor keeps a log of console messages, but some messages are not logged if the system console is redirected to a graphic card’s port. The omitted information could be important if you need to contact customer service about a problem.
You change the system console configuration by setting OpenBoot configuration variables. See System Console OpenBoot Configuration Variable Settings.
The Sun Netra T5440 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 serv ice processor, refer to the ILOM user’s guide and the Integrated Lights Out Management 2.0 Supplement for the Sun Netra T5440 Server.
Ensure that the serial port on your connecting device is set to the following parameters:
To connect to the system console, at the ILOM command prompt, type:
-> start /SP/console |
The start /SP/console command switches you to the system console.
To switch back to the -> prompt, type the #. (Hash-Period) escape sequence.
ok #. |
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 T5440 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.
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.
Log in to the ILOM service processor through the serial management port.
Type one of the following commands:
If your network uses static IP addresses, type the following set of commands:
-> set /SP/network state=enabled Set ’state’ to ’enabled’ -> set /SP/network pendingipaddress=xx.xxx.xx.xxx Set ’pendingipaddress’ to ’xx.xxx.xx.xxx’ -> set /SP/network pendingipdiscovery=static Set ’pendingipdiscovery’ to ’static’ -> set /SP/network pendingipnetmask=255.255.252.0 Set ’pendingipnetmask’ to ’255.255.252.0’ -> set /SP/network pendingipgateway=xx.xxx.xx.xxx Set ’pendingipgateway’ to ’xx.xxx.xx.xxx’ -> set /SP/network commitpending=true Set ’commitpending’ to ’true’ -> |
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’ -> |
Type the following command to verify network settings:
-> show /SP/network |
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.
Complete the physical connection from the serial management port to your terminal server.
The serial management port on the Sun Netra T5440 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 T5440 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:
Connect a serial interface breakout cable directly to the Sun Netra T5440 server. See Accessing the Service Processor.
Connect a serial interface breakout cable to a patch panel and use the straight-through patch cable (supplied by your server’s manufacturer) to connect the patch panel to the 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 T5440 server serial management port to the corresponding pin in the terminal server’s serial port.
The following table shows the crossovers that the cable must perform for connecting to a typical terminal server..
Open a terminal session on the connecting device, and type:
% ssh IP-address-of-terminal-server port-number |
For example, for a Sun Netra T5440 server connected to port 10000 on a terminal server whose IP address is 192.20.30.10, you would type:
% ssh 192.20.30.10 10000 |
Use this procedure to access the Sun Netra T5440 server system console by connecting the serial management port (SER MGT) to the serial port of another system (FIGURE 1-4).
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 T5440 server.
Ensure that the /etc/remote file on the other 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 system is running an older version of 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.
In a shell tool window on the other system, type:
% tip hardwire |
The system responds by displaying:
connected |
The shell tool is now a Tip window directed to the Sun Netra T5440 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 T5440 server using a Tip connection from a 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 system has been altered and no longer contains an appropriate hardwire entry.
Log in as superuser to the system console of a system that you intend to use to establish a Tip connection to your server.
Determine the release level of Solaris OS software installed on the system. Type:
# uname -r |
Take one of the following actions, depending on the number displayed.
If the number displayed by the uname -r command is 5.0 or higher:
The 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.
hardwire:\ :dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D: |
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. |
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: |
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 T5440 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 T5440 server system console by connecting the serial port of an alphanumeric terminal to the serial management port (SER MGT) of the server.
|
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.
Attach the opposite end of the serial cable to the serial management port on the Sun Netra T5440 server.
Connect the alphanumeric terminal’s power cord to an AC/DC outlet.
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 User’s Guide and the Sun Integrated Lights Out Management (ILOM) x.x Supplement for the Sun Netra T5440 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:
Supported PCI-based graphics accelerator card and software driver
Monitor with appropriate resolution to support the frame buffer
|
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.
Attach the monitor’s video cable to the graphics card’s video port.
Connect the USB keyboard cable to one USB port and the USB mouse cable to the other USB port on the Sun Netra T5440 server back panel (FIGURE 1-2).
For more information, see To Obtain the ok Prompt.
Set OpenBoot configuration variables appropriately.
From the existing system console, type:
ok setenv input-device keyboard ok setenv output-device screen |
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 (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).
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:
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 -> prompt indicates that you are at the service processor.
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 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:
If the system console is directed to the serial management and network management ports, you can type the ILOM escape sequence (#.).
You can log in directly to the service processor from a device connected to the serial management port. See Accessing the Service Processor.
You can log in directly to the service processor using a connection through the network management port. See Activating the Network Management Port.
A Sun Netra T5440 server with the Solaris OS installed operates at different run levels. For a full description of run levels, refer to the Solaris system administration documentation.
Most of the time, you operate a Sun Netra T5440 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 T5440 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.
By default, before the operating system is installed the system comes up under OpenBoot firmware control.
When the auto-boot? OpenBoot configuration variable is set to false, the system boots to the ok prompt.
When the operating system is halted, the system transitions to run level 0 in an orderly way.
When the operating system crashes, the system reverts to OpenBoot firmware control.
During the boot process, when there is a serious hardware problem that prevents the operating system from running, the system reverts to OpenBoot firmware control.
When a serious hardware problem develops while the system is running, the operating system transitions smoothly to run level 0.
When you deliberately place the system under firmware control in order to execute firmware-based commands, the OpenBoot firmware is in control.
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 To Obtain the ok Prompt.
The OpenBoot firmware is not available and might be removed from memory once the Solaris OS starts.
To reach the ok prompt from the Solaris OS, you must first halt the domain. Use the 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, these are:
ILOM service processor set /HOST send_break_action=break and start /SP/console command pair
Graceful reset of the control domain using ILOM reset command
A discussion of each method follows. For step-by-step instructions, see To Obtain 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, the shutdown, init, or uadmin command) as described in Solaris system administration documentation.
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 ILOM service processor command prompt using the stop /SYS command.
|
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 server, by pressing the Break key.
Type set /HOST send_break_action=break to force a running Sun Netra T5440 server to drop to a menu:
-> 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 #. |
c)ontinue, s)ync, r)eboot, h)alt? |
Type c to get OpenBoot firmware control.
When init 0 is used, the server drops to this menu:
r)eboot, o)k prompt, h)alt? |
From this menu, you can type o to get OpenBoot firmware control.
If the operating system is already halted, you can use the start /SP/console command instead of set /HOST send_break_action=break to reach the ok prompt.
Note - After forcing the system into OpenBoot firmware control, be aware that issuing certain OpenBoot commands (such as 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 redirected to the appropriate port. For details, see System Console OpenBoot Configuration Variable Settings. |
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 ok prompt suspends the Solaris OS. You cannot return to the Solaris OS without rebooting the OS, for example with the boot 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.
Decide which method you need to use to reach the ok prompt.
See OpenBoot ok Prompt for details.
Follow the appropriate instructions in the following table.
The following table describes ways of accessing the ok prompt.
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 T5440 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.
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-2, there are other variables that affect and determine system behavior. These variables are discussed in more detail in Appendix A.
| Sun Netra T5440 Server | 820-4443-11 |
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.
To Use the Serial Management
Port