ALOM modem does not answer

Verify that cabling is set up correctly.See the if_modem variable for additional information

ALOM modem answers then immediately hangs up

Verify that if_modem variable is set to true.

ALOM modem answers but connections appear dead

1. Type the ALOM escape character #. (pound-period) to see if you can return to the sc> prompt.
2. Ensure that the serial management port speed and modem port speed are set to the same value.
3. Try disabling data compression. On many modems, this is done by using the AT&K0 modem command.

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

Trying 129.148.49.120...

Connected to bert-sc. Escape character is '^]'.

Connection closed by foreign host.

Can't connect to ALOM through the Ethernet connection

First, log in to the server as root and check whether the scadm version command succeeds. If it does, ALOM is working and there is an Ethernet configuration problem. Use the scadm show command to check whether Ethernet configuration variables are set correctly.

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.
• Use the command scadm version to check ALOM status.

No alerts received from ALOM

Check the setting of the sys_eventlevel variable for syslog, 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, log in to the server as root and use the scadm userpassword command to assign new passwords. Inform ALOM users of the new passwords. Refer to scadm userpassword.

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 rotary switch is in the Locked position.
• 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 rotary switch is in the Standby position.

Error: Invalid command option. Type help to list commands.

Help.

help

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.

setsc, showsc,

Configuration Worksheet.

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.

flashupdate.

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.

Configuration Worksheet.

Error: Unable to program flash device when system is locked.

Your host server's rotary switch is in the Locked position. Refer to the server's documentation and set the rotary switch to the Normal (Unlocked) position, then execute the flashupdate command again.

flashupdate.

Error: Unable to set clock while managed system OS 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 Operating Environment synchronizes system time with ALOM time while the server is booting, and periodically while running.

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.

useradd

Error: Cannot delete admin user

You tried to delete the admin user account from ALOM. ALOM does not allow 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.

userpassword.

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.

userpassword

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.

userpassword.

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.

usershow.

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.

usershow

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. Refer to 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.

useradd.

Error: Unable to execute break as system is locked.

The front panel rotary switch on the host server is in the Locked position. Change the position of the rotary switch and retype the break command.

break.

Failed to allocate buffer for console mode

During execution of the console command, ALOM could not allocate enough memory to connect to the console.

console.

Failed to get password for <username>

During execution of the userpassword command, a SEEPROM error occurred. Try executing the command again.

userpassword.

Failed to set <variable> to <value>

During execution of the setsc command, ALOM encountered a SEEPROM error.

setsc.

Invalid login

Login attempt failed. This message appears at the login prompt.

Invalid password

You entered an invalid password with the userpassword command.

userpassword.

Invalid permission: <permission>

You entered an invalid user permission.

userperm.

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.

userdel

Passwords don't match

The two entries for a new password did not match. Enter the password again.

Permission denied

You attempted to execute a shell command for which you do not have the proper user permission level.

userperm.

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.

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.

poweron.

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.

removefru.

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.

showfru.

Passwords didn't match, try again

When you execute the userpassword command, you need to enter the password twice. If the two passwords you enter do not match, this error appears. Execute the userpassword command again.Refer to userpassword.

scadm: all user slots are full

This error occurs when you try to add a user account after ALOM already has the maximum of 16 accounts configured. You must delete an existing account before you can add a new one. Refer to userdel.

scadm: command line too long

You may have typed too many characters on the command line. Make sure that the command you used is valid, and execute the command again using fewer characters.

scadm: command unknown

The command you used is invalid for scadm. If the command is a valid ALOM command but does not exist as an scadm command, you must execute the command from ALOM. Refer to List of scadm Commands, and ALOM Shell Commands.

scadm: could not read date from SC

An undefined error in the ALOM firmware occurred while scadm tried to obtain the current date and time from ALOM. Execute the command again, or run the command from ALOM.

scadm: could not send alert

While executing the send_event command, ALOM firmware could not log an event or send an alert message. Refer to scadm send_event.

scadm: could not set date on SC

