Sun Microsystems Netra 440 User Manual

Netra™ 440 Server System

Administration Guide

Sun Microsystems, Inc. www.sun.com

Part No. 817-3884-11 August 2004, Revision A

Submit comments about this document at: http://www.sun.com/hwdocs/feedback

Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology that is described in this document. In particular, and without

limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.

This document and the product to which it pertains are distributed under licenses restricting their use, copying, distribution, and decompilation. No part of the product or of this 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. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in

the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, AnswerBook2, docs.sun.com, VIS, Sun StorEdge, Solstice DiskSuite, Java, SunVTS, Netra, and Solaris are

trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and in other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and in other

countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and Sun™ Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges

the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun’s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun’s written license agreements.

U.S. Government Rights—Commercial use. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.

DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, Californie 95054, Etats-Unis. Tous droits réservés. Sun Microsystems, Inc. a les droits de propriété intellectuels relatants à la technologie qui est décrit dans ce document. En particulier, et sans la

limitation, ces droits de propriété intellectuels peuvent inclure un ou plus des brevets américains énumérés à http://www.sun.com/patents et un ou les brevets plus supplémentaires ou les applications de brevet en attente dans les Etats-Unis et dans les autres pays.

Ce produit ou document est protégé par un copyright et distribué avec des licences qui en restreignent l’utilisation, la copie, la distribution, et la décompilation. Aucune partie de ce produit ou document ne peut être reproduite sous aucune forme, par quelque moyen que ce soit, sans l’autorisation préalable et écrite de Sun et de ses bailleurs de licence, s’il y ena.

Le logiciel détenu par des tiers, et qui comprend la technologie relative aux polices de caractères, est protégé par un copyright et licencié par des fournisseurs de Sun.

Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l’Université de Californie. UNIX est une marque déposée aux Etats-Unis et dans d’autres pays et licenciée exclusivement par X/Open Company, Ltd.

Sun, Sun Microsystems, le logo Sun, AnswerBook2, docs.sun.com, VIS, Sun StorEdge, Solstice DiskSuite, Java, SunVTS, Netra, et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d’autres pays.

Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d’autres pays. Les produits portant les marques SPARC sont basés sur une architecture développée par Sun Microsystems, Inc.

L’interface d’utilisation graphique OPEN LOOK et Sun™ a été développée par Sun Microsystems, Inc. pour ses utilisateurs et licenciés. Sun reconnaît les efforts de pionniers de Xerox pour la recherche et le développement du concept des interfaces d’utilisation visuelle ou graphique pour l’industrie de l’informatique. Sun détient une license non exclusive de Xerox sur l’interface d’utilisation graphique Xerox, cette licence couvrant également les licenciées de Sun qui mettent en place l’interface d ’utilisation graphique OPEN LOOK et qui en outre se conforment aux licences écrites de Sun.

LA DOCUMENTATION EST FOURNIE "EN L’ÉTAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L’APTITUDE A UNE UTILISATION PARTICULIERE OU A L’ABSENCE DE CONTREFAÇON.

Contents i

Figures v

Tables vii

Preface ix

1. Configuring the System Console 1

Communicating With the System 1

What the System Console Does 3

Using the System Console 3

About the sc> Prompt 8

Access Through Multiple Controller Sessions 9

Reaching the sc> Prompt 9

OpenBoot ok Prompt 9

Reaching the ok Prompt 10

For More Information 13

Getting to the ok Prompt 13

Switching Between the ALOM System Controller and the System Console 15

Accessing the System Controller 16

Using the Serial Management Port 16

Activating the Network Management Port 17

Accessing the System Console Through a Terminal Server 19

Accessing the System Console Through a TIP Connection 22

Modifying the /etc/remote File 25

Accessing the System Console Through an Alphanumeric Terminal 26

Verifying Serial Port Settings on TTYB 28

Accessing the System Console Through a Local Graphics Monitor 29

System Console OpenBoot Configuration Variable Settings 31

