TABLE A-1 provides a list of common ALOM difficulties and their solutions.
TABLE A-1 ALOM Diagnostics Problem
Can't log in to ALOM
Perform the following actions to troubleshoot ALOM log-in problems:
•Check the ALOM device name you are connecting to: (for example, bert-sc). Make sure that you have the correct ALOM name for the corresponding server.
•Check that you are using your correct ALOM username; it might not be the same as your system user name.
•Check that you are using your correct ALOM password.
Can't connect to ALOM using the telnet command
ALOM supports a total of four concurrent Telnet sessions per server. When the maximum number of Telnet sessions are active, further attempts to connect using the telnet command will receive a connection closed error. The following example shows system messages for the UNIX operating environment:
% telnet bert-sc
Connected to bert-sc. Escape character is '^]'.
Connection closed by foreign host.
Can't connect to ALOM through the Ethernet connection
First, check whether ALOM is working or there is an Ethernet configuration problem. You can also perform the following actions to troubleshoot Ethernet problems:
•Log in to ALOM through the serial management port (SERIAL MGT) and use the shownetwork command to see the current settings. Refer to shownetwork.
•Log in to another machine on the network and use the ping command to see whether ALOM is operating. Be sure to use the ALOM device's name (for instance, servername-sc), not the host server's name, as the argument to the ping command.
•Run SunVTS diagnostics to check the Ethernet connection. The external Ethernet test requires that the device be connected to a functional 10-Mbit hub.
•Run SunVTS diagnostics to check the ALOM card.
No alerts received from ALOM
Check the setting of the sc_clieventlevel variable for the ALOM command shell, and the mgt_mailalert variable for email alerts to make sure that you are receiving the proper levels of events in the specified places. Make sure that if_emailalerts is set to true, and that mgt_mailhost is set correctly for email alerts. Refer to sc_clieventlevel and mgt_mailalert.
ALOM passwords are unknown
If users have forgotten ALOM passwords or passwords are not working, re-create the passwords. Use the userpassword command (see userpassword). If no user passwords are known, see Recovering ALOM Passwords.
You can perform some ALOM functions, but not others
Specific user permissions are required to perform functions. Check your permission level. Refer to userperm. In addition, the following problems might exist:
•Cannot see console logs or access the server console using ALOM.
•Cannot put the server in to debug mode or use the ALOM break command: The server virtual keyswitch status is locked.
•The poweroff command has no effect: The server is already powered off.
•The poweron command has no effect: The server is already powered on, or the virtual keyswitch is in the Standby status.
Using ALOM to Troubleshoot Server Problems
ALOM is useful for troubleshooting a server that is not responding. If the server is responsive, connect to it and use standard troubleshooting tools such as Sun Management Center, SunVTS, and OpenBoot firmware.
If the server is not responding, log in to your ALOM account and do the following:
•Check the ALOM event log and server environmental status for problems. Refer to showfaults, showlogs, and showenvironment for more information.
•Check console logs for recent error messages. Refer to consolehistory.
•Try connecting to the system console to reboot the system. Refer to console.
About the System Console Write Lock
Although multiple users can connect to the system console from ALOM, only one user at a time has write access to the console (that is, only one user can type commands into the system console). Any characters that other users type are ignored. This is referred to as a write lock, and the other user sessions are in read-only mode. If no other users are currently logged in to the system console, then you obtain the write lock automatically when you execute the console command. To see which user has the write lock, use the showusers command. Refer to showusers for more information.
ALOM Shell Error Messages
This section contains information about certain types of error messages you might see when using the ALOM command shell:
•CLI Messages Regarding FRU State
These messages appear in response to a command you typed at the sc> prompt.
This table describes usage error messages that are displayed when you type the command using improper command syntax. Refer to the description of the command for the correct syntax.
TABLE A-2 Usage Error Messages Error Message
Error: Invalid command option. Type help to list commands.
Error: Invalid command options Usage: usage string
You typed the shell command correctly, but used an incorrect option for that command. usage string describes the proper syntax for command options. Check the command options and retype the command.
Error: Invalid configuration parameter.
You specified a nonexistent configuration variable when using the setsc or showsc command. Check the configuration variables and their values in your configuration table and retype the command.
Error: Invalid image. Please check file integrity and specified path.
An error occurred when you tried to execute the flashupdate command. Make sure that the path you specified is correct for the firmware image you want to download. If the path is correct, contact the administrator for the server where the image is located.
Error: Invalid setting for parameter param.
You specified an incorrect value for the configuration variable specified in param. Check the configuration variable you want to use and retype the command.
Error: Unable to program flash SC because keyswitch is in LOCKED position.
Your host server's virtual keyswitch has the LOCKED status. Set the keyswitch to the NORMAL status, then execute the flashupdate command again.
Error: Unable to set clock while managed system is running.
You tried to set the ALOM date and time while the host server was running. If you need to set the ALOM date and time, make sure that the system is powered off first. The Solaris OS synchronizes system time with ALOM time while the server is booting, and periodically while running.
ALOM reports the following general errors.
TABLE A-3 General Error Messages Error Message
Error adding user username
An error occurred during execution of the useradd command. This message is followed by a more detailed message that explains the nature of the error.
Error: Cannot delete admin user
You tried to delete the admin user account from ALOM. ALOM does not permit you to delete this account.
Error changing password for username
An error occurred during execution of the userpassword command. This message is followed by a more detailed message that explains the nature of the error.
Error: Inconsistent passwords entered.
During execution of the userpassword command, you typed the password differently the second time than you did the first time you were prompted. Execute the command again.
Error: invalid password entered. Password must be 6-8 characters, differ from the previous by at least 3 characters and contain at least two alphabetic characters and at least one numeric or special character.
You entered an invalid password. Refer to the password restrictions and then enter the password again.
Error: invalid username string. Please re-enter username or type 'usershow' to see a list of existing users.
You tried to specify an ALOM user account that is not on the list of user accounts. To see a list of valid user accounts, use the usershow command.
Error displaying user username
An error occurred during execution of the usershow command. This message is followed by a more detailed message that explains the nature of the error.
Error: Invalid IP address for gateway address
netsc-ipgateway and IP netmask netsc-ipnetmask.
You entered a value for the netsc-ipaddr variable that does not work with the values you specified for the netsc-ipgateway and netsc_ipnetmask variables. Check that the addresses are correct, and then run setupsc or setsc again.
netsc_ipaddr,netsc_ipgateway, setupsc, or setsc
Error: Invalid IP netmask for IP address netsc-ipaddr and IP gateway netsc-ipgateway.
You entered a value for the netsc-ipnetmask variable that does not work with the values you specified for the netsc-ipgateway and netsc-ipaddr variables. Check that the addresses are correct, and then run setupsc or setsc again.
netsc_ipgateway, netsc_ipnetmask, setupsc, or setsc
Error: Invalid IP gateway for IP address netsc-ipaddr and IP netmask netsc-ipnetmask.
You entered a value for the netsc-ipgateway variable that does not work with the values you specified for the netsc-ipnetmask and netsc-ipaddr variables. Check that the addresses are correct, and then run setupsc or setsc again.
netsc_ipgateway, netsc_ipnetmask, netsc_ipaddr, setupsc, or setsc
Error setting permission for username
An error occurred during execution of the userperm command. This message is followed by a more detailed message that explains the nature of the error.
Refer to userperm
Error: Invalid username string. Please re-enter a username of no more than 16 bytes consisting of characters from the set of alphabetic characters, numeric characters, period (.), underscore (_), and hyphen (-). The first character should be alphabetic and the field should contain at least one lower case alphabetic character.
You entered an invalid username. Review the proper syntax for user names and try again.
Error: Unable to execute break because keyswitch is in LOCKED position.
Change the status of the keyswitch and retype the break command.
Failed to get password for username
During execution of the userpassword command, a SEEPROM error occurred. Try executing the command again.
Failed to set variable to value
During execution of the setsc command, ALOM encountered a SEEPROM error.
Login attempt failed. This message appears at the login prompt.
You entered an invalid password with the userpassword command.
Invalid permission: permission
You entered an invalid user permission.
Error: Maximum number of users already configured.
This error occurs if you try to add a user account when ALOM already has the maximum of 16 accounts configured. You must delete an account before you can add another.
Passwords don't match
The two entries for a new password did not match. Enter the password again.
You attempted to execute a shell command for which you do not have the proper user permission level.
Sorry, wrong password
You entered an incorrect password. Enter the password again.
Error: User username already exists.
The user you are trying to add already has an ALOM account on this server.
CLI Messages Regarding FRU State
The following error messages appear when ALOM detects problems with field-replaceable units (FRUs).
TABLE A-4 FRU Error Messages Error Message
Error: xxx is currently powered off.
xxx is the name of the FRU to which you tried to send a command. The FRU is currently powered off. You need to turn it back on before it will accept commands.
Error: xxx is currently powered on.
xxx is the name of the FRU to which you tried to send a poweron command. The FRU is already powered on.
Error: xxx is currently prepared for removal.
xxx is the name of the FRU to which you tried to send a removefru command. The FRU is already powered off and ready for removal.
Error: Invalid FRU name.
You entered a FRU command without specifying an option, or you specified an invalid FRU name with the command. Check that you have a valid FRU name and retype the command.
ALOM Shell Commands
Recovering ALOM Passwords
For security reasons, this procedure is available only while accessing the system directly through the serial port. The procedure resets all ALOM NVRAM settings.
To Recover Your ALOM Passwords:
1. Connect to the ALOM serial port.
2. Power down the server.
Remove the power cords from both power supplies. Wait several seconds for power to discharge before reinserting the cords.
3. Press the Escape key during ALOM boot when the following text is displayed on the console:
Boot Sector FLASH CRC Test
Boot Sector FLASH CRC Test, PASSED.
Return to Boot Monitor for Handshake
After pressing the Escape key, the ALOM boot escape menu is printed:
ALOM <ESC> Menu
e - Erase ALOM NVRAM.
m - Run POST Menu.
R - Reset ALOM.
r - Return to bootmon.
4. Enter e to erase the ALOM NVRAM.
Your selection: e
ALOM NVRAM erased.
ALOM <ESC> Menu
e - Erase ALOM NVRAM.
m - Run POST Menu.
R - Reset ALOM.
r - Return to bootmon.
5. Enter r to return to the ALOM boot process.
Your selection: r
ALOM POST 1.0
Status = 00007fff
ALOM then boots and resets all NVRAM settings. You are automatically logged on as user admin with no password and no permissions. All ALOM NVRAM settings are reset to the factory defaults.