Chapter 4. Connecting Managed Systems to SGIconsole via Ethernet

This chapter provides a description of the steps you must follow to connect managed systems to SGIconsole via Ethernet.

Before following the steps detailed in this Chapter, it is necessary to set up the SGIconsole host system and Ethernet hub(s) as described in Chapter 3, “Setting Up the SGIconsole Host, Ethernet Hubs, and Serial Port Servers”.

For managed systems that connect to SGIconsole via serial port server, see Chapter 5, “Connecting Managed Systems to SGIconsole via Serial Ports”.

This chapter describes detailed steps to connect the SGIconsole to the following SGI servers and graphics systems:

Connecting SGI Origin 300 and Origin 350 Servers with NUMAlink Module to SGIconsole

If you will be connecting one or more SGI Origin 300 or Origin 350 servers with NUMAlink Modules to the SGIconsole, follow the directions in this section. Otherwise, proceed to “Connecting SGI Origin 3000 Series Servers With L2 Controllers to SGIconsole”.


Note: SGI Origin 300 servers, Origin 350 servers, Onyx 300 graphics systems, and Onyx 350 graphics systems without a NUMAlink module are managed via serial connection, as described in Chapter 5, “Connecting Managed Systems to SGIconsole via Serial Ports”.

Methods for connecting an SGI Origin 300 server with NUMAlink Module or an Origin 350 server with NUMAlink Module to an SGIconsole are identical. Figure 4-1 shows the connection of three SGI Origin 300 and Origin 350 servers with NUMAlink Modules through an Ethernet hub to an SGIconsole.


Note: In order for your SGIconsole to operate successfully with your Origin 300 or Origin 350 servers with NUMAlink Module, your servers must be running L1 firm ware revision 1.18.0 or later.



Note: If you connect to one or more partitioned systems (such as partitioned SGI Origin 300 or 3000 series servers), each partitioned system needs only one hardware connection. This is true regardless of the number of partitions into which the system is configured.



Note: In connecting a managed system to your SGIconsole you may want to consult the user's guide for the managed system, which describes how to set up and use that particular system.



Caution: Before connecting the SGIconsole host system to either a 120 VAC or 220 VAC outlet, be sure that the electrical rat ing on the UL-CSA label is in either the 100-120 VAC range or the 200-240 VAC range, whichever applies. In locations without either a 120 VAC or 220 VAC outlet, contact your SGI system support engineer before connecting the power cable.

Figure 4-1. Connecting SGI Origin 300 and Origin 350 Servers with NUMAlink Modules to an SGIconsole (SGI 1100 shown)

Connecting SGI Origin 300 and Origin 350 Servers with NUMAlink Modules to an SGIconsole (SGI 1100 shown)

To connect an SGI Origin 300 or Origin 350 server with NUMAlink Module to the SGIconsole, follow these steps:

  1. Plan your SGIconsole host system, as described in Chapter 2, “Planning an SGIconsole Installation”.

  2. Set up your SGIconsole host system, as described in Chapter 3, “Setting Up the SGIconsole Host, Ethernet Hubs, and Serial Port Servers”.

  3. Make sure that the power switch on your SGIconsole host system is off, and that the SGIconsole and the Ethernet hub are disconnected from a power source.

  4. Make sure that the SGI Origin 300 or Origin 350 server which you are connecting to the SGIconsole is powered off according to the instructions in SGI Origin 300 User's Guide or SGI Origin 350 User's Guide.

  5. Make sure that you have a standard RJ-45 to RJ-45 twisted-pair Ethernet cable (10 feet (3 meters), part number 018-0830-001), as shown in Figure 4-2, to make your cabling connections to one server. If you are connecting multiple servers to the SGIconsole, you need one standard RJ-45 to RJ-45 twisted-pair Ethernet cable for each additional server you are connecting.

    Figure 4-2. Items Needed to Connect an SGI Origin 300 or Origin 350 Server with NUMAlink Module to SGIconsole

    Items Needed to Connect an SGI Origin 300 or Origin 350 Server with NUMAlink Module to SGIconsole

  6. Connect one end of the standard RJ-45 cable to one of the RJ-45 jacks on the Ethernet hub. Connect the other RJ-45 connector end to the L2 controller's RJ-45 Ethernet jack. See Figure 4-3.

    Figure 4-3. Connecting an Origin 300 or Origin 350 Server with NUMAlink Module L2 Controller to an Ethernet Hub

    Connecting an Origin 300 or Origin 350 Server with NUMAlink Module L2 Controller to an Ethernet Hub

  7. Connect the cables for any other SGI Origin 300 or Origin 350 servers with NUMAlink Module at your location as you did in steps 4 through 6.

  8. If you will be connecting other managed systems to the SGIconsole, proceed to “Connecting SGI Origin 3000 Series Servers With L2 Controllers to SGIconsole”.

  9. If you are finished connecting managed systems to the SGIconsole, connect the power cables for your Ethernet hubs, the managed systems, and the SGIconsole host system to a power source.

  10. Power on all your managed systems according to the instructions in their respective user's guides.

  11. Power on your SGIconsole according to the instructions in your host system user's guide.