2. Managing RAS Features and System Firmware 33

ALOM System Controller 34

Logging In To the ALOM System Controller 34

About the scadm Utility 35

Controlling the Locator LED 37

OpenBoot Emergency Procedures 39

OpenBoot Emergency Procedures for Systems With Non-USB Keyboards 39

OpenBoot Emergency Procedures for Systems With USB Keyboards 40

Automatic System Recovery 41

Auto-Boot Options 42

Error Handling Summary 43

Reset Scenarios 44

Automatic System Recovery User Commands 44

Enabling and Disabling Automatic System Recovery 44

Obtaining Automatic System Recovery Information 46

Unconfiguring and Reconfiguring Devices 46

Enabling the Hardware Watchdog Mechanism and Its Options 49

Multipathing Software 50

For More Information 50

ii Netra 440 Server System Administration Guide • August 2004

3. Managing Disk Volumes 51

Disk Volumes 51

Volume Management Software 52

VERITAS Dynamic Multipathing 52

Sun StorEdge Traffic Manager 52

For More Information 53

RAID Technology 54

Disk Concatenation 54

RAID 0: Disk Striping 55

RAID 1: Disk Mirroring 55

RAID 5: Disk Striping With Parity 56

Hot-Spares 56

Hardware Disk Mirroring 56

Physical Disk Slot Numbers, Physical Device Names, and Logical Device

Names 57

A. OpenBoot Configuration Variables 67

B. Alarm Relay Output Application Programming Interface 71

Index 77

Contents iii

iv Netra 440 Server System Administration Guide • August 2004

Figures

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

FIGURE 1-2 Serial Management Port on the ALOM System Controller Card–Default Console

Connection 5

FIGURE 1-3 Alternative Console Ports (Require Additional Configuration) 6

FIGURE 1-4 Separate System Console and System Controller “Channels” 15

FIGURE 1-5 Patch Panel Connection Between a Terminal Server and a Netra 440 Server 20

FIGURE 1-6 TIP Connection Between a Netra 440 Server and Another Sun System 22

FIGURE 3-1 Graphical Representation of Disk Concatenation 54

FIGURE 3-2 Graphical Representation of Disk Striping 55

FIGURE 3-3 Graphical Representation of Disk Mirroring 55

vi Netra 440 Server System Administration Guide • August 2004

Tables

TABLE 1-1 Ways of Communicating With the System 2

TABLE 1-2 Ways of Accessing the ok Prompt 14

TABLE 1-3 Pin Crossovers for Connecting to a Typical Terminal Server 20

TABLE 1-4 OpenBoot Configuration Variables That Affect the System Console 31

TABLE 2-1 Stop Key Command Functions for Systems With Standard (Non-USB) Keyboards 39

TABLE 2-2 Device Identifiers and Devices 47

TABLE 3-1 Disk Slot Numbers, Logical Device Names, and Physical Device Names 57

TABLE A-1 OpenBoot Configuration Variables Stored on the System Configuration Card 67

vii

viii Netra 440 Server System Administration Guide • August 2004

Preface

The Netra 440 Server System Administration Guide is written for experienced system administrators. It includes general descriptive information about the Netra

440 server and detailed instructions for configuring and administering the server. To use the information in this manual, you must have working knowledge of computer network concepts and terms, and advanced familiarity with the Solaris™ Operating System (Solaris OS).

How This Book Is Organized

The Netra 440 Server System Administration Guide is divided into the following chapters:

■ Chapter 1 describes the system console and how to access it.

■ Chapter 2 describes the tools used to configure system firmware, including Sun

Advanced Lights Out Manager (ALOM) system controller environmental monitoring, automatic system recovery (ASR), hardware watchdog mechanism, and multipathing software. In addition, it describes how to unconfigure and reconfigure a device manually.

■ Chapter 3 describes how to manage internal disk volumes and devices.

This manual also includes the following reference appendixes:

■ Appendix A provides a list of all OpenBoot configuration variables, and a short

