Sun Fire Entry-Level Midrange System Administration Guide

This chapter describes how to power on your system using the System Controller command line interface (LOM prompt), how to set up the System Controller using the setupnetwork command, and how to boot the Solaris operating environment.

This chapter contains the following topics:

• Installing and Cabling Hardware
• Using the Power (On/Standby) Switch
• Powering On and Off
• Setting Up the System
• Installing and Booting the Solaris Operating Environment
• Resetting the System

The list below summarizes the major steps you must perform to power on and set up the system, which are explained using step-by-step procedures.

1. Install and cable the hardware.

2. Apply external power to the hardware.

3. Set the date and time for the system.

4. Set the password for the System Controller.

5. Set up system-specific parameters with the setupnetwork command.

6. Power on all hardware with the poweron command.

7. If the Solaris operating environment is not pre-installed, install it.

8. Boot the Solaris operating environment.

9. Install the Lights Out Management packages from the Solaris Supplementary CD.

---

Installing and Cabling Hardware

1. Connect a terminal to the System Controller board serial port.

Refer to FIGURE 1-1.

2. Set up the terminal to use the same baud rate as the serial port.

The serial port settings of the System Controller board are:

• 9600 8N1:
• 9600 baud
• 8 data bits
• No parity
• 1 stop bit

More details can be found in the Sun Fire E2900 System Installation Guide or Sun Fire V1280/Netra 1280 Systems Installation Guide, as appropriate.

---

Using the Power (On/Standby) Switch

Caution - The power switch is not an On/Off switch, it is an On/Standby switch. It does not isolate the equipment.

The power (On/Standby) switch of the Sun Fire entry-level midrange systems system is a rocker type, momentary action switch. It controls only low voltage signals and no high voltage circuits pass through it.

 FIGURE 2-1 Power (On/Standby) Switch

The symbols on the switch are:

On On symbol.

• Press and release to power on the server. This is the equivalent of the LOM poweron command.

Standby Standby symbol.

• Press for less than four seconds to initiate an orderly shutdown of the system into Standby mode. This is equivalent to issuing the shutdown command at the lom> prompt. This is the method to use under normal operation.
• Press and hold down for more than four seconds to perform a system power down to standby mode. This is equivalent to issuing the poweroff command at the lom> prompt. This process is not interruptible. You should ensure that Solaris is cleanly shut down before powering a system to standby mode otherwise data is at risk of being lost. The recommended method of powering down to standby is by using the shutdown command at the LOM prompt.

Use the LOM setupsc command to prevent accidental operation of the On/Standby switch.

---

Powering On and Off

Powering On

1. Ensure all power cables are connected and external circuit breakers are switched on.

2. The system will enter Standby mode.

The only indicator LEDs to be illuminated on the system indicator board are the Source A and Source B indicators. The IB_SSC assembly Active LED will also be illuminated, but not visible from the front of the system.

Powering the system on from Standby mode can be achieved in either of two ways:

• Operating the On/Standby switch
• Sending the poweron command via the LOM port.

If the auto-boot? variable has been set in the OBP, the system will automatically boot into the Solaris operating environment.

Using the On/Standby Switch

1. Check that power is applied to the system and that it is correctly in Standby mode.

The only indicator LEDs to be illuminated on the system indicator board are the Source A and Source B indicators. The IB_SSC assembly Active LED will also be illuminated, but not visible from the front of the system.

2. Momentarily press the On/Standby switch to the right.

The system will power on completely. The System Active indicator will be illuminated in addition to the Source A and Source B indicators. The system will execute the power on self tests (POST).

Using the LOM poweron Command

At the lom> prompt, type:

lom>poweron

The System Controller will first power on all the power supplies, followed by the fan tray. Finally the System Controller will power on the system boards. If the value of the OpenBoot PROM variable auto-boot? is true then the system will also boot the Solaris operating environment.

Individual modules can also be powered on using the poweron command. For further details see the Sun Fire Entry-Level Midrange System Controller Command Reference Manual.

The System Active indicator will be illuminated in addition to the Source A and Source B indicators. The system will execute the power on self tests (POST).

Refer to the Sun Fire Entry-Level Midrange System Controller Command Reference Manual for a full description of the poweron command.

Bringing the System to Standby Mode

This can be achieved in one of five ways:

• Using the UNIX shutdown command.
• Sending the shutdown command via the LOM port
• Sending the shutdown command using the On/Standby switch
• Sending the poweroff command via the LOM port
• Sending the poweroff command using the On/Standby switch

Using the Solaris shutdown Command

At the system prompt, type:

# shutdown -i5

The system will power off to standby mode. The only indicator LEDs to be illuminated on the system indicator board are the Source A and Source B indicators. The IB_SSC assembly Active LED will also be illuminated, but not visible from the front of the system.

