C H A P T E R 5 |
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 or Secure Shell 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. |
Entering Command Options |
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.
TABLE 5-1 lists the ALOM shell commands in alphabetical order within function, briefly describes what these commands do, and shows where to get more information.
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.
To Use the bootmode Command |
Note - You must have reset/power (r) level user permission to use this command. See 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. See 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 poweroff and 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 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 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. See reset. |
|
Results in a normal boot. The server runs low-level diagnostics. After you issue bootmode normal, you must reset the server. See 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. See Server-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.
To Use the break Command |
Note - You must have console (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 option is -y or -c, if desired.
After you type the break command, the server returns the ok prompt.
The break command uses the following options.
Goes immediately to the Solaris OS console upon command completion. |
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 must configure both OpenBoot PROM and Solaris Operating System variables on the host server. See To Configure the -f Option for help in configuring OpenBoot PROM and the Solaris Operating System. |
To Use the console Command |
Note - You must have console (c) level user permission to use this command. See 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. See 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:
After you reset ALOM, the serial connection times out on the login prompt after one minute and takes the console write lock automatically if no one else has it by then. If you use the console -f command after resetting ALOM, you will receive the message immediately above with User <auto>. Type y for yes, if you want to obtain the console write lock. See Resetting ALOM, resetsc, and showusers for more information.
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:
To Configure the -f Option |
Before you use the -f option with the console command, you must configure both OpenBoot PROM and the Solaris Operating System 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. To configure the Solaris OS, log in as superuser 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 kilobytes (KB) 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 OS is up and running, ALOM switches the buffer to the run log.
Each buffer can contain up to 64 kilobytes of information. These buffers are in ALOM RAM memory and are not persistent across an ALOM reboot or alternating current (AC) power-down.
The Sun Fire V215, V245, and V445 servers maintain a one-megabyte persistent log for console messages. There is no distinction between boot and run-time messages in the persistent log. The RAM-based boot log and run log are also maintained on these servers for backward compatibility purposes. See the -p option in TABLE 5-4.
To Use the consolehistory Command |
Note - You must have console (c) level user permission to use this command. See userperm for information about setting user permissions. |
At the sc> prompt, type the following command:
Where logname is the name of the log you want to display:
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 does not pause.
Use the dumpconfig command to save your current ALOM configuration to a remote file server using FTP. This facilitates the setup of new ALOM installations and recovery to a known ALOM configuration.
To Use the dumpconfig Command |
At the sc> prompt, type the following command:
Where ipaddr specifies the IP address of the server to store the log file, and pathname specifies a path name including the configuration file name to be saved.
The dumpconfig command uses the following options.
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
For Sun Fire V215, V245, or V445 servers only, there is one firmware image: alomfw.
For all other servers, there are two firmware images: the main firmware (alommainfw) and the boot monitor firmware (alombootfw). The boot monitor 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 resetrsccommand 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. |
To Use the flashupdate Command |
Note - You must have administrative (a) level user permission to use this command. See userperm for information on setting user permissions. |
To use this command, you must know the following:
If you do not have this information, ask your network administrator. Before you start, if your server has a front panel keyswitch, operation mode switch, or rotary switch, make sure that the switch is in the Normal (unlocked) position. If you use this command with the switch in the Secure (locked) position, the firmware will not update. For more information about the front panel 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.
For Sun Fire V215, V245, or V445 servers only:
Note - The path you use for pathname is /usr/platform/ platform-name/lib/images/alomfw). To find the correct value for platform-name, use the uname -i command. See To Set Your Path to the scadm Utility for help. |
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.
To Use the help Command |
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> |
On Sun Fire V210, V240, V250, and V445 servers, when you type help without specifying a command, you see output similar to CODE EXAMPLE 5-1, depending on your platform.
On other Sun Fire and Netra servers, when you type help without specifying a command, you see output similar to CODE EXAMPLE 5-2, depending on your platform.
Use the logout command to end your ALOM session and close your ALOM serial, Telnet, or Secure Shell connection.
To Use the logout Command |
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.
To Use the password 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.
To Use the poweroff Command |
Note - You must have reset/power (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. See Entering Command Options.
Use the poweron command to power on the server. If the host server's keyswitch, operation mode switch or rotary switch is in the Locked position, or if the server is already powered on, this command has no effect.
To Use the poweron Command |
Note - You must have reset/power (r) level user permission to use this command. See 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 two options:
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.
To Use the removefru Command |
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. Note that some servers have fewer than four power supplies, so refer to your system documentation before executing these commands to verify that you are preparing the proper power supply 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. See 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.
To Use the reset Command |
Note - You must have reset/power (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 options are the desired options, if any.
The reset command uses the following three options. You can use the -x and -y options together. See Overview of the ALOM Command Shell.
Use the resetsc command to perform a hard reset of ALOM. This terminates all current ALOM sessions.
Note - After you reset ALOM, the serial connection times out on the login prompt after one minute and automatically obtains the console write lock. The user name shows as auto in the showusers and console -f commands. Use the console -f command to regain the console write lock. See Resetting ALOM, console, and showusers for more information. |
To Use the resetsc Command |
Note - You must have administrative (a) level user permission to use this command. See userperm for information on setting user permissions. |
1. To perform a reset, type the following command:
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 restartssh command to restart the SSh server after you have generated new hosts keys using the ssh-keygen command. This reloads the keys into the server's dedicated data structure in memory.
To Use the restartssh Command |
At the sc> prompt, type the following command:
Where options are the options shown in TABLE 5-11.
The restartssh command uses the following options.
Use the restoreconfig command to restore an ALOM configuration from a remote file server using FTP. This facilitates set up of new ALOM installations and recovery to a known ALOM configuration.
To Use the restoreconfig Command |
1. At the sc> prompt, type the following command:
Where options are the options shown in TABLE 5-12.
2. If encryption is being used, enter the password for decryption when prompted.
You must give the same password you used when you saved and encrypted the configuration data.
The restoreconfig command uses the following options.
If the -y option is not used, then you might be prompted for the following interactive responses. This is to prevent you from accidently overwriting the current user accounts if you are not familiar with the user accounts in the restore file. If the -y option is specified, then all prompts shown in TABLE 5-13 are automatically answered with yes.
Note - This command applies to Netra 210, 240, and 440 servers only. |
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.
To Use the setalarm Command |
Note - You must have administrative (a) level user permission to use this command. See 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 works only when the server is in the OpenBoot PROM or powered off.
To Use the setdate Command |
Note - You must have administrative (a) level user permission to use this command. See 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 p.m.) in Coordinated Universal Time (UTC).
This example sets the time to September 16, at 9:45 p.m. of the current year in Coordinated Universal Time (UTC).
This example sets the time to 9:45 p.m. of the current month, day, and year in Coordinated Universal Time (UTC).
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.
To Use the setdefaults Command |
Note - You must have administrative (a) level user permission to use this command. See userperm for information on setting user permissions. You must 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 the SC (resetsc) 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.
Note - The -a option removes the admin password. This takes the configuration back to the state when the system was new out-of-box. The special admin account is the only account available. A new password must be entered during an initial login session over the serial management port. For Sun Fire V215, V245, and V445 servers, DHCP over-the-network is enabled by default. See Default DHCP Connection (Sun Fire V215, V245, and V445 Servers). |
Use the setfru command to store up to 80 characters of user-defined text in all field-replaceable unit (FRU) serial electrically erasable programmable read-only memories (SEEPROMs).
To Use the setfru Command |
To store user-defined text in the FRU SEEPROM, type the following command:
The setfru command uses one option: -c
If you use the -c option without user-defined text following it as in this example, the command clears existing data from all FRU SEEPROMs.
Note - Use this command only for Sun Fire V215, V245, or V445 servers. |
Use the setkeyswitch command to control the virtual keyswitch position of the system.
To Use the setkeyswitch Command |
Note - You must have an administrative (a) permission level to use this command. See userperm for information on setting user permissions. You must set the password to execute permission-level commands. |
At the sc> prompt, type the following command:
The setkeyswitch command uses the following options:
The OpenBoot PROM on the host should boot in the diagnostic mode. |
|
System can power itself on; however, you are prohibited from updating any of the flash devices (see flashupdate) or using the break command. |
|
Setting the virtual keyswitch to standby (stby) powers off the server. Before powering off the host server, ALOM asks for a confirmation. The -y flag answers yes to the confirmation.[1] |
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. |
To Use the setlocator Command |
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. See 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 must update a setting after your initial ALOM configuration, use the setsc command. For information about your configuration, see ALOM Configuration Steps; for more information 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). |
To Use the setsc Command |
Note - You must have administrative (a) level user permission to use this command. See 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. For example:
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.
Some variables require that the SC be rebooted before they are effective; for example, the network configuration variables. If a reboot is required after setting a variable, then a warning is issued, and you are prompted to reboot.
sc> setsc netsc_ipaddr 123.456.789 To activate this change you must reset the SC. Are you sure you want to reset the SC [y/n]? |
Use the setupsc command to customize ALOM.
To Use the setupsc Command |
Note - You must have administrative (a) level user permission to use this command. See 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.
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.
To Use the showdate Command |
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).
To Use the showenvironment Command |
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 might be different for your host 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 System prtfru command.
To Use the showfru Command |
At the sc> prompt, type the following command:
Where options are the desired options, if any.
The showfru command uses the following options.
The following example shows sample output for the showfru command.
Note - The above sample is only a partial display. The showfru output can be quite long. |
Use the showkeyswitch command to display the current virtual keyswitch position of the system.
To Use the showkeyswitch Command |
Note - Use this command only for Sun Fire V215, V245, or V445 servers. You do not need user permissions to use this command. |
At the sc> prompt, type the following 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. |
To Use the showlocator Command |
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. See 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.
To Use the showlogs Command |
Note - You do not need user permissions to use this command. |
At the sc> prompt, type the following command:
Where options are the desired options, if any.
The following example shows an event log entry:
Note - Timestamps shown in the ALOM event log reflect Coordinated Universal Time (UTC). |
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, or -p (Sun Fire V215, V245, and V445 servers only) options. If you do not specify the -g option, the screen output does 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. |
To Use the shownetwork Command |
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.
To Use the showplatform Command |
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 |
If you have a Sun Fire V215, V245, or V445 server, this command also shows the Chassis Serial Number (CSN) in the output.
Use the showsc command to display information about the ALOM software configuration and firmware version.
To Use the showsc Command |
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, see 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).
To Use the showusers Command |
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 session that has system under console is the connection that has the console write lock.
If you see auto for the username as in the example following, the serial connection timed out on the login prompt and automatically took the console write lock. The username shows auto in the showusers command output entry for the serial connection. For example:
sc> showusers username connection login time client IP addr console -------------------------------------------------------------- auto serial Apr 14 10:30 system |
See Resetting ALOM, console, and resetsc for more information.
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 ssh-keygen command to generate a new set of Secure Shell (SSH) host keys and display the host key fingerprint on the system controller. The default format (rsa) of the fingerprint is as follows:
md5 1024 a3:28:0d:45:01:e4:ba:21:c8:13:90:df:4e:69:7a.5e
To Use the ssh-keygen Command |
At the sc> prompt, type the following command:
Where options are any of the options listed in TABLE 5-21.
The ssh-keygen command uses the following options.
Use the useradd command to add a user account to ALOM.
To Use the useradd Command |
Note - You must have user administration (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 whose account you want to add to ALOM. The username variable 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.
To Use the userdel Command |
Note - You must have user administration (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 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.
To Use the userpassword Command |
Note - You must have user administration (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 permission. This user is authorized to change the state of ALOM configuration variables and reboot ALOM. See Using ALOM Configuration Variables and resetsc. |
|
User administration permission. This user is authorized to add users and delete users, change user permissions, and change the authorization level of other users. See useradd and userdel. |
|
Console permission. This user is authorized to connect to the host server system console. See console. |
|
Reset/power permission. This user is authorized to reset the host server, and power the server on and off. See 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.
To Use the userperm Command |
Note - You must have user administration (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 in a similar manner 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. See userperm and userpassword.
If you do not enter a username, usershow displays all of the ALOM accounts.
To Use the usershow Command |
Note - You must have user administration (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 |
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.