description of each.

■ Appendix B provides a sample program that illustrates how to get/set the

status of the alarms.

Using UNIX Commands

This document might not contain information on basic UNIX® commands and procedures such as shutting down the system, booting the system, and configuring devices. See the following for this information:

■ Software documentation that you received with your system

■ Solaris OS documentation, which is at

http://docs.sun.com

Shell Prompts

Shell Prompt

C shell machine-name%

C shell superuser machine-name#

Bourne shell and Korn shell $

Bourne shell and Korn shell superuser #

x Netra 440 Server System Administration Guide • August 2004

Typographic Conventions

Typeface

AaBbCc123 The names of commands, files,

AaBbCc123

AaBbCc123 Book titles, new words or terms,

* The settings on your browser might differ from these settings.

Meaning Examples

Edit your.login file. and directories; on-screen computer output

What you type, when contrasted with on-screen computer output

words to be emphasized. Replace command-line variables with real names or values.

Use ls -a to list all files.

% You have mail.

% su

Password:

Read Chapter 6 in the User’s Guide.

These are called class options.

You must be superuser to do this.

To delete a file, type rm filename.

Configuring the System Console

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

Tasks covered in this chapter include:

■ “Getting to the ok Prompt” on page 13

■ “Accessing the System Controller” on page 16

■ “Activating the Network Management Port” on page 17

■ “Accessing the System Console Through a Terminal Server” on page 19

■ “Accessing the System Console Through a TIP Connection” on page 22

■ “Modifying the /etc/remote File” on page 25

■ “Accessing the System Console Through an Alphanumeric Terminal” on page 26

■ “Verifying Serial Port Settings on TTYB” on page 28

■ “Accessing the System Console Through a Local Graphics Monitor” on page 29

Other information in this chapter includes:

■ “Communicating With the System” on page 1

■ “About the sc> Prompt” on page 8

■ “OpenBoot ok Prompt” on page 9

■ “Switching Between the ALOM System Controller and the System Console” on

page 15

■ “System Console OpenBoot Configuration Variable Settings” on page 31

Communicating With the System

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

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

TABLE 1-1 lists these devices and where they are discussed in the document.

TABLE 1-1 Ways of Communicating With the System

Devices Available for Accessing the System Console

During Installation

A terminal server attached to the serial management port (SERIAL MGT) or ttyb. See the following:

• “Accessing the System Controller” on page 16 ✓ ✓

• “Accessing the System Console Through a Terminal Server”

✓ ✓

on page 19

• “Verifying Serial Port Settings on TTYB” on page 28 ✓

• “System Console OpenBoot Configuration Variable Settings”

✓ ✓

on page 31

An alphanumeric terminal or similar device attached to the serial management port (SERIAL MGT) or ttyb. See the following:

• “Accessing the System Controller” on page 16 ✓ ✓

• “Accessing the System Console Through an Alphanumeric

✓ ✓

Terminal” on page 26

• “Verifying Serial Port Settings on TTYB” on page 28 ✓

• “System Console OpenBoot Configuration Variable Settings”

✓ ✓

on page 31

A TIP line attached to the serial management port (SERIAL MGT) or ttyb. See the following:

• “Accessing the System Controller” on page 16 ✓ ✓

• “Accessing the System Console Through a TIP Connection”

✓ ✓

on page 22

• “Modifying the /etc/remote File” on page 25 ✓

• “Verifying Serial Port Settings on TTYB” on page 28 ✓

• “System Console OpenBoot Configuration Variable Settings”

✓ ✓

on page 31

An Ethernet line connected to the network management port (NET MGT). See the following:

• “Activating the Network Management Port” on page 17 ✓

After Installation

2 Netra 440 Server System Administration Guide • August 2004

TABLE 1-1 Ways of Communicating With the System (Continued)

Devices Available for Accessing the System Console

A local graphics monitor (frame buffer card, graphics monitor, mouse, and so forth). See the following:

