Sun Serial Port Configuration
Sun StorEdge 3000 Family Installation, Operation, and Service Manual A P P E N D I X F Configuring a Microsoft Windows Server This appendix provides platform-specific host installation and configuration information to use when you connect a Sun StorEdge 3510 FC array or a Sun StorEdge 3511 SATA array to a host running the Windows 2000 Server, Windows 2000 Advanced Server, Windows 2003 Server, or Windows 2003 Advanced Server operating system. For convenience, these platforms will be referred to collectively in this document as 'Microsoft Windows Server.' The Sun StorEdge 3510 FC array and Sun StorEdge 3511 SATA array support Windows 2000 Server and Windows 2000 Advanced Server, Service Pack 3 or greater, in dual-path configurations using Sun StorEdge Traffic Manager 3.0 failover drivers for Windows 2000. If you are going to use dual-path instead of single-path configuration, refer to the Sun StorEdge Traffic Manager Software Installation Guide for Microsoft Windows. It provides detailed instructions about setting up the device driver on the server and additional information about configuring your Windows 2000 Server or Advanced Server. Customers interested in Sun StorEdge Traffic Manager for multiplatform support should contact Sun Sales or visit: For more information about multiplatform support, refer to: The information in this appendix covers the following steps:. F.1Setting Up the Serial Port Connection The RAID controller can be configured by means of a host system running a VT100 terminal emulation program such as HyperTerminal in Microsoft Windows.
Note - You can also monitor and configure a RAID array over an IP network using the RAID firmware or Sun StorEdge Configuration Service after you assign an IP address to the array. For details, see, and refer to the Sun StorEdge 3000 Family Configuration Service User's Guide. 1.Use a null modem serial cable to connect the COM port of the RAID array to an unused serial port on your host system. A null modem cable has serial signals swapped for connecting to a standard serial interface. Note - A DB9-to-DB25 serial cable adapter is included in your package contents for connecting the serial cable to a DB25 serial port on your host if you do not have a DB9 serial port. 2.Power up the array.
3.On the server, choose Start Programs Accessories Communications HyperTerminal. 4.Type a name and choose an icon for the connection. 5.In the Connect To window, select the COM port from the 'Connect using:' drop-down menu for that array. 7.In the Properties window, set the serial port parameters using the drop-down menus.
Set serial port parameters to:. 38,400 baud. 8 data bits. 1 stop bit. No parity 8.To save the connection and its settings, choose File Save. The connection file name is connection-name where connection-name is the name you gave this HyperTerminal connection in.
9.To make a connection shortcut on your desktop: a.Choose Start Find For Files or Folders. Enter connection-name and click the Search button. Highlight and right-click on the file name in the Search Results window. Choose Create Shortcut and click Yes. You are now ready to configure your array. F.2Accessing the Firmware Application From a Microsoft Windows Server To access the array from a Microsoft Windows Server through a serial port, use the HyperTerminal connection you configured in or install a VT100 terminal emulation program and use the parameters described there.
To access the array through an Ethernet connection, follow the procedures in. To access the command prompt described there from a Microsoft Windows Server, perform this step: Choose Programs Accessories Command Prompt. F.3Enabling a Microsoft Windows Server to Recognize New Devices and LUNs Before beginning this procedure, make sure that you are using a supported FC host bus adapter (HBA) such as a QLogic QLA2310 or QLogic QLA2342. Refer to the release notes for your array for current information about which HBAs are supported.
Also make sure that you are using a supported driver for your HBA. For the QLA2310 or QLA2342, use driver version 8.1.5.13 or later. Note - When the Microsoft Windows operating system recognizes the Sun StorEdge 3510 FC array or Sun StorEdge 3511 SATA array's SCSI Enclosure Services (SES) processor and identifies it as a Sun StorEdge 3510 FC Enclosure or Sun StorEdge 3511 SATA Enclosure, it might prompt you to supply a driver. This is standard plug-and-play behavior when unknown devices are encountered, but no device driver is necessary.
If you see this prompt, simply click Cancel. If you have multiple arrays, you might see this prompt more than once. Each time you see this prompt, click Cancel. 1.Boot your system and verify that the HBA basic input/output system (BIOS) recognizes your new FC device. Note - While your system is starting up, you should see your new Fibre Channel devices. 2.If a Found New Hardware Wizard is displayed, click Cancel.
You are now ready to partition and format your new devices. 3.Open the Disk Management folder. A.Right-click on the My Computer icon to display a pop-up menu. Choose Manage. Select the Disk Management folder. If a Write Signature and Upgrade Disk Wizard is displayed, click Cancel.
A 'Connecting to Logical Disk Manager Server' status message is displayed. 4.Select your new device when it is displayed. 5.Right-click in the Unallocated partition of your device to display a pop-up menu. 6.Choose Create Partition from the pop-up menu. The Create Partition wizard is displayed.
7.Select Primary partition and click Next. 8.Specify the amount of disk space to use or accept the default value, and click Next. 9.Assign a drive letter, if desired, and click Next. 10.Select 'Format this partition with the following settings.' A.Specify NTFS as the 'File system to use.' Make sure the 'Perform a Quick Format' checkbox is selected.
A confirmation dialog box displays the settings you have specified. 11.Click Finish. The new partition is formatted and the formatted partition is identified as NTFS in the Computer Management window. 12.Repeat through for any other new partitions and devices you want to format. F.4Determining the Worldwide Name for Microsoft Windows Servers Before you can create host filters, you need to know the worldwide name (WWN) for the FC HBA that connects your host to your FC array. 1.Boot a specific host system and note the BIOS version and HBA card models connected to your host. 2.Access the HBA card's BIOS with the appropriate command ( Alt-Q or Ctrl-A are commonly used).
If the host has multiple HBA cards, select the card that is connected to the storage. 3.Scan the card to look for devices attached to it (usually with the Scan Fibre Devices or the Fibre Disk Utility).
The node name (or similar label) is the WWN. The following example shows the node name for a Qlogic card. ID Vendor Product Rev Node Name Port ID 0 Qlogic QLA22xx Adapter B 210000E08B02DE2F 0000EF Refer to the Sun StorEdge 3000 Family RAID Firmware User's Guide for more information about creating host filters.
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 the 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 (SER 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.
Lists these devices and where they are discussed in the document. TABLE 1-1 Ways of Communicating With the System Devices Available During Installation After Installation Further Information A terminal server attached to the serial management port (SER MGT). X X X X X X An alphanumeric terminal or similar device attached to the serial management port (SER MGT).
X X X X X X A Tip line attached to the serial management port (SER MGT). X X X X X X X An Ethernet line connected to the network management port (NET MGT). X A local graphics monitor (graphics accelerator card, graphics monitor, mouse, and keyboard). X X What the System Console Does The system console displays status and error messages generated by firmware-based tests during system startup. After those tests 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 service manual for your server.
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 to attach an input/output device to the system. Initially, you might have to configure that hardware, and load and configure appropriate software as well. You must also ensure that the system console is directed to the appropriate port on the Sun Fire T2000 server's back panel-generally, the one to which your hardware console device is attached (see ). You do this by setting the input-device and output-device OpenBoot configuration variables.
FIGURE 1-1 Directing the System Console Default System Console Connection Through the Serial Management and Network Management Ports On your server, the system console comes preconfigured to allow input and output only by means of the system controller. The system controller must be accessed either through the serial management port (SER MGT) or the network management port (NET MGT). By default, the network management port is configured to retrieve network configuration using DHCP and to allow connections using SSH.
You can modify the network management port configuration after connecting to ALOM CMT through either the serial or network management ports. 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 These constraints provide for secure access at the installation site. FIGURE 1-2 Rear I/O panel of the chassis-SC Serial Management Port Is The Default Console Connection Note - USB ports 2 and 3 are located on the front panel Using a Tip line enables you to use windowing and operating system features on the system making the connection to the Sun Fire T2000 server. The serial management port is not a general-purpose serial port. If you want to use a general-purpose serial port with your server - to connect a serial printer, for instance - use the standard 9-pin serial port on the back panel of the Sun Fire T2000. The Solaris OS sees this port as ttya. For instructions on accessing the system console through a terminal server, see.
For instructions on accessing the system console through an alphanumeric terminal, see. For instructions on accessing the system console through a Tip line, see. On your server, the system console comes preconfigured to allow input and output only by means of the system controller. The system controller must be accessed either through the serial management port (SER MGT) or the network management port (NET MGT). By default, the network management port is configured to retrieve network configuration using DHCP and to allow connections using SSH.
You can modify the network management port configuration after connecting to ALOM CMT through either the serial or network management ports. For more information, see. 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 a graphics card's port. For the following reasons, the best practice is to leave the console port in its default configuration:. In a default configuration, the serial management and network management ports enable you to open up to eight additional windows through which you can view, but not affect, system console activity. You cannot open these connections if the system console is redirected to a graphics card's port.
In a default configuration, the serial management and network management ports enable 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 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 a graphic card's port.
The omitted information could be important if you need to contact Sun customer service with a problem. You change the system console configuration by setting OpenBoot configuration variables. Accessing the System Console Through a Graphics Monitor The Sun Fire T2000 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 graphics accelerator card into a PCI slot, and attach a monitor, mouse, and keyboard to the appropriate front or rear USB 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. Note - POST diagnostics cannot display status and error messages to a local graphics monitor. Accessing the System Controller The following sections describe ways of accessing the system controller. Using the Serial Management Port This procedure assumes that the system console uses the serial management and network management ports (the default configuration). When you are accessing the system console using a device connected to the serial management port, you first access the ALOM system controller and its sc prompt. After connecting to the ALOM system controller, you can switch to the system console. For more information about the ALOM system controller card, refer to the ALOM CMT guide for your server.
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 the ALOM CMT guide for your server for instructions.
3.To connect to the system console, at the ALOM system controller command prompt, type. Characters are not echoed to the screen. For instructions on how to use the ALOM system controller, refer to the ALOM CMT guide for your server. 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 the system controller using the serial management port to reconfigure the network management port.
See Note - There is no default password when connecting to the system controller for the first time using the serial management port. When connecting to the system controller using the network management port for the first time, the default password is the last 8 digits of the Chassis Serial Number. The Chassis Serial Number can be found printed on the back of the server or in the printed system information sheet which shipped with your server. You must assign a password during initial system configuration. For more information, refer to your server installation guide and the ALOM CMT guide for your server. You can assign the network management port a static IP address or you can configure the port to obtain an IP address using the Dynamic Host Configuration Protocol (DHCP) from another server.
The network management port can be configured to accept connections from Telnet clients or SSH clients, but not both. 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 10/100 BASE-T port. The IP address assigned to the network management port is a unique IP address, separate from the main Sun Fire T2000 server IP address, and is dedicated for use only with the ALOM system controller.
To Activate the Network Management Port 1.Connect an Ethernet cable to the network management port. 2.Log in to the ALOM system controller through the serial management port.
For more information about connecting to the serial management port, see. 3.Type one of the following commands:. If your network uses static IP addresses, type. Sc shownetwork To connect through the network management port, use the telnet or ssh (based on the value you provided in Step 4) commands to the IP address you specified in 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 (SER MGT) of the Sun Fire T2000 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 Sun Fire T2000 server is a data terminal equipment (DTE) port. The pinouts for the serial management port correspond with the pinouts for the RJ-45 ports on the Serial Interface Breakout Cable supplied by Cisco for use with the Cisco AS2511-RJ terminal server. If you use a terminal server made by another manufacturer, check that the serial port pinouts of the Sun Fire T2000 server match those of the terminal server you plan to use. If the pinouts for the server serial ports correspond with the pinouts for the RJ-45 ports on the terminal server, you have two connection options:. Connect a serial interface breakout cable directly to the Sun Fire T2000 server.
Connect a serial interface breakout cable to a patch panel and use the straight-through patch cable (supplied by Sun) to connect the patch panel to the server. FIGURE 1-3 Patch Panel Connection Between a Terminal Server and a Sun Fire T2000 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 Sun Fire T2000 server serial management port to the corresponding pin in the terminal server's serial port.
Shows the crossovers that the cable must perform. TABLE 1-2 Pin Crossovers for Connecting to a Typical Terminal Server Sun Fire T2000 Serial Port (RJ-45 Connector) Pin Terminal Server Serial Port Pin Pin 1 (RTS) Pin 1 (CTS) Pin 2 (DTR) Pin 2 (DSR) Pin 3 (TXD) Pin 3 (RXD) Pin 4 (Signal Ground) Pin 4 (Signal Ground) Pin 5 (Signal Ground) Pin 5 (Signal Ground) Pin 6 (RXD) Pin 6 (TXD) Pin 7 (DSR /DCD) Pin 7 (DTR) Pin 8 (CTS) Pin 8 (RTS) 2.Open a terminal session on the connecting device, and type. % telnet 192.20.0 Accessing the System Console Through a Tip Connection Use this procedure to access the Sun Fire T2000 server system console by connecting the serial management port (SER MGT) to the serial port of another Sun system. FIGURE 1-4 Tip Connection Between a Sun Fire T2000 Server and Another Sun System 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 Sun Fire T2000 server.
Pinouts, part numbers, and other details about the serial cable and adapter are provided in the service manual for your server. 2.Ensure that the /etc/remote file on the Sun system contains an entry for hardwire. Most releases of Solaris OS software shipped since 1992 contain an /etc/remote file with the appropriate hardwire entry.
However, if the Sun system is running an older version of Solaris OS software, or if the /etc/remote file has been modified, you might need to edit it. See for details.
3.In a shell tool window on the Sun system, type. Connected The shell tool is now a Tip window directed to the Sun Fire T2000 server through the Sun system's serial port. This connection is established and maintained even when the Sun Fire T2000 server is completely powered off or just starting up. 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 Sun Fire T2000 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. Log in as superuser to the system console of a Sun system that you intend to use to establish a Tip connection to the Sun Fire T2000 server.
To Modify the /etc/remote File 1.Determine the release level of Solaris OS software installed on the Sun system. Hardwire::dv=/dev/ttyb:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D: 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 Sun Fire T2000 server system console. If you have redirected the system console to TTYB and want to change the system console settings back to use the serial management and network management ports, see.
Accessing the System Console Through an Alphanumeric Terminal Use this procedure when you are accessing the Sun Fire T2000 server system console by connecting the serial port of an alphanumeric terminal to the serial management port (SER MGT) of the Sun Fire T2000 server. To Access the System Console Through an Alphanumeric Terminal 1.Attach one end of the serial cable to the alphanumeric terminal's serial port. Use a null modem serial cable or an RJ-45 serial cable and null modem adapter. Connect this cable to the terminal's serial port connector. 2.Attach the opposite end of the serial cable to the serial management port on the Sun Fire T2000 server. 3.Connect the alphanumeric terminal's power cord to an AC outlet. 4.Set the alphanumeric terminal to receive:.
9600 baud. 8 bits.
No parity. 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 ALOM system controller, refer to the ALOM CMT guide for your server.
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 the following items:.
Supported PCI-based graphics frame buffer card and software driver. Monitor with appropriate resolution to support the frame buffer. Supported USB keyboard.
Supported USB mouse and mouse pad To Access the System Console Through a Local Graphics Monitor 1.Install the graphics card into an appropriate PCI slot. Installation must be performed by a qualified service provider. For further information, refer to the service manual for your server or contact your qualified service provider. 2.Attach the monitor's video cable to the graphics card's video port. Tighten the thumbscrews to secure the connection.
3.Connect the monitor's power cord to an AC outlet. 4.Connect the USB keyboard cable to one USB port and the USB mouse cable to the other USB port on the Sun Fire T2000 server back panel.
5.Get to the ok prompt. For more information, see. 6.Set OpenBoot configuration variables appropriately. From the existing system console, type.
Ok reset-all The system stores the parameter changes, and boots automatically when the OpenBoot configuration variable auto-boot? Is set to true (the default value). Note - To store parameter changes, you can also power cycle the system using the front panel Power button. You can issue system commands and view system messages using your local graphics monitor. Continue with your installation or diagnostic procedure, as needed. If you want to redirect the system console back to the serial management and network management ports, see. Switching Between the System Controller and the System Console The system controller features two management ports, labeled SER 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 (the default configuration), these ports provide access to both the system console and the ALOM CMT command-line interface (the ALOM system controller prompt), each on a separate channel (see ). FIGURE 1-5 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 CMT command-line interface or the system console. You can switch between the ALOM system controller prompt and the system console at any time, but you cannot access both at the same time from a single terminal window or shell tool. 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 system controller.
Note - If no text or prompt appears, it might be that no console messages were recently generated by the system. If this happens, pressing the terminal's Enter or Return key should produce a prompt. To reach the system console from the system controller,. Type the console command at the sc prompt. To reach the system controller from the system console,. Type the system controller escape sequence, By default, the escape sequence is #.
For more information about communicating with the system controller and system console, see:. The ALOM CMT guide for your server. ALOM CMT sc Prompt The ALOM system controller runs independently of the server and regardless of system power state. When you connect your 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 Sun Fire T2000 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. 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 and you issue an administrative command, the controller forces you to create a password (for the default username: admin) 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.
For more information, see the following: Access Through Multiple Controller Sessions Up to nine ALOM CMT sessions can be active concurrently, one session through the serial management port and up to eight 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: Any additional ALOM CMT 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 ALOM CMT guide for your server.
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 CMT escape sequence ( #.). You can log in directly to the system controller from a device connected to the serial management port. You can log in directly to the system controller using a connection through the network management port. OpenBoot ok Prompt A Sun Fire T2000 server with the Solaris OS installed operates at different run levels. For a full description of run levels, refer to the Solaris system administration documentation. Most of the time, you operate a Sun Fire T2000 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. When a Sun Fire T2000 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, before the operating system is installed the system comes up under OpenBoot firmware control. When the auto-boot? OpenBoot configuration variable is set to false, the system boots to the ok prompt. When the operating system is halted, the system transitions to run level 0 in an orderly way. When the operating system crashes, the system reverts to OpenBoot firmware control.
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. When you deliberately place the system under firmware control in order to execute firmware-based commands. 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. For detailed instructions, see. 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 and console command pair. L1-A (Stop-A) keys or Break key. Manual system reset A discussion of each method follows.
For step-by-step instructions, see. Note - 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.
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 CMT break or console Command Typing break from the sc prompt forces a running Sun Fire T2000 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. Note - 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 Sun Fire T2000 server, press the Break key. Note - 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. Manual System Reset 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. 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.
Solaris Serial Port Configuration
Using these commands result 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 - Accessing the okprompt suspends the Solaris OS.
When you access the ok prompt from a functioning Sun Fire T2000 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 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.
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. 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. Caution - Obtaining the okprompt suspends all application and operating system software.
Usb Port Configuration
After you issue firmware commands and run firmware-based tests from the okprompt, the system might not be able to resume where it left off. If 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. To Obtain the ok Prompt 1.Decide which method you need to use to reach the ok prompt. See for details. 2.Follow the appropriate instructions in.
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. L1-A (Stop-A) keys or Break key. From a Sun keyboard connected directly to the Sun Fire T2000 server, press the Stop and A keys simultaneously.or-. From an alphanumeric terminal configured to access the system console, press the Break key. ALOM system controller break and console commands From the sc prompt, type the break command.
Then issue the console command, provided the operating system software is not running and the server is already under OpenBoot firmware control. Manual system reset From the sc prompt, type: sc bootmode bootscript='setenv auto-boot? False' Press Enter. Then type: sc reset. System Console OpenBoot Configuration Variable Settings The Sun Fire T2000 system console is directed to the serial management and network management ports (SER MGT and NET MGT) by default. However, you can redirect the system console to a local graphics monitor, keyboard, and mouse. You can also redirect the system console back to the serial management and network management ports.
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, or a local graphics monitor as the system console connection. TABLE 1-4 OpenBoot Configuration Variables That Affect the System Console OpenBoot Configuration Variable Name Setting for Sending System Console Output to: Serial and Network Management Ports Local Graphics Monitor/USB Keyboard and Mouse.
output-device virtual-console screen input-device virtual-console keyboard. POST output will still be directed to the serial management port, as POST has no mechanism to direct its output to a graphics monitor. The serial management port does not function as a standard serial connection. (If you want to connect a conventional serial device (such as a printer) to the system, you must connect it to ttya not the serial management port.) It is important to note that the sc prompt and POST messages are only available through the serial management port and network management port. Note that the ALOM system controller console command is ineffective when the system console is redirected to a local graphics monitor.
Serial Port Setup
In addition to the OpenBoot configuration variables described in, there are other variables that affect and determine system behavior. These variables are discussed in more detail in.