Sun Enterprise 10000 Server
 

GCS>Sun Microsystems>Servers>High-End Servers
 
GCS>Sun Microsystems>Enterprise Computing>Systems Management
 

Powering Down The E10K:
[1.] Properly and gracefully shutdown the Solaris{TM} Operating Environment
     on the configured domains on your Sun Enterprise 10000 Server(s).
     You can either telnet/rlogin/ssh directly to the domains and issue 
     the "shutdown" command or you can choose to login to the main SSP 
     (System Service Processor), switch to the domain(s) you want to 
     shutdown via the "domain_switch" command, obtain a netcon session 
     via the "netcon" command to obtain a console interface on the E10K, 
     and then issue the "shutdown" command for each configured domain(s). 
 
     Example: 
              # telnet {domain_name}
              # shutdown -y -g0 -i0 

     This should bring your domain(s) to the OBP (Open boot PROM) level 
     also known as the "ok prompt".

     Perform this on all configured domains on your 
     Sun Enterprise 10000 Server(s).
       
     OR

     Log in to the main SSP (System Service Processor) from  
     a remote workstation or login to the main SSP locally 
     (on the main SSP system). 

     Example: 
              # telnet {mainsspname}  
              
              or login directly to the main SSP: 
                      
              Login: ssp 
              Password:  (Provide the ssp password)
              Please enter SUNW_HOSTNAME:  (Provide the platform_name) 
              sspname:platform_name% 

              Enter 'domain_status' to verify what domains 
              have what system boards.
              sspname:platform_name% domain_status

              Enter 'domain_switch {domain_name}' (Provide the 
                                                   domain_name for the 
                                                   domain you want to access) 
              sspname:platform_name% domain_switch {domain_name}

              Enter 'netcon' and you will now have the console prompt.
              sspname:domain_name%  netcon
                     
              OR
                       
              sspname:platform_name% domain_switch {domain_name}; netcon 
                         
              domain_name# shutdown -y -g0 -i0

              Once the domain(s) drops down to the OBP (Open boot PROM) 
              level also known as the "ok prompt", you will lose your 
              netcon session and return to the sspname:domain_name prompt. 
              If not, then simply disconnect and exit your netcon session 
              via "~.".

              Your prompt should still reflect what domain you are on.

              Repeat these steps for all the other remaining domains.

        NOTE: Here are some SSP netcon commands & tips:

              ~#    Break to OBP or kadb
              ~.    Disconnect and exit the netcon session.
              ~@    Acquire Unlocked Write permission; see -g.
              ~^    Release write permission.
              ~?    Show status of all open console sessions 
                    and the communication path currently in use.
              ~=    Toggle between standard network interface & JTAG.

                    To escape hung window (after kill -9 netcon), 
                    do: ^j, then stty sane, then ^j

[2.] Power off the entire Sun Enterprise 10000 host cabinet and remotely
     controlled I/O cabinets via the "power -B -off" command.  This will 
     power off all the E10K system boards, fan trays, control boards, and
     centerplane support boards which means that this software command will 
     turn off all fan tray breakers, control board, and all system board
     breakers where active boards are located. Note that by issuing 
     this command, to restore power to the E10K, you must manually (and 
     physically) turn on the individual breakers/switches (up to four per
     cabinet) on the AC input modules that feed the 48-volt power supplies. 
       
     Example:
       
     Enter 'domain_switch {platform_name}' to be able to control 
     the entire platform from the ssp.
     sspname:domain_name% domain_switch {platform_name}
     sspname:platform_name%
     sspname:platform_name% power -B -off

[3.] After issuing the "power -B -off" command from the SSP's platform 
     prompt, wait until all of the black power supply breakers (AC Input
     Modules) have flipped off, the fans have stopped spinning, and the
     control boards power down. You can check this by either 
     physically inspecting the LEDs for the said boards (all LEDs should 
     be turned off) or by issuing the "power" command from the SSP's 
     platform prompt.
       
     Example: 
       
     sspname:platform_name% power
 
     If you have an AC sequencer for RSM/A3000/A3500 arrays or any 
     external peripheral cabinet, make sure this is turned to the 
     "off" position. If using remote power commands for peripheral
     cabinets, make sure the A/C sequencer is in "remote" mode. Turn 
     off power to all peripheral cabinets/arrays if they are still 
     turned on. 
       
[4.] Power off the spare SSP first. Log in to the spare SSP as "root" 
     and issue the "shutdown" command to gracefully and properly 
     shutdown and power off this host.
       
     Example:
       
     spare_ssp# sync; sync; shutdown -y -g0 -i5
             
[5.] Power off the main SSP. Log in to the main SSP as "root" and 
     issue the "shutdown" command to gracefully and properly shutdown 
     and power off this host.
       
     Example:
       
     main_ssp# sync; sync; shutdown -y -g0 -i5

Congratulations! This completes the safest and recommended way of 
completely powering down your Sun Enterprise 10000/E10K Server(s).



____________________

Powering Up The E10K: 
____________________

