C H A P T E R 2 - Starting and Setting Up Sun Fire Entry-Level Midrange Systems

C H A P T E R 2

Starting and Setting Up Sun Fire Entry-Level Midrange Systems

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

This chapter contains the following topics:

Setting Up the Hardware

Using the Power On/Standby Switch

Powering On and Off

Setting Up the System

Installing and Booting the Solaris Operating System

Resetting the System

The major steps you must perform to power on and set up the system, are as follows:

1. Installing and cabling the hardware.

2. Applying external power to the hardware.

3. Setting the date and time for the system.

4. Setting the password for the SC.

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

6. Powering on all hardware with the poweron command.

7. If the Solaris Operating System is not pre-installed, installing it.

8. Booting the Solaris Operating System.

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

Setting Up the Hardware

To Install and Cable the Hardware

1. Connect a terminal to the System Controller board serial port (FIGURE 1-1).

2. Set up the terminal to use the same baud rate as the SC serial port (9600 8N1).

The serial port settings of the System Controller board are:

9600 baud

8 data bits

No parity

1 stop bit

You can find more details in the Sun Fire E2900 System Installation Guide or the Sun Fire V1280/Netra 1280 Systems Installation Guide.

Using the Power On/Standby Switch

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.

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

FIGURE 2-1 Power On/Standby Switch

Graphic showing ON/Standby switch.System indicator board showin glocation of On/Standby switch.

The following table describes the switch positions

TABLE 2-1 Power On/Standby Switch Description
Symbol	Description
OnOn 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

When all the power cables are connected and external circuit breakers are switched on, the system enters Standby mode. The Source A and Source B indicators are the only indicator LEDs to be illuminated on the system indicator board. The IB_SSC assembly Active LED is lit, 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 System.

To Power On 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).

To Power On Using the LOM `poweron` Command

At the lom> prompt, type:

lom>poweron

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

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 is lit. The system will execute the power-on self-tests (POST).

Note - The poweron all command only powers on individual components; it does not boot the Solaris software.

See 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 five ways:

Using the UNIX shutdown command.

Sending the shutdown command through the LOM port

Sending the shutdown command using the On/Standby switch

Sending the poweroff command through the LOM port

Sending the poweroff command using the On/Standby switch

Note - Ensure that the system is cleanly shut down before powering to Standby mode, otherwise data is at risk of being lost.

To Use the Solaris `shutdown` Command

At the system prompt, type:

# shutdown -i5

The system powers off to Standby mode. The Source A and Source B indicators are the only indicator LEDs to be illuminated on the system indicator board. The IB_SSC assembly Active LED is lit, but not visible from the front of the system.

To Use the LOM `shutdown` Command

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

Note - If the Solaris software is running, this command attempts to halt the system cleanly before powering down the system to Standby mode, and is the equivalent of the Solaris init 5 command.

At the lom> prompt, type:

lom>shutdown

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

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

To Use the `shutdown` Command With the On/Standby Switch

Press the left side of the system On/Standby switch.

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

To Use the LOM `poweroff` Command

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

1. At the lom> prompt, type:

lom>poweroff

This will abruptly terminate Solaris.

Do you want to continue? [no]

Answer yes only if you wish to forcibly power off the system regardless of the state of the Solaris system. Under normal operation, you should use the shutdown command.

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

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

To Use the `poweroff` Command With the On/Standby Switch

Use this method only if you wish to forcibly power off the system regardless of the state of the Solaris system. Under normal operation you should send the shutdown command either from the lom> prompt or from the On/Standby switch (see To Use the shutdown Command With the On/Standby Switch).

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

After Powering On

You will see the following output on the system controller serial port connection:

CODE EXAMPLE 2-1 Hardware Reset Output From the System Controller
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>

CODE EXAMPLE 2-1 Hardware Reset Output From the System Controller

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 SC 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 System

To Set the Date and Time

If your time zone area is using daylight or summer time, this is set automatically.

Set the date, time, and time zone for the system by 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 Tuesday, April 20, 2004 at 18 hours 15 minutes and 10 seconds.

lom>setdate -t GMT-8 042018152004.10

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

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

To Set Up the Password

1. At the LOM prompt, type the SC password command.

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

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

lom>password

Enter new password:

Enter new password again:

lom>

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

To Configure Network Parameters

The Sun Fire entry-level midrange system can be administered from the SC LOM prompt and from the Solaris software. There are two ways to access the LOM Console connection:

Through the SC serial port connection.

