Chapter 2. System Operation
Prev |  | Next

## Chapter 2. System Operation

This chapter describes some basic system operations that use the chassis manager controller (CMC) commands. It covers the following topics:

- “SGI UV System Control Network”

- “Connecting to the UV System Controller Network Using the CMC”

- “Power on and Booting an SGI UV System from Complete Power Off”

- “Power off an SGI UV System”

- “Power NMI to Drop into KDB”

- “Power NMI to Drop into KDB”

- “Upgrading System BIOS”

## SGI UV System Control Network

SGI Management Center (SMC) software running on the system management node (SMN) provides a robust graphical interface for system configuration, operation, and monitoring. For more information, see the SGI Management Center System Administrator's Guide.

The SGI UV 2000, SGI UV 1000, and the SGI UV 100 system control networks are private, closed networks. It is not to be reconfigured in any way different from the standard UV installation, nor is it to be directly connected to any other network. The SGI UV system control network does not accommodate additional network traffic, routing, address naming other than its own schema, and DCHP controls other than its own configuration. The system control network is not security hardened nor is it tolerant of heavy network traffic. It is vulnerable to Denial of Service attacks. The system management node acts as a gateway between the UV system control network and any other networks. For more information on the SGI UV system control network, see the SGI Altix UV 100 System User's Guide , the SGI Altix UV 1000 System User's Guide, or the SGI UV 2000 System User Guide.

## Connecting to the UV System Controller Network Using the CMC

The SGI UV software controller is designed to manage and monitor the individual blades in SGI UV systems. Depending on your system configuration, you can monitor and operate the system from the system management node (SMN) or on smaller systems, such as, the SGI UV 100 from the CMC itself. SGI UV 1000 systems of up to 16 racks (four building blocks, also called one super block) can also be controlled and monitored from a CMC in the system. For more information, see the SGI UV CMC Software User Guide.

## Power on and Booting an SGI UV System from Complete Power Off

To boot an SGI UV system from complete power off, perform the following steps:

1. Make sure the power breakers are on.

2. Establish a serial connection to the CONSOLE on the CMC or establish a network connection to the CMC. For a network connection, your PC or workstation must be connected to the CMC (via the network connection) and have its `/etc/hosts` file set up to include the CMCs. See “Connecting to the UV System Controller Network Using the CMC”.

3. Type the following command:

       ssh root@hostname-cmc
       SGI Chassis Manager Controller, Firmware Rev. 0.0.22

       CMC:r1i1c>

   Typically, the default password set out of the factory is `root`. The CMC prompt appears. CMC:r1i1c refers to rack 1, IRU 1, CMC.

   If the host name is not set up in the PC or workstation's hosts file, you can simply use the IP address of the CMC, as follows:

       ssh root@<IP-ADDRESS>

4. Power up your SGI UV system, using the `power on` command, as follows:

       CMC:r1i1c> power on

5. Open a second console to the CMC, using the `console` command, to see the system power on, as follows:

       ssh root@hostname-cmc
       SGI Chassis Manager Controller, Firmware Rev. 0.0.22

       CMC:r1i1c> console
       console: attempting connection to localhost...
       console: connection to SMN/CMC (localhost) established.
       console: requesting baseio console access at r001i01b00...
       console: tty mode enabled, use 'CTRL-]' 'q' to exit
       console: console access established
       console: CMC <--> BASEIO connection active
       ************************************************
       *******  START OF CACHED CONSOLE OUTPUT  *******
       ************************************************

       ******** [20100512.143541] BMC r001i01b10: Cold Reset via NL broadcast reset
       ******** [20100512.143541] BMC r001i01b07: Cold Reset via NL broadcast reset
       ******** [20100512.143540] BMC r001i01b08: Cold Reset via NL broadcast reset
       ******** [20100512.143540] BMC r001i01b12: Cold Reset via NL broadcast reset
       ******** [20100512.143541] BMC r001i01b14: Cold Reset via NL broadcast reset
       ******** [20100512.143541] BMC r001i01b04: Cold Reset via NL

   | Note: Use `CTRL-] q` to exit the console.

6. Depending upon the size of your system, in can take 5 to 10 minutes for the SGI UV system to power on. When the shell> prompt appears, enter `fs0:`, as follows:

       shell> fs0:

7. At the fs0: prompt, enter `boot`, as follows:

       fs0:> boot

   The ELILO Linux boot loader is called, various SGI configuration scripts are run, and the SUSE Linux Enterprise Server or Red Hat Enterprise Linux installation program appears.

## Power off an SGI UV System

To power down the SGI UV sytem, use the `power off` command, as follows:

    CMC:r1i1c> power off
    ==== r001i01c (PRI) ====

You can use the `power status` command, to check the power status of your system, as follows:

    CMC:r1i1c> power status
    ==== r001i01c (PRI) ====
    on: 0, off: 32, unknown: 0, disabled: 0

## Power NMI to Drop into KDB

To send a nonmaskable interrupt (NMI) signal from the power command to the CMC to drop into the kernel debugger (KDB), use the `power nmi` command, as follows:

    CMC:r1i1c> power nmi

    Entering kdb (current=0xffff8aa3fe11c040, pid 0) on processor 7 \
    due to NonMaskable Interrupt @ 0xffffffff8100ad42
         r15 = 0x0000000000000000      r14 = 0x0000000000000000
         r13 = 0x0000000000000000      r12 = 0x0000000000000000
          bp = 0xffffffff81927380       bx = 0xffff8ac1ff11dfd8
         r11 = 0xffffffff8101a2c0      r10 = 0xffff88000beefd18
          r9 = 0x00000000ffffffff       r8 = 0x0000000000000000
          ax = 0x0000000000000000       cx = 0x0000000000000000
          dx = 0x0000000000000000       si = 0xffff8ac1ff11dfd8
          di = 0xffffffff81a2b308  orig_ax = 0xffffffffffffffff
          ip = 0xffffffff8100ad42       cs = 0x0000000000000010
       flags = 0x0000000000000246       sp = 0xffff88000bee7ff0
          ss = 0x0000000000000018 &regs = 0xffff88000bee7f58
    [7]kdb>

## Upgrading System BIOS

To upgrade the compute blade PROM, perform the following steps:

1. From the CMC prompt, to show the current PROM level, type the following command:

       CMC:r1i1c> showbios
       Flashed on Sat May  1 14:14:45 UTC 2010 was bios.latest.fd (20100429_1603)

2. Get the newest PROM image from SupportFolio Online at http://support.sgi.com/ .

3. Copy the latest BIOS to a directory on the CMC in /`work/bmc/common/`. An example directory is as follows:

       CMC:r1i1c> ls
       bios.latest.fd flashbios

4. Use the `flashbios` command to flash the compute blade BIOS.

       CMC:r1i1c> flashbios
       Using default bios: bios.latest.fd
       Checking processor status on all nodes....
       Done. System is read for BIOS flash update
       Flashing bios bios.lastest.fd (20100429_1603) This will take several minutes.
       ...

For more information on using CMC software, see the SGI UV CMC Software User Guide.

For information on updating firmware on your SGI UV system from the system management node (SMN) and new firmware update commands, see the SGI UV System Management Node Administrator Guide.

Prev | Table of Contents | Next
Chapter 1. Configuring Your System |  | Index