• “Accessing the System Console Through a Local Graphics

Monitor” on page 29

• “System Console OpenBoot Configuration Variable Settings”

on page 31

* After initial system installation, you can redirect the system console to take its input from and send its output

to the serial port TTYB.

During Installation

After Installation

✓

What the System Console Does

The system console displays status and error messages generated by firmware-based tests during system startup. After those tests have been run, you can enter special commands that affect the firmware and alter system behavior. For more information about tests that run during the boot process, refer to the Netra 440 Server Diagnostics and Troubleshooting Guide.

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

Using the System Console

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

Chapter 1 Configuring the System Console 3

You must also ensure that the system console is directed to the appropriate port on the Netra 440 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.

Netra 440 Server

OpenBoot Conﬁguration Variable Settings

input-device=ttya

output-device=ttya

System

Console

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

input-device=ttyb

output-device=ttyb

input-device=keyboard

output-device=screen

Ports Console Devices

SERIAL MGT

NET MGT

ttyb

Graphics Card

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

TIP

Line

Alphanumeric

terminal

Terminal

server

Graphics

monitor

On Netra 440 servers, the system console comes preconfigured to allow input and output only by means of hardware devices connected to the serial or network management ports. However, because the network management port is not available until you assign it an IP address, your first connection must be to the serial management port (SERIAL MGT).

4 Netra 440 Server System Administration Guide • August 2004

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

■ Terminal server

■ Alphanumeric terminal or similar device

■ TIP line connected to another Sun computer

This provides for secure access at the installation site.

ALOM serial management port

ALOM network management port

FIGURE 1-2 Serial Management Port on the ALOM System Controller Card–Default

Console Connection

Using a TIP line might be preferable to connecting an alphanumeric terminal, since TIP lets you use windowing and operating system features on the machine being used to make the connection to the Netra 440 server.

Although the Solaris OS sees the serial management port as ttya, the serial management port is not a general-purpose serial port. If you want to use a generalpurpose serial port with your server—to connect a serial printer, for instance—use the regular 9-pin serial port on the back panel of the Netra 440. The Solaris OS sees this port as ttyb.

■ For instructions on accessing the system console through a terminal server, see

“Accessing the System Console Through a Terminal Server” on page 19.

■ For instructions on accessing the system console through an alphanumeric

terminal, see

“Accessing the System Console Through an Alphanumeric

Terminal” on page 26.

■ For instructions on accessing the system console through a TIP line, see

“Accessing the System Console Through a TIP Connection” on page 22.

Chapter 1 Configuring the System Console 5

Once you have assigned an IP address to the network management port (NET MGT), you can connect an Ethernet-capable device to the system console through your network. This provides for remote monitoring and control. In addition, up to four simultaneous connections to the system controller sc> prompt are available through the network management port. For more information, see

“Activating the

Network Management Port” on page 17.

Alternative System Console Configuration

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

Serial port (TTYB)

FIGURE 1-3 Alternative Console Ports (Require Additional Configuration)

USB ports (for keyboard and mouse)

Six PCI card slots

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

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

■ Power-on self-text (POST) output can only be directed to the serial management

and network management ports. It cannot be directed to ttyb or to a graphics card’s port.

6 Netra 440 Server System Administration Guide • August 2004

■ If you have directed the system console to ttyb, you cannot use this port for any

other serial device.

■ In a default configuration, the serial management and network management ports

allow you to open up to four additional windows through which you can view, but not affect, system console activity. You cannot open these windows if the system console is redirected to ttyb or to a graphics card’s port.

■ In a default configuration, the serial management and network management ports

allow you to switch between viewing system console and system controller output on the same device by typing a simple escape sequence or command. The escape sequence and command do not work if the system console is redirected to ttyb or to a graphics card’s port.

■ The system controller keeps a log of console messages, but some messages are not

logged if the system console is redirected to ttyb or to a graphic card’s port. The omitted information could be important if you need to contact Sun customer service with a problem.

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

