Sun Fire 12K Server
 
Sun Fire 15K Server
 

GCS>Sun Microsystems>Servers>High-End Servers
 

Applies to:

Goal

Solution

Powering On the Sun Fire[TM] 12K/15K/20K/25K Platform

Description:
This procedure describes how to power on the Sun Fire 12K/15K/20K/25K Platform.

Prerequisites:
You must have platform administrator privileges to run this procedure.

Notes:
* This procedure assumes that the Sun Fire 12K/15K/20K/25K platform has power, and all circuit breakers are in the on position.
* All circuit breakers (AC0, AC1) are on for all power supplies in the platform.
* All circuit breakers for fans are on.
* All circuit breakers are on for all expander board slots containing boards including the circuit breakers for the system controller and its peripherals (SC0, SCPER0, CS0, etc).
* A system controller is functioning in the master role.

Note: System controllers will automatically boot (unless auto-boot? is set to false) when power is applied to the Sun Fire platform and their circuit breaker is in the on position. The first system controller to boot will assume the master role.

Step 1

Power on any expansion cabinets that contain devices connected to any Sun Fire 12K/15K/20K/25K domain.

Step 2

Power on any devices connected to any Sun Fire 12K/15K/20K/25K domain.

Step 3

If the domains are correctly configured, and if the keyswitch position was last set to on, diag or secure, the domain will boot automatically once the platform is powered on.

Step 4

Log in to the main system controller with platform administrator privileges.

 admin workstation # telnet f15k-floating-sc

  Trying f15k-floating-sc
Connected to f15k-floating-sc.
Escape character is '^]'.

  SunOS 5.8

  login: sms-svc
Password: ********

  Last login: Tue Oct 26 14:43:18 from adminworkstation
Sun Microsystems Inc.   SunOS 5.8       Generic Patch   October 2001
f15k-sc0:sms-svc >

Step 5

Power on the Sun Fire 12K/15K/20K/25K platform and boot any domains as outlined in Step 3.

 f15k-sc0:sms-svc:> poweron

notes :If sufficient power and cooling is not available, the poweron operation will fail. A minimum of five 48V power supply modules (4 KW modules) are required to power a fully configured system.

Step 6

Check to see that the failover mechanism is enabled and active.

 f15k-sc0:sms-svc:> showfailover -v

Check to see that all components are OK.

 f15k-sc0:sms-svc:> showenvironment

Step 7

Set the failover mechanism to on, if necessary.

 f15k-sc0:sms-svc:> setfailover on

Step 8

You are now ready to begin booting any Sun Fire 12K/15K/20K/25K domains which did not boot (keyswitch in the off position). Refer to Starting a Sun Fire 12K/15K/20K/25K Domain for more information.

Starting a Sun Fire 12K/15K/20K/25K Domain

Description:
This procedure describes how to start (boot) a Sun Fire 12K/15K/20K/25K Domain.

Prerequisites:
You must have domain administrator privileges on the domain to use the console or the setkeyswitch option.

Note:
Assume jupiter is the domain name or you can replace jupiter with domain id ie: "A"

Step 1

If you are already at the OpenBoot PROM prompt for the domain, skip to Step 4.
If you are at the SMS user prompt, use the showkeyswitch command to determine the state of the virtual keyswitch for the domain.
If the virtual keyswitch state is on, diag, or secure, the domain should be powered up. If this is the case, proceed to step 3.
If the virtual keyswitch state is standby or off, proceed to Step 2.
Throughout this procedure, the variable domain represents the appropriate domain tag or domain ID.

 f15k-sc0:sms-svc:> showkeyswitch -d jupiter 

Step 2

If the virtual keyswitch state is standby or off, then set it to on with the command shown.

 f15k-sc0:sms-svc:> setkeyswitch -d jupiter on

Step 3

Use the console to access the desired domain. Once the domain is at the OBP ok> prompt, proceed to Step 4.

 f15k-sc0:sms-svc:> console -d jupiter

Note: If the domain is in the process of running POST, it can take some time, depending on the diagnostics level.
Note: If the OBP option auto-boot?=FALSE is set, this setkeyswitch command will not start Solaris. In such case, proceed to Step 4 to boot the domain from the
ok> prompt.

Step 4

 ok> boot

Boot the domain from the OBP prompt as shown.

Step 5

After the normal bootup process of the domain, you can optionally disconnect from the domain console and login through "ssh" or "telnet".

 jupiter console login: ~.

Terminate the console session.

At the login prompt, press with <~> keys then press <.> key simultaneously.

SNAPSHOT

  f15k-sc0:sms-svc:> showkeyswitch -d jupiter
Virtual key switch position: OFF
f15k-sc0:sms-svc:> setkeyswitch -d jupiter on
Reading domain blacklist file /etc/opt/SUNWSMS/config/A/blacklist ...
Reading platform blacklist file /etc/opt/SUNWSMS/config/platform/blacklist ...
Reading system ASR blacklist file /etc/opt/SUNWSMS/config/asr/blacklist ...
stage asic_probe: ASIC probe and JTAG/CBus integrity test...
stage brd_rev_eval: Board Revision Evaluation and Compliance...
stage cpu_probe: CPU Module probe...
stage cdc_probe: CDC DIMM probe...

  <...output emitted...>

  Configured in 333 with 4 procs, 8.000 GBytes, 2 IO adapters.