Connecting SGI Origin 3000 Series Servers With L2 Controllers to SGIconsole

If you will be connecting one or more SGI Origin 3000 series servers with L2 controllers to the SGIconsole, follow the directions in this section. Otherwise, proceed to “Connecting SGI Onyx 3000 Series Graphics Systems to SGIconsole”.

Methods for connecting the various SGI Origin 3000 series server with L2 controller to an SGIconsole are identical. Figure 4-4 shows the connection of the following SGI Origin 3000 series servers with L2 controllers through an Ethernet hub to an SGIconsole: the SGI Origin 3200, the SGI Origin 3400, and the SGI Origin 3800.

If you are connecting the SGIconsole to an SGI Origin 3200 server without an L2 controller, refer to “Connecting SGI Origin 3200 Servers Without L2 Controllers to SGIconsole” in Chapter 5. Alternately, you may acquire an L2 controller (part number HU-L2-SYSCTLR) and a USBA to USBB cable (part number 018-0809-001) to connect the L1 USB port on the C–brick to one of the L1 USB ports on the L2 controller. Once these parts are added, you may connect your SGI Origin 3200 server as described in this section.


Note: In order for your SGIconsole to operate successfully with your Origin 3000 series servers, your servers must be running L1 firmware revision 1.18.0 or later.



Note: If you connect to one or more partitioned systems (such as SGI partitioned Origin 300 or 3000 series servers), each partitioned system needs only one hardware connection. This is true regardless of the number of partitions into which the system is configured.



Note: In connecting a managed system to your SGIconsole you may want to consult the user's guide for the managed system, which describes how to set up and use that particular system.



Caution: Before connecting the SGIconsole host system to either a 120 VAC or 220 VAC outlet, be sure that the electrical rating on the UL-CSA label is in either the 100-120 VAC range or the 200-240 VAC range, whichever applies. In locations without either a 120 VAC or 220 VAC outlet, contact your SGI system support engineer before connecting the power cable.

Figure 4-4. Connecting SGI Origin 3000 Series Servers with L2 Controllers to SGIconsole

Connecting SGI Origin 3000 Series Servers with L2 Controllers to SGIconsole

Working with Multiple Origin 3000 Series Server Systems

When connecting multiple Origin 3000 series systems to the same Ethernet network, all the L2 controllers in those 3000 series systems must be configured as described in this section.

Normally all the L2 system controllers on an Ethernet network seek out all other L2 controllers on that network and share configuration information, assuming that they are all in the same Origin 3000 series system. If L2 controllers from multiple systems are connected to the same Ethernet network (as they would be if they are being controlled by the same SGIconsole), each such L2 controller must have the multisys option enabled, and must have the system serial number set.

Follow the steps in this section for each L2 system controller in every system to prepare them for use in a multi-system configuration.

  1. Connect a serial console to the console serial port on the L2.

  2. To enable the multisys option, type the following at the L2 command prompt:

    L2> msys on 

  3. To set a system serial number, type the following at the L2 command prompt:

    L2> serial serial number 

    where <serial number> is a letter followed by seven digits.

    For more information about L2 controller commands, see the SGI Origin 3000 Series Owner's Guide.

