C H A P T E R  2

Using the Embedded Lights Out Manager System

This chapter assumes that you have your server cabled, powered on, and the operating system installed. Setting up and cabling your system is covered in your server operating system installation guide. If you have not completed these steps, please return to the server operating system installation guide appropriate for your platform.

This chapter includes the following sections:


Embedded Lights Out Manager System Components

The embedded lights out manager (ELOM) system provides an embedded service processor (SP), flash memory, RAM, separate Ethernet interfaces, and server management software. This server management software provides superior management tools to help you administer local or remote servers efficiently.

You can use the web-based interface, the command-line interface (CLI), SNMP integration with third-party frameworks, or IPMI to configure and manage the platform through the SP.

The dedicated SP provides complete operating system independence and maximum availability of server management. Through the integrated service processor you can configure and manage the server hardware, firmware, and associated applications from a single point of entry.

FIGURE 2-1 ELOM Communications


A block diagram graphic showing the ELOM communication paths.


Accessing the Service Processor

Make sure your server system is properly set up and cabled. See your platform documentation for instructions on installing the hardware and cabling and for instructions on powering on the server. Your point of entry to the system is the service processor (SP).

You can access the SP on your server from your laptop or from a workstation or PC.

To begin, apply only standby power to your server to access the service processor. Setting up the SP is covered in Chapter 3.


Setting Up Communications

From the system serial port or the dedicated Ethernet port you will be able to communicate with the service processor’s ELOM in several ways.

Determining a DHCP Address

Dynamic Host Configuration Protocol (DHCP) is a powerful tool in connecting to the Ethernet because it automatically assigns IP addresses, subnet masks, default routers, and other IP parameters. Your embedded lights out manager is shipped with DHCP enabled by default.



Note - If the IP address assigned to the 10/100 ELOM Ethernet port by DHCP is known, the 10/100 ELOM Ethernet port can be accessed without using the Serial A port.



TABLE 2-1

If a DHCP Server is Present

If a DHCP Server is Not Present

Obtain an IP address using serial port: See Connecting Through the Serial Port

Change IP address using serial port: See Connecting Through the Serial Port

To view the IP address in System BIOS: See To View the System IP Address in the BIOS.

|

|

To view IP address from DHCP server: See To Configure Your DHCP Server

Configure system using SSH or web-based interface: See Managing the ELOM Network Settings and Accessing the System Using the Web-Based Interface



Connecting Through the Serial Port


procedure icon  To Connect to the SP Through the Serial Port.

1. Open a terminal window to connect to the ELOM service processor through the serial port.

a. On Solaris, issue the command tip -9600 /dev/term/a to connect through serial port A.

b. On Windows, use hypertrm. The settings should be 9600, 8, N, 1.

2. Press Enter on the terminal device.

This will make the service processor issue a login prompt.

3. To log in to the CLI:

a. Enter the default user name, root.

b. Enter the default password, changeme.

Once you have successfully logged in, the service processor displays the SP default command prompt:

SP->

You can now run CLI commands (see Appendix A for a list of commands).

By default each new system comes with the IP address and DHCP enabled. Step 4 explains what to do if the DHCP is not enabled. Change the IP address if you need a different static IP address.



Note - If you connect a terminal or emulator to the serial port before it has been powered up or during its power up sequence, you will see boot-up messages.


4. Do one of the following, depending on whether the DHCP server is present:

show /SP/AgentInfo

A portion of the sample output from the above command:


  Properties:
        HWVersion = 0
        FWVersion = 3.20
        MacAddress = 00:16:36:5B:97:E4
        IpAddress = 10.13.60.63
        NetMask = 255.255.255.0
        Gateway = 10.13.60.1
        DhcpConfigured = disable



Note - Be sure to record the IP address assigned to the ELOM SP.



procedure icon  To View System Output Within CLI

single-step bullet  To access the host serial console (host COM 0), enter the following command:

SP-> start /SP/AgentInfo/console