Sending the LOM shutdown Command

Use the LOM shutdown command to perform a clean shutdown of Solaris followed by a power down of all modules and system chassis to standby mode.

At the lom> prompt, type:

lom>shutdown

After Solaris has been stopped, the system will power off to standby mode. The only indicator LEDs to be illuminated on the system indicator board are the Source A and Source B indicators. The IB_SSC assembly Active LED will also be illuminated, but not visible from the front of the system.

Refer to the Sun Fire Entry-Level Midrange System Controller Command Reference Manual for a full description of the LOM shutdown command.

Sending the shutdown Command Using the On/Standby Switch

Momentarily press the system On/Standby switch to the left.

This initiates an orderly shutdown of the system into Standby mode. This is equivalent to issuing the shutdown command at the lom> prompt.

Sending the LOM poweroff Command

Use the poweroff command when you wish to power down all modules and system chassis to standby mode.

At the lom> prompt, type:

lom>poweroff

This will abruptly terminate Solaris.

Do you want to continue? [no] 

Only answer yes if you wish to forcibly power down the system regardless of the state of Solaris. Under normal operation you should use the shutdown command.

Type y to continue or press Return to cancel the command.

The system will power off to standby mode. The only indicator LEDs to be illuminated on the system indicator board are the Source A and Source B indicators. The IB_SSC assembly Active LED will also be illuminated, but not visible from the front of the system.

Refer to the Sun Fire Entry-Level Midrange System Controller Command Reference Manual for a full description of the poweroff command.

Sending the poweroff Command Using the On/Standby Switch

Only use this method if you wish to forcibly power down the system regardless of the state of Solaris. Under normal operation you should send the shutdown command either from the lom> prompt or from the On/Standby Switch (see Sending the shutdown Command Using the On/Standby Switch).

Press the On/Standby switch to the left and hold it for at least four seconds.

The system will power down to standby mode. The only indicator LEDs to be illuminated on the system indicator board are the Source A and Source B indicators. The IB_SSC assembly Active LED will also be illuminated, but not visible from the front of the system.

After Powering On

You will see the following output on the System Controller serial port connection:

Hardware Reset...