Making the Connections for SGI Origin 3000 Series Server Systems

To connect an SGI Origin 3000 series server with an L2 controller to the SGIconsole, follow these steps:

  1. Plan your SGIconsole host system, as described in Chapter 2, “Planning an SGIconsole Installation”.

  2. Set up your SGIconsole host system, as described in Chapter 3, “Setting Up the SGIconsole Host, Ethernet Hubs, and Serial Port Servers”.

  3. Make sure that the power switch on your SGIconsole host system is off, and that the SGIconsole and the Ethernet hubs are disconnected from a power source.

  4. Make sure that the SGI Origin 3000 series server which you are connecting to the SGIconsole is powered off according to the instructions in SGI Origin 3000 User's Guide.

  5. Make sure that you have a standard RJ-45 to RJ-45 twisted-pair Ethernet cables (10 feet (3 meters), part number 018-0830-001), as shown in Figure 4-5, to make your cabling connections to one server. If you are connecting multiple servers to the SGIconsole, you need one standard RJ-45 to RJ-45 twisted-pair Ethernet cable for each additional server you are connecting.

    Figure 4-5. Items Needed to Connect SGIconsole to an SGI Origin 3000 Series Server with an L2 Controller

    Items Needed to Connect SGIconsole to an SGI Origin 3000 Series Server with an L2 Controller

  6. Connect one end of the standard RJ-45 cable to one of the RJ-45 jacks on the Ethernet hub. Connect the other RJ-45 connector end to the L2 controller's RJ-45 Ethernet jack. See Figure 4-6.

    Figure 4-6. Connecting an Origin 3000 Series Server with L2 Controller to an Ethernet Hub

    Connecting an Origin 3000 Series Server with L2 Controller to an Ethernet Hub

  7. Connect the cables for any other SGI Origin 3000 series servers with L2 modules at your location as you did in steps 4 through 6.

  8. If you will be connecting other managed systems to the SGIconsole, proceed to “Connecting SGI Onyx 3000 Series Graphics Systems to SGIconsole”.

  9. If you are finished connecting managed systems to the SGIconsole, connect the power cables for your Ethernet hubs, the managed systems, and the SGIconsole host system to a power source.

  10. Power on all your managed systems according to the instructions in their respective user's guides.

  11. Power on your SGIconsole according to the instructions in your host system user's guide.

Connecting SGI Onyx 3000 Series Graphics Systems to SGIconsole

If you will be connecting one or more SGI Onyx 3000 series graphics systems to the SGIconsole, follow the directions in this section. Otherwise, proceed to “Connecting SGI Altix 3000 Series Servers (With L2) to SGIconsole”.

The SGI Onyx 3000 series graphics system is actually the G–brick for the SGI Origin 3000 series servers. Management and monitoring of the SGI Onyx 3000 series graphics systems is performed through the SGIconsole connections to the SGI Origin 3000 series servers. See “Connecting SGI Origin 3000 Series Servers With L2 Controllers to SGIconsole” for details on how to connect an SGIconsole to the SGI Origin 3000 series servers.

Once you have finished connecting your Onyx 3000 graphics system, proceed to “Connecting SGI Altix 3000 Series Servers (With L2) to SGIconsole”.


Note: In order for your SGIconsole to operate successfully with your SGI Onyx 3000 series graphics system, your system must be running L1 firmware revision 1.18.0 or later.


Connecting SGI Altix 3000 Series Servers (With L2) to SGIconsole

If you will be connecting one or more SGI Altix 3000 series servers to the SGIconsole, follow the directions in this section. Otherwise, proceed to Chapter 5, “Connecting Managed Systems to SGIconsole via Serial Ports”.

Methods for connecting the various SGI Altix 3000 series servers to an SGIconsole are identical. Figure 4-7 shows the connection of Altix 3300 and Altix 3700 servers through an Ethernet hub to an SGIconsole.


Note: In order for your SGIconsole to operate successfully with your Altix 3000 series servers, your servers must be running L1 firmware revision 1.18.0 or later.