Note - Use the Esc-Shift-9 key sequence to toggle back to the local console flow. Enter Ctrl-b to terminate the connection to the serial console.


Chapter 8 describes how to use the CLI.

Setting Up Serial Over LAN

See the section that corresponds to the operating system that you are using to use serial over LAN to interact with the ELOM SP.


procedure icon  To Set Up Serial Over LAN With the Solaris OS

1. Log in to the Solaris system as root (superuser).

2. Edit the /boot/solaris/bootenv.rc file to point to ttyb speed to 115200 as follows:

setprop ttyb-mode 115200,8,n,1,-

setprop console ‘ttyb’

3. In the /boot/grub/menu.1st file, edit the splashimage and kernel lines to read as follows:

# splashimage /boot/grub/splash.xpm.gz

kernel /platform/i86pc/multiboot -B console=ttyb

4. Change the login service to listen at 115200 by making the following edits to /var/svc/manifest/system/console-login.xml:

a. Change console to 115200 in the propval line to read as follows:

<propval name=’label’ type=’astring’ value=’115200’>

b. Add the following text to the file /kernel/drv/asy.conf:

  bash-3.00# more /kernel/drv/asy.conf
  #
  # Copyright (c) 1999 by Sun Microsystems, Inc.  # All rights reserved.  #  # pragma ident "@(#)asy.conf 1.12 99/03/18 SMI" interrupt- priorities=12;name="asy" parent="isa" reg=1,0x2f8,8 interrupts=3;

 

5. Enter the following to reboot the operating system:

# reboot -- -r


procedure icon  To Set Up Serial Over LAN With Linux

These instructions apply for all supported Red Hat and SUSE operating systems, except as noted.

1. Log in to the system as root (superuser).

2. Open the /etc/inittab file in a text editor.

3. Change the following in the /etc/inittab file:

a. Find the getty section of the inittab, and edit the gettys for init level 3 so that the line reads as follows:

3:2345:respawn:/sbin/agetty -L 115200 ttyS1 vt100t

b. Locate the following line in the file:

id:5:initdefault

c. Change the default init level from 5 to 3 as shown in the following example:

id:3:initdefault

4. If you plan to log in to the OS as root using the Remote Console, add the following line to edit the /etc/securetty file:

ttyS1

Alternatively, you can creat a non-root account, to which you can log in without this change.

5. To see all of the startup messages in Red Hat, edit the /etc/grub.conf file as follows:

a. Open the /etc/grub.conf file in a text editor.

b. Add the following to the kernel line:

’console=tty1 console=ttyS1,115200’


Connecting Over Ethernet

The embedded lights out manager (ELOM) software on the SP offers several interfaces to support system management on your server. Before you take advantage of those interfaces over your Ethernet local area network (LAN), you need to do the following:



Note - This procedure assumes that you have already completed the hardware setup, and have applied standby power for your server, as described in your platform documentation.


Once you have determined the IP address of the SP, you can access its firmware applications through a secure command shell (SSH) or a web browser.


procedure icon  To Connect to the SP Over the Ethernet

1. Insert an Ethernet cable into the Net Mgmt RJ-45 port.

See your platform documentation setup guide for an illustration and instructions on installing the hardware and cabling, and for powering on.

2. Open an Internet Explorer web browser.

See TABLE 2-2 for other browsers able to run the web-based interface.


TABLE 2-2 Minimum Level of Supported Browsers

Operating System

Mozilla

Firefox

 

Solaris x86

1.7

1.5.0.4

 

RHEL 32-bit

1.7.12

1.0.7

 

RHEL 64 bit

1.7.13

1.5.0.4

 

SLES 32 bit

1.7.8

1.5.0.4

 

SLES 64 bit

1.7.13

1.5.0.4


3. In the address bar enter the address assigned to the SP.

By default, each new Sun Fire X2100 M2 and Sun Fire X2200 M2 server system comes with DHCP enabled. If no DHCP server is found within five seconds, the system defaults to the static IP address 192.168.1.2. Change the IP address if you need a different static IP address. If you change to a different static IP address it must be on the same network segment.