An undefined error in the ALOM firmware occurred while scadm tried to set the current date and time in ALOM. Execute the command again, or run the command from ALOM. Refer to scadm date.

scadm: couldn't add user

scadm encountered an internal error while trying to add a user account. This may be due to a faulty SEEPROM. Refer to scadm useradd

scadm: couldn't change password

scadm encountered an internal error while trying to change a user password. This may be due to a faulty SEEPROM. Refer to scadm userpassword.

scadm: couldn't change permissions

scadm encountered an internal error while trying to change user permissions. This may be due to a faulty SEEPROM.

scadm: couldn't delete user

scadm encountered an internal error while trying to delete a user account. This may be due to a faulty SEEPROM. Refer to scadm userdel.

scadm: couldn't get information on user

scadm encountered an internal error while trying to execute the usershow command. This may be due to a faulty SEEPROM. Refer to usershow.

scadm: download failed, SC reported erase error

ALOM reported a hardware problem while executing the flashupdate command. There may be a problem with the SEEPROM. Refer to scadm download.

scadm: download failed, SC reported int_wp error

ALOM reported a hardware problem while executing the flashupdate command. There may be a problem with the SEEPROM. Refer to scadm download.

scadm: download failed, SC reported range error

ALOM reported a hardware problem while executing the flashupdate command. There may be a problem with the SEEPROM. Refer to scadm download.

scadm: download failed, SC reported verify error

ALOM reported a hardware problem while executing the flashupdate command. There may be a problem with the SEEPROM. Refer to scadm download.

scadm: download failed, SC reported vpp error

ALOM reported a hardware problem while executing the flashupdate command. There may be a problem with the SEEPROM.Refer to scadm download.

scadm: download failed, SC reported wp error

ALOM reported a hardware problem while executing the flashupdate command. There may be a problem with the SEEPROM. Refer to scadm download.

scadm: download rejected, rotary switch in secure mode?

You cannot execute the flashupdate command while the server rotary switch is in the Locked position. Check the rotary switch position and execute the command again. Refer to scadm download.

scadm: Error downloading file

An internal error occurred during execution of the flashupdate command. Run the command again. Refer to scadm download.

scadm: ERROR, callback init failed

An internal error occurred during execution of the flashupdate command. Run the command again. Refer to scadm download.

scadm: 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. Refer to Configuration Worksheet.

scadm: 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. Refer to setsc, or showsc, and Configuration Worksheet.

scadm: ERROR, passwords didn't match

When you execute the userpassword command, you need to enter the password twice. If the two passwords you enter do not match, this error appears. Execute the command again. Refer to userpassword.

scadm: ERROR, unable to set up message queue

An internal error occurred during execution of the download command. Run the command again. Refer to scadm download.

scadm: event message can't exceed 80 characters

The message you enter for the send_event command must contain fewer than 80 characters. Refer to scadm send_event.

scadm: file could not be opened

An error occurred during execution of the download command; scadm could not open the file specified on the command line. Check that you specified the correct file and run the command again. Refer to scadm download.

scadm: file not a valid s-record

An error occurred during execution of the flashupdate command; the file you specified for downloading is not a valid srecord file. Check the file name and run the command again. Refer to scadm download.

scadm: INTERNAL ERROR in set date

An internal error occurred during execution of the date command. Run the command again. Refer to scadm date.

scadm: INTERNAL ERROR, overflow in callback

An internal error occurred during execution of the flashupdate command. Run the command again. Refer to scadm download.

scadm: invalid variable

You entered an invalid variable while executing the set command. Check the list of configuration variables and execute the command again. Refer to scadm set.

scadm: invalid variable or value

You entered an invalid variable or value while executing the set command. Check the list of configuration variables and execute the command again. Refer to scadm set.

scadm: malformed password

You entered an invalid password. A valid password has between six and eight characters, at least two of which are letters, and at least one of which is a digit or special character.

scadm: malformed username

You entered invalid characters in a user name. scadm: maximum username length is 16 The user name you entered exceeded the maximum of 16 characters. Enter the user name again using 16 or fewer characters.

