A P P E N D I X A |
Troubleshooting |
This chapter consists of tables of the most common issues you may experience with ALOM, shell error messages you see in ALOM, and troubleshooting suggestions. It contains the following sections:
TABLE A-1 provides a list of common ALOM difficulties and their solutions.
Perform the following actions to troubleshoot ALOM log-in problems:
|
|
ALOM supports a total of four concurrent Telnet or eight concurrent SSH sessions per server. When the maximum number of Telnet or SSH sessions are active, further attempts to connect using the telnet or ssh commands will receive a connection closed error. The following example shows system messages for the UNIX operating environment: |
|
First, check whether ALOM is working or there is an Ethernet configuration problem. You can also perform the following actions to troubleshoot Ethernet problems:
|
|
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. |
|
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. |
|
Specific user permissions are required to perform functions. Check your permission level. Refer to userperm. In addition, the following problems might exist:
|
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:
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 controls the flow rate of the system console to match the flow-rate of the user session holding the write lock. This ensures that the user session with the write lock does not lose data. However, this arrangement can cause data loss for user sessions with read-only console access. For example, if the user session with the write lock is connected over the fast NET MGT port and a session with reader is connected over the slow SERIAL MGT port, the console can produce output at a rate that could overrun the capacity of the reader session. To reduce the likelihood of such console data loss, each console reader session is allocated 65535 characters of buffer space.
This section contains information about certain types of error messages you might see when using the ALOM command shell:
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.
ALOM reports the following general errors.
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. |
||
You tried to delete the admin user account from ALOM. ALOM does not permit you to delete this account. |
||
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. |
||
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. |
|
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
|
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. |
|
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. |
|
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 |
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. |
|
During execution of the userpassword command, a SEEPROM error occurred. Try executing the command again. |
||
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. |
||
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. |
||
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. |
||
You entered an incorrect password. Enter the password again. |
||
The user you are trying to add already has an ALOM account on this server. |
The following error messages appear when ALOM detects problems with field-replaceable units (FRUs).
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.
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:
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. Your selection: |
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. Your selection: |
5. Enter r to return to the ALOM boot process.
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.
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.