A P P E N D I X A - Troubleshooting

This chapter consists of tables of the most common issues you might experience with error messages you see and troubleshooting suggestions. It contains the following sections:

If you are having problems connecting to the network, check your cabling to ensure that the switch is properly connected to the management port as well as the InfiniBand ports and connectors. Then refer to Diagnosing Switch Indicators to verify that the corresponding port on the switch is functioning properly.

Diagnosing Switch Indicators

If you have connected a device to a port on the switch, but the Link LED is off, then check the following items:

Verify that all system components have been properly installed. If any network cabling appears to be malfunctioning, test it in an alternate environment where you are sure that all the other components are functioning properly.

Diagnosing Port Connections

Using System Logs

The Sun IB switch logs information about important system events to both internal non-volatile event logs and Solaris host-based system logs (using syslog mechanism). The internal non-volatile event log is used only by ALOM. You can view its contents by using the ALOM showlogs command.

The Solaris host based system log is used by both InfiniBand management software and ALOM. System logs can be accessed through usual Solaris syslog means.

Using ALOM Event Logs

The contents of the switch's non-volatile event log can be seen using the ALOM showlogs command.

If a fault occurs, ensure that the problem you encountered is actually caused by the switch. If the problem appears to be caused by the switch, then follow these next steps.

CODE EXAMPLE A-1 Sample Output of `showlogs` Command
sc> `showlogs -t SSC0` Jan 01 00:00:14: MINOR: SSC0: Service Required LED state changed to OFF. Jan 01 00:00:14: MINOR: SSC0: Locator LED state changed to OFF. Jan 01 00:00:31: MAJOR: Factory commands Enabled Jan 01 00:00:03: MINOR: SSC0: Environmental monitoring enabled. Jan 01 00:00:06: MINOR: SSC0: Active LED state changed to ON. Jan 01 00:00:06: MINOR: SSC0: Service Required LED state changed to OFF. Jan 01 00:00:06: MINOR: SSC0: Locator LED state changed to OFF. Jan 01 00:00:03: MINOR: SSC0: Environmental monitoring enabled. Jan 01 00:00:06: MINOR: SSC0: Active LED state changed to ON. Jan 01 00:00:06: MINOR: SSC0: Service Required LED state changed to OFF. Jan 01 00:00:06: MINOR: SSC0: Locator LED state changed to OFF. Jan 01 00:01:58: MAJOR: Factory commands Enabled Jan 01 00:00:03: MINOR: SSC0: Environmental monitoring enabled. Jan 01 00:00:06: MINOR: SSC0: Active LED state changed to ON. Jan 01 00:00:06: MINOR: SSC0: Service Required LED state changed to OFF. Jan 01 00:00:06: MINOR: SSC0: Locator LED state changed to OFF. Jan 04 16:32:22: MINOR: SSC0: Service Required LED state changed to ON. Jan 04 16:32:39: MINOR: SSC0: Service Required LED state changed to OFF. Nov 30 11:28:42: MINOR: SSC0: Locator LED state changed to FLASHING. Nov 30 11:28:54: MINOR: SSC0: Locator LED state changed to OFF. ------------------------------------------------------------------------------ Boot and loopback log ------------------------------------------------------------------------------ JAN 01 00:00:03: MAJOR: SSC0: Port 0: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 1: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 2: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 3: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 4: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 5: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 6: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 7: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 8: SC loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 0: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 1: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 2: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 3: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 4: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 5: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 6: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 7: Internal loopback test failed JAN 01 00:00:03: MAJOR: SSC0: Port 8: Internal loopback test failed sc>

CODE EXAMPLE A-1 Sample Output of showlogs Command

sc> showlogs -t SSC0

Jan 01 00:00:14: MINOR: SSC0: Service Required LED state changed to OFF.

Jan 01 00:00:14: MINOR: SSC0: Locator LED state changed to OFF.

Jan 01 00:00:31: MAJOR: Factory commands Enabled