Through a remote (network) connection using the 10/100 Ethernet port.

Note - The system can be administered solely through the serial port, but if you want to use the 10/100 Ethernet port, use a separate secure subnet for this connection. Remote connection capability is not enabled by default. If you use SSH or Telnet to administer the system, you must set the connection type to SSH or Telnet, using the setupnetwork command.

At the LOM prompt, type setupnetwork

lom>setupnetwork

Note - If you press the Return key after each question, the current value will not be changed.

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.

CODE EXAMPLE 2-2 Output From the `setupnetwork` Command
lom> `setupnetwork` Network Configuration --------------------- Is the system controller on a network? [yes]: Use DHCP or static network settings? [static]: Hostname [hostname]: IP Address [xxx.xxx.xxx.xxx]: Netmask [xxx.xxx.xxx.x]: Gateway [xxx.xxx.xxx.xxx]: DNS Domain [xxxx.xxx.xxx]: Primary DNS Server [xxx.xxx.xxx.xx]: Secondary DNS Server [xxx.xxx.xx.x]: Connection type (ssh, telnet, none) [ssh]: Rebooting the SC is required for changes in the above network settings to take effect. lom>

CODE EXAMPLE 2-2 Output From the setupnetwork Command

lom> setupnetwork

Network Configuration

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

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

Use DHCP or static network settings? [static]:

Hostname [hostname]:

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

Netmask [xxx.xxx.xxx.x]:

Gateway [xxx.xxx.xxx.xxx]:

DNS Domain [xxxx.xxx.xxx]:

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

Secondary DNS Server [xxx.xxx.xx.x]:

Connection type (ssh, telnet, none) [ssh]:

Rebooting the SC is required for changes in the above network settings to take effect.

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 System

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

To Install and Boot the Solaris Operating System

1. Access the LOM prompt.

For detailed instructions on how you can access the LOM prompt, see Chapter 3.

2. To power on the system, type poweron

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

lom>poweron

<POST messages displayed here . . . >

. . .

. . .

ok

3. If necessary, install the Solaris Operating System.

See your installation documentation, which is available with your Solaris Operating System release.

At the ok prompt, boot the Solaris Operating System 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 System is booted, the login: prompt is displayed.

login:

Installing the Lights Out Management Packages

There are three LOM packages needed on a Sun Fire entry-level midrange system available on the Solaris Supplementary CD.

SUNWlomu (LOMlite Utilities (usr))

SUNWlomm (LOMlite manual pages)

SUNWlomr (LOM drivers).

Note - The latest patches to these packages are available from SunSolve trademark . It is strongly advised that you obtain the latest versions of patches from SunSolve and install them on your Sun Fire E2900 and Sun Fire V1280/Netra 1280 to make use of the latest LOM utility updates.

To Install the LOM Drivers

As root, type:

CODE EXAMPLE 2-3 Installing the LOM Drivers
# `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. #

CODE EXAMPLE 2-3 Installing the LOM Drivers

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

Note - The WARNING messages concerning lomp, lomv, and lom driver attachment seen during the installation of the SUWNlomr package can be safely ignored since the SUNWlomr package is not used on the Sun Fire entry-level midrange systems. However, the presence of the package is required to allow successful upgrade through future patches.

To Install the LOM Utility

As superuser, type:

CODE EXAMPLE 2-4 Installing the LOM Utility
# `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. #

CODE EXAMPLE 2-4 Installing the LOM Utility

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

To Install the LOM Manual Pages

As superuser, type:

CODE EXAMPLE 2-5 Installing the LOM Manual Pages
# 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.

CODE EXAMPLE 2-5 Installing the LOM Manual Pages

# 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 resets the system in the event of a system hang or hardware problem. If the Solaris OS is running then you will be prompted to confirm this action:

To Forcibly Reset the System

Type:

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 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 System core file. After saving the debug information, if the value of the OpenBoot PROM variable auto-boot? is true, the system boots the Solaris OS. The OpenBoot PROM error reset recovery actions are controlled by setting the OpenBoot PROM error-reset-recovery configuration variable.

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

Note - If the system is still hung (you cannot log into the Solaris Operating System), type the break command to force control of the system back into the OpenBoot PROM ok prompt. If that did not work after you type the reset command for the first time, you must next type reset -a in order to reset everything.

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

To Reset the System Controller

Use the resetsc command to reset the SC. 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 causes the SC to reset, executes the SC POST level specified using the setupsc command, and restarts the LOM software.