You change the system console configuration by setting OpenBoot configuration variables. See

“System Console OpenBoot Configuration Variable Settings” on

page 31.

You can also set OpenBoot configuration variables using the ALOM system controller. For details, refer to the Advanced Lights Out Manager User’s Guide (8175481-xx).

Accessing the System Console Through a Graphics Monitor

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

After starting the system, you might need to install the correct software driver for the PCI card you have installed. For detailed hardware instructions, see

the System Console Through a Local Graphics Monitor” on page 29.

Note – POST diagnostics cannot display status and error messages to a local

graphics monitor.

Chapter 1 Configuring the System Console 7

“Accessing

About the sc> Prompt

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

Note – To view ALOM system controller boot messages, you must connect an

alphanumeric terminal to the serial management port before connecting the AC power cords to the Netra 440 server.

You can log in to the ALOM system controller at any time, regardless of system power state, as long as AC power is connected to the system and you have a way of interacting with the system. You can also access the ALOM system controller prompt (sc>) from the 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. For more information, see the following:

■ “Getting to the ok Prompt” on page 13

■ “Switching Between the ALOM System Controller and the System Console” on

page 15

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

Note – When you access the ALOM system controller for the first time, it forces you

to create a user name and password for subsequent access. After this initial configuration, you will be prompted to enter a user name and password every time you access the ALOM system controller.

8 Netra 440 Server System Administration Guide • August 2004

Access Through Multiple Controller Sessions

Up to five ALOM system controller sessions can be active concurrently, one session through the serial management port and up to four sessions through the network management port. Users of each of these sessions can issue commands at the sc> prompt. 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:

■ “Accessing the System Controller” on page 16

■ “Activating the Network Management Port” on page 17

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

Reaching the sc> Prompt

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

■ If the system console is directed to the serial management and network