Jan 01 00:00:03: MINOR: SSC0: Environmental monitoring enabled.

Jan 01 00:00:06: MINOR: SSC0: Active LED state changed to ON.

Jan 01 00:00:06: MINOR: SSC0: Service Required LED state changed to OFF.

Jan 01 00:00:06: MINOR: SSC0: Locator LED state changed to OFF.

Jan 01 00:00:03: MINOR: SSC0: Environmental monitoring enabled.

Jan 01 00:00:06: MINOR: SSC0: Active LED state changed to ON.

Jan 01 00:00:06: MINOR: SSC0: Service Required LED state changed to OFF.

Jan 01 00:00:06: MINOR: SSC0: Locator LED state changed to OFF.

Jan 01 00:01:58: MAJOR: Factory commands Enabled

Jan 01 00:00:03: MINOR: SSC0: Environmental monitoring enabled.

Jan 01 00:00:06: MINOR: SSC0: Active LED state changed to ON.

Jan 01 00:00:06: MINOR: SSC0: Service Required LED state changed to OFF.

Jan 01 00:00:06: MINOR: SSC0: Locator LED state changed to OFF.

Jan 04 16:32:22: MINOR: SSC0: Service Required LED state changed to ON.

Jan 04 16:32:39: MINOR: SSC0: Service Required LED state changed to OFF.

Nov 30 11:28:42: MINOR: SSC0: Locator LED state changed to FLASHING.

Nov 30 11:28:54: MINOR: SSC0: Locator LED state changed to OFF.

------------------------------------------------------------------------------

Boot and loopback log

------------------------------------------------------------------------------

JAN 01 00:00:03: MAJOR: SSC0: Port 0: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 1: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 2: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 3: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 4: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 5: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 6: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 7: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 8: SC loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 0: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 1: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 2: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 3: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 4: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 5: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 6: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 7: Internal loopback test failed

JAN 01 00:00:03: MAJOR: SSC0: Port 8: Internal loopback test failed

sc>

System Log Messages

If the SUNWsibs9p package is installed and set up for the switch, event messages from the switch will occur on the host (See System Log Proxy). Some messages are informational, others represent errors. The messages can be divided into two categories: messages from the switch platform itself (TABLE A-1 and TABLE A-2) and messages from the InfiniBand management software (TABLE A-3).

TABLE A-1 System Log Error Messages from the Platform
Message	Description	Solution
`Platform top_LBIST_PLL FAILED`	A major fault of the InfiniBand switch chip occurred during boot test.	Try rebooting. If the same error message reappears, contact service.
`Platform smaif_LBIST_PLL FAILED`	A major fault of the InfiniBand switch chip occurred during boot test.	Try rebooting. If the same error message reappears, contact service.
`Platform xm9_LBIST_PLL FAILED`	A major fault of the InfiniBand switch chip occurred during boot test.	Try rebooting. If the same error message reappears, contact service.
`Platform olc`number`_LBIST_PLL FAILED`	A major fault of the InfiniBand switch chip occurred during boot test.	Try rebooting. If the same error message reappears, contact service.
`Platform olc`number`_MBIST_PLL FAILED`	A major fault of the InfiniBand switch chip occurred during boot test.	Try rebooting. If the same error message reappears, contact service.
`Platform olc`4_xm9_smaif`_MBIST_PLL FAILED`	A major fault of the InfiniBand switch chip occurred during boot test.	Try rebooting. If the same error message reappears, contact service.
`Platform NULL memory error struct pointer`	Memory allocation fault during init.	Try rebooting.
`Platform single-bit corrected error at xx on yy`	Memory fault corrected	Try rebooting. If the same error message reappears, contact service.
`Platform single-bit uncorrectable error at xx on yy`	Memory fault	Try rebooting. If the same error message reappears, contact service.
`Platform multi-bit uncorrectable error at xx on yy`	Memory fault	Try rebooting. If the same error message reappears, contact service.
`Platform AMD1026 init FAILED`	Hardware fault during boot.	Try rebooting. If the same error message reappears, contact service.
`Platform PCA9554@40 init FAILED`	Hardware fault during boot	Try rebooting. If the same error message reappears, contact service.
`Platform PCA9554@42 init FAILED`	Hardware fault during boot	Try rebooting. If the same error message reappears, contact service.
`Platform PCA9554 init on Mezzanine FAILED`	Hardware fault during boot.	Try rebooting. If the same error message reappears, contact service.
`Platform PSU`number `init failed`	Hardware fault during boot	Try rebooting. If the same error message reappears, replace the PSU.
`Platform Ibdevice init failed`	Software fault during boot	Try rebooting.
`ASSP init failed`	Hardware fault during boot	Try rebooting. If the same error message reappears, contact service.
`Platform External loopback mode on port number FAILED, not Link up or 12X.`	Loopback test failed during boot	The port number might be bad. Try rebooting. If the same error message reappears, avoid using that port.
`Platform External loopback mode on port number FAILED, sent` xx `received` yy	Loopback test failed during boot	The port number might be bad. Try rebooting. If the same error message reappears, avoid using that port.
`Platform External loopback mode on port number FAILED, not Link up or 12X.`	Loopback test failed during boot	The port number might be bad. Try rebooting. If the same error message reappears, avoid using that port.
`Platform External loopback mode on port number FAILED, sent` xx `received` yy	Loopback test failed during boot	The port number might be bad. Try rebooting. If the same error message reappears, avoid using that port.

