Sun Fire™ V100 Server User’s Guide Sun Microsystems, Inc. 901 San Antonio Road Palo Alto, CA 94303 U.S.A. 650-960-1300 Part No.816-2756-10 Revision A December 2001 Send comments about this document to: docfeedback@sun.
Copyright 2001 Sun Microsystems, Inc., 901 San Antonio Road, Palo Alto, CA 94303-4900 U.S.A. All rights reserved. This product or document is distributed under licenses restricting its use, copying, distribution, and decompilation. No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors, if any. Third-party software, including font technology, is copyrighted and licensed from Sun suppliers.
Contents 1. Introducing the Sun Fire V100 Server Overview of the Sun Fire V100 Server Contents of the Ship Kit Preinstalled Software 2 3 3 Optional Components 4 Installation Quick Start 2. 1 5 Installing the Sun Fire V100 Server Into a Rack Choosing Between a Rack and a Cabinet 7 8 Installing the Sun Fire V100 Server Into a 19-Inch Wide or 72-inch Tall Four-Post Rack The 19-Inch Rackmounting Kit 8 Tips for Using a Sun StorEdge 72-inch Rack Connecting the Cables 3.
Connecting to the Server Using a Sun Workstation or ASCII Terminal Connecting to the Server Using a Terminal Server Connecting to a Cisco Terminal Server 25 Connecting to Other Terminal Servers 26 25 Connecting to the Server Using a System Running Microsoft Windows Connecting to the Server Using a Handheld Device Using the Arrow Keys 4. Powering On and Configuring the Sun Fire V100 Server Using the Power (On/Standby) Switch 5.
Checking the Supply Rail Voltages and Internal Circuit Breakers (lom v) 67 Configuring Automatic Server Restart 73 Enabling the LOM Watchdog Process From Your Own Script or Command (lom -W on) 74 Other LOM Tasks You Can Perform From the Solaris Prompt 7. Interpreting the LEDs 81 Interpreting the Front- and Back-Panel LEDs 8.
No LOM Messages Displayed at the Terminal 105 Cannot Display the lom> Prompt Using the #.
Figures FIGURE 1-1 The Sun Fire V100 server 2 FIGURE 2-1 Cable Management Bracket FIGURE 2-2 Positioning the Slide Mounts for a Sun StorEdge 72-Inch Tall Rack 10 FIGURE 2-3 Positioning the Slide Mounts for a Standard 19-Inch Wide Rack 10 FIGURE 2-4 Fastening the Slide Mounts to a Sun StorEdge 72-inch Tall Rack – Rear View (Side Panels Removed for Clarity) 11 FIGURE 2-5 Fastening the Slide Mounts to a Sun StorEdge 72-inch Expansion Rack – Front View (Side Panels Removed for Clarity) 12 FIGURE 2-
viii FIGURE 8-3 Removing the Top Cover 89 FIGURE 8-4 Replacing the Top Cover 90 FIGURE 8-5 DIMM Insertion and Removal Sequence 91 FIGURE 8-6 Installing Memory Into a Socket on the System Board 92 FIGURE 8-7 Removing the HDD Placeholder FIGURE 8-8 Installing a Hard Disk Drive 94 FIGURE 10-1 The obdiag Menu 101 93 Sun Fire V100 Server User’s Guide • December 2001
Tables TABLE 1-1 Contents of the Ship Kit 3 TABLE 1-2 Customer Installable Hardware 4 TABLE 2-1 19-inch Rackmounting Kit TABLE 3-1 Server Serial Ports TABLE 3-2 Settings for Connecting to the Serial A/LOM or Serial B Port 21 TABLE 3-3 Serial Adapters 22 TABLE 3-4 Pin Crossovers in the Sun DB-25 (25-Pin) Adapter 22 TABLE 3-5 Pin Crossovers in the DB-9 (9-Pin) Adapter 23 TABLE 3-6 Pin Crossovers for Connecting to a Typical Terminal Server TABLE 3-7 Example PalmOS Terminal Emulator Macros
x Sun Fire V100 Server User’s Guide • December 2001
Preface The Sun Fire™ V100 Server User’s Guide describes how to install, manage, and maintain the Sun Fire V100 server. The manual is intended for system administrators who have experience in setting up networked SolarisTM servers. How This Book Is Organized Part I Installation and Configuration Chapter 1 introduces the Sun Fire V100 server, gives an overview of its specifications, lists the optional components available and includes an installation quick start guide.
Part III Maintenance and Troubleshooting Chapter 7 provides information about the fault and power indicators and explains how to identify a faulty system in a rack. Chapter 8 describes how to swap system configuration cards and how to open the Sun Fire V100 server to add memory or a hard disk drive. Chapter 9 describes how to reinstall the Solaris operating environment. Chapter 10 describes the diagnostic tools that are available, and provides troubleshooting and frequently asked questions sections.
Typographic Conventions Typeface Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your .login file. Use ls -a to list all files. % You have mail. AaBbCc123 What you type, when contrasted with on-screen computer output % su Password: AaBbCc123 Book titles, new words or terms, words to be emphasized Read Chapter 6 in the User’s Guide. These are called class options. You must be superuser to do this.
Accessing Sun Documentation Online A broad selection of Sun system documentation is located at: http://www.sun.com/products-n-solutions/hardware/docs A complete set of Solaris documentation and many other titles are located at: http://docs.sun.com Ordering Sun Documentation Fatbrain.com, an Internet professional bookstore, stocks select product documentation from Sun Microsystems, Inc. For a list of documents and how to order them, visit the Sun Documentation Center on Fatbrain.com at: http://www.fatbrain.
■ Follow all cautions and instructions marked on the equipment. ■ Never push objects of any kind through openings in the equipment. Dangerous voltages may be present. Conductive foreign objects can produce a short circuit that could cause fire, electric shock, or damage to your equipment. Symbols The following symbols may appear in this manual: Caution – There is a risk of personal injury and equipment damage. Follow the instructions. Caution – Hazardous voltages are present.
Caution – Mounting of the equipment in a rack or cabinet should be such that a hazardous condition is not created due to uneven mechanical loading or weight distribution. Caution – Ensure that the connection of multiple system units to the circuit does not overload the supply overcurrent protection or supply wiring. Consider the Sun agency label electrical ratings when determining the correct branch circuit rating for your installation.
PA RT I Installation and Configuration
CHAPTER 1 Introducing the Sun Fire V100 Server This chapter gives an overview of the Sun Fire V100 server. It lists the features of the server and the contents of the ship kit, and lists the optional components available. It also gives you an overview of the installation process.
Overview of the Sun Fire V100 Server The Sun Fire V100 server is a single-processor server in a one rack unit (1 RU) chassis. It is designed to maximize the density of high-performance Solaris servers in a rack.
Contents of the Ship Kit The Sun Fire V100 server is supplied with the following components: TABLE 1-1 Contents of the Ship Kit Item Part Number Quantity RJ-45 to RJ-45 patch cable for Ethernet or serial connection 530-2093-xx 2 RJ-45 to DB-25 adapter 530-2889-xx 1 RJ-45 to DB-9 adapter 530-3100-xx 1 Rackmounting screws, 10-32x1/2 240-1207-xx 8 Front slide mount 340-6125-xx 2 Rear slide mount 340-6234-xx 2 Cable management bracket 340-6151-xx 1 M4 nuts 240-1373-xx 4 Rack screw
Optional Components Sun offers additional hard disk drives and memory modules for the server. To order them, contact your local Sun sales representative. See TABLE 1-2 for a list of components and part numbers. The server should be seen as a replaceable unit: if a fault occurs, contact your local Sun sales representative for a replacement.
Installation Quick Start Task See in the Sun Fire V100 Server User’s Guide 1 Install the Hardware Mount in the rack. “Installing the Sun Fire V100 Server Into a Rack” on page 7 Connect the cables. “Connecting the Cables” on page 17 Set up a console connection. “Setting Up a Console Connection to the Server” on page 20 2 Configure the Server Note: The server is preinstalled with the Solaris 8 operating environment. Power on the server.
6 Sun Fire V100 Server User’s Guide • December 2001
CHAPTER 2 Installing the Sun Fire V100 Server Into a Rack This chapter explains how to install the Sun Fire V100 server into a rack and describes the mounting options available. It also contains a guide on connecting the cables to the server.
Choosing Between a Rack and a Cabinet The Sun Fire V100 server can be installed in either a rack or a cabinet. Factors that might influence your decision include: ■ Security If other people have access to the room in which your servers are located, you can increase security by locking the servers in a cabinet. ■ Thermal issues Cabinets often require additional fans, because the systems installed in them generate heat in an enclosed space. Two-post racks, however, may require no special cooling systems.
A bracket is provided to aid cable management at the back of the server (see FIGURE 2-1). Use zip ties to secure the cables to the cable management bracket and hold them in place. FIGURE 2-1 ▼ Cable Management Bracket To Assemble the Slides and Mount the Server 1. Position the two parts of the slide so that the double-angled ear (A) is in the correct position for the rack you are installing into.
■ For a standard 19-inch wide rack, the double-angled ear (A) must be to the front (see FIGURE 2-3). A FIGURE 2-2 Positioning the Slide Mounts for a Sun StorEdge 72-Inch Tall Rack A FIGURE 2-3 Positioning the Slide Mounts for a Standard 19-Inch Wide Rack 2. Loosely screw the two parts of the slide mounts together using the M4 nuts supplied. 3. Measure the distance between the front and back posts of your rack. 4.
5. Move the brackets so that the studs are in suitable slots and tighten the nuts. 6. Fasten the mounting slides to the rack using the screws supplied. For the Sun StorEdge 72-inch rack, refer to FIGURE 2-4 and FIGURE 2-5. Leave the screws slightly loose to allow adjustment when you slide the server into the rack. For a standard 19-inch rack, refer to FIGURE 2-6. Leave the screws slightly loose to allow adjustment when you slide the server into the rack.
FIGURE 2-5 12 Fastening the Slide Mounts to a Sun StorEdge 72-inch Expansion Rack – Front View (Side Panels Removed for Clarity) Sun Fire V100 Server User’s Guide • December 2001
FIGURE 2-6 Fastening the Slide Mounts to a Standard 19-inch Rack 7. Slide the server into the rack (see FIGURE 2-7).
FIGURE 2-7 14 Sliding the Sun Fire V100 Server Into a Standard 19-Inch Rack Sun Fire V100 Server User’s Guide • December 2001
8. Align the thumbscrews on the sides of the server with the slide mounts in the rack (see FIGURE 2-8). If necessary, readjust the slide mounts to align the server properly. The thumbscrews need to be finger-tight. FIGURE 2-8 Adjusting the Slide Mounts and Screwing the Server Into the Rack 9. Tighten the slide mounts in the rack if you have not fully secured them yet. 10. When the slide mounts are secure, use a screwdriver to tighten the thumbscrews on the side of the server.
Cable management bracket FIGURE 2-9 Fitting the Cable Management Bracket to a Sun StorEdge or a Standard 19Inch Rack Tips for Using a Sun StorEdge 72-inch Rack 16 ■ For maximum stability, fill the rack from the bottom up and at the top leave at least four rack units empty.
■ ■ ■ ■ ■ 1 2 3 4 5 RU RU RU RU RU (part (part (part (part (part number: number: number: number: number: 330-2610-01) 330-2611-01) 330-2613-01) 330-2614-01) 330-2615-01) ■ Position your racks so that the warm air exhaust from one rack does not flow directly into the cool air intake area for another. ■ If space is limited at the back of your Sun StorEdge 72-inch rack, install a redundant fan tray (part number: X9819A) into the top of the rack.
2. Connect a serial device. For more information, see “Setting Up a Console Connection to the Server” on page 20. If you want to use the server’s Lights Out Management (LOM) facilities, use the port labeled Serial A/LOM to make your serial connection to the server. Note – The Sun Fire V100 server is supplied with shielded serial cables. Use only these cables when making serial connections to the server. 3. Connect the server to a maximum of two Ethernet hubs.
CHAPTER 3 Communicating With the Server This chapter provides information on setting up a console connection to a Sun Fire V100 server using a variety of devices.
Setting Up a Console Connection to the Server To perform the initial configuration and to continue to monitor and manage a server, you can connect any of the following devices to the appropriate serial port on the server’s back panel: ■ ■ ■ ■ ■ Sun workstation or ASCII terminal connected directly to the server Sun workstation connected via a terminal server Modem PC Handheld device Which Is the Appropriate Serial Port? There are two serial ports on the rear of the Sun Fire V100 server.
8 1 A LOM 1 8 B Serial FIGURE 3-1 Serial Port Pins 1 to 8 Serial Connection Settings The settings you need to use for a serial connection are listed in TABLE 3-2. If you need to perform binary data transfers (that is, transfers of anything more than simple ASCII character streams), use the B Serial port, as communication on the A LOM port is subject to interruption by the LOM device (see “Introduction to LightsOut Management” on page 43).
Serial Adapters Depending on the type of device you use to connect to the server, you could need to use either a DB-25 or DB-9 serial adapter. TABLE 3-3 describes which type to use, and the following sections describe the crossovers each adapter performs.
▼ To Use the DB-25 Adapter 1. Insert one end of the standard RJ-45 patch cable supplied with the Sun Fire V100 server into one of the server’s serial ports. 2. Insert the other end of the RJ-45 patch cable into the supplied DB-25 adapter. 3. Attach the adapter to the appropriate port in your serial device. The Sun DB-9 Adapter Some devices, such as a PC or handheld computer, require you to use either a male or female DB-9 adapter.
■ RJ-45 to RJ-45 patch cable Both are supplied with the Sun Fire V100 server. ▼ To Connect to the Server Using a Sun Workstation 1. Connect to the server using the RJ-45 patch cable and DB-25 adapter as described in “To Use the DB-25 Adapter” on page 23. 2. From a terminal session, type: # tip /dev/term/a -9600 The tip command above is for a console that is using its ttya serial port.
3. Make the setting changes shown below. Property Setting Duplex Full Bit Rate 9600 Parity No Data Bits 8 Stop Bit 1 Flow Control Xon/Xoff VT100 Emulation On (if applicable) The lom> prompt appears. For information about how to power on and configure the server, go to “Powering On and Configuring the Server” on page 34.
■ Connect the breakout cable directly to the Sun Fire V100 server. ■ Connect the breakout cable to a patch panel and use the straight-through patch cable (supplied by Sun) to connect the patch panel to the server. Connecting to Other Terminal Servers For terminals from other manufacturers, check the documentation to see if the pinouts of the serial ports on the Sun Fire V100 server match those of the serial ports on your terminal server.
For example, for a Sun Fire V100 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 Connecting to the Server Using a System Running Microsoft Windows If you want to configure and operate a Sun Fire V100 server from a PC or laptop running Microsoft Windows, you can do so using the Windows Hyperterminal. Note – The following procedure relates to Windows 98. Other variants of Microsoft Windows may differ slightly.
c. Click OK. 6. In the Connect To window: a. Click Edit. b. Click Connect Using. c. In the drop-down menu, click Direct to COM1. Note – If you connected the DB-9 adaptor to a port other than COM1 on your PC or laptop in Step 3, choose the appropriate option from the list in the drop-down menu. d. Click OK. 7. In the COM1 Properties window: a. Change the Bits Per Second value to 9600. b. Set Flow Control to Xon/Xoff. The correct values for all settings in this window are as shown below.
Connecting to the Server Using a Handheld Device The Sun Fire V100 server can be configured from a handheld device that uses PalmOS 2.0 or later, as long as you have VT100 terminal emulation software installed on the device and the correct hardware with which to connect to the server. ▼ To Set Up the Hardware Note – To connect a handheld device to a Sun Fire V100 server you need a male DB9 adapter that performs the same crossovers as those listed in TABLE 3-5. 1.
3. Choose Menu > Options > Communications and make the following settings. This ensures correct communication with the server. Property Method Method Serial Port Serial Baud Rate 9600 Data Bits 8 Parity None Stop Bits 1 RTS/CTS Unchecked Xon/Xoff Unchecked 4.
The following sections give some additional information that may make using the handheld device’s terminal emulator easier. Using the Arrow Keys The arrow keys available on the PalmOS device do not work with a Sun Fire V100 server. To work around this problem, specify while you configure the Solaris operating environment that you are using an Xterm device. The following keystrokes help you navigate the menus. ▼ Keystroke Action Ctrl-F or Tab Go forward to the next option (down).
Table 3-7 shows some example macros. TABLE 3-7 32 Example PalmOS Terminal Emulator Macros Macro Name Command Action backspace stty erase ^H\n Enables the Graffiti stroke for “delete” to work on the screen without printing the ^H character. arrow-enable csh;setenv TERM dtterm\n Switch to csh and set the terminal variable to dtterm. This enables the on-screen arrows to work on applications such as vi.
CHAPTER 4 Powering On and Configuring the Sun Fire V100 Server This chapter explains how to power on and configure the server, and how to use the Power (On/Standby) switch.
Powering On and Configuring the Server The Sun Fire V100 server comes preinstalled with the Solaris 8 operating environment. When you power on the server for the first time, you will automatically be taken through a configuration procedure. This procedure consists of a number of questions. The answers you give determine how the server is configured.
1. Connect the server to the power supply but do not power it on. 2. Set up a serial connection to the Serial A/LOM port and also a connection to at least one Ethernet hub (as described in Chapter 3). 3. At the console lom> prompt, type the following command to power on the server: lom> poweron For more information about the lom> prompt and the commands that are available from it, see Chapter 5. During booting you will be prompted for certain information.
3. At the lom> prompt, type the following command to power on the server: lom> poweron For more information about the lom> prompt and the commands that are available from it, see Chapter 5. During booting you will be prompted for certain information. The information you provide determines the configuration of the server. 4. Specify the type of terminal you are using to communicate with the Sun Fire V100 server. 5. When asked if you want the server to be networked, answer Yes.
17. At the system you are setting up, follow the prompts to provide time and date information. 18. When prompted, give a password (if any) for users logging in as root. The system will boot when you have provided it with the information it needs. ▼ To Power On a Standalone Server for the First Time 1. Connect the server to the power supply but do not power it on. 2. Set up a serial connection using the Serial A/LOM port (as described in “Setting Up a Console Connection to the Server” on page 20). 3.
● If you are at the lom> prompt, go to the ok prompt by typing: lom> break 1. Boot the server into the Solaris environment by typing: ok boot 2. At the Solaris prompt, type: # sys-unconfig 3. When prompted to confirm that you want to create a “blank” server, type y. 4. When the server has unconfigured itself, type the LOM escape sequence. By default, this is: # #.
Using the Power (On/Standby) Switch Caution – The power switch on the back panel of the Sun Fire V100 server is not an On/Off switch, it is an On/Standby switch. It does not isolate the equipment. The power (On/Standby) switch is a rocker type, momentary action switch. It controls only low-voltage signals; no high-voltage circuits pass through it. This means that the main method of connecting or disconnecting power is by inserting or removing the power supply cord.
To completely remove power from the server: ■ 40 Disconnect the power cable from the server.
PA RT II Remote and Local Management
CHAPTER 5 Managing the Sun Fire V100 Server From the lom> Prompt This chapter introduces the Lights-Out Management (LOM) facilities available for the Sun Fire V100 server and describes how to use the /usr/sbin/lom utility, which provides a user interface to the device.
LOM commands enable you to: ■ Power the server on or to standby mode. ■ Monitor the server’s temperature and the status of its power supply, fans, internal voltage rails, fault LED, and alarms, even when the server is in standby mode. ■ Turn a Fault LED on. ■ Configure the server to restart automatically after a lockup. These LOM facilities are provided by the LOM device, which in the Sun Fire V100 server is contained on the system board.
Powering On or Resetting the Server From the LOM Shell Note – When a Sun Fire V100 server is connected to a power supply, it is always either fully powered on or in standby mode. To remove power entirely from the server you must disconnect its power cables or open all external circuit breakers. The methods referred to in this chapter for powering the server on and off by using lom> prompt commands are methods either of powering the server on or returning it to standby power mode.
▼ To Display the lom> Prompt ● To display the lom> prompt, type the following LOM escape sequence: # #. When you type the LOM escape sequence, the LOM device takes control of the Serial A/LOM port and the lom> prompt appears on your terminal screen. You can type the LOM escape sequence at any time. Note – If you are at the console and you type the first character of the LOM escape sequence (by default this is #), there is a delay of one second before the character appears on the screen.
▼ To Reset the Server ● To reset the server, type: lom> reset ● To perform a limited reset affecting the processor only, type: lom> reset -x The -x option generates the equivalent of an externally initiated reset (XIR) of the server. You must have r-level permission to use this command. (For information about user authorization levels, see “Setting Up LOM Privileges for Named Users” on page 54.) The -x option takes the server into OpenBootTM PROM mode and causes it to display the ok prompt.
This command enables you to dictate the behavior of the server after a reset. Its functionality is identical to that available on Sun keyboards with the Stop key combinations. (However, the bootmode command is provided because the Stop key combinations are not available for the Sun Fire V100 server: you cannot use them from a keyboard that is connected to the server with a serial link.) You must have r-level LOM permission to use the bootmode command.
TABLE 5-1 Boot Modes Mode Description reset_nvram In this mode, the server returns all NVRAM data to its default setting. The command is equivalent to the Stop-N key combination for Sun keyboards. To cause the parameter to take effect, you must reset the server after using the bootmode command at the lom> prompt. diag In this mode, the server performs full self-diagnostics as part of the boot process. The command is equivalent to the Stop-D key combination for Sun keyboards.
▼ To Check How Long the Server Has Been Running ● To find out how much time has elapsed since the last boot, type: lom> date Time since last boot: +8d+20h48m2s or: lom> showdate Time since last boot: +8d+21h49m6s ▼ To Check the Current Status of All Components ● To see the current status of all the components monitored by the LOM device, type: lom> environment CODE EXAMPLE 5-1 shows sample output from the environment command.
Overheat sensors: 1 OK Supply rails: 1 OK 2 OK 3 OK 4 OK 5 OK lom> Viewing the LOM Event Log The eventlog command reports the last 10 events. The loghistory command can report up to several hundred events.
▼ To View the Entire Event Log ● Type: lom> loghistory [pause x] [level y] where x is the number of lines you want to display before pausing, and y is the severity level of the events you want to see. By default, the loghistory command displays all the events in the log and does not pause the display. If you specify a severity level, you will see reports for the level you specify and above. For example, if you specify level 2, you will see reports of level 2 and level 1 events.
▼ To View All Events From the Last One Logged to the nth Event Before It ● Type: lom> loghistory index -n [pause x] [level y] where n is the number of events you want to see listed that were logged before the last event in the current log, x is the number of lines you want to display before pausing, and y is the severity level of the events you want to see. By default, the loghistory command does not pause the display.
Setting Up LOM Privileges for Named Users You can specify up to four named users of the LOM device on a Sun Fire V100 server. By default, no users are set up, and therefore no user login prompt appears when you use the LOM escape sequence. However, if you set up one or more users, every time you use the LOM escape sequence to display the lom> prompt, you will be prompted for a user name and password. Therefore, one of the user accounts you set up must be for yourself.
▼ To Create a LOM User Account ● Type: lom> useradd username where the username is up to eight characters long, begins with an alphabetic character, and contains at least one lowercase alphabetic character. You can use any of the following characters in the user name: ■ ■ ■ ■ Alphanumeric Period (.) Underscore (_) Hyphen (-) Note – You must have User Administration (u-level) authorization to add a user (see “Permissions Available for LOM Users” on page 54).
▼ To View the Details of a LOM User Account ● Type: lom> usershow This command displays the details of all users. Note – You must have User Administration (u-level) authorization to view the details of a LOM user account (see “Permissions Available for LOM Users” on page 54). ▼ To Change Your Own User Password 1. To change the password for the account you are currently logged into, type: lom> password 2. When prompted, type the current password. 3.
By default, all four areas of authorization are available to each named user you set up. You can limit users to a particular area or areas of authorization by specifying permissions for a named user. ▼ To Specify Permissions for a Named User ● Type: lom> userperm username [c][u][a][r][-] You can specify: ■ All four parameters (for example, userperm cuar) This also makes all four areas available to the named user.
▼ To Quit a LOM Named User Session ● Type: lom> logout This returns you to the LOM login prompt. Setting the LOM Configurable Variables Note – To be able to run the commands described in this section, the named user must have a-level permission. For more information, see “Setting Up LOM Privileges for Named Users” on page 54.
● Turn the alarm off by typing: lom> alarmoff n where n is the number of the alarm you want to turn off: 1, 2, or 3. Alarms 1, 2, and 3 are software flags. They are not associated with any specific conditions, but are available to be set by your own processes or from the command line. For more information, see “To Turn the Alarms On and Off (lom -A)” on page 76.
Separating LOM From the Console on the Serial A/LOM Port By default, the LOM device shares the Serial A/LOM port with the console, and when it has an event report to send, it takes control of the Serial A/LOM port itself, interrupting any console activity you are performing. To prevent the LOM device from interrupting the console, either turn serial event reporting off (see Chapter 6), or dedicate the Serial A/LOM port to the LOM device and use the Serial B port for console activity.
The Serial B port (ttyb) is now your console port. The Serial A/LOM port remains in the control of the LOM device. ▼ To Share the Serial A/LOM Port Between LOM and the Console Note – By default, the Serial A/LOM port is shared by the LOM device and the console.
In this file, the reports are displayed with a label identifying them as lom reports and indicating their severity. Starting with the most severe, the levels of severity are: 1. Fatal Fatal events can cause the server to shut itself down. Examples of fatal events are: ■ ■ Supply rail failures. Exceeded temperature thresholds. 2. Warning Warning events do not cause the server to shut down, but they do require immediate attention. Examples of warning events are: ■ ■ ■ Fans turning too slowly.
TABLE 5-2 LOM Commands (Continued) Command Description check Resets monitoring to report all failures. If a monitored component has failed, the LOM device will not continue to report the same failure. To check the status of the component, for example, after attempting to fix it, use the check command. This updates the status of all monitored components. console Takes you out of the LOM shell and back to the Solaris prompt. It returns control of the serial connection to the console.
64 Sun Fire V100 Server User’s Guide • December 2001
CHAPTER 6 Managing the Sun Fire V100 Server From the Solaris Prompt This chapter describes how to monitor and manage the Sun Fire V100 server with LOM-specific commands in the Solaris 8 operating environment.
Monitoring the System From the Solaris Prompt To use the Lights-Out Management (LOM) facilities either remotely or locally, you need a terminal connection to the Serial A/LOM port on the server (see “Setting Up a Console Connection to the Server” on page 20). There are two ways to interrogate LOM or to send it commands to perform: ■ Use LOM commands from the lom> shell prompt. For information about how to do this, see Chapter 5. ■ Use LOM-specific Solaris commands from the Solaris prompt.
▼ To Check the Fan Status (lom -f) ● Type: # lom -f Fans: 1 OK speed 99% # Checking the Supply Rail Voltages and Internal Circuit Breakers (lom -v) The supply rails are the Sun Fire V100 server’s internal power lines. If the status of any of these is faulty, contact your local Sun sales representative. It means that you have either a faulty system board or a faulty PSU. The -v option also displays the status of the server’s internal circuit breakers.
▼ To Check the Status of the Supply Rails and Internal Circuit Breakers ● Type: # lom -v Supply voltages: 1 5V status=ok 2 3V3 status=ok 3 +12V status=ok 4 -12V status=ok 5 VDD-CORE status=ok System status flags (circuit breakers): 1 USB0 status=ok 2 USB1 status=ok ▼ To Check the Internal Temperature ● Type: # lom -t System Temperature Sensors: 1 enclosure 25 degC : warning 67 degC : shutdown 72 degC System Over-temperature Sensors: 1 cpu status=ok # This checks the server’s internal temperature, an
▼ To Check Whether the Fault LED and Alarms Are On or Off ● Type: # lom -l LOMlite alarm states: Alarm1=off Alarm2=off Alarm3=off Fault LED=on # Alarms 1, 2, and 3 are software flags. They are not associated with any specific conditions, but are available to be set by your own processes or from the command line. For more information, see “To Turn the Alarms On and Off (lom -A)” on page 76.
● To configure the LOM device to perform an automatic server restart (ASR) after a lockup, you must enable the Hardware reset option as well as the Watchdog option. For more information, see “Configuring Automatic Server Restart” on page 73.
CODE EXAMPLE 6-1 Sample lom -a output PSUs: 1 OK speed 68% LOMlite configuration settings: serial escape character=# serial event reporting=default Event reporting level=fatal, warning & information Serial security=enabled Disable watchdog on break=enabled Automatic return to console=disabled alarm3 mode=user controlled firmware version=3.9 firmware checksum=2262 product revision=0.
CODE EXAMPLE 6-1 Sample lom -a output PSUs: System status flags (circuit breakers): 1 USB0 status=ok 2 USB1 status=ok 3 SCC status=ok System Temperature Sensors: 1 Enclosure 27 degC : warning 67 degC : shutdown 72 degC System Over-temperature Sensors: 1 CPU status=ok Console output prior to last reset: ▼ To View the Event Log (lom -e) ● To see the event log, type: # lom -e n,[x] where n is the number of reports (up to 128) that you want to see and x specifies the level of reporting you require.
# lom -e 10 LOMlite Event Log: +0h0m21s host reset 9/15/2000 17:35:28 GMT LOM time reference +0h3m20s fault led state - ON +0h3m24s fault led state - OFF +0h39m34s Alarm 1 ON +0h39m40s Alarm 3 ON +0h39m54s Alarm 3 OFF +0h40m0s Alarm 1 OFF +0h48m52s fault led state - OFF +0h49m39s Fan 1 FATAL FAULT: failed +0h50m58s fault led state - ON # lom -e 10 FIGURE 6-1 Sample LOM Device Event Log (Oldest Event Reported First) Configuring Automatic Server Restart You can configure automatic server restart (ASR) to r
You can turn the option on and off from the Solaris command prompt. For more information, see “To Set the Hardware Reset Option From a Script or Command (lom -R on)” on page 75. However, as long as you have the -R on option set in /etc/rc2.d/S25lom, the Hardware Reset option will always be enabled when you start the system. Enabling the LOM Watchdog Process From Your Own Script or Command (lom -W on) Note – You do not normally need to do this.
● If you have no LOM watchdog process running already and you want the process to run, type the following, or add it to another script file: # lom -W on,40000,10000 ● If you want the LOM device to perform an automatic server restart after a lockup, you must include the -R on option in the command, as follows: # lom -W on,40000,10000 -R on Note – Unless you include the lom -W on and -R on options in a script file, you must run the lom command every time you reboot the system if you want to use the automa
Other LOM Tasks You Can Perform From the Solaris Prompt This section describes how to: ▼ ■ Turn the alarms and Fault LEDs on and off with the lom command. ■ Change the first character of the lom escape sequence. ■ Stop LOM sending reports to the Serial A/LOM port. ■ Remove driver protection from the device driver. ■ Make the LOM interface backward compatible. ■ Upgrade LOM firmware. To Turn the Alarms On and Off (lom -A) There are three alarms associated with LOM.
● To turn the Fault LED off, type: # lom -F off ▼ To Change the First Character of the Sequence for Escaping to the lom> Prompt (lom -X) The character sequence #. (hash, dot) enables you to exit the Solaris prompt to the lom> prompt. ● To change the first character of this default lom escape sequence, type: # lom -X x where x is the alphanumeric character you want to use instead of #.
● To turn serial event reporting on again, type: # lom -E on If you want to dedicate the Serial A/LOM port to the LOM device and you want to use the Serial B port as your console port, see “To Dedicate Serial A/LOM to LOM” on page 60.
PA RT III Maintenance and Troubleshooting
CHAPTER 7 Interpreting the LEDs This chapter describes the location and function of the warning LEDs on the server, and contains the following section: ■ “Interpreting the Front- and Back-Panel LEDs” on page 82 81
Interpreting the Front- and Back-Panel LEDs The Sun Fire V100 server contains two front panel LEDs (see FIGURE 7-1) and four rear panel LEDs (see FIGURE 7-2). Those on the front panel indicate power and faults only. Those on the back panel indicate the presence of up to two ethernet connections, and replicate the power and fault information of the front LEDs. Front-Panel LEDs The front panel LEDs are located at the top left of the servers front bezel.
■ The LOM watchdog has timed out, indicating that the server has locked up. You can configure the server to restart automatically after a lockup (see Chapter 6). The Fault LED flashes when a problem has occurred that is fatal to the server. Circumstances that cause the Fault LED to flash include the following: ■ ■ ■ ■ The speed of the fan inside the server is too low. The temperature inside the server’s enclosure is too high. By default, this causes the server to shut down.
Ethernet 0 Ethernet 1 Fault Power LED FIGURE 7-2 ▼ Back-Panel Power and Fault LEDs To Turn the Fault LED On or Off ● To turn the Fault LED on, type: # lom -F on ● To turn the Fault LED off, type: # lom -F off For information about turning the Fault LEDs on and off from the LOM shell, see Chapter 5. For more information about the lom commands included in the Solaris operating environment, see Chapter 6.
CHAPTER 8 Removing and Replacing Components This chapter details the procedures for moving the system configuration card from one server to another, and for changing replaceable components.
Adding Components or Replacing A Server For a list of components that are available for the Sun Fire V100 server, see “Optional Components” on page 4. If there is a fault with any of the components listed below, replace the whole server. Should you need to do this, contact your Sun sales representative. ■ ■ ■ ■ ■ Motherboard Processor Power Supply Unit Fan CD-ROM drive The server contains a memory card called the system configuration card.
4. Replace the zip tie on the new system. 5. Power on the new system (see Chapter 4). Caution – Never remove the system configuration card when the server is booting or running Solaris. Power the server off or down to standby mode before removing or inserting the system configuration card. Caution – Do not handle the system configuration card unless you need to transfer it to another system. If you need to handle it for this reason, avoid contact with the gold terminals on the underside of the card.
your area. You can then arrange to return the system to Sun for repair under the terms of your warranty or you can order the components and have them installed by your own qualified service engineers. Caution – The system contains electronic parts that are extremely sensitive to static electricity. Do not touch any metal parts. Place the system on top of an electrostatic discharge (ESD) pad (see FIGURE 8-2).
2. Hold the On/Standby switch in the Standby position for more than four seconds to put the server in standby mode. 3. Disconnect the power cord. 4. Disconnect all other cables. 5. If the system is installed in a rack or cabinet, remove it. ▼ To Remove the Top Cover ■ If the Sun Fire V100 server is not in use, go straight to step 1. ■ If the server is already in use, see “To Change Components In a Sun Fire V100 Server That Is In Use” on page 88. FIGURE 8-3 Removing the Top Cover 1.
3. Slide the top cover back until the arrow on the cover lines up with the arrow on the server body. 4. Lift the cover up and off. ▼ To Replace the Top Cover 1. Align the arrow on the cover with the arrow on the server body. 2. Press the cover down so that it clips into the server body. FIGURE 8-4 Replacing the Top Cover 3. Slide the cover forwards so that its leading edge is flush with the back of the server’s front bezel.
4. Tighten the captive screw on the back of the unit. Memory Installation and Removal There are four industry standard PC133 memory module sockets on the Sun Fire V100 server’s system board. To see the location of the memory modules inside the server, see FIGURE 8-5 or the underside of the server’s top cover. ▼ To Install and Remove Memory ■ If the server is not in use, go straight to Step 1.
FIGURE 8-6 Installing Memory Into a Socket on the System Board 5. If you are removing memory, open the latches and remove the module(s) in the order 0, 1, 2, 3. 6. Replace the system cover and tighten the captive screw (see FIGURE 8-4). Installing and Removing the Hard Disk Drive The server can accept two hard disk drives, which are numbered 0 and 1. ▼ To Install a Hard Disk Drive ■ 92 If the Sun Fire V100 server is not in use, go straight to Step 1.
■ If the server is already in use, see “To Change Components In a Sun Fire V100 Server That Is In Use” on page 88. 1. Place the unit on an ESD surface and attach an antistatic wrist strap (see FIGURE 8-2). 2. Remove the server’s top cover (see “To Remove the Top Cover” on page 89). 3. Remove the metal placeholder if your server has one (if it was configured with a single hard disk drive, the second hard disk drive slot will have the placeholder installed). FIGURE 8-7 Removing the HDD Placeholder 4.
Step 4b Step 4a FIGURE 8-8 Installing a Hard Disk Drive 5. Attach the power and data cables (see FIGURE 8-8). 6. Replace the system cover and tighten the captive screw (see FIGURE 8-4). ▼ To Remove a Hard Disk Drive ■ If the server is not in use, go straight to Step 1. ■ If the server is already in use, see “To Change Components In a Sun Fire V100 Server That Is In Use” on page 88. 1. Place the unit on an ESD surface and attach an antistatic wrist strap (see FIGURE 8-2). 2.
4. Unfasten the hard disk drive’s handle from the two clips securing it. 5. Slide the hard disk drive until it is free from the clips on the base of the server. 6. Lift the hard disk drive up and out of the server.
96 Sun Fire V100 Server User’s Guide • December 2001
CHAPTER 9 Reinstalling the Solaris Operating Environment This chapter explains how to reinstall the Solaris operating environment onto the Sun Fire V100 server.
Reinstalling the Solaris Operating Environment The Sun Fire V100 server is supplied with the Solaris operating environment preinstalled. If for any reason you decide to reinstall the Solaris operating environment (for example, if you need to repartition your root disk or recover from a failure) follow the instructions in the Solaris Installation Guide (806-0955-10) and the Solaris Advanced Installation Guide (806-0957-10).
CHAPTER 10 Troubleshooting This chapter describes the diagnostic tools you can use with the Sun Fire V100 server, lists some of the problems you might encounter when setting up or using a server, and gives information to help fix those problems.
Diagnostic Tools The following troubleshooting tools are available for the servers: ■ ■ ■ Power On Self Test (POST) Diagnostics OpenBoot Diagnostics (OBDiag) SunVTS POST Diagnostics To view Power On Self Test (POST) diagnostic and error messages you need to have a serial connection set up to the server. For more information, see “Setting Up a Console Connection to the Server” on page 20.
OpenBoot Diagnostics Like POST diagnostics, OpenBoot Diagnostics can be run if the diag-switch? variable is set to true. You can also run OpenBoot Diagnostics interactively and select which tests you want it to perform. To do so, follow the steps below from the ok prompt. 1. Type: ok setenv diag-switch? true ok setenv auto-boot? false ok reset-all 2.
3. When you have finished testing, exit OpenBoot Diagnostics and restore the value of auto-boot? to true. To do this, type: obdiag> exit ok setenv auto-boot? true ok auto-boot? true ok boot The function of each test is shown below.
● Type: ok setenv diag-level value SunVTS SunVTS, the Sun Validation and Test Suite, is an online diagnostics tool which you can use to verify the configuration and functionality of hardware controllers, devices and platforms. It runs in the Solaris 8 operating environment using any of the following: ■ ■ ■ command line interface serial (tty) interface graphical interface within a windowed desktop environment. SunVTS software lets you view and control a testing session on a remotely connected server.
■ If SunVTS software is not loaded, you will see the following error message: ERROR: information for “SUNWvts” was not found Installing SunVTS By default, SunVTS is not installed on the Sun Fire V100 server. SunVTS is distributed via the Software Supplement for the Solaris Operating Environment CD. See the Sun Hardware Platform Guide for details. The default directory to use when you install SunVTS software is /opt/SUNWvts.
You can fine-tune your testing session by selecting the appropriate check boxes for each of the tests you want to run. Problems You Might Encounter This section outlines some particular problems you might encounter when setting up and using the Sun Fire V100 server and, where applicable, tells you where to look in the Sun Fire V100 Server User’s Guide for more information.
Cannot Display the lom> Prompt Using the #. Escape Sequence Check whether the first character of the #. escape sequence has been changed (this is a user-configurable value). To check the current value, type the following from the Solaris prompt: # lom -c The information that this command displays includes the serial escape character. If this is not “#”, then type the character that is currently specified and follow it immediately with a dot.
IDE Controller Failure The probe-IDE diagnostic transmits an inquiry command to internal and external IDE devices connected to the system’s on-board IDE interface. If the IDE device is connected and active, the target address, unit number, device type, and manufacturer name are displayed. Initialize the probe-IDE diagnostic by typing the probe-ide command at the ok prompt.
Frequently Asked Questions What hardware configurations is the Sun Fire V100 available in? The Sun Fire V100 server is available in the following configurations: Processor RAM Hard Disk Drive Sun Part Number 500MHz 128 MB 1 * 40 GB (7200 rpm) 600-7881-xx 500MHz 512 MB(2 * 256MB) 1 * 40 GB (7200 rpm) 600-7882-xx 500MHz 1 GB (4 * 256MB) 2 * 40 GB (7200 rpm) 600-7883-xx 500MHz 2 GB (4 * 512MB) 2 * 40 GB (7200 rpm) 600-7884-xx What software is preinstalled? The Sun Fire V100 server comes pr
What are the Sun Fire V100 server’s expandability options? The Sun Fire V100 server provides simplified expansion options. You cannot upgrade the CPU, and the server does not ship with PCI slots. Optional components and part numbers are listed in “Optional Components” on page 4. Can I install my own PC DIMM memory? Doing so risks breaking your warranty agreement. Only Sun service personnel should install memory and only Sun certified memory may be used.
How many Sun Fire V100 servers can be put in a standard 19-inch rack? Physically and electrically, you can put up to 40 Sun Fire V100 servers into a standard 19-inch rack with two 20-amp circuits. However, a more practical deployment would be 32 servers in a rack with termservers, network gear, and additional power strips.
Do the serial ports support synchronous protocols? No. Will the server need a null-modem cable to connect to the console port? No. Because the Sun Fire V100 server requires the use of console port, Sun has designed the server not to need a null-modem cable. All you need to connect a Sun Fire V100 server to a termserver is a standard Category 5 cable.
112 Sun Fire V100 Server User’s Guide • December 2001
PA RT IV Appendixes
APPENDIX A Physical and Environmental Specifications In the following sections, this appendix gives the physical dimensions of the Sun Fire V100 server and describes the conditions in which the server is capable of operating: ■ “Physical Specifications” on page 116 ■ “Environmental Specifications” on page 116 ■ “Operating Power Statistics” on page 117 ■ “Calculating Power Consumption” on page 118 ■ “Calculating Heat Dissipation” on page 118 115
Physical Specifications TABLE A-1 Sun Fire V100 Server Physical Specifications Dimension U.S. Metric Height 1.72 in. 43.6 mm Width 17.2 in. 436.7 mm Depth 18.8 in. 478 mm Weight 9 kg (with two hard disk drives and four memory modules installed) Environmental Specifications You can operate and store the system safely in the conditions detailed below.
Environmental Compliance Information ■ Electromagnetic compatibility ■ Immunity: The server conforms to EN55024. ■ Emissions: The server conforms to EN55022 Class A and FCC Class A. ■ Safety The system conforms to UL 1950 (3rd edition), EN60950 Operating Power Statistics TABLE A-2 Operating Power Statistics Maximum operating current 1.
Note – Power from the standby output is available whenever input power is connected. Calculating Power Consumption A Sun Fire V100 server containing two disk drives has an estimated current requirement of approximately 1 amp. TABLE A-3 shows the estimated power consumed by the individual components in a fully powered system. However, when you are calculating the power requirements for your system, you must allow for 63 percent PSU efficiency.
APPENDIX B Configuring LOM Driver This appendix describes the parameters that you can use to configure the LOM driver, and contains the following sections: ■ “The LOM Device Driver and Script Files” on page 120 ■ “Configuring the LOM Device Driver” on page 121 119
The LOM Device Driver and Script Files The LOM driver software included in the Solaris 8 (10/00) operating environment is as follows: ■ /platform/sun4u/kernel/drv/lom (the lom driver [32-bit]) ■ /platform/sun4u/kernel/drv/sparcv9/lom (the lom driver [64-bit]) ■ /platform/sun4u/kernel/drv/lom.conf (the driver configuration file) The driver is started by the following three scripts in the Solaris 8 (10/00) environment: ■ /etc/init.d/lom ■ /etc/rc2.d/S25lom ■ /etc/rc0.
Configuring the LOM Device Driver The full list of parameters you can set in this file is given in TABLE B-1. TABLE B-1 LOM Configuration File Parameters Field Format Default Effect wdog_reset= Boolean 0=FALSE 1=TRUE 0 Causes LOM to reset the server after a watchdog timeout. Setting this to 1 is equivalent to using the lom -R on command described in Chapter 6. wdog_alarm3= Boolean 0=FALSE 1=TRUE 0 Turns on software alarm 3 when the LOM watchdog times out.
TABLE B-1 122 LOM Configuration File Parameters (Continued) Field Format Default Effect disable_wdog_on_break= Boolean 0=FALSE 1=TRUE 1 Causes LOM to disable its watchdog if it detects a break signal on the Serial A/LOM port. disable_wdog_on_panic= Boolean 0=FALSE 1=TRUE 1 Causes LOM to try to disable its watchdog after a system “panic”.
TABLE B-1 LOM Configuration File Parameters (Continued) Field Format Default Effect serial_timeout= Multiples of 4 secs 0 Specifies the period after which LOM gives control of the Serial A/LOM port back to the console when it has finished sending a report (or when the user has issued a LOM shell command, if you have enabled the serial_return= option). By default, there is no delay at all.
124 Sun Fire V100 Server User’s Guide • December 2001
Index A acoustic noise, 116 alarms, setting, 62, 76 altitude, 116 anti-static wrist strap, 88 automatic server restart, 73 B back panel LEDs, 82 BTU rating, 117 POST, 100 domain name, 36 dumb terminal, serial connection, 23 E electro-magnetic compatibility, 117 Ethernet ports, 2 event log, viewing, 51 F C cables, 17 Cisco L2511 Terminal Server, connecting, 25 console connection ASCII terminal, 24 setting up, 20 Sun workstation, 24 terminal server, 25 cooling (heat dissipation), 118 cross-over (null mode
I M IDE controller failure, 107 input voltage range, 117 in-rush current, 117 installation quickstart, 5 rack mounting, 7 internal circuit breakers, 67 memory installing and removing, 91 part number, 4 monitoring the system, See Lights-Out Management (LOM) N L LEDs back panel, 83 Ethernet port indicators, 83 fault indicator, 82 front panel, 82 power indicator, 82 Lights Out Management (LOM) commands, 62 displaying the host name, 63 displaying the version number of the LOM device, 63 monitoring the syste
Q T quickstart, 5 temperature checking the system’s temperature, 68 terminal server, 25 thermal issues, 8 tip session, 22 top cover removing, 89 replacing, 90 R remote reset, 47 removal hard disk drives, 92 memory, 91 system top cover, 93 replacing the server, 86 resetting remotely, 47 S safety, 117 SCC (system configuration card), 86 security, 8 LOMlite2 named user accounts, 54 to 58 Serial A/LOM port data subject to interruption by LOMlite2, 77 serial A/LOM port, 35, 37 dedicating to the LOMlite2 dev
Index-128 Sun Fire V100 Server User’s Guide • December 2001