management ports, you can type the ALOM system controller escape sequence (#.).

■ You can log in directly to the ALOM system controller from a device connected to

the serial management port. See

■ You can log in directly to the ALOM system controller using a connection through

the network management port. See

on page 17.

“Accessing the System Controller” on page 16.

“Activating the Network Management Port”

OpenBoot ok Prompt

A Netra 440 server with the Solaris OS installed is capable of operating at different run levels. A synopsis of run levels follows. For a full description, refer to the Solaris system administration documentation.

Most of the time, you operate a Netra 440 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.

Chapter 1 Configuring the System Console 9

When a Netra 440 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, the system comes up under OpenBoot firmware control before the

operating system is installed.

■ The system boots to the ok prompt when the auto-boot? OpenBoot

configuration variable is set to false.

■ The system transitions to run level 0 in an orderly way when the operating

system is halted.

■ The system reverts to OpenBoot firmware control when the operating system

crashes.

■ 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.

■ You deliberately place the system under firmware control in order to execute

firmware-based commands or to run diagnostic tests.

It is the last of these scenarios which 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” on page 10. For detailed instructions,

see “Getting to the ok Prompt” on page 13.

Reaching the ok Prompt

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 order of desirability, these are:

■ Graceful shutdown

■ ALOM system controller break or console command

■ L1-A (Stop-A) keys or Break key

■ Externally initiated reset (XIR)

■ Manual system reset

A discussion of each method follows. For step-by-step instructions, see “Getting to

the ok Prompt” on page 13.

10 Netra 440 Server System Administration Guide • August 2004

Graceful Shutdown

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. You can also use the system Power button to initiate a graceful system shutdown.

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

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

ALOM System Controller break or console Command

Typing break from the sc> prompt forces a running Netra 440 server to drop into OpenBoot firmware control. If the operating system is already halted, you can use the console command instead of break to reach the ok prompt.

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

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

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

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

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

OpenBoot Configuration Variable Settings” on page 31.

Chapter 1 Configuring the System Console 11

“System Console

Externally Initiated Reset (XIR)

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

For more information, refer to:

■ Netra 440 Server Diagnostics and Troubleshooting Guide (817-3886-xx)

■ Advanced Lights Out Manager User’s Guide (817-5481-xx)

Caution – Because an XIR precludes an orderly shutdown of applications, it should

only be attempted if previously described methods do not work.

Manual System Reset

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

Caution – Forcing a manual system reset results in loss of system state data, and

should be attempted only as a last resort. After a manual system reset, all state information is lost, which inhibits troubleshooting the cause of the problem until the problem reoccurs.

Caution – Accessing the ok prompt suspends the Solaris OS.

When you access the ok prompt from a functioning Netra 440 server, you are suspending the Solaris OS and placing the system under firmware control. Any processes that were running under the operating system are also suspended, and the state of such processes might not be recoverable.

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

12 Netra 440 Server System Administration Guide • August 2004

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

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

For More Information

For more information about the OpenBoot firmware, refer to the OpenBoot 4.x

Command Reference Manual. An online version of the manual is included with the OpenBoot Collection AnswerBook that ships with Solaris software.

Getting to the ok Prompt

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

Prompt” on page 9.

Caution – Dropping the Netra 440 server to the ok prompt suspends all application

and operating system software. After you issue firmware commands and run firmware-based tests from the ok prompt, the system might not be able to resume where it left off.

“OpenBoot ok

If at all possible, back up system data before starting this procedure. Also exit or stop all applications and warn users of the impending loss of service. For information about the appropriate backup and shutdown procedures, see Solaris system administration documentation.

Chapter 1 Configuring the System Console 13

▼ To Get to the ok Prompt

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

See “OpenBoot ok Prompt” on page 9 for details.

2. Follow the appropriate instructions in TABLE 1-2.

TABLE 1-2 Ways of Accessing the ok Prompt

Access Method What to Do

Graceful shutdown of the Solaris OS

L1-A (Stop-A) keys or Break key

ALOM system controller console or break command

Externally initiated reset (XIR)

Manual system reset • From the sc> prompt, type the reset command.

* Requires the OpenBoot configuration variable input-device=keyboard. For more information, see “Ac-

cessing the System Console Through a Local Graphics Monitor” on page 29 and “System Console OpenBoot Configuration Variable Settings” on page 31.

• From a shell or command tool window, issue an appropriate command (for example, the

shutdown or init command) as

described in Solaris system administration documentation.

• From a Sun keyboard connected directly to the Netra 440 server, press the Stop and A keys simultaneously.

–or–

• From an alphanumeric terminal configured to access the system console, press the Break key.

• From the sc> prompt, type the break command. The console command also works, provided the operating environment software is not running and the server is already under OpenBoot firmware control.

• From the sc> prompt, type the reset -x command.

14 Netra 440 Server System Administration Guide • August 2004

Switching Between the ALOM System Controller and the System Console

The Netra 440 server features two management ports, labeled SERIAL MGT and NET MGT, located on the server’s back panel. If the system console is directed to use the serial management and network management ports (its default configuration), these ports provide access to both the system console and the ALOM system controller, each on a separate “channel” (see

FIGURE 1-4).

System Console

NET MGT

or SERIAL MGT

Por t

FIGURE 1-4 Separate System Console and System Controller “Channels”

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

console #.

sc>

ALOM System Controller

Chapter 1 Configuring the System Console 15

+ 67 hidden pages

Sun Microsystems Netra 440 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual

Contents

Figures

Tables

Preface

Configuring the System Console

Communicating With the System

What the System Console Does

Using the System Console

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

Alternative System Console Configuration

Accessing the System Console Through a Graphics Monitor

About the sc> Prompt

Access Through Multiple Controller Sessions

Reaching the sc> Prompt

OpenBoot ok Prompt

Reaching the ok Prompt

Graceful Shutdown

ALOM System Controller break or console Command

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

Externally Initiated Reset (XIR)

Manual System Reset

For More Information

Getting to the ok Prompt

Switching Between the ALOM System Controller and the System Console