TABLE A-2 System Log Informational Messages from the Platform
Message	Description
`Platform Sun IB Switch 9 port platform init started`	The init of the platform has started.
`Platform Last reset was done by WDOG`	The switch was rebooted by the watchdog due to a hang of the system.

The InfiniBand (IB) management software is responsible for setting up and controlling all the IB devices that are connected together. The events reported by this software can therefore be for some other device than the switch where the software is running. In InfiniBand a port on a IB device (switch or channel adapter card) is uniquely identified by a value called PortGUID. This value is often displayed in the IB related syslog messages. This value is also used by the showib command when listing the connections in the IB topology.

Many of the messages also contain IB-specific parameters. Refer to the InfiniBand Specification, Volume 1 for an exact explanation. All the IB related syslog messages contain a prefix of the type IBSRM event event_number. This part of the message is omitted from TABLE A-3 to make it more readable.

TABLE A-3 Syslog Messages
Message	Severity	Description
`IBSRM_EVENT_PORT_UNKNOWN_MKEY at port with GUID =` port-GUID	Warning	The IB management software is unable to control (set up and initialize) the port identified by port-GUID due to an unknown key setting. If this device is expected to be connected to the switch, set up the identified device with MKEY set to 0 and reboot that device. If it is an unexpected connection, remove the cable.
`IBSRM_EVENT_PORT_GID_ONLINE, port with GUID =` port-GUID	Information	The IB port identified by port-GUID has become operational. This is an expected event for all IB ports connected to the IB subnet. This port should now be visible in the topology list displayed by the `showib` CLI.
`IBSRM_EVENT_PORT_GID_OFFLINE, port with GUID =` port-GUID	Information	The IB port identified by port-GUID is no longer operational (it cannot participate in any data transfers). The usual cause of this event is that the cable is unplugged. It can also happen if the cable is not properly connected or if the cable or connector is bad.
`IBSRM_EVENT_PORT_STATE_CHANGED, port with GUID =` port-GUID`, ib port =`IB-port-number`, connector =`connector-number`, new_state =` new-state-value`, old_state =` old- state-value	Information	The IB port identified by port-GUID, port-number and connector-number has changed the IB port state from old-state-value to new-state-value. The state values can be decoded as follows: 1 = Down 2 = Initialize 3 = Armed 4 = Active This message is often seen together with the _ONLINE and _OFFLINE messages.
`IBSRM_EVENT_PORT_BAD_DIAG_CODE, port_GUID =` port-GUID`, diag_code =`diag-code-value	Error	The IB port identified by port-GUID has reported a bad diagnostic code diag code value. The port will not be become operational. Reboot the device to see if it recovers.
`IBSRM_EVENT_PORT_LINK_INTEG_REACHED, port_GUID =` port-GUID	Error	This is an error event causing the IB port identified by port-GUID to have poor performance. Check that the cables are properly inserted. If cables are properly inserted, try rebooting the device.
`IBSRM_EVENT_PORT_EXCESS_BUFF_OVERRUN, port_GUID =` port-GUID	Error	This is an error event causing the IB port identified by port-GUID to have poor performance. Check that the cables are properly inserted. If it does not help, try rebooting the device.
`IBSRM_EVENT_PORT_FLOW_CNTL_TIMER_EXPD, port_GUID =` port-GUID	Error	This is an error event causing the IB port identified by port-GUID to have poor performance. Check that the cables are properly inserted. If cables are properly inserted, try rebooting the device.
`IBSRM_EVENT_PORT_CAP_MASK_CHANGED, port_GUID =` port-GUID`, cap_mask =`capability-mask	Information	The IB port identified by port-GUID has had a change in IB capabilities. The new port capabilities are identified by the value of the capability mask.
`IBSRM_EVENT_PORT_SYS_IMG_GUID_CHANGED, port_GUID =` port-GUID`, sys_im_GUID =` system-image-GUID	Information	The system image GUID of IB port identified by port-GUID has changed to system-image-GUID
`IBSRM_EVENT_PORT_BAD_MKEY, src GUID =` source-port-GUID`, dest GUID =`destination-port-GUID`, attr_ID =` attribute-ID`, method =`method	Warning	The IB port destination-port-GUID has received a package from source-port-GUID that has a bad MKey value. attribute-ID and method describe the type of packet received. The packet has been dropped. Check to ensure that no unexpected IB devices are connected to this IB network.
`IBSRM_EVENT_PORT_BAD_PKEY, src GUID =` source-port-GUID`, dest GUID =`destination-port-GUID`, PKey =` PKey-value`, src qp =`source-QP-number`, dest qp =`destination-QP-number	Warning	The IB port destination-port-GUID has received a package from source-port-GUID that has a bad partition key PKey-value. The packet will be dropped. source-QP-number and destination-QP-number further describe this packet. The packet has been dropped. Check to ensure that no unexpected IB devices are connected to this IB network.
`IBSRM_EVENT_PORT_BAD_QKEY, src GUID =` source-port-GUID`, dest GUID =` destination-port-GUID`, qkey =` QKey-value`, src qp =`source-QP-number`, dest qp =`destination-QP-number	Warning	The IB port destination-port-GUID has received a package from source-port-GUID that has a bad QKey value QKey-value.The packet will be dropped. source-QP-number and destination-QP-number further describe this packet. The packet has been dropped. Check to ensure that no unexpected IB devices are connected to this IB network.
`IBSRM_EVENT_PORT_PKEY_TABLE_FULL`, port_GUID = port-GUID, `PKey =` PKey-value	Warning	The PKey PKey-value could not be written into the PKey table of the IB port identified by port-GUID because the table was already full. The port will not be able to participate in transmissions involving this PKey. This should not happen unless there are many simultaneously running IB services in the IB subnet.
`IBSRM_EVENT_NODE_DISC_FAILED, port_GUID =`port-GUID	Warning	Even after several attempts, one or more devices attached to the node identified by port-GUID could not be discovered. The device is not able to participate in any data transfers. Check cabling and connections. If cabling seems to be OK reboot the device.
`IBSRM_EVENT_NODE_PROG_FAILED, port_GUID =`port-GUID`, IB port number port/connector` `number` connector	Warning	Even after several attempts, the node/port port-GUID could not be programmed (setup for proper IB usage). Check cabling and connections. If cabling seems to be OK reboot the device.
`IBSRM_EVENT_PORT_NO_MORE_LIDS, port_GUID =` port-GUID	Error	The port identified by port-GUID could not be owned/managed because the management software ran out of LIDs it is allowed to use. This should not happen unless the switch is part of an extremely large IB network, which is not supported.
`IBSRM_EVENT_TOO_SMALL_LFT, switch GUID` switch-GUID, `max lids supported`max-supported-lids, `max lid in use` max-lid	Error	The switch identified by switch-GUID cannot be programmed with wanted LID value max-lid because this LID is beyond the size of the switch forward table max-supported-lids. Any packets addressed for max-lid will fail to transfer through the indicated IB switch.This should not happen unless the switch is part of an extremely large IB network, which is not supported.
`IBSRM_EVENT_PORT_DUPLICATE_GUID`, `duplicate` `GUID =` GUID-value`, original peer switch GUID` switch-GUID-1`, duplicate peer switch GUID` switch-GUID-2, `original peer IB port` port1`, duplicate peer IB port` port2	Error	Duplicate ports in the IB topology have the same GUID value GUID-value. One instance is connected to switch-GUID-1 port1 while the other is connected to switch-GUID-2 port2. The IB subnet will most likely perform badly since unique GUID values are central for correct IB management. The only way to correct this is to exchange one of the indicated devices with another one having a proper GUID.
`IBSRM_EVENT_MCG_CREATED, mclid =`mc-lid-value	Information	The multicast group identified by multicast lid mc-LID-value has been created.
`IBSRM_EVENT_MCG_DELETED, mclid =` mc-lid-value	Information	The multicast group identified by multicast lid mc-LID-value has been deleted.
`IBSRM_EVENT_SM_BECAME_MASTER, sm_GUID =` GUID-value	Information	The master SM in the IB subnet is running behind the port identified by GUID-value.
`IBSRM_EVENT_MISC_EMPTY_SUBNET, local GUID` GUID-value	Information	The IB subnet that the local switch GUID-value is part of is currently empty. (No hosts are connected or yet done booting.)
`IBSRM_EVENT_MISC_BAILOUT, reason =` reason`, file` source-file`, line` source-line	Error	The IB management software running on the switch is bailing out. The bailout point in the source is identified by source-file and source-line. The reason for the bailout is indicated by reason, 1 is lack of memory, 2 is package transfer errors, 3 is other. The IB switch will try to automatically restart the IB management software when this event occurs. If the event recurs after the restart, contact service.
`IBSRM will not write to journal`	Information	This message is expected on each IB management (re)start on the switch and does not indicate any error. It is simply an indication that the switch does not support stable storage to save IB management policy and configuration information.
`IBSRM_EVENT_MISC_PORT_ADD_DDP_FAILED, port_GUID =` port-GUID	Warning	An attempt to auto-add the port port-GUID to the default data partition (DDP) failed. This will cause failures in data transfers to and from this port, which uses the default data partition.
`IBSRM_EVENT_MISC_PORT_ADD_DDP_DONE, port_GUID =` port-GUID	Information	The port port-GUID has been auto-added to the default data partition. This port had previously failed to be added to the DDP because of a full PKey table. However, the removal of the port from some other partition has freed up an entry in the PKey table which allowed the auto-add to the DDP.

