Skip to main content
  1. Home >
  2. Products >
  3. Computing Products >
  4. Servers >
  5. Fujitsu SPARC servers >
  6. Downloads >
  7. User Manuals >
  8. Fujitsu SPARC M12-2S Installation Guide >
  9. A.1 Understanding the Usual Problems and Their Corrective Actions

A.1 Understanding the Usual Problems and Their Corrective Actions


A.1 Understanding the Usual Problems and Their Corrective Actions
If system operation is not normal during installation work, you may wonder whether there was a failure. In such cases, inspect the following items and take corrective measures accordingly.
Table A-1  List of Problem Case Examples
Case Possible Cause Corrective Action
The input power cannot be turned on. The power cord is disconnected. Connect the power cord correctly.
The breaker on the distribution board is turned off. Turn on the breaker.
The system management terminal does not display the login prompt. The serial cable is not connected to the serial port. Connect the serial cable correctly to the serial port on the rear of the SPARC M12-2S.
See Figure 5-1 in "5.1 Connecting Cables to the SPARC M12-2S."
For a building block configuration, connect the serial cable to the serial port of the SPARC M12-2S whose MASTER LED of the XSCF unit is lit.
  After a connection is established for the serial connection to the XSCF, the [Enter] key must be pressed. After the serial connection is established, press the [Enter] key.
See "6.3 Logging In to the XSCF."
  There are cases where the XSCF shell prompt does not appear after the console command was executed to terminate the previous established serial connection. If the XSCF shell prompt does not appear, enter "#." to move from the console to the XSCF shell.
The sethostname command changed the host name of the XSCF, but this change was not reflected. This is because the applynetwork command was not executed after the sethostname command was executed. After changing the host name with the sethostname command, execute the applynetwork command, and reboot the XSCF with the rebootxscf command.
After the input power is turned on, the MASTER LED on every SPARC M12-2S is lit. BB-IDs have not been set. Initialize each SPARC M12-2S to the factory default settings, and change the BB-IDs to the correct settings.
See "A.3.1 BB-IDs Not Set (BB-ID 00)."
The XCP firmware version check displays only BB#00. BB-IDs have not been set. Initialize each SPARC M12-2S to the factory default settings, and change the BB-IDs to the correct settings.
See "A.3.1 BB-IDs Not Set (BB-ID 00)."
The XCP firmware version check displays only BB#00 and BB#01 even though the configuration has at least three BBs. The BB-IDs of BB#00 and BB#01 are reversed. Initialize BB#00 and BB#01 to the factory default settings, and change the BB-IDs to the correct settings.
See "A.3.3 Mistaken Settings for BB#00 and BB#01."
The XCP firmware version check does not display BB#03 even though the configuration has four BBs. BB#03 has the wrong BB-ID setting. Change the BB-ID to the correct setting.
See "A.3.2 Mistaken Settings for BB-IDs Other Than BB#00 or BB#01."
The component status check (by the showhardconf command) of a building block configuration displays only BB#00. The XSCF BB control cables between the SPARC M12-2S units are incorrectly connected. Check messages by using the showlogs command.
See "A.2.2 Checking the Contents of Logs."
"Failed" appears in the results of a diagnosis test performed on a building block configuration. The crossbar cables between the SPARC M12-2S units are incorrectly connected. Check messages by using the showlogs command.
See "A.2.2 Checking the Contents of Logs."
The following errors are displayed by the showlogs error command executed in a system with the 3BB configuration or larger:
- BB control cable detected unexpected

- Cannot communicate with the other XSCF
The XSCF BB control cable is not completely in contact, or the cable is faulty. Connect the XSCF BB control cable correctly.
If the error is still displayed after you confirm the connection, replace the cable.