| Sun Advanced Lights Out Manager Software User's Guide |    
|
| Sun Advanced Lights Out Manager Software User's Guide |
|
| C H A P T E R 4 |
|
Using the ALOM Command Shell |
This chapter contains the following sections:
The ALOM command shell is a simple command-line interface. Through the ALOM command shell, you can administer, diagnose, or control the host server, and you can configure and manage ALOM.
You are in the ALOM command shell when you see the sc> prompt. ALOM supports a total of four concurrent Telnet sessions and one serial session per server. This means that you can run five command shell operations at once.
After you log in to your ALOM account, the ALOM shell prompt (sc>) appears, and you can enter ALOM shell commands. See Logging In To Your ALOM Account and ALOM Shell Commands for assistance.
|
Note - Some of these commands are also available through the scadm utility. See Overview of the scadm Utility, and List of scadm Commands. |
|
If the command you want to use has multiple options, you can either enter the options individually or grouped together, as shown in this example. These two commands are identical.
The following table lists the ALOM shell commands and briefly describes what these commands do.
|
Sets the date and time, when the managed operating system is not running. |
||
|
setdefaults [-y] [- a] |
Resets all ALOM configuration parameters to their default values. The -y option enables you to skip the confirmation question. The -a option resets the user information to the factory default (one admin account only). |
|
|
Runs the interactive configuration script. This script configures the ALOM configuration variables. |
||
|
showplatform [-v] |
Displays information about the host system's hardware configuration, and whether the hardware is providing service. The -v option displays verbose information about the displayed component(s). |
|
|
Displays information about the FRUs (field-replaceable units) in a host server. |
||
|
showusers [-g] |
Displays a list of users currently logged in to ALOM. The display for this command has a similar format to that of the UNIX command who. The -g option pauses the display after the number of lines you specify for lines. |
|
|
showsc [-v] |
Displays the current NVRAM configuration parameters. The -v option is needed for full version information. |
|
|
Displays the ALOM set date. The Solaris Operating Environment and ALOM time are synchronized, but ALOM time is expressed in UTC (Coordinated Universal Time) rather than local time. |
||
|
Displays a list of all user accounts, permission levels, and whether passwords are assigned. |
||
|
userdel [-y] |
Deletes a user account from ALOM. The -y option enables you to skip the confirmation question. |
|
|
showlogs [-v] |
Displays the history of all events logged in the ALOM event buffer. |
|
|
consolehistory [-v] [boot | run] |
Displays the host server console output buffers. The -v option displays the entire contents of the specified log. |
|
|
Displays the environmental status of the host server. This information includes system temperatures, power supply status, front panel LED status, hard disk drive status, fan status, voltage and current sensor status, and rotary switch position. |
||
|
shownetwork [-v] |
Displays the current network configuration information. The -v option shows additional information about your network, including information about your DHCP server. |
|
|
console [-f] |
Connects to the host system console. The -f option forces the console write lock from one user to another. |
|
|
break [-y] |
Drops the host server from running the Solaris Operating Environment into OpenBoot PROM or kadb. |
|
|
bootmode [skipdiag | diag | reset_nvram | normal | bootscript="string"] |
Controls the host server OpenBoot PROM firmware method of booting. |
|
|
Updates the ALOM firmware. This command downloads main and bootmon firmware images to ALOM. |
||
|
reset[-y] [-x] |
Generates a hardware reset on the host server. The -x option generates an XIR (externally initiated reset). The -y option enables you to skip the confirmation question. |
|
|
poweroff [-y] [-f] |
Removes the main power from the host server. The -y option enables you to skip the confirmation question. The -f option forces an immediate shutdown. |
|
|
setalarm[critical| major|minor|user] [on|off] |
||
|
setlocator [on/off] |
Turns the Locator LED on the server on or off. This function is available only on host server that have Locator LEDs. |
|
|
Displays the current state of the Locator LED as either on or off. This function is available only on host servers that have Locator LEDs. |
||
|
Displays information about the FRUs (field-replaceable units) in a host server. |
||
|
removefru [-y] [FRU] |
Prepares a FRU (for example, a power supply) for removal, and illuminates the host system's OK-to-Remove indicator light. The -y option enables you to skip the confirmation question. |
|
|
Displays a list of all ALOM commands with their syntax and a brief description of how each command works. |
||
|
resetsc [-y] |
Reboots ALOM. The -y option enables you to skip the confirmation question. |
|
|
showlogs [-v] |
Displays the history of all events logged in the ALOM event buffer. |
|
|
Displays the ALOM set date. The Solaris Operating Environment and ALOM time are synchronized, but ALOM time is expressed in UTC (Coordinated Universal Time) rather than local time. |
||
|
Displays a list of all user accounts, permission levels, and whether passwords are assigned. |
||
|
userdel [-y] |
Deletes a user account from ALOM. The -y option enables you to skip the confirmation question. |
|
The following pages provide full descriptions of the ALOM shell commands in alphabetic order.
Use the bootmode command to control the behavior of the host server's firmware while the host server is initializing or after you reset the server.
The bootmode setting overrides the server's OpenBoot PROM Diagnostics diagswitch?,post-trigger, and obdiag-trigger settings immediately after the next server reset. If ALOM does not detect a server reset after 10 minutes, ALOM ignores the command and then clears the bootmode setting and returns to normal.
The bootmode reset_nvram command option sets the OpenBoot NVRAM (non-volatile read-only memory) variables to default settings. The diag-switch? default does not take effect until the next server reset. This is because OpenBoot has previously taken a snapshot of the diag node of the system. This snapshot consists of rotary switch position, diag-switch? value, and bootmode diag/skip_diag overrides. Once the diag node is set, it remains in effect until the next server reset.
|
Note - You must have r level user permission to use this command. Refer to userperm for more information. |
All bootmode command options require that you reset the host server within 10 minutes after issuing the command. If you do not issue the poweroff and poweron commands or the reset command within 10 minutes, the host server ignores the bootmode command and changes the bootmode setting back to normal. Refer to poweroff, poweron, and reset for more information.
1. At the sc> prompt, type the following command:
Where option(s) is the desired option, if any (skip_diag, diag, reset_nvram, normal, or bootscript = "string").
2. Type either poweroff and then poweron (preferred), or reset.
sc> bootmode skip_diag sc> poweroff Are you sure you want to power off the system [y/n]? y SC Alert: Host system has shut down. sc> poweron |
If you use the bootmode diag option, POST (power-on self test) runs after the next reset, regardless of the OpenBoot PROM post-trigger setting. OpenBoot diagnostics tests also run after the next reset, regardless of the obdiag-trigger setting (provided that the OpenBoot PROM diag-script setting is not set to none).
If you use the bootmode command without specifying any option, ALOM displays the currently selected boot mode and the time when it will expire.
The bootmode command uses the following options:
|
Forces the server to skip diagnostics. After you issue the bootmode skip_diag command, you must issue the poweroff and poweron commands within 10 minutes. |
|
|
Forces the server to run full POST (power-on self-test) diagnostics. After you issue the bootmode diag command, you must issue the poweroff and poweron commands within 10 minutes. |
|
|
Resets all of the parameters in the host system's OpenBoot PROM NVRAM (nonvolatile read-only memory) settings to the factory default values. You must reset the server within 10 minutes. Refer to reset. |
|
|
Results in a normal boot. The server runs low-level diagnostics. After you issue bootmode normal, you must reset the server. Refer to reset. |
|
|
Controls the host server OpenBoot PROM firmware method of booting. It does not affect the current bootmode setting. string can be up to 64 bytes in length. You can specify a bootmode setting and set the bootscript within the same command. For example: sc> bootmode reset_nvram bootscript = "setenv diag-switch? true" SC Alert: SC set bootmode to reset_nvram, will expire 20030305211833 SC Alert: SC set bootscript to "setenv diag-switch? true" After the server resets and OpenBoot PROM reads the values stored in the bootscript, it sets the OpenBoot PROM variable diag-switch? to the user requested value of true. Note: If you set bootmode bootscript = "", ALOM sets the bootscript to empty. To view the bootmode settings, do the following: |
Use the break command to bring the server to the OpenBoot PROM prompt (ok). If you have configured the kadb debugger, then the break command brings the server into debug mode.
Make sure that the server front panel rotary switch is not in the Locked position, and that the system console is directed to ALOM. SeePlatform-Specific Information for further information. If the front panel rotary switch is in the Locked position, ALOM returns the error message Error: Unable to execute break as system is locked.
|
|
Note - You must have c level user permission to use this command. Refer to userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where option is -y, if desired.
After you type the break command, the server returns the ok prompt.
The break command uses one option: -y.
If you specify -y, the break occurs without first asking: Are you sure you want to send a break to the system [y/n]?
Use the console command to enter console mode and to connect to the system console from the ALOM command shell. When you use this command, the system displays a standard Solaris login prompt. To exit the system console and return to the ALOM command shell, type #. (pound-period).
Although multiple users can connect to the system console from ALOM, only one user at a time has write access to the console. Any characters that other users type are ignored. This is referred to as a write lock, and the other user sessions view the console session in read-only mode. If no other users have access to the system console, then the user entering the console session first obtains the write lock automatically by executing the console command. If another user has the write lock, you can use the -f option to force the console to give you the write lock.This forces the other user's connection into read-only mode.
|
Note - Before you use the -f option, you need to configure both OpenBoot PROM and Solaris Operating Environment variables on the host server. See To Configure the -f Option for help in configuring OpenBoot PROM and the Solaris Operating Environment. |
|
Note - You must have c level user permission to use this command. Refer to userperm for information on setting user permissions. |
1. At the sc> prompt, type the following command:
Where option is the option(s) you want to use, if any.
The Solaris system prompt is then displayed.
|
Note - The Solaris system prompt that appears depends on the default Solaris shell on the host server. Refer to Shell Prompts |
2. To return to the sc> prompt from the Solaris system prompt, type the escape character sequence.
The default sequence is #. (pound-period).
If the admin account has the write lock, ALOM returns the following messages at the console command:
If you do not have the write lock, ALOM returns a different message at the console command as shown in this example:
If you do not have the write lock and you use -f option with the console command, ALOM returns a message at the console command that is similar to the following:
The console command uses one option: -f. This option forces ALOM to release the write lock from another user and assign it to your console session. This places the other user's console session in read-only mode. Using this option returns the following message:.
Warning: User username currently has write permission to this console and forcibly removing them will terminate any current write actions and all work will be lost. Would you like to continue [y/n]? |
At the same time, the user who has the write lock receives the following message:
Before you use the -f option with the console command, you must configure both OpenBoot PROM and the Solaris Operating Environment on your host server.
1. To configure the OpenBoot PROM variable, type the following command at the ok prompt:
For instructions on how to reach the ok prompt, refer to the Administration Guide for your server.
2. Next, you need to configure the Solaris Operating Environment. Log in as root and type the following commands at the superuser prompt. Type the second command all on one line, even though it appears on three lines in the example.
# pmadm -r -p zsmon -s ttya # pmadm -a -p zsmon -s ttya -i root -fu -m "/dev/term/a:I::/usr/bin/login::9600:ldterm,ttcompat:ttya login\: ::tvi925:n:" -v 1 |
Use the consolehistory command to display system console messages logged in ALOM buffers. You can read the following system console logs:
Each buffer can contain up to 64 Kbytes of information.
If ALOM senses a host server reset, it begins to write that data into the boot log buffer. When the server senses that the Solaris Operating System is up and running, ALOM switches the buffer to the run log.
|
Note - You must have c level user permission to use this command. See userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where logname is the name of the log you want to display (boot or run). If you type the consolehistory command without an option, ALOM returns the last 20 lines of the run log.
The consolehistory command uses the following options for both logs. You can use the -g option in combination with the -b, -e, or -v options. If you do not specify the -g option, the screen output will not pause.:
Use the flashupdate command to install a new version of the ALOM firmware from a location that you specify. The values you enter for command options specify the IP address of the site from which you download and the path at which the firmware image is located.
You can find the links to the download sites on the ALOM product page at: http://www.sun.com/servers/alom.html
There are two types of ALOM firmware images: the main firmware and the bootmon (boot monitor) firmware. The bootmon firmware is the low-level bootstrap image. Be sure to locate the correct image when preparing to use the flashupdate command.
|
Caution - Do not use the scadm resetrsc command while a firmware update is in progress. If you need to reset ALOM, wait until after the update is complete. Otherwise, you could corrupt the ALOM firmware and render it unusable. For more information see scadm resetrsc. |
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions. |
To use this command, you need to know the following:
If you do not have this information, ask your network administrator. Before you start, if your server has a front panel rotary switch, make sure that the rotary switch is in the Normal (unlocked) position. If you use this command with the rotary switch in the Secure (locked) position, the firmware will not update. For more information about the front panel rotary switch, refer to your server's documentation.
1. At the sc> prompt, type one of the following commands. Substitute the IP address of the server where the firmware image is stored for ipaddr, and the path name for pathname.
|
Note - The path you use for pathname is /usr/platform/ platform-name/lib/images/(alommainfw|alombootfw). To find the correct value for platform-name, use the uname -i command. See To Set Your Path to the scadm Utility for help. |
2. When prompted, type your username and password, which are based on your UNIX or LDAP user name and password and not your ALOM username and password.
After you type your user name and password, the download process continues. As the download process progresses, a series of periods appear across your screen. (If you selected the -v option, ALOM returns status messages as the download process occurs.) When the download process is finished, ALOM displays the message: Update complete.
3. Type the resetsc command to reset ALOM.
See resetsc for details.
For example (replace xxx.xxx.xxx.xxx with a valid IP address):
The flashupdate command uses the following options.
Use the help command to display a list of all ALOM commands and the syntax for each.
|
Note - You do not need user permissions to use this command. |
Where command-name is the name of the specific command.
sc> help poweron This command applies power to the managed system or FRU and turns off ok-2-remove LED on FRU with FRU option. sc> |
The following example shows the output you see when you type help without specifying a command.
Use the logout command to end your ALOM session and close your ALOM serial or Telnet connection.
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
Use the password command to change the ALOM password for the account to which you are currently logged in. This command works like the UNIX passwd(1) command.
|
Note - This command enables you to change the password for your own ALOM account. You do not need user permissions to use this command. If you are an administrator and want to change a user account's password, use the userpassword command. See userpassword for more information. |
At the sc> prompt, type password.
When you use this command, ALOM prompts you for your current password. If you enter the password correctly, it prompts you twice to enter the new password.
sc> password password: Changing password for username Enter current password: ****** Enter new password: ****** Re-enter new password: ****** sc> |
Passwords have the following restrictions:
Use the poweroff command to power off the host server to standby mode. If the server is already powered off, this command has no effect. However, ALOM is still available when the server is powered off, since ALOM uses the server's standby power. Some environmental information is not available when the server is in standby mode.
|
Note - You must have r level user permission to use this command. See userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where option(s) is the desired option(s), if any.
If you type the poweroff command without any options, the command initiates a graceful shutdown of the Solaris Operating System, similar to one of the Solaris commands shutdown, init, or uadmin.
It can take up to 65 seconds for the poweroff command to completely shut down the system. This is because ALOM attempts to wait for a graceful shutdown to complete before the system is powered off.
|
Note - After the poweroff command shuts down the system, ALOM issues the following message: |
Wait until you see this message before powering the system back on.
The poweroff command uses the following options. You can use these two options together. Refer to Entering Command Options.
Use the poweron command to power on the server. If the host server's rotary switch is in the Locked position, or if the server is already powered on, this command has no effect.
|
Note - You must have r level user permission to use this command. Refer to userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
|
Note - If you have just used the poweroff command to power off the host server, ALOM issues the following message: |
Wait until you see the message before powering the system back on.
To turn on power to a specific FRU (field-replaceable unit) in the server, type the following command:
Where fru is the name of the FRU you want to power on.
For example, to turn power on to Power Supply 0, type:
The poweron command uses one option: fru.
Specifying the fru option powers on the specified FRU, (for example, you can use this command when a power supply is replaced in the host server.) ALOM supports the following FRUs.
|
Powers on Power Supply 2 in the host server.[1] |
|
|
Powers on Power Supply 3 in the host server.* |
Use the removefru command to prepare a FRU (field-replaceable unit) for removal and to illuminate the corresponding OK-to-Remove LED on the host server. For information about the location of the OK-to-Remove LED, refer to your server's documentation.
At the sc> prompt, type the following command:
Where fru is the name of the FRU you want to prepare for removal.
For example, to prepare Power Supply 0 for removal, type:
The removefru command has one option: fru.
Specifying the fru option prepares the specified FRU for removal. ALOM supports the following FRUs.
|
Prepares Power Supply 2 in the host server for removal.[2] |
|
|
Prepares Power Supply 3 in the host server for removal.* |
Use the reset command to force the host server to reset immediately. The server reboots using the options you specified (if any) in the bootmode command. Refer to bootmode. Note that reset does not perform a graceful shutdown of the system, and you might lose data. When possible, reset the server through the Solaris Operating System instead.
If the OpenBoot PROM variable auto-boot? is set to false, you might need to boot the server into Solaris to resume operation.
|
|
Note - You must have r level user permission to use this command. Refer to userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where option(s) is the desired option(s), if any.
The reset command uses the following two options. You can use these two options together. Refer to Overview of the ALOM Command Shell.
Use the resetsc command to perform a hard reset of ALOM. This terminates all current ALOM sessions.
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions. |
1. To perform a reset, type the following command:
Where option is -y, if desired.
ALOM responds with the following message:
2. Type y to proceed, or n to exit without resetting ALOM.
The resetsc command uses one option: -y
If you use the -y option, the reset proceeds without first asking you to confirm the reset.
Use the setalarm command to control the Netra server alarms (four dry contact alarm relays and four corresponding LED indicators).
You can set or clear these alarms depending on the system status.
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions |
At the sc> prompt, type setalarm and the option (critical, major, minor, or user), followed by on or off.
For example, to turn the critical alarm on type:
Use the setdate command to set the current ALOM date and time.
When the server boots, it sets the current ALOM date and time. The server also periodically sets the ALOM date and time while running. If you use the setdate command while the server is starting or running, ALOM returns the following error message:
The setdate command only works when the server is in OpenBoot PROM or powered off.
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
This command accepts settings for the month, day, hour, minute, century, year, and second. If you omit the month, day, and year, ALOM applies the current values as defaults. You can also omit the century value and the value for seconds in the time.
|
Note - Your server uses local time, but ALOM uses Coordinated Universal Time (UTC). ALOM does not accept time zone conversions or daylight time changes. |
This example sets the time to September 16, 2002, at 21:45 (9:45 PM) (Coordinated Universal Time).
This example sets the time to September 16, at 9:45 PM of the current year (Coordinated Universal Time).
This example sets the time to 9:45 PM of the current month, day, and year (Coordinated Universal Time).
The setdate command uses the following options.
Use the setdefaults command to set all ALOM configuration variables back to their factory default values. The -a option sets the ALOM configuration and all user information back to the factory default value.
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions. You need to set the password to execute permission-level commands. |
1. At the sc> prompt, type the following command:
Where option(s) is the desired option(s), if any.
The Please reset your ALOM message is displayed.
2. Type the resetsc command to reset ALOM.
When ALOM resets, it uses the factory default values. For example:
sc> setdefaults Are you sure you want to reset the SC configuration [y/n]? y Note: Please reset your ALOM to make the new configuration active. |
sc> setdefaults -a Are you sure you want to reset the SC configuration and users [y/n]? y Note: Please reset your ALOM to make the new configuration active. |
The setdefaults command uses the following options.
Use the setlocator command to turn the host server's Locator LED on or off. For more information about the Locator LEDs, refer to the server's documentation.
|
Note - This command works only with server models that have front-panel Locator LEDs. |
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
Where option is either on or off.
To show the state of the Locator LED, use the showlocator command. Refer to showlocator for more information.
This setlocator command has two options: on and off.
The ALOM software comes preinstalled on your host server, and is ready to run as soon as you apply power to the server. If you want to customize the ALOM configuration for your installation, you set up the initial configuration with the setupsc command. If you need to update a setting after your initial ALOM configuration, use the setsc command. For information about your configuration, see ALOM Configuration Steps; for more about the setupsc command, see setupsc.
|
Note - You can create a script to run the setsc command and use it to configure multiple variables (for example, all of the event variables). |
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions. |
Make sure that you have your configuration table with you as you run the command, and that it includes your planned values for each of the configuration variables you plan to change. See Configuration Worksheet and Using ALOM Configuration Variables for more information.
At the sc> prompt, type the following command:
Substitute the configuration variable and the variable's value for variable and value.
Where xxx.xxx.xxx.xxx is a valid IP address.
If the variable you are configuring requires more than one value, type the values, using spaces to separate them. Because the setsc command is designed to be used in scripts as well as at the command prompt, it does not return any information after you enter a value for a variable.
If you type setsc without including a configuration variable, ALOM returns a list of the variables you can configure.
Use the setupsc command to customize ALOM.
Make sure that you have your configuration table with you as you run the command, and that it includes your planned values for each of the configuration variables you plan to change. See Configuration Worksheet and Using ALOM Configuration Variables for more information.
|
Note - You must have a level user permission to use this command. Refer to userperm for information on setting user permissions. |
1. At the sc> prompt, type the following command:
2. To exit the script, do one of the following:
For example, the script starts as follows:
sc> setupsc Entering interactive script mode. To exit and discard changes to that point, use Ctrl-C or to exit and save changes to that point, use Ctrl-Z. |
Answer the interactive questions to customize ALOM.
The script asks you whether you want to enable each set of configuration variables. See Using ALOM Configuration Variables for help.
If you type y or press Return to accept the default, the setupsc script then prompts you to enter values for the variables. The script helps you set up the following types of variables:
|
Note - You do not need to set or adjust the serial interface variables. These variables are automatically set for you by the host server. |
Use the showdate command to show the current ALOM date and time.
Note that the time ALOM shows is Coordinated Universal Time (UTC), and that your host server shows your local date and time.
|
Note - You do not need user permissions to use this command. |
At the sc> prompt type the following command:
To change the ALOM date and time, use the setdate command. See setdate.
|
Note - When the server boots, it synchronizes with the current ALOM date and time. |
Use the showenvironment command to display a snapshot of the server's environmental status.The information this command can display includes system temperatures, hard disk drive status, power supply and fan status, front panel LED status, rotary switch position, voltage and current sensors, alarm status, and so on. The output uses a format similar to the UNIX command prtdiag (1m).
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
The display output differs according to your host server's model and configuration. Some environmental information might not be available when the server is in standby mode.
The following example show sample output when the host server is powered on. Note that some information shown in the following example may be different for your Netra system, such as the number of power supplies and hard drives.
The following example shows the environmental information you might see when the host server is powered off.
Use the showfru command to display the contents of all FRU PROMs (field- replaceable units programmable read-only memory) in the host server. The output uses a format similar to that of the Solaris Operating Environment prtfru command.
At the sc> prompt, type the following command:
The following example shows sample output for the showfru command.
Use the showlocator command to view the state of the host server's Locator LED (on or off). For more information about the Locator LEDs, refer to your server's documentation.
|
Note - This command works only with servers that have the front panel Locator LEDs. |
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
To change the state of the Locator LED, use the setlocator command. Refer to setlocator.
Use the showlogs command to display the history of all events logged in the ALOM event buffer. These events include server reset events and all ALOM commands that change the state of the system (such as reset, poweroff, and poweron). See reset, poweroff, and poweron.
Each event recorded in the log has the following format:
date hostname: message
date signifies the time at which the event occurred, as recorded by ALOM. hostname is the name of the host server, and message is a short description of the event.
If you use the showlogs command without any option, ALOM displays the last 20 lines of the event log.
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
Where option(s) is the desired option(s), if any.
The following example shows an event log entry:
|
Note - Timestamps shown in the ALOM event log reflect UTC (Coordinated Universal Time). |
This example shows the output of the showlogs command with the -v option. The -v option displays the persistent event log. The persistent event log is comprised of the contents of NVRAM.
The showlogs command uses four options. You can use the -g option in combination with the -b, -e, or -v options. If you do not specify the -g option, the screen output will not pause.
Use the shownetwork command to display the current ALOM network configuration.
|
Note - If you changed the ALOM network configuration since the last time you booted ALOM, the output from this command might not show the updated configuration information. Reboot ALOM to see the changed configuration. See Redirecting the System Console From ALOM to Other Devices for information on rebooting ALOM. |
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
Where option is -v, if desired.
The command output appears similar to the following example, with the actual IP addresses, netmask, and Ethernet addresses in your network configuration in place of xxx.xxx.xxx.xxx.
sc> shownetwork SC network configuration is: IP Address: XXX.XXX.XXX.XXX Gateway address: XXX.XXX.XXX.XXX Netmask: XXX.XXX.XXX.XXX Ethernet Address: XX:XX:XX:XX:XX:XX |
The shownetwork command uses one option: -v.
If you type shownetwork -v, ALOM returns additional information about your network, including information about your DHCP (Dynamic Host Configuration Protocol) server, if you have one configured. See Configuring Your Network Using DHCP.
Use the showplatform command to display information about the host server's platform ID and status.
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type showplatform.
The host server returns information similar to the following:
sc> showplatform SUNW,Netra-x40 Domain Status ------ ------ vsp75-202-priv OS Running |
Use the showsc command to display information about the ALOM software configuration and firmware version.
|
Note - You do not need user permissions to use this command. |
Where param is the param option. See Using ALOM Configuration Variables for further information.
For example, xir is the current value for the sys_autorestart configuration variable:
For more on sys_autorestart, refer to sys_autorestart.
The -v option provides additional details about the specified variable.
For example, to display the ALOM version, type either of the following:
The showsc command uses the following options. If you type showsc without using any options, ALOM displays all of its configuration variables.
Use the showusers command to display the list of users currently logged in to ALOM. The list includes details such as the type of connection, the duration of each user's session, the IP address of the client (if the user is using a network connection), and whether the user has the host system console's write lock (this determines whether the user can type input in a console session, or just monitor the console stream in read-only mode).
|
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
Where option is -g lines, if desired.
If a user has more than one session running, each session is listed.
The showusers command uses one option: -g lines.
This option pauses the display after the number of lines you specify for lines. After each pause, ALOM returns the message:
If ALOM encounters an alert condition or an event, it displays the information after this message. Press any key to continue, or press q to exit the display and return to the sc> prompt.
Use the useradd command to add a user account to ALOM.
|
Note - You must have u level user permission to use this command. Refer to userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where username is the name of the user whose account you want to add to ALOM.
username has the following restrictions:
You can add a maximum of 15 unique user accounts to ALOM.
To assign a password to a user name, use the userpassword command. See userpassword.
To set permission levels for a user name, use the userperm command. See userperm.
Use the userdel command to delete an ALOM user account. Once the account is deleted, the deleted user's configuration information can never be recovered.
If the user name you specify is not on the list of ALOM users, ALOM returns an error message. Likewise, if there is only one user on the list, ALOM will not delete that user account.
|
Note - You must have u level user permission to use this command. Refer to userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where useracct is the name of the user account you want to delete.
The userdel command uses one option: -y.
If you specify the -y option, userdel deletes the account without prompting the following confirmation question:
Use the userpassword command to change the password for the specified user account. This command is for administrators who need to change user passwords on ALOM, but who might not know what the user account passwords are. If you are trying to change the password on your own ALOM account, use the password command. See password.
|
Note - You must have u level user permission to use this command. See userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where username is the name of the user account for which you want to change the password.
When you use this command, ALOM does not prompt you for the existing password.
Passwords have the following restrictions:
Use the userperm command to set or change permission levels for a specified user account. By default, the initial setup procedure creates the ALOM admin account. This account cannot be deleted, nor can you change the user permissions for the account.
All users can read ALOM information, but you need authorization to perform ALOM functions or change settings. There are four permission levels that increase a user's authorization. You can specify zero through four permission levels.
|
Administrative. This user is authorized to change the state of ALOM configuration variables and reboot ALOM. Refer to Using ALOM Configuration Variables and resetsc. |
|
|
User administration. This user is authorized to add users and delete users, change user permissions, and change the authorization level of other users. Refer to useradd and userdel. |
|
|
Console permission. This user is authorized to connect to the host server system console. Refer to console. |
|
|
Reset/power permission. This user is authorized to reset the host server, and power the server on and off. Refer to reset, poweron, and poweroff. |
If you do not assign a permission level to the specified user (that is, you assign zero permission levels), then that user has read-only permission. This is the default level for a new ALOM user account.
To see a user's permission levels, use the usershow command. See usershow.
|
Note - You must have u level user permission to use this command |
At the sc> prompt, type the following command:
Where username is the name of the user to whom you want to assign permissions, and permission(s) is the permission(s) you want to assign to that user.
For example, to assign c and r user permissions to user msmith, type the following at the ALOM command prompt:
To see a user's permission levels, use the usershow command.
A user with read-only permission can use only the following commands:
A user who has read-only permissions would appear similar to the user jeremy in the following example:
sc> usershow Username Permissions Password --------------- ----------------- ------------ admin cuar Assigned jeremy ---- Assigned |
Use the usershow command to display a specified user's ALOM account, along with each user's permissions and whether a password has been assigned. Refer to userperm and userpassword.
If you do not enter a username, usershow displays all of the ALOM accounts.
|
Note - You must have u level user permission to use this command. See userperm for information on setting user permissions. |
At the sc> prompt, type the following command:
Where username is the name of the specified user.
sc> usershow Username Permissions Password? admin cuar Assigned wwilson cuar Assigned jadams --cr None |
| Sun Advanced Lights Out Manager Software User's Guide | 817-5481-11 |
|
Copyright © 2004, Sun Microsystems, Inc. All rights reserved.
Entering Command Options