Troubleshooting ALOM Problems

TABLE A-4 ALOM Diagnostics
Problem	Description
Can't connect to ALOM using the `telnet` command	ALOM supports a total of four concurrent Telnet sessions and a single serial session. If that limit is reached, further attempts to start a Telnet session will fail with an error message about exceeded maximum number of login sessions. Example: $ `telnet ib_switch19` Trying 129.148.49.120... Connected to 129.148.49.120 Escape character is '^]'. Maximum login sessions (5) exceeded please retry later. Connection closed by foreign host. If that is the case, terminate one or more of the four active telnet sessions and retry. (The `showusers` command will show where and by whom the active sessions are being run.) If `telnet` fails but there is no error message about exceeded maximum number of login sessions, perform the following steps: Log in to ALOM through the serial management port and use the `showsc` command to check the current IP settings. Log in to a host on the network and use the `ping` command to see whether ALOM can be reached on the IP address displayed by the `showsc` command in the previous step. Check that the Ethernet cable is attached.
No alerts received from ALOM	Check the CLI event level setting using `showsc` command (since it also applies for `syslog`) to make sure that you are receiving the proper levels of events. Also ensure that the Ethernet cable is properly attached and the switch can be reached using `ping` and `telnet`.
You can perform some ALOM functions, but not others	Specific user permissions are required to perform functions. Check your permission level.

