Skip to main content

18.3 Frequently Asked Questions / FAQ

18.3 Frequently Asked Questions / FAQ
This section contains frequently asked questions about using the XSCF.
Q: Are IP addresses assigned by default to the LAN ports used with the XSCF-LAN?
  1. A: No IP address is assigned by default. For details on XSCF-LAN IP addresses, see "3.9.2  Understanding the XSCF Network Interfaces."
Q: Is a default IP address assigned for SSCP?
  1. A: An IP address is assigned by default. For the default SSCP IP address, see "3.9.5  Understanding the IP Addresses that are Set with SSCP." If the default IP address may affect the user LAN environment, change it.
Q: If Oracle Solaris hangs up during Oracle Solaris startup after the server is powered on, can the server be powered off from the XSCF?
  1. A: If a guest domain hangs up, collect an Oracle Solaris dump by using the ldm panic-domain command. For details of the ldm command, see the Oracle VM Server for SPARC Reference Manual of the version used.
    If a control domain hangs up, do the following.
  2. 1. Execute the reset command with the panic option specified in the XSCF shell to give an instruction for an Oracle Solaris dump.
  3. 2. If the Oracle Solaris dump failed even though step 1. was performed, execute the poweroff command in the XSCF shell to turn off the power.
Q: What kind of processing is executed by the XSCF after input power is supplied to the server until Oracle Solaris starts?
  1. A: The processing flow until the system starts is as follows. For details, see "Chapter 6  Starting/Stopping the System."
  1. 1. The operator turns on the input power.
  2. 2. The XSCF starts.
  3. 3. The operator powers on the server.
  4. 4. The XSCF initializes hardware.
  5. 5. POST starts and performs an initial hardware diagnosis.
  6. 6. OpenBoot PROM starts.
  7. 7. OpenBoot PROM starts the boot process.
  8. 8. Oracle Solaris starts.
Q: What kind of messages appear on the terminal during normal XSCF login or logout?
  1. A: XSCF login success/failure is described below.
    The following example shows login has succeeded.
login: jsmith
Password: xxxxxxxx
  1. The following example shows login failed.
login: jsmith
Password: xxxxxxxx
Login incorrect
  1. A: XSCF logout success/failure is described below.
    The following example shows logout has succeeded.
XSCF> exit
  1. The following example shows logout failed.
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 the error information in a MIB definition file?
  1. A: The error information reflected in a MIB definition file is the latest XSCF error log.