[1.] Power on the main SSP first. Either turn on the switch on this 
     system or press the "power" button on your Sun keyboard. You will 
     hear a "beep indicating that the system is powering on. Assuming 
     that your OBP (Open Boot PROM) parameter called "auto-boot?" is 
     set to "true", the system should boot all the way up and load the 
     Solaris[TM] Operating System. On the other hand if your OBP (Open 
     Boot PROM) parameter called "auto-boot?" is set to "false", and 
     upon powering on the main SSP, it should drop to the "ok prompt". 
     Then, manually boot it using the "boot" command.
 
     Example:
       
              ok> boot       
        
     Once the main SSP is fully booted, it starts the SSP and the 
     SSP daemons. Check your SSP platform message file for completion 
     of the SSP daemon startup process. 

     Example: 
       
              # telnet {mainsspname} 
   
              or login directly to the main SSP: 
                      
              Login: ssp 
              Password:  (Provide the ssp password)
              Please enter SUNW_HOSTNAME:  (Provide the platform_name) 
              sspname:platform_name% 
                       
              sspname:platform_name% tail -f $SSPVAR/adm/messages

[2.] Once the main SSP is fully booted, power on the spare SSP next. 
     Either turn on the switch on this system or press the "power" 
     button on your Sun keyboard. You will hear a "beep indicating 
     that the system is powering on. Assuming that your OBP (Open 
     Boot PROM) parameter called "auto-boot?" is set to "true", the 
     system should boot all the way up and load the Solaris Operating 
     Environment. On the other hand if your  OBP (Open Boot PROM) 
     parameter called "auto-boot?" is set to "false", and upon 
     powering on the main SSP, it should drop to the "ok prompt". 
     Then, manually boot it using the "boot" command.
 
     Example:
       
              ok> boot       
       
     After the spare fully boots up, go back to the main SSP and 
     verify that failover is okay and that there are no known problems.
       
     Example:

     sspname:platform_name% showfailover
     sspname:platform_name% power
     
     NOTE: At this point, the SSP is still not communicating with 
           the Control Boards, since the E10K is still completely 
           powered off and no housekeeping voltage/power is running.

[3.] From a hardware perspective, power on the Sun Enterprise 10000 
     host cabinet and remotely controlled I/O cabinets by flipping 
     and turning on the switches on the black power supply breakers 
     (AC Input Modules) as well as turning on the AC sequencer to 
     power any peripheral cabinets/arrays. When you physically turn 
     on the individual breakers/switches (up to four per cabinet) on 
     the AC input modules that feed the 48-volt power supplies, this 
     will effectively turn on the housekeeping voltage which in turn 
     turns on the power supplies for the control boards and boots 
     these up. After the CBs (Control Boards) have been powered up, 
     they will attempt to communicate with the SSP. You must wait for 
     the LEDs to display a walking "1s" pattern (green LEDs) indicative 
     of the Control Board Executive (CB daemon) operating normally. The 
     fans will also spin down from a "high" rate to a "normal" rate 
     indicative of the CB operating normally.

     NOTE: This hardware transition may take anywhere up to 3 minutes 
           or so, and you must wait until this phase is complete before
           executing "power" commands on the SSP from a software standpoint.

[4.] Once the initial housekeeping voltage is up and running based on 
     the LED status on the control boards and normal fan speed, you can 
     then execute the "power -on -all" command from the main SSP's 
     platform prompt.

     Example: 
              # telnet {mainsspname}  
               
              or login directly to the main SSP: 
                      
              Login: ssp 
              Password:  (Provide the ssp password)
              Please enter SUNW_HOSTNAME:  (Provide the platform_name) 
              sspname:platform_name% 
                       
              sspname:platform_name% power -on -all

     This will turn on, and validate power to all system boards, 
     including centerplane support boards. The Sun Enterprise 10000 
     platform does not automatically boot any domains when powered 
     on. The domains must be initialized by the "bringup" command 
     individually from the SSP.

[5.] The Sun Enterprise 10000 host cabinet is now completely powered 
     up. Be sure that before booting each individually configured 
     domains that all external devices (peripheral/storage) connected 
     to this E10K is powered up, assuming that the AC sequencer was 
     either not turned on or the devices are not being controlled by 
     the AC sequencer in step [3.].
    
[6.] Login to the main SSP and individually perform a "bringup -A on" 
     command for each configured domain. The "bringup" command is run 
     from the SSP to configure and boot the current domain as defined 
     by the SUNW_HOSTNAME environment variable. It starts the same 
     process that the "reset" command from the "ok prompt" does for 
     other Sun systems. The "bringup" command is responsible for 
     coordinating all the other commands and processes required to 
     configure, test, and boot the domain. It runs on the SSP, 
     coordinating the activities of the domain being configured 
     through the control board. 
       
     Log in to the main SSP (System Service Processor) from  
     a remote workstation or login to the main SSP locally 
     (on the main SSP system). 

     Example: 
              # telnet {mainsspname}  
               
              or login directly to the main SSP: 
                      
              Login: ssp 
              Password:  (Provide the ssp password)
              Please enter SUNW_HOSTNAME:  (Provide the platform_name) 
              sspname:platform_name% 

              Enter 'domain_status' to verify what domains 
              have what system boards.
              sspname:platform_name% domain_status

              Enter 'domain_switch {domain_name}' (Provide the domain_name 
                                                  for the domain you want 
                                                  to access) 
              sspname:platform_name% domain_switch {domain_name}

              sspname:domain_name%  bringup -A on
                      
              where "-A on" toggles the OBP "auto-boot?" 
              environment variable to "true" (on).

        NOTE: As of SSP 3.3 or higher, when the "bringup" 
              command prompts for a response, it will time 
              out after 10 minutes if none is provided. The 
              default taken after the timeout is always "safe", 
              such as terminating the bringup operation or not
              configuring the centerplane.

        Repeat these steps for all the other remaining 
domains.                          

Congratulations! This completes the safest and recommended way of completely 
powering up your Sun Enterprise 10000/E10K Server(s).

This solution has no attachment