18.1 Troubleshooting for the XSCF
18.1 Troubleshooting for the XSCF
This section describes problems that may occur during use of the XSCF, and how to solve the problems.
Login to the XSCF Not Possible
- Check whether the user name entered for login is correct.
- Check whether the password used is correct.
- Check the number of the users currently connected to the XSCF. For details of the number of users, see "2.6 Number of Connectable Users."
Forgotten Login Password for the XSCF
- Ask the system administrator to reset the password. A system administrator who has the platadm or useradm user privilege can reset the password by using the password command.
- If the system administrator forgets the login password, log in using the "default" account, and set the password again by using the password command. For details on login authentication with the "default" account, see "Performing an Initial System Diagnosis" in the Installation Guide for your server.
XSCF Cannot be Connected via the Serial Port
- Check whether the terminal software is connected to the serial port.
- Check the terminal software setting (baud rate of 9600 bps, delay of other than 0, etc.) For details of settings, see "2.2.1 How to Log In to the XSCF Shell With a Serial Connection."
Note - If the XSCF connection fails even after you have performed the measures above, the problem could be solved by pressing the RESET switch on the rear panel. For details, see "18.2 Precautions Concerning Using the RESET Switch." |
XSCF Cannot be Connected Using Telnet via the XSCF-LAN
- Check whether the LAN cable between the XSCF shell terminal and server is correctly connected.
- Check whether the terminal software is connected to the Telnet port.
- Use the shownetwork command to check whether the XSCF-LAN is enabled.
- Use the showtelnet command to check whether the Telnet service is enabled.
- Confirm that the entered IP address and port number do not differ from the settings.
- Confirm that the number of connections via Telnet/SSH does not exceed the upper limit. For details of the upper limit, see "2.6 Number of Connectable Users."
- If necessary, use the console on a PC connected directly to the XSCF through the serial port to log in to the XSCF shell, and check the XSCF-LAN settings by using the shownetwork command.
Note - If the XSCF connection fails even after you have performed the measures above, the problem could be solved by pressing the RESET switch on the rear panel. For details, see "18.2 Precautions Concerning Using the RESET Switch." |
XSCF Cannot be Connected Using SSH via the XSCF-LAN
- Confirm that the LAN cable between the XSCF shell terminal and the server is correctly connected.
- Execute the shownetwork command to confirm that the XSCF-LAN setting is enabled.
- Execute the showssh command to confirm that the SSH service is enabled.
- Confirm that the entered IP address and port number do not differ from the settings.
- Confirm that the number of connections via Telnet/SSH does not exceed the upper limit. For details of the upper limit, see "2.6 Number of Connectable Users."
- If necessary, use the console on a PC connected directly to the XSCF through the serial port to log in to the XSCF shell, and check the XSCF-LAN settings by executing the shownetwork command.
- Confirm that the host key setting is correct. Note that replacing an XSCF unit returns the host key to the preset key on the XSCF.
- Confirm that the client software has the correct settings.
Note - If the XSCF connection fails even after you have performed the measures above, the problem could be solved by pressing the RESET switch on the rear panel. For details, see "18.2 Precautions Concerning Using the RESET Switch." |
Unknown XSCF IP Address
- Use the shownetwork command to check the current network configuration. If the address has not been set, notify the network administrator to check the settings.
- If necessary, use the console on a PC connected directly to the XSCF through the serial port to log in to the XSCF shell, and check the XSCF-LAN settings by using the shownetwork command.
XSCF Shell Terminal or Domain Console Suddenly Disconnected
- After the setnetwork, setroute, sethostname, setnameserver, and setsscp commands related to the XSCF network were executed by another user, the applynetwork and rebootxscf commands may have been executed. Alternatively, the flashupdate command may have been executed. To use the XSCF, establish another connection, and log in again.
- The setdate or switchscf command with respect to the XSCF may have been executed by another user. To use the XSCF, establish another connection, and log in again.
- If the XSCF shell is left unused for a specific duration after login, the XSCF automatically terminates the shell. This forced termination occurs after that length of time has elapsed, only if the time monitoring function is enabled and the length of time is set for this function in the XSCF settings.
- Oracle Solaris Secure Shell or the SSH client of OpenSSH is disconnected by the input of the escape character (e.g., "#") and "." (period) key that were set by the client. If the escape character of Oracle Solaris Secure Shell or the SSH client of OpenSSH has the same setting as the escape character that has been set by the console command, the terminal is disconnected. Therefore, change either of the setting values. For details, see the SSH client manual.
Server Power-on/off Operation Not Possible
- The power-on/off operations for the whole system are not available for operations with a user privilege other than the platadm or fieldeng privilege. For details of user privileges, see "3.5.3 Types of User Privilege."
XSCF User Cannot be Added
- Check the registered number of XSCF users. For details of the registered number, see "2.6 Number of Connectable Users." Alternatively, notify the system administrator.
No E-mail Notification From the XSCF
- The XSCF does not necessarily report all events. It sends e-mails for parts failures, authentication failure events, etc. To check for the intended notification in the error log or among the reported events in the event log, see "12.1 Checking a Log Saved by the XSCF."
- Use the showemailreport command to check whether enabled is the setting. If no e-mail has arrived, check whether an error e-mail was sent to the error e-mail notification recipient, or check the errors recorded in the error log.
- If a mobile phone is used to receive such e-mails, check the mobile phone settings for any receiving limit on its e-mail address.
Top Page of XSCF Web Not Accessible
- Use the showhttps command to check whether XSCF Web is enabled.
- Check whether the entered URL is correct. (Examples include a missing "s" for https.)
- Check with the system administrator about permission settings for the IP address.
- Check whether the connection setting with TLS of the Web browser is enabled.
XSCF Web Window Not Displayed
- If the individual windows of XSCF Web do not appear after login from the top page of XSCF Web, JavaScript may be disabled in the Web browser settings. Enable JavaScript in the Web browser settings, and log in again.
- If pop-up windows are blocked by the Web browser settings, XSCF Web windows cannot appear. Check the Web browser settings.
Forgotten Password for XSCF Web
- XSCF Web authentication is the same as XSCF shell authentication. See the above "Forgotten Login Password for the XSCF."
Initial Access Failed After Login With XSCF Web
- Check whether cookies are accepted in the Web browser settings.
XSCF Web Not Displayed Correctly in the Web Browser Window
- Some versions of Web browsers may not correctly show the XSCF in their windows. See the supported browsers in "Web Browser" in the latest Product Notes for your server, and update the Web browser to the latest version.
Warning Displayed on XSCF Web
- Check the contents of the security warning, and stop the use of XSCF Web. Take appropriate action according to the contents of the checked warning. If the expiration time has passed, configure the HTTPS service of the XSCF again. For details of HTTPS service settings, see "3.8 Configuring the HTTPS Service for Login to the XSCF."
Displayed Message Regarding the NTP Server
- The following message regarding the NTP server might appear when the XSCF starts. It means there may be a time deviation from the XSCF because time synchronization failed between the NTP server and the XSCF.
NTP service failed to reach appropriate NTP server. |
- If the physical partition starts in this situation, the logical domain time may shift.
Set the XSCF time before starting the physical partition.
For details, see "6.1.2 Setting the XSCF Time Before System Startup."
Other Troubles
- Notify the system administrator. If you need to collect/save an XSCF log, use XSCF shell commands to save the XSCF log. For details on how to save a log, see "12.1.15 Saving a Log to a File With Snapshot."
< Previous Page | Next Page >