Interconnect frequency is 149.979 MHz, Measured.
Golden sram is on slot 1.1.
POST (level=16, verbose=20) execution time 3:16
#
# console -d jupiter
Trying to connect...
Connected to Domain Server.
Your console is in exclusive mode now. 

  jupiter console login:

Stopping a Sun Fire 12K/15K/20K/25K Domain

Description :
This procedure describes how to stop a Sun Fire 12K/15K/20K/25K Domain.

Prerequisites :
You must have superuser access to the domain.
If you choose to use the console or the setkeyswitch option, you must have domain administrator privileges on the domain.

Notes:
Follow your site's procedures to notify personnel of the impending outage.

Step 1

Use the console command from the master system controller with domain privileges login id to access the desired domain.
Throughout this procedure, the "jupiter" domain represents the appropriate domain tag or domain ID.

 f15k-sc0:sms-svc:> console -d jupiter

Step 2

Ensure that you have selected the right domain to be shutdown.

 jupiter # uname -a

Step 3

Bring the domain to the OpenBoot PROM prompt.

 jupiter:sms-svc:> shutdown -y -g 0 -i 0 

Step 4

 OK> ~. 

Terminate the console session.

At the OK> prompt, press with <~> keys then press <.> key simultaneously.

Step 5

 f15k-sc0:sms-svc:> setkeyswitch -d jupiter off 

If desired, set the virtual keyswitch to off, to prevent the domain from rebooting and place the system boards in low power mode.

SNAPSHOT

  jupiter # shutdown -y -g0 -i0    

  Shutdown started.    Sat Sep  8 16:34:18 PDT 2001   

  Changing to init state 0 - please wait
Broadcast Message from root (console) on dom-b Sat Sep  8 16:34:18...
THE SYSTEM jupiter IS BEING SHUT DOWN NOW ! ! !
Log off now or risk your files being damaged  

  showmount: jupiter: RPC: Program not registered
#
INIT: New run level: 0
The system is coming down.  Please wait.
System services are now being stopped.
Print services stopped.
Sep  8 16:34:29 dom-b syslogd: going down on signal 15
The system is down.
syncing file systems... done
Program terminated
{22} ok
Connection closed - console exit.
# setkeyswitch -d jupiter off
Current virtual key switch position is "ON".
Are you sure you want to change to the "OFF" position (yes/no)? yes
Domain is down.
Powering off: CPU at SB1
Powering off: HPCI at IO1
Powering off: EXB at EX1
#

Powering Off the Sun Fire 12K/15K/20K/25K Platform

Description:
This procedure describes how to power off the Sun Fire 12K/15K/20K/25K Platform.

Prequisites:
You must have platform administrator privileges to run this command.

Notes:
Follow your procedures to notify users of the impending outage.

Step 1

Log in to the main system controller with platform administrator privileges.

 admin workstation # telnet f15k-floating-sc

  Trying f15k-floating-sc
Connected to f15k-floating-sc.
Escape character is '^]'.

  SunOS 5.8

login: sms-svc
Password: ******** 

  Last login: Tue Oct 26 14:43:18 from adminworkstation
Sun Microsystems Inc.   SunOS 5.8       Generic Patch   October 2001
f15k-sc0:sms-svc > 

Step 2

 f15k-sc0:sms-svc:> showfailover -r 

Verify that this is the main system controller.
If this is not the main system controller, log on to the other system controller.

Step 3

Shut down all domains, refer to Stopping a Sun Fire Domain for more information.

Step 4

 f15k-sc0:sms-svc:> poweroff 

This command (with no arguments) when run by a user with platform administrator permissions will power down the Sun Fire 12K/15K/20K/25K platform, except for the main system controller, the spare system controller, the bulk power supplies, and the fan trays.

Step 5

 f15k-sc0:sms-svc:> showplatform 

Use the showplatform command to verify that all the domains have been powered off.

Step 6

 f15k-sc0:sms-svc:> setdatasync backup 

Synchronize the spare system controller to ensure that both system controller have the same configuration data.

Step 7

 f15k-sc0:sms-svc:> showdatasync 

Verify the data sync has completed.

Step 8

 f15k-sc0:sms-svc:> setfailover off 

Set failover to off on the main system controller.

Step 9

 f15k-sc0:sms-svc:> showfailover -v 

Verify that failover is set to off.

Step 10

 admin workstation # telnet f15k-sc1

 f15k-sc1# init 0
OK>

Access to the serial console to the spare system controller, login as root and halt the spare system controller to OBP.

Step 11

 admin workstation # telnet f15k-sc1
f15k-sc0 # init 0
OK>

Access to the serial console to the main system controller, login as root and halt the main system controller OBP.

Step 12

Set circuit breakers on the power supplies only to the off position and disconnect power cables, if desired.

NOTE - You should NEVER turn off the circuit breakers for individual boards!

Step 13

Power off any expansion cabinets which contain devices connected to this domain.

This solution has no attachment