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.
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.
Contents Contents 1.
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 Verifying Serial Port Settings on TTYB 28 Accessing the System Console Through a Local Graphics Monitor System Console OpenBoot Configuration Variable Settings 2.
3. Managing Disk Volumes Disk Volumes 51 51 Volume Management Software 52 VERITAS Dynamic Multipathing Sun StorEdge Traffic Manager For More Information RAID Technology 52 53 54 Disk Concatenation 54 RAID 0: Disk Striping RAID 1: Disk Mirroring 55 55 RAID 5: Disk Striping With Parity Hot-Spares 52 56 56 Hardware Disk Mirroring 56 Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names 57 A. OpenBoot Configuration Variables B.
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) FIGURE 1-4 Separate System Console and System Controller “Channels” FIGURE 1-5 Patch Panel Connection Between a Terminal Server and a Netra 440 Server FIGURE 1-6 TIP Connection Between a Netra 440 Server and Another Sun System FIGURE 3-1
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 TABLE 1-3 Pin Crossovers for Connecting to a Typical Terminal Server TABLE 1-4 OpenBoot Configuration Variables That Affect the System Console 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
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 NetraTM 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).
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.
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. Replace command-line variables with real names or values. Read Chapter 6 in the User’s Guide. These are called class options.
Accessing Sun Documentation You can view, print, or purchase a broad selection of Sun documentation, including localized versions, at: http://www.sun.com/documentation Third-Party Web Sites Sun is not responsible for the availability of third-party web sites mentioned in this document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources.
CHAPTER 1 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.
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 (Continued) During Installation* Devices Available for Accessing the System Console After Installation A local graphics monitor (frame buffer card, graphics monitor, mouse, and so forth).
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.
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.
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.
■ 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.
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.
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.
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.
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.
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.
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.
▼ 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 • 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.
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 ok # NET MGT or SERIAL MGT Port console #.
The prompt displayed on the terminal or shell tool tells you which “channel” you are accessing: ■ The # or % prompt indicates that you are at the system console and that the Solaris OS is running. ■ The ok prompt indicates that you are at the system console and that the server is running under OpenBoot firmware control. ■ The sc> prompt indicates that you are at the ALOM system controller.
For more information about the ALOM system controller card, refer to the Netra 440 Server Product Overview (817-3881-xx) and the Advanced Lights Out Manager User’s Guide (817-5481-xx). ▼ To Use the Serial Management Port 1. Ensure that the serial port on your connecting device is set to the following parameters: ■ ■ ■ ■ ■ 9600 baud 8 bits No parity 1 stop bit No handshaking 2. Establish an ALOM system controller session. See Advanced Lights Out Manager User’s Guide (817-5481-xx) for instructions. 3.
Data centers frequently devote a separate subnet to system management. If your data center has such a configuration, connect the network management port to this subnet. Note – The network management port is a 10BASE-T port. The IP address assigned to the network management port is a unique IP address, separate from the main Netra 440 server IP address, and is dedicated for use only with the ALOM system controller. For more information, see the Netra 440 Server Product Overview.
To connect through the network management port, use the telnet command to the IP address you specified in Step 3 of the preceding procedure. Accessing the System Console Through a Terminal Server The following procedure assumes that you are accessing the system console by connecting a terminal server to the serial management port (SERIAL MGT) of the Netra 440 server. ▼ To Access The System Console Through a Terminal Server 1.
Terminal server Straight-through cable Patch panel Patch cable to serial management port Netra 440 server FIGURE 1-5 Patch Panel Connection Between a Terminal Server and a Netra 440 Server If the pinouts for the serial management port do not correspond with the pinouts for the RJ-45 ports on the terminal server, you need to make a crossover cable that takes each pin on the Netra 440 server serial management port to the corresponding pin in the terminal server’s serial port.
2. Open a terminal session on the connecting device, and type: % telnet IP-address-of-terminal-server port-number For example, for a Netra 440 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 3. If you want to use TTYB instead of the serial management port, do the following: a. Redirect the system console by changing OpenBoot configuration variables.
d. Power on the system. Refer to the Netra 440 Server Installation Guide for power-on procedures. Continue with your installation or diagnostic test session as appropriate. When you are finished, end your session by typing the terminal server’s escape sequence and exit the window. For more information about connecting to and using the ALOM system controller, refer to the Advanced Lights Out Manager User’s Guide.
▼ To Access the System Console Through the TIP Connection 1. Connect the RJ-45 serial cable and, if required, the DB-9 or DB-25 adapter provided. The cable and adapter connect between another Sun system’s serial port (typically ttyb) and the serial management port on the back panel of the Netra 440 server. Pinouts, part numbers, and other details about the serial cable and adapter are provided in the Netra 440 Server Service Manual (817-3883-xx). 2.
Note – You can only access the sc> prompt and view POST messages from either the serial management port or the network management port. Note – There are many other OpenBoot configuration variables. Although these variables do not affect which hardware device is used to access the system console, some of them affect which diagnostic tests the system runs and which messages the system displays at its console. For details, refer to the Netra 440 Server Diagnostics and Troubleshooting Guide (817-3886-xx). b.
Modifying the /etc/remote File This procedure might be necessary if you are accessing the Netra 440 server using a TIP connection from a Sun system running an older version of the Solaris OS software. You might also need to perform this procedure if the /etc/remote file on the Sun system has been altered and no longer contains an appropriate hardwire entry.
Note – If you intend to use the Sun system’s serial port A rather than serial port B, edit this entry by replacing /dev/ttyb with /dev/ttya. The /etc/remote file is now properly configured. Continue establishing a TIP connection to the Netra 440 server system console. See “Accessing the System Console Through a TIP Connection” on page 22.
5. If you want to use ttyb instead of the serial management port, do the following: a. Redirect the system console by changing the OpenBoot configuration variables. At the ok prompt, type the following commands: ok setenv input-device ttyb ok setenv output-device ttyb Note – You can only access the sc> prompt and view POST messages from either the serial management port or the network management port. Note – There are many other OpenBoot configuration variables.
Verifying Serial Port Settings on TTYB This procedure lets you verify the baud rate and other serial port settings used by the Netra 440 server to communicate with a device attached to its ttyb port. Note – The serial management port always operates at 9600 baud, 8 bits, with no parity and 1 stop bit. You must be logged in to the Netra 440 server, and the server must be running Solaris OS software. ▼ To Verify the Serial Port Settings on TTYB 1. Open a shell tool window. 2.
Accessing the System Console Through a Local Graphics Monitor After initial system installation, you can install a local graphics monitor and configure it to access the system console. You cannot use a local graphics monitor to perform initial system installation, nor can you use a local graphics monitor to view power-on self-test (POST) messages. To install a local graphics monitor, you must have: ■ ■ ■ ■ A A A A supported PCI-based graphics frame buffer card and software driver.
Note – There are many other OpenBoot configuration variables. Although these variables do not affect which hardware device is used to access the system console, some of them affect which diagnostic tests the system runs and which messages the system displays at its console. For details, refer to the Netra 440 Server Diagnostics and Troubleshooting Guide (817-3886-xx). 7.
System Console OpenBoot Configuration Variable Settings The Netra 440 system console is directed to the serial management and network management ports (SERIAL MGT and NET MGT) by default. However, you can redirect the system console to the serial DB-9 port (TTYB), or to a local graphics monitor, keyboard, and mouse. You can also redirect the system console back to the serial management and network management ports.
32 Netra 440 Server System Administration Guide • August 2004
CHAPTER 2 Managing RAS Features and System Firmware This chapter describes how to manage reliability, availability, and serviceability (RAS) features and system firmware, including Sun Advanced Lights Out Manager (ALOM) system controller, automatic system recovery (ASR), and the hardware watchdog mechanism. In addition, this chapter describes how to unconfigure and reconfigure a device manually, and introduces multipathing software.
ALOM System Controller The ALOM system controller supports a total of five concurrent sessions per server: four connections available through the network management port and one connection through the serial management port. Note – Some of the ALOM system controller commands are also available through the Solaris scadm utility. For more information, refer to the Advanced Lights Out Manager User’s Guide (817-5481-xx).
▼ To Log In To the ALOM System Controller 1. If you are logged in to the system console, type #. to get to the sc> prompt. Press the pound sign key, followed by the period key. Then press the Return key. 2. At the ALOM login prompt, enter the login name and press Return. The default login name is admin. Sun(tm) Advanced Lights Out Manager 1.3 Please login: admin 3. At the password prompt, enter the password and press Return twice to get to the sc> prompt.
Note – Do not use the scadm utility while SunVTS™ diagnostics are running. See your SunVTS documentation for more information. You must be logged in to the system as root to use the scadm utility. The scadm utility uses the following syntax: # scadm command The scadm utility sends its output to stdout. You can also use scadm in scripts to manage and configure ALOM from the host system.
The information this command can display includes temperature, power supply status, front panel LED status, system control keyswitch position, and so on. The display uses a format similar to that of the UNIX command prtdiag(1m). Note – Some environmental information might not be available when the server is in standby mode. Note – You do not need ALOM system controller user permissions to use this command. The showenvironment command has one option: -v.
● To turn off the Locator LED, do one of the following: ■ In the Solaris OS, log in as superuser and type the following command: # /usr/sbin/setlocator -f Locator LED is off. ■ From the ALOM system controller command prompt, type: sc> setlocator off Locator LED is off. ● To display the state of the Locator LED, do one of the following: ■ In the Solaris OS, log in as superuser and type the following command: # /usr/sbin/showlocator Locator LED is on.
OpenBoot Emergency Procedures The introduction of Universal Serial Bus (USB) keyboards with the newest Sun systems has made it necessary to change some of the OpenBoot emergency procedures. Specifically, the Stop-N, Stop-D, and Stop-F commands that were available on systems with non-USB keyboards are not supported on systems that use USB keyboards, such as the Netra 440 server.
OpenBoot Emergency Procedures for Systems With USB Keyboards The following sections describe how to perform the functions of the Stop commands on systems that use USB keyboards, such as the Netra 440 server. These same functions are available through Sun Advanced Lights Out Manager (ALOM) system controller software.
3. To reset the system, type the following command: sc> reset Are you sure you want to reset the system [y/n]? sc> console y 4. To view console output as the system boots with default OpenBoot configuration variables, switch to console mode. sc> console ok 5. Type set-defaults to discard any customized IDPROM values and to restore the default settings for all OpenBoot configuration variables. Stop-F Functionality The Stop-F functionality is not available on systems with USB keyboards.
An auto-configuring capability designed into the OpenBoot firmware enables the system to unconfigure failed components and to restore system operation. As long as the system is capable of operating without the failed component, the ASR features enable the system to reboot automatically, without operator intervention. Note – ASR is not activated until you enable it. See “Enabling and Disabling Automatic System Recovery” on page 44.
Error Handling Summary Error handling during the power-on sequence falls into one of the following three cases: ■ If no errors are detected by POST or OpenBoot Diagnostics, the system attempts to boot if auto-boot? is true. ■ If only nonfatal errors are detected by POST or OpenBoot Diagnostics, the system attempts to boot if auto-boot? is true and auto-boot-on-error? is true. Nonfatal errors include the following: ■ Ultra-4 SCSI subsystem failure.
Reset Scenarios Three OpenBoot configuration variables, diag-switch?, obdiag-trigger, and post-trigger, control whether the system runs firmware diagnostics in response to system reset events. The standard system reset protocol bypasses POST and OpenBoot Diagnostics completely unless the variable diag-switch? is set to true, or the system control keyswitch is in the Diagnostics position. The default setting for this variable is false.
2. Set the obdiag-trigger variable to any combination of power-on-reset, error-reset, and user-reset. For example, type: ok setenv obdiag-trigger power-on-reset error-reset Note – For more information about OpenBoot configuration variables, refer to the Netra 440 Server Diagnostics and Troubleshooting Guide (817-3886-xx). 3.
Obtaining Automatic System Recovery Information Use the following procedure to retrieve information about the status of the automatic system recovery (ASR) feature. ● At the ok prompt, type: ok .asr In the .asr command output, any devices marked disabled have been manually unconfigured using the asr-disable command. The .asr command also lists devices that have failed firmware diagnostics and have been automatically unconfigured by the OpenBoot ASR feature.
where the device-identifier is one of the following: Any full physical device path, as reported by the OpenBoot show-devs command Any valid device alias, as reported by the OpenBoot devalias command Any device identifier from TABLE 2-2 ■ ■ ■ Note – The device identifiers are not case sensitive. You can type them as uppercase or lowercase characters. TABLE 2-2 Device Identifiers and Devices Device Identifiers Devices cpu0-bank0, cpu0-bank1, cpu0-bank2, cpu0-bank3, ...
■ To create your own device alias for a physical device, type: ok devalias alias-name physical-device-path where alias-name is the alias that you want to assign, and physical-device-path is the full physical device path for the device. Note – If you manually disable a device using asr-disable, and then assign a different alias to the device, the device remains disabled even though the device alias has changed. 2.
Enabling the Hardware Watchdog Mechanism and Its Options For background information about the hardware watchdog mechanism and related externally initiated reset (XIR) functionality, refer to the Netra 440 Server Product Overview (817-3881-xx). ▼ To Enable the Hardware Watchdog Mechanism 1. Edit the /etc/system file to include the following entry: set watchdog_enable = 1 2. Bring the system to the ok prompt by typing the following: # init 0 3. Reboot the system so that the changes can take effect.
Multipathing Software Multipathing software lets you define and control redundant physical paths to I/O devices, such as storage devices and network interfaces. If the active path to a device becomes unavailable, the software can automatically switch to an alternate path to maintain availability. This capability is known as automatic failover.
CHAPTER 3 Managing Disk Volumes This chapter describes redundant array of independent disks (RAID) concepts, how to manage disk volumes, and how to configure hardware mirroring using the on-board Ultra-4 SCSI controller.
Volume Management Software Volume management software lets you create disk volumes.
The Sun StorEdge Traffic Manager software integrates multiple path I/O capabilities, automatic load balancing, and path failover functions into one package for Sun servers connected to supported Sun StorEdge systems. Sun StorEdge Traffic Manager can provide you with increased system performance and availability for building mission-critical storage area networks (SANs).
RAID Technology VERITAS Volume Manager and Solstice DiskSuite™ software support RAID technology to optimize performance, availability, and cost per user. RAID technology reduces recovery time in the event of file system errors, and increases data availability even in the event of a disk failure. There are several levels of RAID configurations that provide varying degrees of data availability with corresponding trade-offs in performance and cost.
RAID 0: Disk Striping Disk striping (RAID 0) is a technique for increasing system throughput by using several hard drives in parallel. Whereas in non-striped disks the operating system writes a single block to a single disk, in a striped arrangement, each block is divided and portions of the data are written to different disks simultaneously.
On the Netra 440 server, you can configure hardware disk mirroring using the onboard Ultra-4 SCSI controller. This provides higher performance than with conventional software mirroring using volume management software.
only one device (the master) appears in the device tree. The mirrored device (the slave) is invisible to the operating system, and is accessed only by the Ultra-4 SCSI controller. Caution – Creating or restoring a disk mirror destroys all data previously stored on the hard drive. Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names To perform a disk hot-swap procedure, you must know the physical or logical device name for the drive that you want to install or remove.
To verify that a hardware disk mirror does not exist already, type: # raidctl No RAID volumes found. The example above indicates that no RAID volume exists. In another case: # raidctl RAID RAID RAID Disk Volume Status Disk Status ---------------------------------------c1t1d0 DEGRADEDc1t1d0 OK c1t2d0 DEGRADED The example above indicates a hardware mirror has degraded at disk c1t2d0.
3. To check the status of a RAID mirror, type the following command: # raidctl RAID RAID RAID Disk Volume Status Disk Status -------------------------------------------------------c1t0d0 RESYNCING c1t0d0 OK c1t1d0 OK The example above indicates that the RAID mirror is still resynchronizing with the backup drive. The example below shows that the RAID mirror is completely restored and online.
2. Determine the name of the mirrored volume. Type the following command: # raidctl RAID RAID RAID Disk Volume Status Disk Status -----------------------------------c1t0d0 OK c1t0d0 OK c1t1d0 OK In this example, the mirrored volume is c1t0d0. Note – The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. 3.
▼ To Perform a Mirrored Disk Hot-Plug Operation 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names” on page 57. Caution – Ensure that the hard drive OK-to-Remove LED is lit, indicating that the hard drive is offline. If the hard drive is still online, you risk removing the disk during a read/write operation, which could result in data loss. 2.
5. To check the status of a RAID rebuild, type the following command: # raidctl For example: # raidctl RAID RAID RAID Disk Volume Status Disk Status ---------------------------------------c1t1d0 RESYNCING c1t1d0 OK c1t2d0 OK This example indicates that RAID volume c1t1d0 is resynchronizing.
2. View the status of the SCSI devices.
Note that while you can use the Solaris OS cfgadm install_device and cfgadm remove_device commands to perform a hard drive hot-swap procedure, these commands issue the following warning message when you invoke these commands on a bus containing the system disk: # cfgadm -x remove_device c0::dsk/c1t1d0 Removing SCSI device: /devices/pci@1f,4000/scsi@3/sd@1,0 This operation will suspend activity on SCSI bus: c0 Continue (yes/no)? y dev = /devices/pci@1f,4000/scsi@3/sd@1,0 cfgadm: Hardware specific failure: fa
4. Verify that the device has been removed from the device tree.
8. Verify that the new hard drive is in the device tree.
APPENDIX A OpenBoot Configuration Variables TABLE A-1 describes the OpenBoot firmware configuration variables stored on the system configuration card (SCC). The OpenBoot configuration variables are printed here in the order in which they appear when you issue the showenv command. TABLE A-1 OpenBoot Configuration Variables Stored on the System Configuration Card Variable Possible Values Default Value Description test-args variable_name none Default test arguments passed to OpenBoot Diagnostics.
TABLE A-1 OpenBoot Configuration Variables Stored on the System Configuration Card (Continued) Variable Possible Values Default Value Description ttyb-rts-dtr-off true, false false If true, operating system does not assert rts (request-to-send) and dtr (data-transfer-ready) on ttyb. ttyb-ignore-cd true, false true If true, operating system ignores carrierdetect on ttyb.
TABLE A-1 OpenBoot Configuration Variables Stored on the System Configuration Card (Continued) Variable Possible Values Default Value Description nvramrc variable_name none Command script to execute if use-nvramrc? is true. security-mode none, command, full none Firmware security level. security-password variable_name none Firmware security password if security-mode is not none (never displayed) - do not set this directly.
70 Netra 440 Server System Administration Guide • August 2004
B APPENDIX Alarm Relay Output Application Programming Interface This appendix provides a sample program that illustrates how to get/set the status of the alarms. The application can use LOMIOCALSTATE ioctl to obtain the status of each alarm and LOMIOCALCTL ioctl to set them individually. For more details on the Alarm Indicators, refer to the Netra 440 Server Service Manual (817-3883-xx).
CODE EXAMPLE B-1 Example Program for get/set Status of the Alarms (Continued) #include
CODE EXAMPLE B-1 Example Program for get/set Status of the Alarms (Continued) #include if ((ald.alarm_state != ALARM_OFF) && (ald.alarm_state != ALARM_ON)) { printf("Invalid value returned: %d\n", ald.alarm_state); exit(1); } printf("ALARM.%s = %s\n", alarm, get_alarmval(ald.
CODE EXAMPLE B-1 Example Program for get/set Status of the Alarms (Continued) #include
CODE EXAMPLE B-1 Example Program for get/set Status of the Alarms (Continued) #include
76 Netra 440 Server System Administration Guide • August 2004
Index obtaining recovery information, 46 SYMBOLS /etc/remote file, 23 modifying, 25 B A Activity (disk drive LED), 65 Advanced Lights Out Manager (ALOM) commands, See sc> prompt escape sequence (#.
D F default system console configuration, 4 device identifiers, listed, 47 device reconfiguration, manual, 48 device unconfiguration, manual, 46 DHCP (Dynamic Host Configuration Protocol), 17 diag-device (OpenBoot configuration variable), 43 disk configuration concatenation, 54 hot-spares, 56 mirroring, 54 RAID 0, 55 RAID 1, 55 RAID 5, 56 striping, 55 disk drives LEDs Activity, 65 OK-to-Remove, 61, 64, 65 logical device names, table, 57 disk hot-plug mirrored disk, 61 non-mirrored disk, 62 disk mirror (RA
Stop-F (non-USB keyboard sequence), 39 Stop-N (non-USB keyboard sequence), 39 L L1-A keyboard sequence, 10, 11, 14 LEDs Activity (disk drive LED), 65 Locator (system status LED), 37 OK-to-Remove (disk drive LED), 61, 64, 65 Locator (system status LED) controlling, 37 controlling from sc> prompt, 37, 38 controlling from Solaris, 37, 38 logging in to the Advanced Lights Out Manager (ALOM), 34 logical device name (disk drive), reference, 57 M manual device reconfiguration, 48 manual device unconfiguration, 4
PCI graphics card configuring to access system console, 29 connecting graphics monitor to, 29 physical device name (disk drive), 57 port settings, verifying on ttyb, 28 power-off (OpenBoot command), 21, 24, 27 poweroff (sc> command), 12 poweron (sc> command), 12 probe-ide (OpenBoot command), 11 probe-scsi (OpenBoot command), 11 probe-scsi-all (OpenBoot command), 11 R RAID (redundant array of independent disks) disk concatenation, 54 hardware mirror, See hardware disk mirror striping, 55 RAID 0 (striping),
uadmin, 11 uname, 25 uname -r, 25 Solaris Volume Manager, 52, 53 Solstice DiskSuite, 54 Stop (non-USB keyboard) command, 39 Stop-A (non-USB keyboard sequence) See L1-A keyboard sequence Stop-A (USB keyboard functionality), 40 Stop-D (non-USB keyboard command), 39 Stop-D (USB keyboard functionality), 41 Stop-F (non-USB keyboard command), 39 Stop-F (USB keyboard functionality), 41 Stop-N (non-USB keyboard command), 39 Stop-N (USB keyboard functionality), 40 striping of disks, 55 Sun StorEdge 3310, 53 Sun Stor
82 Netra 440 Server System Administration Guide • August 2004
