Seitenanzahl: 84 T1admin_u.ti1 Seite 1 Mittwoch, 6. Dezember 2006 11:12 11 Administration Guide SPARC® Enterprise T1000 Server Herausgegeben von / Published by Fujitsu Siemens Computers GmbH Printed in the Federal Republic of Germany Ausgabe/Edition November 2006 Bestell-Nr./ Order No.
SPARC® Enterprise T1000 Server Administration Guide Order No. : U41696-J-Z816-1-76 Part No.
Copyright 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. FUJITSU LIMITED provided technical input and review on portions of this material. Sun Microsystems, Inc. and Fujitsu Limited each own or control intellectual property rights relating to products and technology described in this document, and such products, technology and this document are protected by copyright laws, patents and other intellectual property laws and international treaties.
Copyright 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, Etats-Unis. Tous droits réservés. Entrée et revue tecnical fournies par FUJITSU LIMITED sur des parties de ce matériel. Sun Microsystems, Inc. et Fujitsu Limited détiennent et contrôlent toutes deux des droits de propriété intellectuelle relatifs aux produits et technologies décrits dans ce document.
Contents Preface 1.
Accessing the System Console Through an Alphanumeric Terminal ▼ 13 To Access the System Console Through an Alphanumeric Terminal 13 Switching Between the System Controller Prompt and the System Console ALOM CMT and The sc> Prompt 16 Access Through Multiple Controller Sessions Reaching the sc> Prompt OpenBoot ok Prompt 17 17 18 Methods To Reach the ok Prompt Graceful Shutdown 19 19 ALOM CMT break or console Command L1-A (Stop-A) Keys or Break Key Manual System Reset 20 20 For More Information
Reset Scenarios 32 Automatic System Recovery User Commands 33 Enabling and Disabling Automatic System Recovery ▼ To Enable Automatic System Recovery ▼ To Disable Automatic System Recovery 34 34 Obtaining Automatic System Recovery Information Unconfiguring and Reconfiguring Devices To Unconfigure a Device Manually 36 ▼ To Reconfigure a Device Manually 36 ▼ 37 To Display System Fault Information Multipathing Software 37 37 For More Information on Multipathing Software Storing FRU Informati
Index viii 61 SPARC Enterprise T1000 Server Administration Guide • April 2007
Figures FIGURE 1-1 Directing the System Console 4 FIGURE 1-2 Rear I/O Panel of the Chassis 5 FIGURE 1-3 Patch Panel Connection Between a Terminal Server and Your Server FIGURE 1-4 TIP Connection Between a Server and Another System FIGURE 1-5 Switching between the System Console and the System Controller Prompt FIGURE 2-1 Locator Button on the Front of the Server Chassis FIGURE 3-1 Graphical Representation of Disk Striping FIGURE 3-2 Graphical Representation of Disk Mirroring 9 11 15 30
x SPARC Enterprise T1000 Server Administration Guide • April 2007
Tables TABLE 1-1 Ways of Communicating With the System 2 TABLE 1-2 Pin Crossovers for Connecting the Server to a Terminal Server TABLE 1-3 Ways of Accessing the ok Prompt TABLE 1-4 OpenBoot Configuration Variables That Affect the System Console TABLE 2-1 LED Behavior and Meaning TABLE 2-2 LED Behaviors With Assigned Meanings TABLE 2-3 Virtual Keyswitch Setting for Reset Scenario TABLE 2-4 ALOM CMT Variable Settings for Reset Scenario TABLE 2-5 Device Identifiers and Devices TABLE 3-1 Di
xii SPARC Enterprise T1000 Server Administration Guide • April 2007
Preface The SPARC Enterprise T1000 Server Administration Guide is written for experienced system administrators. It includes general descriptive information about the 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).
Describes the tools used to configure system firmware, including Advanced Lights Out Manager (ALOM) CMT system controller environmental monitoring, automatic system recovery (ASR), and multipathing software. In addition, it describes how to unconfigure and reconfigure a device manually. ■ CHAPTER 3 Managing Disk Volumes Describes redundant array of independent disks (RAID) concepts, and how to configure and manage RAID disk volumes using your server’s on-board serial attached SCSI (SAS) disk controller.
Related Documentation The latest versions of all the SPARC Enterprise Series manuals are available at the following Web sites: http://manuals.fujitsu-siemens.com/ Title Order No.
Using UNIX Commands This document might not contain information about basic UNIX® commands and procedures such as shutting down the system, booting the system, and configuring devices. Refer to the following for this information: ■ Software documentation that you received with your system ■ Solaris™ Operating System documentation, which is at: http://docs.sun.com Text Conventions This manual uses the following fonts and symbols to express specific types of information.
Prompt Notations The following prompt notations are used in this manual. Shell Prompt Notations C shell machine-name% C shell superuser machine-name# Bourne shell and Korn shell $ Bourne shell and Korn shell and Korn shell superuser # Fujitsu Siemens Computers Welcomes Your Comments We would appreciate your comments and suggestions to improve this document.
Reader's Comment Form xviii SPARC Enterprise T1000 Server Administration Guide • April 2007
FOLD AND TAPE NO POSTAGE NECESSARY IF MAILED IN THE UNITED STATES BUSINESS REPLY MAIL FIRST-CLASS MAIL PERMIT NO 741 SUNNYVALE CA POSTAGE WILL BE PAID BY ADDRESSEE FUJITSU COMPUTER SYSTEMS AT TENTION ENGINEERING OPS M/S 249 1250 EAST ARQUES AVENUE P O BOX 3470 SUNNYVALE CA 94088-3470 FOLD AND TAPE Preface xix
xx SPARC Enterprise T1000 Server Administration Guide • April 2007
CHAPTER 1 Configuring the System Console This chapter explains what the system console is, describes the different ways of configuring it on your server, and helps you understand its relation to the system controller.
The system console must be accessed through the system controller during 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) Devices Available During Installation After Installation Further Information X X “System Console OpenBoot Configuration Variable Settings” on page 23 X “Activating the Network Management Port” on page 7 An Ethernet line connected to the network management port (NET MGT). What the System Console Does The system console displays status and error messages generated by firmware-based tests during system startup.
You must also ensure that the system console is directed to the appropriate port on your server’s rear 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 outputdevice 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 computer These constraints provide for secure access at the installation site.
from SSH to Telnet. Up to eight 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 7. Accessing the System Controller The following sections describe ways of accessing the system controller.
Activating the Network Management Port The network management port is configured by default to retrieve network settings using DHCP and allow connections using SSH. You may need to modify these settings for your network. If you are unable to use DHCP and SSH on your network, you must connect to ALOM CMT through the system controller using the serial management port to reconfigure the network management port.
■ If your network uses static IP addresses, type: sc> sc> sc> sc> ■ setsc setsc setsc setsc netsc_dhcp false netsc_ipaddr ip-address netsc_ipnetmask ip-netmask netsc_ipgateway ip-address If your network uses Dynamic Host Configuration Protocol (DHCP), type: sc> setsc netsc_dhcp true 4.
Accessing the System Console Through a Terminal Server The following procedure assumes that you are accessing ALOM CMT on the system controller by connecting a terminal server to the serial management port (SER MGT) of your server. ▼ To Access The System Console Through a Terminal Server 1. Complete the physical connection from the serial management port to your terminal server. The serial management port on the server is a data terminal equipment (DTE) port.
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 server serial management port to the corresponding pin in the terminal server’s serial port. TABLE 1-2 shows the crossovers that the cable must perform.
FIGURE 1-4 TIP Connection Between a Server and Another System ▼ To Access the System Console Through a 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 system’s serial port (typically TTYB) and the serial management port on the rear panel of the server. Pinouts, part numbers, and other details about the serial cable and adapter are provided in the service manual for your server. 2.
Note – Use a shell tool or a CDE terminal (such as dtterm), not a command tool. Some TIP commands might not work properly in a command tool window. Modifying the /etc/remote File This procedure might be necessary if you are accessing the server using a TIP connection from a remote 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 remote system has been altered and no longer contains an appropriate hardwire entry.
■ If the number displayed by the uname -r command is less than 5.0: Check the /etc/remote file and add the following entry, if it does not already exist. hardwire:\ :dv=/dev/ttyb:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D: Note – If you intend to use the remote 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 server system console.
■ ■ 1 stop bit No handshake protocol Refer to the documentation accompanying your terminal for information about how to configure the terminal. You can issue system commands and view system messages using the alphanumeric terminal. Continue with your installation or diagnostic procedure, as needed. When you are finished, type the alphanumeric terminal’s escape sequence. For more information about connecting to and using the system controller, refer to the ALOM CMT guide for your server.
Switching Between the System Controller Prompt and the System Console The server features two management ports, labeled SER MGT and NET MGT, located on the server’s rear panel. If the system console is directed to the virtualconsole device (its default configuration), these ports provide access to both the system console and the ALOM CMT command-line interface (also called the system controller prompt, see FIGURE 1-5). Network management or Serial management port console ok sc> # #.
The prompt displayed on the terminal or shell tool indicates 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 CMT command-line interface.
Note – To view system controller boot messages, you must connect an alphanumeric terminal to the serial management port before connecting the AC power cords to the server. You can log in to the 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. The sc> prompt indicates that you are interacting with the system controller directly.
■ You can log in directly to the system controller from a device connected to the serial management port. See “Accessing the System Controller” on page 6. ■ You can log in directly to ALOM CMT on the system controller using a connection through the network management port. See “Activating the Network Management Port” on page 7.
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. The section “Methods To Reach the ok Prompt” on page 19 lists several ways. For detailed instructions, see “Getting to the ok Prompt” on page 21. Methods To Reach 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.
ALOM CMT break or console Command Typing break from the sc> prompt forces a running 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. Caution – 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.
When you access the ok prompt from a functioning 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. After a manual system reset the system can be configured to boot automatically if the OpenBoot auto-boot? configuration variable is set to true. See “System Console OpenBoot Configuration Variable Settings” on page 23.
▼ 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 18 for details. 2. Follow the appropriate instructions in TABLE 1-3. TABLE 1-3 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.
System Console OpenBoot Configuration Variable Settings The server’s system console is directed to the serial management and network management ports (SER MGT and NET MGT) by default. Certain OpenBoot configuration variables control from where system console input is taken and to where its output is directed. The table below shows how to set these variables in order to use the serial management and network management ports.
24 SPARC Enterprise T1000 Server Administration Guide • April 2007
CHAPTER 2 Managing RAS Features and System Firmware This chapter describes how to manage reliability, availability, and serviceability (RAS) features and system firmware, including Advanced Lights Out Manager (ALOM) system controller, and automatic system recovery (ASR). In addition, this chapter describes how to unconfigure and reconfigure a device manually, and introduces multipathing software.
After you log in to your ALOM account, the system controller command prompt (sc>) appears, and you can enter system controller commands. If the command you want to use has multiple options, you can either enter the options individually or grouped together, as shown in the following example. The commands shown in the following example are identical. sc> poweroff -f -y sc> poweroff -fy Logging In To The System Controller All environmental monitoring and control is handled by the system controller.
▼ To Log In To ALOM CMT 1. If you are logged in to the system console, type #. (Hash-Period) to get to the sc> prompt. Press the Hash key, followed by the Period key. Then press the Return key. 2. At the ALOM CMT login prompt, enter the login name and press Return. The default login name is admin. Advanced Lights Out Manager CMT v1.3 Please login: admin 3. At the password prompt, enter the password and press Return to get to the sc> prompt.
2. Use the showenvironment command to display a snapshot of the server’s environmental status. The information this command can display includes temperature, power supply status, front panel LED status, and so on. Note – Some environmental information might not be available when the server is in Standby mode. Note – You do not need system controller user permissions to use this command.
The LEDs have assigned meanings, described in TABLE 2-2. TABLE 2-2 LED Behaviors With Assigned Meanings Color Behavior Definition White Off Steady State Fast Blink 4 Hz repeating sequence, equal intervals On and Off. Off Steady State Steady On Steady State Off Steady State Steady On Steady State Off Steady State Standby Blink Repeating sequence consisting of a brief (0.1 sec.) on flash followed by a long off period (2.9 sec.
Controlling the Locator LED You control the Locator LED from the sc> prompt or by the Locator button on the front of the chassis.
Automatic system recovery functionality enables the system to resume operation after experiencing certain nonfatal hardware faults or failures. When ASR is enabled, the system’s firmware diagnostics automatically detect failed hardware components. An autoconfiguring capability designed into the system firmware enables the system to unconfigure failed components and to restore system operation.
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: ■ Ethernet interface failure. ■ Serial interface failure. ■ PCI-Express card failure.
The standard system reset protocol bypasses POST completely unless the virtual keyswitch or ALOM CMT variables are set as follows: TABLE 2-3 Virtual Keyswitch Setting for Reset Scenario Keyswitch Value virtual keyswitch diag TABLE 2-4 ALOM CMT Variable Settings for Reset Scenario Variable Value Default diag-mode normal or service normal diag-level min or max max diag-trigger power-on-reset error-reset power-on-reset Therefore, ASR is enabled by default.
▼ To Enable Automatic System Recovery 1. At the sc> prompt, type: sc> setsc diag-mode normal sc> setsc diag-level max sc> setsc diag-trigger power-on-reset 2. At the ok prompt, type: ok setenv auto-boot true ok setenv auto-boot-on-error? true Note – For more information about OpenBoot configuration variables, refer to the SPARC Enterprise T1000 Server Service Manual. 3.
Note – To store parameter changes, you can also power cycle the system using the front panel Power button. After you disable the automatic system recovery (ASR) feature, it is not activated again until you re-enable it. Obtaining Automatic System Recovery Information Use the following procedure to retrieve information about the status of system components affected by automatic system recovery (ASR).
▼ To Unconfigure a Device Manually ● At the sc> prompt, type: sc> disablecomponent asr-key The asr-key is one of the device identifiers from TABLE 2-5 Note – The device identifiers are not case-sensitive. You can type them as uppercase or lowercase characters.
Displaying System Fault Information ALOM CMT software enables you to display current valid system faults. The showfaults command displays the fault ID, the faulted FRU device, and the fault message to standard output. The showfaults command also displays POST results. ▼ To Display System Fault Information ● Type showfaults For example: sc> showfaults ID FRU 0 FT0.F2 Fault SYS_FAN at FT0.F2 has FAILED.
■ Solaris IP Network Multipathing software provides multipathing and load-balancing capabilities for IP network interfaces. ■ VERITAS Volume Manager (VVM) software includes a feature called Dynamic Multipathing (DMP), which provides disk multipathing as well as disk load balancing to optimize I/O throughput.
CHAPTER 3 Managing Disk Volumes This document describes redundant array of independent disks (RAID) concepts, and how to configure and manage RAID disk volumes using the server’s on-board serial attached SCSI (SAS) disk controller.
The on-board disk controller of the server provides for the creation of one hardware RAID volume. The controller supports either a two-disk RAID 1 (integrated mirror, or IM) volume or a two-disk RAID 0 (integrated stripe, or IS) volume. Note – Due to the volume initialization that occurs on the disk controller when a new volume is created, properties of the volume such as geometry and size are unknown.
FIGURE 3-1 Graphical Representation of Disk Striping Caution – There is no data redundancy in an IS volume configuration. Thus, if a single disk fails, the entire volume fails, and all data is lost. If an IS volume is manually deleted, all data on the volume is lost. IS volumes are likely to provide better performance than IM volumes or single disks.
Caution – Creating RAID volumes using the on-board disk controller destroys all data on the member disks. The disk controller’s volume initialization procedure reserves a portion of each physical disk for metadata and other internal information used by the controller. Once the volume initialization is complete, you can configure the volume and label it using format(1M). You can then use the volume in the Solaris Operating System.
You can use TABLE 3-1 to associate internal disk slot numbers with the logical and physical device names for each hard drive.
3. Verify that the member disks are available and that there is not a volume already created. using the raidctl command: The server’s on-board SAS controller can configure one RAID volume. Prior to volume creation, ensure that the member disks are available and that there is not a volume already created. # raidctl No RAID volumes found. See “Physical Disk Slot Numbers, Physical Device Names, and Logical Device Names for Non-RAID Disks” on page 42. The preceding example indicates that no RAID volume exists.
4. Create the RAID 1 volume: # raidctl -c primary secondary The creation of the RAID volume is interactive, by default. For example: # raidctl -c c0t0d0 c0t1d0 Creating RAID volume c0t0d0 will destroy all data on member disks, proceed (yes/no)? yes Volume ’c0t0d0’ created # As an alternative, you can use the –f option to force the creation if you are sure of the member disks, and sure that the data on both member disks can be lost.
The Disk Status column displays the status of each physical disk. Each member disk might be OK, indicating that it is online and functioning properly, or it might be FAILED, MISSING, or otherwise OFFLINE, indicating that the disk has hardware or configuration issues that need to be addressed.
6. Relabel the disk using the format utility. # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@7c0/pci@0/pci@8/scsi@2/sd@0,0 Specify disk (enter its number): 0 selecting c0t0d0 [disk formatted] FORMAT MENU: ... format> type AVAILABLE DRIVE TYPES: 0. Auto configure ... 19. SUN72G 20. other Specify disk type (enter its number)[19]: 0 c0t0d0: configured with capacity of 68.
Note – The logical device names might appear differently on your system, depending on the number and type of add-on disk controllers installed. ▼ To Create a Hardware Striped Volume 1. Determine which disk is the default boot device. From the OpenBoot ok prompt, type the printenv command, and if necessary the devalias command, to identify the default boot device. For example: ok printenv boot-device boot-device = disk ok devalias disk disk /pci@7c0/pci@0/pci@8/scsi@2/disk@0,0 2.
4. Create the RAID 0 volume. # raidctl -c –r 0 disk1 disk2 The creation of the RAID volume is interactive, by default. For example: # raidctl -c -r 0 c0t0d0 c0t1d0 Creating RAID volume c0t1d0 will destroy all data on member disks, proceed (yes/no)? yes Volume ’c0t0d0’ created # When you create a RAID striped volume, the other member drives (in this case, c0t1d0) disappear from the Solaris device tree.
6. Relabel the disks using the format utility. # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@7c0/pci@0/pci@8/scsi@2/sd@0,0 Specify disk (enter its number): 0 selecting c0t0d0 [disk formatted] FORMAT MENU: ... format> type AVAILABLE DRIVE TYPES: 0. Auto configure ... 19. SUN72G 20. other Specify disk type (enter its number)[19]: 0 c0t0d0: configured with capacity of 68.
▼ To Delete a Hardware RAID Volume 1. Verify which hard drive corresponds with which logical device name and physical device name. See “Disk Slot Numbers, Logical Device Names, and Physical Device Names” on page 43. 2. Determine the name of the RAID volume. # raidctl RAID Volume RAID RAID Disk Volume Type Status Disk Status -----------------------------------------------------c0t0d0 IM OK c0t0d0 OK c0t1d0 OK In this example, the RAID volume is c0t1d0.
3. Delete the volume. # raidctl -d volume For example: # raidctl -d c0t0d0 In the event that the RAID volume is an IS volume, the deletion of the RAID volume is interactive, for example: # raidctl -d c0t0d0 Are you sure you want to delete RAID-1 Volume c0t0d0(yes/no)? yes /pci@7c0/pci@0/pci@8/scsi@2 (mpt0): Volume 0 deleted. /pci@7c0/pci@0/pci@8/scsi@2 (mpt0): Physical disk 0 deleted. /pci@7c0/pci@0/pci@8/scsi@2 (mpt0): Physical disk 1 deleted. Volume ’c0t0d0’ deleted.
5. To re-label all of the member disks of the volume using the format command, select the disk name that represents the RAID volume that you have configured. In this example, c0t0d0 is the logical name of the volume. # format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@7c0/pci@0/pci@8/scsi@2/sd@0,0 1.
6. Type the type command at the format> prompt, then select 0 (zero) to auto configure the volume. For example: format> type AVAILABLE DRIVE TYPES: 0. Auto configure 1. Quantum ProDrive 80S 2. Quantum ProDrive 105S 3. CDC Wren IV 94171-344 4. SUN0104 5. SUN0207 6. SUN0327 7. SUN0340 8. SUN0424 9. SUN0535 10. SUN0669 11. SUN1.0G 12. SUN1.05 13. SUN1.3G 14. SUN2.1G 15. SUN2.9G 16. Zip 100 17. Zip 250 18. Peerless 10GB 19. LSILOGIC-LogicalVolume-3000 20.
9. Verify that the new labels have been written by printing the disk list using the disk command. format> disk AVAILABLE DISK SELECTIONS: 0. c0t0d0 /pci@7c0/pci@0/pci@8/scsi@2/sd@0,0 1. c0t1d0 /pci@7c0/pci@0/pci@8/scsi@2/sd@1,0 Specify disk (enter its number)[0]: 1 selecting c0t1d0 [disk formatted] Note that c0t1d0 now has a type indicating it is an LSILOGIC-LogicalVolume. 10.
56 SPARC Enterprise T1000 Server Administration Guide • April 2007
APPENDIX A OpenBoot Configuration Variables TABLE A-1 describes the OpenBoot firmware configuration variables stored in nonvolatile memory on the system. 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 (Continued) Variable Possible Values Default Value Description ttya-mode 9600,8,n,1,- 9600,8,n,1,- Serial management port (baud rate, bits, parity, stop, handshake). The serial management port only works at the default values. output-device virtualconsole, screen virtualconsole Power-on output device. input-device virtualconsole, keyboard virtualconsole Power-on input device.
TABLE A-1 OpenBoot Configuration Variables Stored on the System Configuration Card (Continued) Variable Possible Values Default Value Description diag-switch? true, false false If • If • error-reset-recovery boot, sync, none boot Command to execute following a system reset generated by an error. network-bootarguments [protocol, ] [key=value, ] none Arguments to be used by the PROM for network booting. Defaults to an empty string.
60 SPARC Enterprise T1000 Server Administration Guide • April 2007
Index Symbols C /etc/remote file, 11 modifying, 12 Cisco L2511 terminal server, connecting, 9 command prompts, explained, 16 communicating with the system about, 1 options, table, 2 console (sc> command), 20 console configuration, connection alternatives explained, 16 console -f (sc> command), 17 A Advanced Lights Out Manager (ALOM) commands, See sc> prompt escape sequence (#.
environmental information, viewing, 27 error handling, summary, 32 escape sequence (#.
RAID 0 (striping), 40 RAID 1 (mirroring), 41 raidctl (Solaris command), 43 to 52 reset manual system, 20, 22 scenarios, 32 reset (sc> command), 20 run levels explained, 18 ok prompt and, 18 S sc> commands break, 20 console, 20 console -f, 17 poweroff, 20 poweron, 20 reset, 20 setlocator, 30 setsc, 8 showlocator, 30 shownetwork, 8 sc> prompt about, 16, 25 accessing from network management port, 18 accessing from serial management port, 18 multiple sessions, 17 system console escape sequence (#.
64 SPARC Enterprise T1000 Server Administration Guide • April 2007
Seitenanzahl: 84 T1admin_u.ti1 Seite 1 Mittwoch, 6. Dezember 2006 11:12 11 Administration Guide SPARC® Enterprise T1000 Server Herausgegeben von / Published by Fujitsu Siemens Computers GmbH Bestell-Nr./ Order No.