Note: If you connect to one or more partitioned systems (such as partitioned SGI Origin 300 or 3000 series servers), each partitioned system needs only one hardware connection. This is true regardless of the number of partitions into which the system is configured.



Note: In connecting a managed system to your SGIconsole you may want to consult the user's guide for the managed system, which describes how to set up and use that particular system.



Caution: Before connecting the SGIconsole host system to either a 120 VAC or 220 VAC outlet, be sure that the electrical rating on the UL-CSA label is in either the 100-120 VAC range or the 200-240 VAC range, whichever applies. In locations without either a 120 VAC or 220 VAC outlet, contact your SGI system support engineer before connecting the power cable.

Figure 4-7. Connecting SGI Altix 3000 Series Servers (With L2) to an SGIconsole

Connecting SGI Altix 3000 Series Servers (With L2) to an SGIconsole

Working with Multiple Altix 3000 Series Server Systems

When connecting multiple Altix 3000 series systems to the same Ethernet network, all the L2 controllers in those 3000 series systems must be configured as described in this section.

Normally all the L2 system controllers on an Ethernet network seek out all other L2 controllers on that network and share configuration information, assuming that they are all in the same Altix 3000 series system. If L2 controllers from multiple systems are connected to the same Ethernet network (as they would be if they are being controlled by the same SGIconsole), each such L2 controller must have the multisys option enabled, and must have the system serial number set.

Follow the steps in this section for each L2 system controller in every system to prepare them for use in a multi-system configuration.

  1. Connect a serial console to the console serial port on the L2.

  2. To enable the multisys option, type the following at the L2 command prompt:

    L2> msys on 

  3. To set a system serial number, type the following at the L2 command prompt:

    L2> serial serial number 

    where <serial number> is a letter followed by seven digits.

    For more information about L2 controller commands, see the SGI Origin 3000 Series Owner's Guide.

Making the Connections for SGI Altix 3000 Series Server Systems

To connect the SGIconsole to an SGI Altix 3000 series server, follow these steps:

  1. Plan your SGIconsole host system, as described in Chapter 2, “Planning an SGIconsole Installation”.

  2. Set up your SGIconsole host system, as described in Chapter 3, “Setting Up the SGIconsole Host, Ethernet Hubs, and Serial Port Servers”.

  3. Make sure that the power switch on your SGIconsole host system is off, and that the SGIconsole and the Ethernet hubs are disconnected from a power source.

  4. Make sure that the SGI Altix 3000 series server to which you are connecting the SGIconsole is powered off according to the instructions in the SGI Altix 3000 User's Guide.

  5. Make sure that you have a standard RJ-45 to RJ-45 twisted-pair Ethernet cable (10 feet (3 meters), part number 018-0830-001), as shown in Figure 4-8, to make your cabling connections to one server. If you are connecting the SGIconsole to multiple servers, you need one standard RJ-45 to RJ-45 twisted-pair Ethernet cable for each additional server you are connecting.

    Figure 4-8. Items Needed to Connect an SGI Altix 3000 Series Server to an SGIconsole

    Items Needed to Connect an SGI Altix 3000 Series Server to an SGIconsole

  6. Connect one end of the standard RJ-45 cable to one of the RJ-45 jacks on the Ethernet hub. Connect the other RJ-45 connector end to the L2 controller's RJ-45 Ethernet jack. See Figure 4-9.

    Figure 4-9. Connecting an Altix 3000 Series Server to an Ethernet Hub (3700 Shown, 3300 Similar)

    Connecting an Altix 3000 Series Server to an Ethernet Hub (3700 Shown, 3300 Similar)

  7. Connect the cables for any other SGI Altix 3000 series servers with L2 modules at your location as you did in steps 4 through 6.

  8. If you will be connecting other managed systems to the SGIconsole, proceed to Chapter 5, “Connecting Managed Systems to SGIconsole via Serial Ports”.

  9. If you are finished connecting managed systems to the SGIconsole, connect the power cables for your Ethernet hubs, the managed systems, and the SGIconsole host system to a power source.

  10. Power on all your managed systems according to the instructions in their respective user's guides.

  11. Power on your SGIconsole according to the instructions in your host system user's guide.