@(#) SYSTEM CONTROLLER(SC) POST 23 2002/03/22 18:03

PSR = 0x044010e5

PCR = 0x04004000

Basic sanity checks done.

Skipping POST ...

ERI Device Present

Getting MAC address for SSC1

Using SCC MAC address

MAC address is 0:3:xx:xx:xx:xx

Hostname: some_name

Address: xxx.xxx.xxx.xxx

Netmask: 255.255.255.0

Attached TCP/IP interface to eri unit 0

Attaching interface lo0...done

Gateway: xxx.xxx.xxx.xxx

interrupt: 100 Mbps half duplex link up

          Copyright 2001-2002 Sun Microsystems, Inc.  All rights reserved.

          Use is subject to license terms.

Lights Out Management Firmware

RTOS version: 23

ScApp version: 5.13.0007 LW8_build0.7

SC POST diag level: off

The date is Friday, July 19, 2002, 3:48:50 PM BST.

Fri Jul 19 15:48:51 some_name lom: Boot: ScApp 5.13.0007, RTOS 23

Fri Jul 19 15:48:54 some_name lom: SBBC Reset Reason(s): Power On Reset 

Fri Jul 19 15:48:54 some_name lom: Initializing the SC SRAM

Fri Jul 19 15:48:59 some_name lom: Caching ID information

Fri Jul 19 15:49:00 some_name lom: Clock Source: 75MHz

Fri Jul 19 15:49:02 some_name lom: /N0/PS0: Status is OK

Fri Jul 19 15:49:03 some_name lom: /N0/PS1: Status is OK

Fri Jul 19 15:49:03 some_name lom: Chassis is in single partition mode.

Fri Jul 19 15:49:05 some_name lom: Cold boot detected: recovering active domains

Fri Jul 19 15:49:06 some_name lom: NOTICE: /N0/FT0 is powered off

Connected.

lom>

---

Setting Up the System

After powering on, you must set up your system using the System Controller setdate and setupnetwork commands described in this chapter.

This section contains the following topics:

• To Set the Date and Time
• To Configure Network Parameters
• To Install and Boot the Solaris Operating Environment

Set the date, time, and time zone for the system using the setdate command at the LOM prompt:

The following example shows setting the time zone to Pacific Standard Time (PST) using the offset from Greenwich mean time (GMT), date, and time to Thursday, April 20, 2000 at 18 hours 15 minutes and 10 seconds.

lom>setdate -t GMT-8 042018152000.10 

If Solaris is running, use the Solaris date command instead.

For more information on the setdate command, refer to the Sun Fire Entry-Level Midrange System Controller Command Reference Manual.

1. At the LOM prompt, type the System Controller password command.

2. At the Enter new password: prompt, type in your password.

3. At the Enter new password again: prompt, re-type in your password.

lom>password

Enter new password:

Enter new password again:

lom>

In the event that your password has been lost or forgotten, contact SunService for advice.

The Sun Fire entry-level midrange systems system can be administered from the System Controller LOM prompt and from Solaris. There are two ways to access the LOM/Console connection.

• Through the System Controller Serial port connection.
• Through a Telnet (network) connection using the 10/100 Ethernet port.

At the LOM prompt type setupnetwork:

lom>setupnetwork 

See the Sun Fire Entry-Level Midrange System Controller Command Reference Manual for full details of the setupnetwork command. CODE EXAMPLE 2-2 shows an example of the setupnetwork command.

lom>setupnetwork

Network Configuration

---------------------

Is the system controller on a network? [yes]: 

Use DHCP or static network settings? [static]: 

Hostname [hostname-sc]: 

IP Address [123.xxx.xxx.xxx]: 

Netmask [255.255.255.0]: 

Gateway [123.xxx.xxx.xxx]: 

DNS Domain [xxx.somewhere.com]: 

Primary DNS Server [123.xxx.xxx.xxx]: 

Secondary DNS Server [123.xxx.xxx.xxx]: 

Connection type (telnet, none)[none]: 

lom>

Use the information in CODE EXAMPLE 2-2 as a guide for the information you need to enter for each parameter value entry.

---

Installing and Booting the Solaris Operating Environment

To use LOM commands you must install the Lights Out Management 2.0 packages (SUNWlomu, SUNWlomr and SUNWlomm) from the Solaris Supplementary CD.

1. Access the LOM prompt.

See Chapter 3.

2. Power on the system. Type poweron.

Depending on the setting of the OpenBoot PROM auto-boot? parameter the system will attempt to boot Solaris or will remain at the OpenBoot PROM ok prompt. The default setting is true which will attempt to initiate a Solaris boot. If the setting of auto-boot? is false or there is no bootable Solaris image installed then you will get the OpenBoot PROM ok prompt.

lom>poweron

<POST messages displayed here . . . >

. . .

. . .

ok 

3. If necessary, install the Solaris operating environment.

Refer to your installation documentation, which is available with your Solaris operating environment release.

4. At the ok prompt, boot the Solaris operating environment by typing the OpenBoot PROM boot command:

ok boot [device]

For the optional device parameter, see the OpenBoot PROM devalias command, which displays the predefined aliases.

After the Solaris operating environment is booted, the login: prompt is displayed.

login:

The three LOM packages needed on a Sun Fire entry-level midrange systems are SUNWlomu (LOMlite Utilities (usr)), SUNWlomm (LOMlite manual pages), and SUNWlomr (LOM drivers). These are available on the Solaris Supplementary CD.

As root, type:

# pkgadd -d . SUNWlomr

Processing package instance <SUNWlomr> from </var/tmp>

LOMlite driver (root)

(sparc) 2.0,REV=2000.08.22.14.14

Copyright 2000 Sun Microsystems, Inc. All rights reserved.

## Executing checkinstall script.

Using </> as the package base directory.

## Processing package information.

## Processing system information.

   9 package pathnames are already properly installed.

## Verifying package dependencies.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs.

This package contains scripts which will be executed with super-user

permission during the process of installing this package.

Do you want to continue with the installation of <SUNWlomr> [y,n,?] y

Installing LOMlite driver (root) as <SUNWlomr>

## Installing part 1 of 1.

20 blocks

i.drivers (INFO): Starting

i.drivers (INFO): Installing /var/tmp/SUNWlomr/reloc/platform/sun4u/kernel/drv/lom

i.drivers (INFO): Installing /var/tmp/SUNWlomr/reloc/platform/sun4u/kernel/drv/lomp

i.drivers (INFO): Installing /var/tmp/SUNWlomr/reloc/platform/sun4u/kernel/drv/sparcv9/lom

i.drivers (INFO): Installing /var/tmp/SUNWlomr/reloc/platform/sun4u/kernel/drv/sparcv9/lomp

i.drivers (INFO): Installing /var/tmp/SUNWlomr/reloc/platform/sun4u/kernel/drv/sparcv9/lomv

i.drivers (INFO): Identified drivers 'lom lomp lomv'

i.drivers (INFO): Cleaning up old driver 'lom'...

Cleaning up old devlink entry  'type=ddi_pseudo;name=SUNW,lom   lom'

i.drivers (INFO): Cleaning up old driver 'lomp'...

Cleaning up old devlink entry  'type=ddi_pseudo;name=lomp       lomp'

i.drivers (INFO): Cleaning up old driver 'lomv'...

Cleaning up old devlink entry  'type=ddi_pseudo;name=SUNW,lomv  \M0

type=ddi_pseudo;name=lomv       \M0'

i.drivers (INFO): Cleaning up old driver 'lomh'...

Cleaning up old devlink entry  'type=ddi_pseudo;name=SUNW,lomh  lom'

i.drivers (INFO): Adding driver 'lomp'...

  driver  = 'lomp'

  aliases = ''

  link    = 'lomp'

  spec    = 'lomp'

Adding devlink entry 'type=ddi_pseudo;name=lomp lomp'

adding driver with aliases '' perm '* 0644 root sys'

devfsadm: driver failed to attach: lomp

Warning: Driver (lomp) successfully added to system but failed to attach

i.drivers (INFO): Adding driver 'lomv'...

  driver  = 'lomv'

  aliases = 'SUNW,lomv'

  link    = 'SUNW,lomv lomv'

  spec    = '\M0'

Adding devlink entry 'type=ddi_pseudo;name=SUNW,lomv    \M0'

Adding devlink entry 'type=ddi_pseudo;name=lomv \M0'

adding driver with aliases 'SUNW,lomv' perm '* 0644 root sys'

devfsadm: driver failed to attach: lomv

Warning: Driver (lomv) successfully added to system but failed to attach

i.drivers (INFO): Adding driver 'lom'...

  driver  = 'lom'

  aliases = 'SUNW,lomh SUNW,lom'

  link    = 'SUNW,lomh SUNW,lom'

  spec    = 'lom'

Adding devlink entry 'type=ddi_pseudo;name=SUNW,lomh    lom'

Adding devlink entry 'type=ddi_pseudo;name=SUNW,lom     lom'

adding driver with aliases 'SUNW,lomh SUNW,lom' perm '* 0644 root sys'

devfsadm: driver failed to attach: lom

Warning: Driver (lom) successfully added to system but failed to attach

i.drivers (SUCCESS): Finished

[ verifying class <drivers> ]

Installation of <SUNWlomr> was successful.

# 

As root, type:

# pkgadd -d . SUNWlomu

Processing package instance <SUNWlomu> from </cdrrom/suppcd_s28u7_multi_s28u7_supp.08al1/Lights_Out_Management_2.0/Product>

LOMlite Utilities (usr)

(sparc) 2.0,REV=2000.08.22.14.14

Copyright 2000 Sun Microsystems, Inc. All rights reserved.

Using </> as the package base directory.

## Processing package information.

## Processing system information.

   4 package pathnames are already properly installed.

## Verifying package dependencies.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs.

Installing LOMlite Utilities (usr) as <SUNWlomu>

## Installing part 1 of 1.

1432 blocks

Installation of <SUNWlomu> was successful.

# 

As root, type:

# pkgadd -d . SUNWlomm

Processing package instance <SUNWlomm> from 

</cdrom/suppcd_s28u7_multi_s28u7_supp.08al1/Lights_Out_Management_2.0/Product>

LOMlite manual pages

(sparc) 2.0,REV=2000.08.22.14.14

Copyright 2000 Sun Microsystems, Inc. All rights reserved.

Using </> as the package base directory.

## Processing package information.

## Processing system information.

   5 package pathnames are already properly installed.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs.

Installing LOMlite manual pages as <SUNWlomm>

## Installing part 1 of 1.

71 blocks

Installation of <SUNWlomm> was successful.

---

Resetting the System

The reset command is used to reset the system in the event of a system hang or hardware problem. If Solaris is running then you will be prompted to confirm this action:

lom>reset

This will abruptly terminate Solaris.

Do you want to continue? [no] y

NOTICE: XIR on CPU 3

By default, reset uses XIR (externally initiated reset) to reset the CPU processors in the system. The externally initiated reset forces control of the processors into the OpenBoot PROM and begins the OpenBoot PROM's error reset recovery actions. The error reset recovery actions preserve most of the Solaris states to allow the collection of data need for debugging the hardware and software, including a Solaris operating environment core file. After saving the debug information, if the value of the OpenBoot PROM variable auto-boot? is true, the system will boot Solaris. The OpenBoot PROM's error reset recovery actions are controlled by setting the OpenBoot PROM error-reset-recovery configuration variable.

reset is prevented in standby, and the message reset not allowed, domain A keyswitch is set to off is displayed.

The reset -a command is equivalent to the OpenBoot PROM reset-all word.

Use the resetsc command to reset the System Controller. This can be used in the event of a hardware or software problem causing the System Controller Application to malfunction.

lom>resetsc

Are you sure you want to reboot the system controller now? [no] y

This will cause the System Controller to reset, execute the System Controller POST level specified using the setupsc command and restart the LOM software.

Sun Fire Entry-Level Midrange System Administration Guide

817-5233-10

Copyright © 2004, Sun Microsystems, Inc. All rights reserved.