Troubleshooting

A P P E N D I X D

Troubleshooting

This chapter describes problems that can occur during use of the XSCF console or during the operation of the system and provides solutions for them.

D.1 Troubleshooting XSCF and FAQ

This section describes problems that may occur during the use of XSCF and provides solutions for the problems. The section also contains frequently asked questions along with their answers.

Could Not Log in to XSCF

Check whether you entered the correct user name for login.

Check whether you entered the correct password.

Check the number of XSCF users. For information about the number of users, see Chapter 2 and Chapter 3.

Forgot the Login Password for XSCF

Ask a system administrator who has the platadm or useradm user privilege to reset your password using the password(8) command.

If a system administrator forgets the login password, log in using the "default" account. Then use the password(8) command to register again. For details about logging in using the "default" account, see Chapter 2.

Could Not Connect to XSCF Through the Serial Port

Check the connection between the terminal software and the serial port.

Check the settings of the terminal software (baud rate is set to 9600 bps, delay is set to 0, etc.). For information about the settings, see "Connecting to XSCF via the serial port" in Chapter 3.

Could Not Connect Using Telnet to XSCF via the XSCF-LAN

Check the LAN cable connection between the XSCF terminal and the server.

Check the connection between the terminal software and the telnet port.

Use the shownetwork(8) command to check whether the setting for the XSCF-LAN is enabled.

Use the showtelnet(8) command to check whether the setting for telnet is enabled.

Check whether the entered IP address and port number match their settings.

Confirm that the number of connections using telnet/SSH does not exceed its maximum number. For information about the maximum number, see Chapter 2 and Chapter 3.

If necessary, use the console on the personal computer that is directly connected to XSCF through the serial port to log in to the XSCF Shell, and check the XSCF-LAN settings by using the shownetwork(8) command.

Could Not Connect Using SSH to XSCF via the XSCF-LAN

Check the LAN cable connection between the XSCF terminal and the server.

Use the shownetwork(8) command to check whether the setting for the XSCF-LAN is enabled.

Use the showssh(8) command to check whether the setting for SSH is enabled.

Check whether the entered IP address and port number match their settings.

Confirm that the number of connections using telnet/SSH does not exceed limit. For information about the limitation, see Chapter 3.

If necessary, use the console on the personal computer that is directly connected to XSCF through the serial port to log in to the XSCF Shell, and check the XSCF-LAN settings using the shownetwork(8) command.

Check whether the host key has the correct setting. During XSCF Unit replacement, the host key setting is restored to the preset key setting of XSCF.

Check whether the client software has the correct settings.

Do Not Know the IP Address of XSCF

Use the shownetwork(8) command to check the current network configuration. If it has not yet been set, ask the network administrator to check the setting.

If necessary, use the console on the personal computer that is directly connected to XSCF through the serial port to log in to the XSCF Shell, and check the XSCF-LAN settings using the shownetwork(8) command.

The Console of the XSCF Shell or the Domain Console was Suddenly Disconnected

Someone may perform the applynetwork(8) and rebootxscf(8) commands after the setnetwork(8), setroute(8), sethostname(8), and setnameserver(8) commands were executed, or the flashupdate(8) command may have been executed. To use the XSCF, establish another connection and log in to the system again.

Someone may have used the setdate(8) command or the switchscf(8) command. To use the XSCF, establish another connection and log in to the system again.

If the XSCF Shell is not used during the specified length of time after login, it automatically terminates itself. This forced termination occurs when the specified period has elapsed, only if the time monitoring function is enabled and a length of time is specified for this function in the XSCF settings.

When the escape character (Example: "#") set by client and "." (period) keys are entered, the Oracle Solaris Secure Shell or SSH client of OpenSSH is disconnected. If the setting of escape character is the same in the Oracle Solaris Secure Shell/SSH client and console(8) command, the terminal is disconnected. So, please change the value of either setting. For more information, see the manual for SSH Client.

Could Not Power On or Off the Server

In operation with a user privilege other than the platadm or fieldeng privilege, the power on and power off operations for the entire system are not available. For information about user privileges, see the Administration Guide or XSCF Reference Manual.

Could Not Add an XSCF User

Check the number of XSCF registration users. For information about the number of registration users, see Chapter 2 and Chapter 3. Otherwise, contact the system administrator.

A Mail Report Was Not Received From XSCF

XSCF does not necessarily report all events. It sends a mail message for each part fault or authentication failure event. Check for the relevant event in the error log, or use the reference for event logs in Appendix B to check whether this is an event in an event log to be reported.

Use the showemailreport(8) command to check whether the appropriate setting is enabled. If no mail message for this event has been received, check whether an error mail message has been sent to the error mail recipient, or check the log of recorded errors.

If a cellular phone is used for receiving mail messages, check the phone settings for any set restriction on receiving messages.

Could Not Access the Top Page of the XSCF Web Function

Use the showhttps(8) command to check whether the setting for XSCF is enabled.

Check whether the entered URL is correct (e.g., whether the “s” in "https" is missing).

Ask the system administrator to check whether access through the IP address that is set is permitted.

Check whether the SSL/TSL function setting of the web browser is enabled.

Could Not Display XSCF Web Windows