4. Log In to the SP.

The account name is “root” and the password is “changeme


procedure icon  To View the System IP Address in the BIOS

1. Attach a local video display screen to the server’s video port.

2. Attach a USB keyboard to one of the USB ports on the server.

3. Attach an Ethernet cable from the network to the NET MGT Ethernet port on the server.

4. Apply power to the server.

The system will begin displaying the large full screen Sun Logo. During this process perform Step 5.

5. Press the F2 key on the USB keyboard to enter the BIOS setup mode.

The system will carry out some additional configuration operations before entering the blue BIOS setup mode.

a. If you have a system without a display you can:

i. Start the CLI, and log in.

ii. Launch a system console by entering the command:

-> start /SP/AgentInfo/console

iii. Reboot the server, and press the hot keys to enter the BIOS.

6. Under Advanced choose: Ipmi 2.0 configuration.

7. Choose: Set Lan Configuration,

8. Select IP Address and the Current IP address is displayed.


procedure icon  To Configure Your DHCP Server

1. Verify that your DHCP server will accept new MAC addresses.

2. Confirm that an Ethernet cable is connected to the RJ-45 NET MGT Ethernet port on your server.

3. Obtain the SP MAC address from one of the following locations.



Note - MAC addresses are 12-digit hexadecimal strings in the format xx:xx:xx:xx:xx:xx.
Where xx:xx:xx:xx:xx:xx represents a single hexadecimal letter (0-9, A-F, a-f).


4. Make note of the MAC address for future reference.

5. Obtain the SP IP address from one of the following locations. Record the IP address for future reference.

a. Log in to your DHCP server, and view its DHCP log file.



Note - Different DHCP server applications running on different operating systems store these log files in different locations. Consult your DHCP system administrator to locate the correct path to the log file.


b. In the log file, identify the IP address that corresponds to the MAC address of your SP.

Typically, DHCP log file entries are individual lines with the following comma-separated fields:

ID, Date, Time, Description, IP Address, Host Name, MAC Address

Locate the MAC address of your SP in the MAC Address (seventh) field of the correct DHCP file entry, and record the corresponding value of the IP Address (fifth) field. This is the IP address that you must use to access the system management firmware applications on your SP.

6. Open a session to the SP using the IP address that you obtained in Step 5.

Each SP firmware application requires a different web browser or shell.

To establish a Secure Shell (SSH) connection to the SP command-line interface (CLI), enter the appropriate connection command in the SSH application. For example, to connect to the SP with the DHCP-assigned IP address of 192.168.0.0, enter the following command:

# ssh -l root 198.168.0.0

Once you have entered the default password for the SP, changeme, you can enter commands to manage user accounts or to monitor the status of devices on your server.


Finding Task Information

The following table describes where to find the information you need for the task you want to perform.


TABLE 2-3 Task Information

Task

Where to Find the Information

Communicate with the system.

Setting Up Communications

Use the SSH to log in to the SP.

To Log In Using SSH

Set up the Service Processor (SP) from the web browser.

Setting Up the Service Processor Using the Web-Based Interface

Find out the health of the system using the web-based interface.

Accessing the System Using the Web-Based Interface

Discover what hardware is installed using the web-based interface.

Using the System Information Screens

Monitor temperatures, voltages, fans, and chassis from the web-based interface.

Using the System Monitoring Screens

View the Event Log.

Examining, Saving, and Clearing the Event Log

Determine which events to monitor from the web-based interface.

Defining Traps with the Platform Event Filter

Addand delete users, and set user access

Managing Users

Update the SP firmware

Service Processor Maintenance

Start a remote console session from the web-based interface.

Launching the Remote Console Application

Get system information using intelligent Platform Management Interface (IPMI) commands.

Supported IPMI 2.0 Commands

Manage the system from the command line.

Logging In to the CLI