| Sun Fire V490 Server Administration Guide |    
|
| Sun Fire V490 Server Administration Guide |
|
| C H A P T E R 7 |
|
Configuring Console Access |
This chapter includes instructions on how to configure and access the system console from different physical devices.
Tasks covered in this chapter include:
|
Note - Many of the procedures in this chapter assume that you are familiar with the OpenBoot firmware and that you know how to enter the OpenBoot environment. For background information, see About the ok Prompt. For instructions, see How to Get to the ok Prompt. |
Qualified service technicians should use the following procedure to prevent static damage whenever they access any of the internal components of the system.
You must have the following items:
1. Disconnect the AC power cords from the wall power outlet only when performing the following procedures:
The AC power cord provides a discharge path for static electricity, so it should remain plugged in except when you are servicing the parts noted above.
2. Use an antistatic mat or similar surface.
When performing any installation or service procedure, place static-sensitive parts, such as boards, cards, and disk drives, on an antistatic surface. The following items can be used as an antistatic surface:
3. Use an antistatic wrist strap.
Attach the appropriate end to the system chassis sheet metal and attach the other end of the strap to your wrist. Refer to the instructions that come with the strap.
|
Note - Make sure that the wrist strap is in direct contact with the metal on the chassis. |
4. Detach both ends of the strap after you have completed the installation or service procedure.
To power on the system, complete this task:
Do not use this power-on procedure if you have just added any new internal option or external storage device, or if you have removed a storage device without replacing it. To power on the system under those circumstances, you must initiate a reconfiguration boot. For those instructions, see How to Initiate a Reconfiguration Boot .
You can also use RSC software to power on the system. For details, see:
|
Caution - Never move the system when the system power is on. Movement can cause catastrophic disk drive failure. Always power off the system before moving it. |
|
Caution - Before you power on the system, make sure that all access panels are properly installed. |
1. Turn on power to any peripherals and external storage devices.
Read the documentation supplied with the device for specific instructions.
2. Turn on power to the ASCII terminal or local graphics terminal, if present.
Use the system key to unlock the media door.
4. Insert the system key into the system control switch and turn the system control switch to the Normal position.
See System Control Switch for information about each system control switch setting.
5. Press the Power button that is below the system control switch to power on the system.
6. Turn the system control switch to the Locked position.
This prevents anyone from accidentally powering off the system.
7. Remove the system key from the system control switch and keep it in a secure place.
To power off the system, complete this task:
Applications running on the Solaris OS can be adversely affected by a poorly executed system shutdown. Make sure that you have gracefully shut down any applications before powering off the system.
You can also use Solaris commands, the OpenBoot firmware power-off command, or RSC software to power off the system. For details, see:
1. Notify users that the system will be powered down.
2. Back up the system files and data, if necessary.
3. Ensure that the system control switch is in the Normal position.
4. Press and release the Power button on the system front panel.
The system begins a graceful software system shutdown.
5. Wait for the front panel Power/OK LED to turn off.
6. Turn the system control switch to the Forced Off position.
7. Remove the system key from the system control switch and keep it in a secure place.
Qualified service technicians can now continue with parts removal and installation, as needed.
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:
If at all possible, back up system data before starting this procedure. Also halt all applications and warn users of the impending loss of service. For information about the appropriate backup and shutdown procedures, see Solaris system administration documentation.
1. Decide which method you need to use to reach the ok prompt.
See About the ok Prompt for details.
2. Refer to TABLE 7-1 for instructions.
1. Locate the RJ-45 twisted-pair Ethernet (TPE) connector for the appropriate Ethernet interface--the top connector or the bottom connector.
See Locating Back Panel Features. For a PCI Ethernet adapter card, see the documentation supplied with the card.
2. Connect a Category-5 unshielded twisted-pair (UTP) cable to the appropriate RJ-45 connector.
You should hear the connector tab click into place. The UTP cable length must not exceed 100 meters (328 feet).
3. Connect the other end of the cable to the RJ-45 outlet to the appropriate network device.
You should hear the connector tab click into place.
Consult your network documentation if you need more information about how to connect to your network.
If you are installing your system, complete the installation procedure. Return to Chapter 1.
If you are adding an additional network interface to the system, you need to configure that interface. See:
The following procedure assumes you are connecting to the serial port (ttya) of the Sun Fire V490 system using a tip connection from serial port B (ttyb) of another Sun server, and that the other Sun server has its own local graphics terminal.
1. Decide whether you need to reset OpenBoot configuration variables on the Sun Fire V490 system.
Certain OpenBoot configuration variables control from where system console input is taken and to where its output is directed.
2. If necessary, reset OpenBoot configuration variables.
From the existing system console, type:
|
Note - There are many other OpenBoot configuration variables, and although these do not affect which hardware device is used as the system console, some of them affect what diagnostic tests the system runs and what messages the system console displays. For details, see Controlling POST Diagnostics. |
3. Connect the RJ-45 serial cable and adapter.
The cable and adapter connect the Sun server's ttyb serial port to the Sun Fire V490 system's built-in ttya serial port. Pinouts, part numbers, and other details about the serial cable and adapter are provided in the Sun Fire V490 Server Parts Installation and Removal Guide.
4. Ensure that the /etc/remote file on the Sun server 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 server is running an older version of Solaris OS software, or if the /etc/remote file has been modified, you may need to edit it. See How to Modify the /etc/remote File for details.
5. In a terminal tool window on the Sun server, type:
The Sun server responds by displaying:
The terminal tool is now a tip window directed to the Sun Fire V490 system via the Sun server's ttyb port. This connection is established and maintained even if the Sun Fire V490 system is completely powered off or just starting up.
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.
You may need to perform this procedure to access the system console via a tip connection from a Sun server running an older version of the Solaris OS software.
You may also need to perform this procedure if the /etc/remote file on the Sun server has been altered and no longer contains an appropriate hardwire entry.
This procedure assumes you are connecting via tip line from serial port B (ttyb) of a Sun server to the serial port (ttya) of the Sun Fire V490 machine.
1. Determine the release level of system software installed on the Sun server.
The system responds with a release number.
2. Do one of the following, depending on the number displayed.
The server software shipped with an appropriate entry for hardwire in the /etc/remote file. If you have reason to suspect this file was altered and the hardwire entry modified or deleted, check the entry against the example given in CODE EXAMPLE 7-1, and edit it as needed.
|
Note - If you intend to use the Sun server'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 entry shown in CODE EXAMPLE 7-2, if it does not already exist.
|
Note - If you intend to use the Sun server'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 Fire V490 server's system console. See
This procedure lets you verify the baud rate and other serial port settings used by the Sun Fire V490 server to communicate with attached serial port devices.
You must be logged in to the Sun Fire V490 server, and the server must be running Solaris OS software.
1. Open a terminal tool window.
3. Look for the following output:
This line indicates that the Sun Fire V490 server's serial port is configured for:
For more information about serial port settings, see the eeprom man page. For instructions on setting the ttya-mode OpenBoot configuration variable, see
To perform initial installation of the system, you need to attach an alphanumeric (ASCII) terminal to the server. Alternatively, you can create a tip connection from another Sun system. For instructions, see How to Access the System Console via tip Connection.
After initial installation of Solaris OS software, if you have reconfigured the system console to take its input and output from different devices, you can follow this procedure to change back to using an alphanumeric terminal as the system console.
For detailed information about system console options, see About Communicating With the System.
1. Attach one end of the serial cable to the alphanumeric terminal's serial port.
Use an RJ-45 null modem serial cable or an RJ-45 serial cable and null modem adapter. Plug this into the terminal's serial port connector.
2. Attach the opposite end of the serial cable to the Sun Fire V490 system.
Plug the cable into the system's built-in serial port (ttya) connector.
3. Connect the alphanumeric terminal's power cord to an AC outlet.
4. Set the alphanumeric terminal to receive:
See the documentation accompanying your terminal for information about how to configure it.
5. Decide whether you need to reset OpenBoot configuration variables.
Certain OpenBoot configuration variables control from where system console input is taken and to where its output is directed.
6. If necessary, reset OpenBoot configuration variables.
From the existing system console, type:
|
Note - There are many other OpenBoot configuration variables, and although these do not affect which hardware device is used as the system console, some of them affect what diagnostic tests the system runs and what messages the system console displays. For details, see Controlling POST Diagnostics. |
7. To cause the changes to take effect, type:
The system permanently stores the parameter changes and boots automatically if the OpenBoot variable auto-boot? is set to true (its default value).
You can issue system commands and view system messages on the ASCII terminal. Qualified service technicians can now continue with parts removal and installation, as needed.
After initial system installation, a qualified service technician can install a local graphics terminal and set it up as the system console. You cannot use a local graphics terminal to perform initial system installation, nor can you use a local graphics terminal to view power-on self-test (POST) messages. For detailed information about system console options, see About Communicating With the System.
To install a local graphics terminal, you must have:
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 V490 Server Parts Installation and Removal Guide or contact your qualified service provider.
2. Attach the monitor 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 keyboard USB cable to any USB port on the back panel.
5. Connect the mouse USB cable to any USB port on the back panel.
6. Set OpenBoot configuration variables appropriately.
From the existing system console, type:
|
Note - There are many other OpenBoot configuration variables, and although these do not affect which hardware device is used as the system console, some of them affect what diagnostic tests the system runs and what messages the system console displays. For details, see Controlling POST Diagnostics. |
7. To cause the changes to take effect, type:
The system permanently stores the parameter changes and boots automatically if the OpenBoot variable auto-boot? is set to true (its default value).
You can issue system commands and view system messages from your local graphics terminal. Continue with your diagnostic or other procedure as needed.
After installing any new internal option or external storage device, you must perform a reconfiguration boot so that the operating system is able to recognize the newly installed device(s). In addition, if you remove any device and do not install a replacement device prior to rebooting the system, you must perform a reconfiguration boot in order for the operating system to recognize the configuration change. This requirement also applies to any component that is connected to the system's I2C bus, including memory modules, CPU/Memory boards, and power supplies.
This requirement does not apply to any component that is:
|
Caution - Before you power on the system, make sure that the system doors and all panels are properly installed. |
To issue software commands, you need to set up a system ASCII terminal, a local graphics terminal, or a tip connection to the Sun Fire V490 system. See:
1. Turn on power to any peripherals and external storage devices.
Read the documentation supplied with the device for specific instructions.
2. Turn on power to the ASCII terminal or local graphics terminal.
3. Insert the system key into the system control switch and turn the switch to the Diagnostics position.
See System Control Switch for information about control switch settings.
4. Press the Power button below the control switch to power on the system.
5. Wait for the ok prompt to appear.
The system may take anywhere from 15 to 30 minutes before the ok prompt appears. This time depends on the system configuration (number of processors, memory modules, PCI cards) being tested.
6. Turn the system control switch to the Normal position.
Depending on how the auto-boot OpenBoot configuration variable is set, the system may or may not start to reboot its operating system.
8. If the operating system starts to reboot, do the following.
a. Wait until the system has completed initializing memory.
During initialization, you see the message:
b. Watch carefully, as you will need to act quickly.
Once the process is complete, the Initializing memory message is erased and the system displays a line similar to:
c. At this point, abort the boot process as promptly as possible.
To do this, use one of the following methods:
The system should return to the ok prompt.
|
Note - If the system does not return to the ok prompt, it means you did not abort quickly enough. If this occurs, wait for the system to reboot, force the system to return to the ok prompt, and repeat Step 7. |
The boot -r command rebuilds the device tree for the system, incorporating any newly installed options so that the operating system will recognize them.
10. Turn the control switch to the Locked position, remove the key, and keep it in a secure place.
This prevents anyone from accidentally powering off the system.
The system's front panel LED indicators provide power-on status information. For more information about the system LEDs, see:
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 ttya, the system controller, or a local graphics terminal as the system console.
In addition to the above OpenBoot configuration variables, there are other variables that determine whether and what kinds of diagnostic tests run. These variables are discussed in Controlling POST Diagnostics.
| Sun Fire V490 Server Administration Guide | 817-3951-10 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