If XSCF Web windows are not displayed even after login to the system from the top page of XSCF Web, JavaScript may be disabled in the web browser settings. Enable JavaScript in the browser settings, and retry login.

If pop-up window display is disabled in the web browser settings, XSCF Web windows cannot be displayed. Check the browser settings.

Forgot the Login Password for the XSCF Web

Since XSCF Web authentication is the same as XSCF Shell authentication, see the above Forgot the Login Password for XSCF.

Failed in the First Attempt to Access the XSCF Web Function After Login

Check whether Cookies are accepted in the web browser settings.

Web Pages of the XSCF Web Function are not Displayed Correctly

Some versions of web browsers do not display the windows correctly. See "Supported browsers" in Chapter 9, and update your browser to the latest version.

Alert Message is Displayed in XSCF Web

Please confirm the content of the security alert message and stop the use of XSCF Web. Perform the countermeasure to the content of the confirmed warning. When the expiration is over, re-set the https setting of XSCF. For the details of settings, see Section 2.2.8, Https Administration in Chapter 2.

Frequently Asked Questions (FAQ)

Q. Is an IP address assigned by default to the LAN port used for the XSCF-LAN?

A. An IP address is not assigned by default. If an IP address were assigned by default, one IP address would be temporarily duplicated during the concurrent setup of multiple units. This may affect the user LAN environment. To prevent this, the XSCF-LAN network function is disabled by default. However, there is a default value for the IP address for the network connecting redundantly configured XSCF Units (ISN). For information about the default value, see Section 2.2.1, Network Configuration in Chapter 2.

Q. If an Oracle Solaris OS hang-up event occurs during Oracle Solaris OS startup after the main unit is powered on, can the main unit power be turned off?

A. If an Oracle Solaris OS hang-up event occurs, the first action is to do the following instead of turning off the main unit power:

1. First, execute the reset(8) command with the panic option from the XSCF Shell.

2. After doing Step 1, if the Oracle Solaris OS dump fails, move to the ok prompt by executing "Break", or executing the reset(8) command with the xir option from the XSCF Shell. At this point, execute the "sync" command.

3. After doing Step 2, if the reset operation or the "sync" command fails, execute the reset(8) command with the "por" option from the XSCF Shell, or forcibly turn off power by using any of the following methods:

Method 1. Press and hold down the POWER switch on the operator panel of the main unit for four seconds.

Method 2. Execute the poweroff(8) command from the XSCF Shell.

Q. What kind of processing is executed by XSCF from the time that input power to the main unit is turned on until the Oracle Solaris OS starts?

A. The processing flow before system startup is as follows:

1. The operator turns on input power.

2. XSCF starts.

3. The operator turns on the power to the server.

4. XSCF initializes the hardware.

5. The POST starts and performs an initial diagnosis of hardware.

6. OpenBoot PROM starts.

7. OpenBoot PROM starts the boot process.

8. The Oracle Solaris OS starts.

Q. During normal log in to or log out from XSCF, what kind of messages are displayed on the terminal?

A. The following example shows successful log in to XSCF:

login: jsmith
Password: xxxxxxxx
XSCF>

The following example shows an unsuccessful log in:

login: jsmith
Password: xxxxxxxx
Login incorrect

The following example shows a successful log out from XSCF:

XSCF> exit
logout

The following example shows an unsuccessful log out:

XSCF> exit
Not supported in this system.

Note - The above examples vary depending on the client software on the terminal.

Q. What is the relationship between the XSCF error log and error information in the MIB file?

A. Error information reflected in the MIB file is the latest log data of XSCF.

D.2 Troubleshooting the Server While XSCF Is Being Used

This section describes how to effectively use XSCF in case the main unit is not responding, which means that a problem or panic occurred in the unit.

Before Contacting Our Authorized Service Personnel

Before contacting our authorized service personnel, first follow the procedure below. This procedure may be helpful not only in solving the problem but also could eliminate the need to make an inquiry.

1. If the server does not respond, set the Mode switch on the operator panel to Service mode.

2. Check the system status by using either of the following methods:

When you cannot use the XSCF Shell through SSH/telnet

a. Connect a terminal to the serial port of XSCF.

b. Enter your user account and password to log in to the XSCF Shell.

c. Use the XSCF Shell to check error logs.

When you can use the XSCF Shell through SSH/telnet or the serial port

a. Use your XSCF user account to log in to XSCF.

b. Establish a connection through the XSCF-LAN port, and use the XSCF Shell to check error logs and other information. See Appendix B for the corrective action.

c. Otherwise, check the XSCF event logs and server status by using the XSCF Shell through the serial port.

Use the following commands to check the events that occurred at the time the problem occurred:

showlogs error

showlogs event

showlogs power

showlogs monitor

showlogs console

fmdump

If you find an error, see Appendix B in this manual for the corrective action.

d. Check the XSCF console log or panic log for the latest messages. A message may have been output by the Oracle Solaris OS after it detected the problem. In cases involving a panic, use the showlogs(8) command with the panic option to check the events that occurred at the time the panic occurred. For information about using the command, see the XSCF Reference Manual.

3. If you cannot find any problem after checking the above points, restart the system.

4. If you find any problem, see Appendix B and take measures based on the corrective action that is described, such as using the maintenance guidance of the XSCF Shell command for replacement of the relevant component.