scadm: SC did not respond during boot initialization

An internal error occurred during execution of the flashupdate command. Run the command again. Refer to scadm download.

scadm: SC failed to respond during download

During execution of the flashupdate command, ALOM did not enter boot mode correctly. Refer to scadm download.

scadm: SC firmware not responding

The main ALOM firmware is not responding. This can happen when ALOM is booting, or because the main firmware is corrupt, or ALOM has a hardware problem. Wait a few minutes, and then execute the command again.

scadm: SC not responding to requests

ALOM did not send a response that scadm was expecting. Check that ALOM is working.

scadm: ALOM returned fatal error

During execution of the flashupdate command, ALOM returned an undocumented error. Run the command again. Refer to scadm download.

scadm: ALOM returned garbage

This error can occur in various situations. Run the command again.

scadm: ALOM returned unknown error

During execution of the download command, ALOM returned undocumented status (neither success nor failure). Run the command again. Refer to scadm download.

scadm: ALOM returned wrong response

ALOM returned an invalid response during a user command. This is considered an internal error in ALOM or the scadm utility. Refer to Overview of the scadm Utility.

scadm: ALOM unable to free up memory

This message can occur in various situations. The scadm utility was unable to free the received message from the ALOM firmware.

scadm: Unable to reset ALOM hardware

During execution of the resetsc command, an attempt to hard reset ALOM failed. Refer to resetsc.

scadm: unable to send data to ALOM

ALOM did not acknowledge data sent to it. Check that ALOM is working.

scadm: user already exists

The user you are trying to add already has an ALOM account on this server.

scadm: username did not start with letter or did not contain lowercase letter

You used an invalid user name format when trying to add an ALOM user account. Refer to the useradd command and try running it again. Refer to useradd.

scadm: username does not exist

The user name you specified is not associated with an ALOM account on this server.

This program MUST be run as root

Log in to the server as root and execute scadm again.

USAGE: scadm <command> [options]

For a list of commands, type scadm help.

USAGE: scadm date [-s] | [[mmdd]HHMM | mmddHHMM[yyyy]][.SS]

You entered an incorrect value for scadm date. Refer to the date command for proper syntax and run the scadm date command again. Refer to scadm date.

USAGE: scadm download [boot] <file>

You entered an incorrect value for scadm download. Refer to the download command for proper syntax and run the scadm download command again. Refer to scadm download.

USAGE: scadm loghistory

You entered an incorrect value for scadm loghistory. Refer to the loghistory command for proper syntax and run the scadm showlogs command again. Refer to scadm loghistory.

USAGE: scadm resetrsc [-s]

You entered an incorrect value for scadm resetrsc. Refer to the resetrsc command for proper syntax and run the scadm resetrsc command again. Refer to scadm resetrsc.

USAGE: scadm set<variable> <value>

You entered an incorrect value for scadm set. Refer to the set command for proper syntax and run the scadm set command again. Refer to scadm set.

USAGE: scadm show [variable]

You entered an incorrect value for scadm show. Refer to scadm show for proper syntax and run the scadm show command again.

USAGE: scadm shownetwork

You entered an incorrect value for scadm shownetwork. Refer to scadm shownetwork for proper syntax and run the scadm shownetwork command again.

USAGE: scadm useradd <username>

You entered an incorrect value for scadm useradd. Refer to the useradd command for proper syntax and run the scadm useradd command again. Refer to scadm useradd.

USAGE: scadm userdel <username>

You entered an incorrect value for scadm userdel. Refer toscadm userdel for proper syntax and run the scadm userdel command again.

USAGE: scadm userpassword <username>

You entered an incorrect value for scadm userpassword. Refer to scadm userpassword for proper syntax and run the scadm userpassword command again.

USAGE: scadm userperm <username> [cuar]

You entered an incorrect value for scadm userperm. Refer to scadm userperm for proper syntax and run the scadm userperm command again.

USAGE: scadm usershow [username]

You entered an incorrect value for scadm usershow. Refer to scadm usershow for proper syntax and run the scadm usershow command again.