| Advanced Lights Out Management (ALOM) CMT v1.2 Guide |    
|
| Advanced Lights Out Management (ALOM) CMT v1.2 Guide |
|
| C H A P T E R 3 |
|
Configuring ALOM |
This chapter provides help on some basic configuration tasks including:
Your ALOM software comes preinstalled on your host server, so it works as soon as you apply power to the server. You can connect a terminal to the serial management port (SERIAL MGT) and immediately start working with ALOM.
However, if you want to customize ALOM for your installation, you must perform some basic tasks.
Here are the tasks you must complete to customize ALOM:
1. Plan how to customize your configuration. Refer to Planning Your ALOM Configuration for more information.
2. Use the configuration worksheet to record your settings. Refer to Configuration Variable Worksheet.
3. Run the setupsc command. Refer to Setting Up ALOM.
4. Use the configuration variables to customize the ALOM software. See To Use Configuration Variables in the ALOM Command Shell.
Explanations of the listed tasks follow.
ALOM software comes preinstalled on your host server. Follow the directions in this section to reinstall or update ALOM.
|
Note - Refer to your system administration guide to find the location of the serial and Ethernet connections for ALOM. |
Before you run the setupsc command to set up ALOM, you must decide how you want ALOM to manage your host server. You need to make the following decisions about your configuration:
Once you make those decisions, print the configuration worksheet shown in Configuration Variable Worksheet, and use it to record your responses to the setupsc command.
The ALOM hardware contains two types of communication ports:
Both ports give you access to the ALOM command shell. By default, ALOM communicates through the SERIAL MGT port at startup.
|
Note - Refer to your system administration guide to find the location of the server's serial management and network management (Ethernet) connections. |
You can connect to the ALOM serial management port with an ASCII terminal or terminal emulator (such as a serial connection from a workstation).
This port is not an all-purpose serial port; it is a dedicated port used to access ALOM and the server console through ALOM.
On your server, this port is referred to as the SERIAL MGT port. This port takes a standard RJ-45 connector.
Ensure that your console serial port is set to the following parameters:
The host server automatically sets these parameters for ALOM when it starts up. The settings are read-only, and cannot be changed from the ALOM sc> prompt. To view the settings for the parameters from the sc> prompt after you establish an ALOM session, check the serial port variables. Refer to Serial Management Port Variables for more information.
See Connecting to ALOM and Logging In To ALOM Accounts for detailed instructions on establishing an ALOM system controller session.
The ALOM shell prompt (sc>) is displayed.
2. To connect to the system console, in the ALOM system controller window type:
3. To return to the ALOM shell prompt (sc>) type the escape sequence (Hash- Period):
The 10/100-Mbit Ethernet port enables you to access ALOM from within your company network. You can connect to ALOM remotely using any standard Telnet client with TCP/IP (Transmission Control Protocol/Internet Protocol) or Secure Shell (ssh). On your server, the ALOM Ethernet port is referred to as the NET MGT port.
|
Note - When you connect a terminal device to the NET MGT port, the server must be connected to a 10-Mbit or 100-Mbit network. ALOM does not support 1-Gbit networks. |
When Dynamic Host Configuration Protocol is enabled, the SC acquires its network configuration, such as IP address, automatically from a DHCP server. DHCP is enabled by default.
DHCP enabled-by-default allows a network connection to be established to the SC without first requiring a serial connection to manually configure the network. To make best use of this feature, the administrator must be aware of the associated default configuration variables and default parameters for the DHCP server and for log in to the SC.
The following ALOM variables and the default contents support DHCP on-by-default:
A DHCP client, in this case the SC, provides a unique client identifier (clientid) to identify itself to the DHCP server. The clientid is based on a system property easily obtainable by an authorized administrator with physical access to the system. Once a clientid is determined, the DHCP server can be preconfigured to map the clientid to a known IP address. After the SC is assigned an IP address, it starts the SSH server. An administrator can then initiate an ssh session with the SC. If the system is brand-new out-of-box, or upon reboot after the setdefaults -a command is run, the default admin user account requires a default password to log in. The default password is also composed of a system property that is easily obtainable by an administrator with physical access to the system. The next two sections show how clientid and default password can be constructed.
The clientid is based on the base ethernet address for the system. The base ethernet address is available on the Customer Information Sheet that is delivered with each system and is also available on a label on the rear panel of the system chassis. The clientid is composed of the following concatenation:
For example, if the base-ethernet-address is 08:00:20:7C:B4:08, then the clientid that the SC generates is the string prefix SUNW,SC= concatenated with the 12-digit base-ethernet-address minus the colons:
This clientid is in ASCII format. It should be possible to program the DHCP server with an ASCII clientid. The actual entry into the DHCP mapping table is the hexadecimal equivalent.
When a system is shipped new from the factory, or upon reboot after a setdefaults -a command, a default password is required to log in from an ssh session. The default password is unique for each system. It is derived from the chassis serial number. The chassis serial number can be found on the Customer Information Sheet shipped with each platform and can be found on a label attached to the rear panel of the chassis. The default password is composed of the last 8 digits of the chassis serial number. For example, if the chassis serial number is 0547AE81D0 then the default password is:
1. Determine the clientid from the host system base ethernet address. The base ethernet address can be obtained from the Customer Information Sheet or label on the rear panel of the chassis.
2. Determine the default admin user login password from chassis serial number. The chassis serial number can be obtained from the Customer Information Sheet or label on the rear panel of the chassis.
3. Program the DHCP server to serve the new clientid.
4. Attach the system to the network and ensure the system has AC power.
5. Start the ssh session using the IP address assigned by the DHCP server.
6. Log in as the admin user using the predetermined default password.
|
Note - It is not necessary to preprogram the DHCP server to map the SC clientid to an explicit IP address; however, it is a best practice and can make long-term administration easier. |
If the DHCP server is configured to pull from a block of IP addresses, then the administrator can use a DHCP administrative utility to determine the IP address that was assigned, although it may first be necessary to convert the clientid to a hexadecimal equivalent. For example, if the DHCP server is running the Solaris OS, then the pntadm(1M) command can be used to display the IP address assignments. In the following example, the SC with ethernet address 123456789012 is connected to the .203 subnet.
# pntadm -P 129.156.203.0 Client ID Flags Client IP ... 53554E572C5353433D313233343536373839404142 00 129.156.203.240 ... ... |
In this case it is necessary to convert ASCII to a hexadecimal equivalent clientid to determine the IP address assignment. For example:
53|55|4E|57|2C|53|43|3D|31|32|33|34|35|36|37|38|39|30|31|32
S U N W , S C = 1 2 3 4 5 6 7 8 9 0 1 2
You only need to use this worksheet if you want to customize ALOM for your installation.
To customize ALOM, you use the configuration variables. Refer to Using ALOM Configuration Variables for details of variables.
There are two ways to set up the configuration variables for ALOM:
Print this section and use the table to record your inputs. This table can also serve as your record of the host server configuration in case you need to reinstall the server software or modify the ALOM settings.
Make sure that your terminal device is connected to ALOM before you customize the ALOM software. Choosing ALOM Communication Ports details the process.
TABLE 3-2 identifies the configuration variables responsible for Ethernet control and their default values. Enter your values in the extreme right column.
|
Manually, see Configuring Your Network Manually. Using DHCP, see Configuring Your Network Using DHCP. |
if_network, see if_network |
|||
|
if_connection, see if_connection |
||||
|
netsc_ipaddr, see netsc_ipaddr. |
||||
|
netsc_ipnetmask see netsc_ipnetmask. |
||||
|
IP address for the default gateway to use when the destination is not on the same subnet as ALOM |
netsc_ipgateway, see netsc_ipgateway. |
|||
|
Do you want ALOM to send alerts by email? Email addresses to use for sending alerts (maximum of two mail servers supported) |
mgt_mailalert, see mgt_mailalert. |
|||
|
IP address for your Simple Mail Transfer Protocol (SMTP) mail server (maximum of two mail servers supported) |
see mgt_mailhost. |
There are two ways to configure Dynamic Host Configuration Protocol (DHCP) for ALOM:
If you use DHCP to control your network configuration, configure the DHCP server to assign a fixed IP address to ALOM.
There are two ways to manually configure the network for ALOM:
If you set each variable individually, you need to set the following variables:
To send email alerts, the ALOM Ethernet port must be enabled, (see Network Management (Ethernet) Port).
When a problem occurs, ALOM sends an alert message to all users who are logged in to ALOM accounts on that server. In addition, you can configure ALOM to send alerts by email to users who are not logged in. When a user receives an alert, that user can connect to the ALOM account for that host server and address the alert condition.
The ALOM software permits you to set up to eight unique email addresses to receive alerts. You can configure each email address to receive its own severity level of alerts (critical, major, or minor). Refer to Sending and Receiving Alert Messages.
After you have finished planning your configuration, run the setupsc command described on setupsc. Follow the prompts on the screen to customize the ALOM software for your installation.
|
Note - You do not have to customize the ALOM software before you can use it. The ALOM software works as soon as you connect power to the server. |
The setupsc command runs a script that steps you through each ALOM function that you can customize. Each function is associated with one or more configuration variables. For more on configuration variables, refer to Chapter 7. To configure a function, type y when the setupsc script prompts you to do so. To skip a function, type n.
If you later need to change a setting, run the setsc command as described on setsc.
The setupsc script enables you to set up a number of configuration variables at once. See Chapter 7 for more information. If you want to change one or more configuration variables without running the setupsc script, use the setsc command as shown on To Use the setsc Command.
| Advanced Lights Out Management (ALOM) CMT v1.2 Guide | 819-6672-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Connect to the Serial Port