ALOM Shell Error Messages

This section contains information about certain types of error messages you might see when using the ALOM command shell:

Usage Errors

TABLE A-5 describes usage error messages that are displayed when you typed the command using improper command syntax. Refer to the description of the command for the correct syntax.

TABLE A-5 Usage Error Messages
Error Message	Command/Description
`Error: Invalid command option. Type help to list commands.`	`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 `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.

CLI Messages

TABLE A-6 CLI Messages
Message	Description
`Error: Maximum number of users already configured`	Once the maximum number of users is configured, no more can be added.
`Error: Invalid IP address`	Invalid IP address given.
fru`: Already ready to remove.`	`removefru` attempted on a FRU that is already ready to remove.
fru`: Cannot make ready to remove.`	`removefru` failed (reason is given in the preceding line).
`Error: addition of user` username `failed`	The username was not added.
`Error: Too many command line arguments (31 max.)`	Malformed command.
`Cannot open the tftp connection`	TFTP server given in flashupdate command, for example, does not respond.
`Error: User username already exists`	Each username must be unique.
`Usage:` command usage	Command attempted used with wrong or insufficient parameters.
`Error: Invalid password entered.`	Password string is invalid (for reason given in lines that follow, for example 'too short' and others.).
`Error: permissions not set for user %s`	The user does not have sufficient permissions for the attempted operation.
`Error: admin user's permissions are fixed as aucr`	`admin` user permissions are fixed to all and cannot be revoked.
`Error: Invalid user permissions.`	The user does not have sufficient permissions for the attempted operation.
`Error: did not set password for user %s`	Selected password may not meet system requirements.
`Error: Inconsistent passwords entered.`	Inconsistent new password entered (has to be entered twice).
`Error: wrong password entered.`	Wrong current password is provided in an attempt to change password using `password` command.
`Error:` username `is in use. Cannot remove it.`	The user does not have sufficient permissions for the attempted operation.
`Error: delete of user` username `failed`	The user does not have sufficient permissions for the attempted operation.
`Initial state for user admin has no permissions: enter 'password' to set password and enable full permissions.`	The default user `admin` has no permissions right after the switch is shipped. A password has to be assigned to it.
`Error: User name specified is too long`
`Error: Invalid username string`
`Deleted user %s successfully.`
`Image too large for flash location`	Corrupted flash image.
`Flash segment out of range`	Corrupted flash image.
`SRecord address out of range`	Corrupted flash image.
fru`: Operation invalid`	Operation is not supported on this FRU.
fru`: Waiting for FRU to be configured. Press control-C to abort operation.`	Power operation attempted while the FRU is being brought up. Either wait for a while or stop the operation using Ctrl-C.
`Unknown Flash Image`	Corrupted flash image.
`flashupdate of %s failed`	Flashupdate failed for reason mentioned in the line preceding this message.
`Error: Invalid FRU name` string `- type showplatform for list of FRUs.`	Wrong FRU given as parameter.
`Error: Invalid command options`	Non-existent command option entered.
`Error: Invalid command` string `- type help for a list of commands.`	Wrong command name given.
`Do not issue a resetsc, setfailover, or power cycle to this system. You MUST first successfully complete a flashupdate of the SC bootrom before doing so, otherwise this system will require a hardware level flash.`	Flashupdate of `bootrom` or the whole flash failed. The switch must not be reset, because it will not be able to boot. Flashupdate has to be repeated until `bootrom` is successfully programmed.
`flashupdate: Checksum failed`	Wrong image file checksum.
`Bad SRecord`	Image file provided to flashupdate command is not a valid S-record image.
`%s: Cannot power on.`	Power on failed for reason given in preceding lines.
`Password must differ from old one by at least 3 characters.`	Wrong password given using `password` command by user without `u` permission.
`Password too short (Must be at least 6 characters).`	Wrong password given using `password` command by user without `u` permission.
`Password cannot match username.`	Wrong password given using `password` command by user without `u` permission.
`%s: Already powered on.`	Power on attempted on a FRU that is already powered on.
`%s: Cannot power off.`	Power off failed for reason given in preceding lines.
`%s: Already powered off.`	Power off attempted on a FRU that is already powered off.
`Password unchanged from old one.`	Wrong password given using `password` command by user without `u` permission.
`Password must have at least 2 alphabetic characters and 1 numeric character.`	Wrong password given using `password` command by user without `u` permission.
fru`: Not present.`	Operation attempted on a FRU that is not present.
`Error: Invalid command option - type help to list commands`	Help sought on non-existent command.
`Password cannot match reversed username.`	Wrong password given using `password` command by user without `u` permission.
`First character must be an alphabetic character.`	Wrong password given using `password` command by user without `u` permission.
`Password cannot be a circular shift of username.`	Wrong password given using `password` command by user without `u` permission.

