Chapter 1. Introducing the SGIconsole

SGIconsole 2.1 is a software product used to monitor and manage SGI Origin 200 servers, SGI Origin 300 servers, SGI Origin 350 servers, the SGI Origin 2000 series of servers, the SGI Origin 3000 series of servers, the SGI Altix 3000 and SGI Altix 350 series of servers, Silicon Graphics Onyx2 deskside workstations, Silicon Graphics Onyx2 rackmount graphics systems, Silicon Graphics Onyx 300 systems, Silicon Graphics Onyx 350 systems, SGI Onyx 3000 graphics systems, and selected other SGI and non-SGI systems.

SGIconsole is used with one or more Silicon Graphics EL serial port servers to manage and monitor the various hardware configurations that connect via serial port.

The SGIconsole is used with one or more Ethernet hubs to manage and monitor the various hardware configurations that connect via Ethernet.

Figure 1-1 shows the SGIconsole server host connected to an Ethernet hub to which are connected various systems that may be managed by SGIconsole. A second SGIconsole at another location is shown connected to the first SGIconsole through the general Ethernet. A remote workstation is shown connected to these two SGIconsoles via the general Ethernet.

In addition to running and viewing Console Manager on the SGIconsole host system, you may also monitor and manage your servers and graphics systems using a remote workstation running selected versions of IRIX, Linux, or Microsoft Windows. For more information on this, see “Controlling SGIconsole from a Remote Workstation” in Chapter 3.

A monitor, keyboard, and mouse may also be connected directly to the SGIconsole at the local site.

Figure 1-1. SGIconsole in a Multiple-Server Hardware Configuration

SGIconsole in a Multiple-Server Hardware Configuration

Connection Types

This section describes the various devices to which SGIconsole may be connected. This section is intended only to provide an overview. For the details of the connections, refer to the appropriate sections of Chapter 4, “Connecting Managed Systems to SGIconsole via Ethernet”, and Chapter 5, “Connecting Managed Systems to SGIconsole via Serial Ports”.

SGIconsole is designed to manage SGI systems with MSCs (module system controllers), MMSCs (multi-module system controllers), L1s (level 1 system controllers), and L2s (level 2 system controllers). Each controller type is outlined below.

MSC (Module System Controller)

The MSC (module system controller) is used in all SGI Origin 200, SGI Origin 2000-series, and Onyx2 systems. The following systems contain one MSC, but do not contain any MMSCs (which are described in the next section):

  • SGI Origin 200 systems,

  • SGI Origin 2100 deskside systems,

  • SGI Origin 2200 deskside systems,

  • Onyx2 deskside systems

In all such systems, SGIconsole connects to the MSC with a serial cable, and connects to the console port with a second serial cable.

All systems with an MSC but with no MMSCs therefore require two serial connections to SGIconsole.

MMSC (Multi-Module System Controller)

The MMSC (multi-module system controller) is used in systems that contain more than one MSC[1] . The MMSCs connect to a console port on one of the modules in the system, connect to the MSCs in both the upper and lower bays in each rack, and connect to MMSCs in other racks, if any.

The following systems contain one or more MMSCs:

  • SGI Origin 2400 rack systems,

  • SGI Origin 2800 rack systems,

  • Onyx2 rack systems.

In all such systems, SGIconsole connects to one of the MMSCs via a single serial cable. Through the MMSC, SGIconsole is able to communicate with any other MMSCs in the system, with the system console, and with the MSCs in every module in the system.

All systems with at least one MMSC therefore require one serial connection to SGIconsole.

L1 (Level 1 System Controller)

The L1 (level 1 system controller) is used in SGI Origin 300/350, Altix 350, SGI Origin 3000-series, and Onyx 3000 systems. The following systems contain at least one L1, but do not contain any L2s:

  • SGI Origin 300 systems without NUMAlink module,

  • SGI Origin 350 systems without NUMAlink module,

  • SGI Altix 350 server systems,

  • Silicon Graphics Onyx 300 systems without NUMAlink module,

  • Silicon Graphics Onyx 350 systems without NUMAlink module,

  • SGI Origin 3200 systems without L2.

In all such systems, SGIconsole connects to the L1 with a single serial cable.

All systems with an L1 but with no L2s therefore require one serial connection to SGIconsole.

L2 (Level 2 System Controller)

The L2 (level 2 system controller) is used in many SGI systems that contain more than one L1. The L2s connect to each of the L1s in their rack and can connect to any L2s in other racks.

The following systems contain one or more L2s:

  • SGI Origin 300 with NUMAlink Module,

  • SGI Origin 350 with NUMAlink Module,

  • SGI Origin 3000-series servers (except SGI Origin 3200 system without L2),

  • SGI Onyx 3000 systems,

  • SGI Altix 3000-series servers (except 3700 Bx2 series).

In all such systems SGIconsole connects to the L2 dedicated Ethernet subnet via a single Ethernet cable. Through this connection, SGIconsole is able to communicate with all L2s in the system, and through those L2s, with all L1s in the system.

All systems with at least one L2 therefore require one Ethernet connection to SGIconsole.



[1] SGI Origin 200 systems configured in a dual-chassis (master/slave) arrangement actually contain two MSCs, but do not contain an MMSC. They therefore require two serial connections, as described in “MSC (Module System Controller)” on page 5, just as a single-chassis SGI Origin 200 does.