Additional Important Messages

TABLE A-7 Additional Important Messages
Message	Description
`Are you sure you want to reset the SC configuration (y/n)?`	`setdefaults` confirmation
`%s: flashupdate complete.`	`flashupdate` succeeded. The system must now be reset using the `resetsc` command
`Are you sure you want to remove all permissions for user %s (y/n) ?`	Cautionary prompt to ensure you are not removing all permissions accidently.
`The system must be reset (using resetsc) for the new image to be loaded`
`Are you sure you want to power off FRU %s (y/n)?:`	`poweroff` confirmation.
`Event log is empty.`	No messages are in the event log.
`Are you sure you want to remove %s (y/n)?:`	`removefru` confirmation.
`Are you sure you want to restore the SC to factory defaults? All dynamic FRUID and NVRAM container data will be regenerated (y/n)?`	Restore factory defaults confirmation.
`Use of factory-mode is strictly reserved for SUN Service Personnel. Unauthorized use may invalidate your service warranty. Do you wish to continue [n]?`	Comment: A command reserved for Sun service personnel attempted. User must answer 'n', that is, not continue.
`Warning: Are you sure you want to flashupdate the SSC0/SC flash image (y/n)?`	`flashupdate` confirmation.
`Are you sure you want to reset the SC? All user sessions will be lost (y/n)?`	`resetsc` confirmation.

General Errors

TABLE A-8 General Error Messages
Error Message	Command/Description
`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 enable 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 and IP netmask.`	Check that the addresses are correct, and then run `setupsc` again.
`Error: Invalid IP gateway for IP address and IP netmask.`	Check that the addresses are correct, and then run `setupsc`.
`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.
`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.
`Failed to get password for` username	During execution of the `userpassword` command, an SEEPROM error occurred. Try executing the command again.
`Invalid login`	Login attempt failed. This message appears at the login prompt.
`Invalid password`	You entered an invalid password with the `userpassword` command.
`Invalid permission:` permission	You entered an invalid user permission.
`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.
`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 switch.

FRU Errors

TABLE A-9 lists the error messages that appear when ALOM detects problems with field-replaceable units (FRUs) or customer-replaceable units (CRUs).

Error Message	Command/Description
`Error:` fru-name `is currently powered off.`	fru-name is the name of the FRU to which you tried to send a command. The FRU is currently powered off. You must turn it back on before it accepts commands.
`Error:` fru-name `is currently powered on.`	fru-name is the name of the FRU to which you tried to send a `poweron` command. The FRU is already powered on.
`Error:` fru-name `is currently prepared for removal.`	fru-name 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.