Skip to main content

Problems Resolved in XCP 2280


Problems Resolved in XCP 2280
The following table lists the problems resolved in XCP 2280.
Table 3-26  Problems Resolved in XCP 2280
RTI No. RTIF2-210209-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The "SCF process down detected" error may occur in some very rare cases.
Workaround There is no effective workaround.
RTI No. RTIF2-201119-001
Model SPARC M10-4S
Description If a CPU hardware error occurs in the standby or slave chassis in a system with a building block configuration, a normal CPU may be mistakenly degraded.
Workaround There is no effective workaround.
[How to restore]
After powering off the physical partition (PPAR), turn on the input power again to restore the mistakenly degraded CPU.
RTI No. RTIF2-201119-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description After changing the memory mirror mode setting, scfComponentSerialNumber does not have the changed value of memory mirror mode when an SNMP Trap is sent.
[Trap example] No value after "STRING:"
XSCF-SP-MIB::scfMIBTraps Enterprise Specific Trap (XSCF-SP-MIB::scfComponentEvent) Uptime: 0:06:21.82
XSCF-SP-MIB::scfComponentSerialNumber.mbu.0.cpu.0.notApplicable.0 = STRING:
XSCF-SP-MIB::scfTrapEventType.0 = INTEGER: psbConfMemoryMirrorValid(100)
Workaround There is no effective workaround.
RTI No. RTIF2-201118-003
Model SPARC M10-4S
Description When a SPARC M10-4S is added by using the addfru command, "XSCF hang-up is detected" or "Shutdown synchronization timeout" may be registered in the error log.
Workaround There is no effective workaround.
This is only registered in the error log. The command completes successfully. Ignore this error log entry.
RTI No. RTIF2-201118-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If a hardware error occurs in a physical partition (PPAR) and the PPAR is forcibly powered off, "No analytical target" may be registered in the error log after a while without registering the correct cause of the error.
Workaround There is no effective workaround.
RTI No. RTIF2-201118-006
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Some of the OID information in the MIB definition file for XSCF expansion may not have been updated correctly, so the SNMP manager acquired the wrong information.
Workaround There is no effective workaround.
RTI No. RTIF2-201118-011
Model SPARC M10-4S
Description Suppose that a user without the fieldeng privilege specifies an IP address for host and executes the ping or traceroute command on the system connected to a crossbar box. Then, the message "This private IP address cannot be accessed." appears, and the command ends with an error.
Workaround There is no effective workaround.
Log in as a user with the fieldeng privilege.
RTI No. RTIF2-201117-004
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Login to the XSCF may take a while when using a self-authenticated certificate in the LDAP server certificate chain.
Workaround There is no effective workaround.
RTI No. RTIF2-201117-009
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description You may be able to log in to XSCF Web even when XSCF initialization has not been completed.
Workaround There is no effective workaround.
Once login to the XSCF shell is possible, log in to XSCF Web and perform operations.
RTI No. RTIF2-160909-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The XSCF may be unable to detect power supply unit (PSU) failures.
Workaround Use one of the following methods to determine whether a PSU has failed. If a PSU failure has been determined, replace the PSU.
- The PSU LED goes on (amber) or blinks (green) while the physical partition (PPAR) is running.

- After the physical partition (PPAR) is powered off, a PSU failure is registered in an XSCF log when the PPAR is powered on again.
RTI No. RTIF2-160613-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Security fixes.
(CVE-2013-2566)
For details, see the Oracle website relating to the following: Critical Patch Updates
Workaround Update the XCP firmware to XCP 2280 or later.
RTI No. RTIF2-151117-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If there are multiple iSCSI targets when the show-iscsi command is executed at the ok prompt, one of the iSCSI targets may be unable to log in. The detection of such a target will terminate the command with the "login failed" error displayed. At this time, no information is output about other iSCSI targets that have not tried to log in.
[Example] Login failure of the second iSCSI target
{0} ok show-iscsi /pci@8100/pci@4/pci@0/pci@0/network@0
1000 Mbps full duplex Link up
Target: iqn.1986-03.com.sun:02:27f6951c-a432-4a86-b6c4-de72743cd25a
Lun 0-0-0-0
Disk SUN COMSTAR 1.0 71669440 Blocks, 36 GB
Lun 1-0-0-0
Disk SUN COMSTAR 1.0 71669440 Blocks, 36 GB
Target: iqn.1986-03.com.sun:02:c5662c3b-a6d9-4a69-b0d0-c6445a23383b
Evaluating:
login failed
{0} ok
Workaround If the output of the show-iscsi command does not show the intended iSCSI target, check the iSCSI target information from the target. For the check procedure from the iSCSI target, see the respective target manual.
RTI No. RTIF2-151105-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Security fixes.
(CVE-2015-4000)
For details, see the Oracle website relating to the following: Critical Patch Updates
Workaround Update the XCP firmware to XCP 2280 or later.
RTI No. RTIF2-151105-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose that you select [Verified Boot] from the [PPAR Operation] menu of XSCF Web to register the X.509 public key certificate for the user using the verified boot. In this case, "Space is not allowed." is displayed for the attempt to register the copied X.509 public key certificate, and the certificate cannot be registered.
Workaround To register the copied X.509 public key certificate, use the addvbootcerts(8) command. Use XSCF Web to register the X.509 public key certificate by specifying USB media or an http/https server.
RTI No. RTIF2-151105-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If a fan failure occurs, the physical partition (PPAR) may be powered off even when it does not need to be powered off.
Workaround There is no effective workaround.
[How to restore]
Replace the faulty fan unit. After that, power on the PPAR.
RTI No. RTIF2-151105-004
Model SPARC M10-4, SPARC M10-4S
Description If "PSU input power failure / PSU input power recover" is frequently registered in the event log because of power supply unit (PSU) failures, an XSCF panic may occur repeatedly, and the XSCF may stop.
Workaround There is no effective workaround.
If this is frequently registered in the PSU event log, replace the faulty PSU.
RTI No. RTIF2-151105-005
Model SPARC M10-4S
Description Suppose that a FRU fails when you replace or add a SPARC M10-4S chassis or replace an XSCF unit (XSCFU). In this case, a timeout may occur in 90 minutes even though the timeout is supposed to occur in 45 minutes according to the display of the maintenance menu.
[Example] A FRU of the XSCFU is faulty.
Waiting for XBBOX#81/XSCFU to enter ready state.
[This operation may take up to 45 minute(s)]
(progress scale reported in seconds) 0..... 30..... 60..... 90..... 120..... 150..... 180..... 210.....
240..... 270..... 300..... 330..... 360..... 390..... 420..... 450.....
480..... 510..... 540..... 570..... 600..... 630..... 660..... 690.....
--- Omitted ---

2400.....2430.....2460.....2490.....2520.....2550.....2580.....2610....

2640.....2670.....2700.....Omitted
Workaround There is no effective workaround.
[How to restore]
Use another FRU.
RTI No. RTIF2-151105-006
Model SPARC M10-1
Description Suppose that you select [PSB Configuration] from the [PPAR Operation] menu of XSCF Web to set memory mirror mode for the CPU of the system board. In this case, "System error: unknown error." is displayed and the setting cannot be made.
Workaround To set memory mirror mode for the SPARC M10-1, use the setupfru(8) command.
RTI No. RTIF2-151020-001
Model SPARC M10-4S
Description Suppose that the firmware version is XCP 2250 or later in a system configuration that has at least 3 BBs or a crossbar box. In this system configuration, if Oracle Solaris stays running for a long time after XSCF master/standby switching, the Oracle Solaris time may shift when the physical partition (PPAR) is powered off and on.
Also, in the same system configuration with a similar firmware version, the following error log is registered with the XSCF every 10 days after XSCF master/standby switching.
Date: Sep 15 11:42:38 JST 2015
 Code: 20000000-00560300fcff0000ff-01e400010000000000000000
 Status: Notice Occurred: Sep 15 11:43:08.531 JST 2015
 FRU: /BB#2/CMUL,/FIRMWARE
 Msg: XSCF self diagnosis warning detection
Workaround After XSCF master/standby switching, promptly perform any of the following operations.
- Execute the rebootxscf(8) command to reset all the XSCFs.

- Execute the rebootxscf(8) command to reset the XSCFs that are neither the master nor standby.

- Stop all the PPARs, and then turn off all the input power supplies. After that, wait at least 30 seconds, and then turn on the input power supplies.

[How to restore]
Execute the following procedure to start Oracle Solaris in single user mode and then set the time.
1. Execute the poweroff(8) command to power off the PPAR.

2. Execute the showpparstatus(8) command to confirm that the status is "Powered off," indicating that the PPAR has been powered off.

3. Set the OpenBoot PROM environment variable auto-boot? to "false."

XSCF> setpparparam -p ppar_id -s bootscript "setenv auto-boot? false"
4. Execute the poweron(8) command to power on the PPAR.
5. Execute the console(8) command to connect to the control domain console and display the ok prompt.

6. Start Oracle Solaris in single user mode.

{0} ok boot -s
7. Execute the date(1) command to set the Oracle Solaris time.

[Example] Setting for 18:30:00 on October 20, 2015
# date 1020183015.00
RTI No. RTIF2-150818-001
Model SPARC M10-4S
Description When you execute the deleteboard(8) command with the DR feature to remove a system board (PSB) where the XSCF is rebooting, the deleteboard(8) command may end abnormally with the "SCF process down detected" error. If the target system board is the standby XSCF, the master XSCF will become non-responsive while inactive. If the target system board is the slave XSCF, the master XSCF will reboot, with the result of switching between the master XSCF and standby XSCF.
In contrast, when the addboard(8) command is executed to add a PSB, and a command timeout is detected, then the command ends abnormally. In this event, the master XSCF and standby XSCF are not switched.
The following example shows the deleteboard(8) command terminated due to an internal error:
[Example]
XSCF> deleteboard -c disconnect -m unbind=resource 00-0
PSB#00-0 will be unconfigured from PPAR immediately. Continue?[y|n] :y
All domains are temporarily suspended, proceed?[y|n] :y
Start unconfigure preparation of PSB. [1200sec]
0|/end
An internal error has occurred. Please contact your system administrator.
XSCF> 
Workaround Execute the showhardconf(8) command to confirm that [Status] of every crossbar box and the SPARC M10-4S is "Normal." Then, execute the deleteboard(8) or addboard(8) command.
During the execution of the deleteboard(8) or addboard(8) command, do not execute any command that involves an XSCF reboot by the rebootxscf -a or switchscf(8) command.
[How to restore]
- If the target system board is the standby XSCF

Turn off the input power to all SPARC M10 system chassis or crossbar box chassis, and then turn it on again (AC OFF/ON).

- If the target system board is the slave XSCF

Follow the instructions in [Workaround] to remove or add the system board using the DR feature.
RTI No. RTIF2-150729-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When a DIMM failure is detected during the self-diagnosis test (POST) on the physical partition (PPAR), the component is marked as a failure. Even after DIMM replacement, the failure mark is not cleared. In the following example, after replacement, components are marked as failures and their status is "Deconfigured."
[Example]
XSCF> showstatus
*   MBU Status:Deconfigured;
*      CPU#0 Status:Deconfigured;
*      MEM#00A Status:Deconfigured;
*      MEM#01A Status:Deconfigured;
*      MEM#02A Status:Deconfigured;
*      MEM#03A Status:Deconfigured;
Workaround There is no effective workaround.
[How to restore]
Update the firmware to XCP 2250 or later. Set the mode switch on the operation panel to Service mode, turn off the input power, and then turn it on again (AC OFF/ON).
RTI No. RTIF2-150708-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose the motherboard unit (MBU), CPU memory unit lower (CMUL), or CPU memory unit upper (CMUU) is replaced at the same time as a microSD card. Then, the self-diagnosis test (POST) on the physical partition (PPAR) detects and marks the component as a failure. Even after the replacement, the failure mark is not cleared. In the following example, after replacement, components are marked as failures and their status is "Deconfigured."
[Example]
XSCF> showstatus
*   MBU Status:Deconfigured;
*      CPU#0 Status:Deconfigured;
*      MEM#00A Status:Deconfigured;
*      MEM#01A Status:Deconfigured;
*      MEM#02A Status:Deconfigured;
*      MEM#03A Status:Deconfigured;
Workaround When replacing the motherboard unit (MBU), CPU memory unit lower (CMUL), or CPU memory unit upper (CMUL) and a microSD card, replace them one at a time, not at the same time.
[How to restore]
Update the firmware to XCP 2250 or later. Set the mode switch on the operation panel to Service mode, turn off the input power, and then turn it on again (AC OFF/ON).
RTI No. RTIF2-150626-001
Model SPARC M10-4S
Description
Suppose that you select [PPAR Operation] from the [Verified Boot] menu of XSCF Web and specify a PPAR that is not PPAR#0 to display details of the X.509 public key certificate for a user using the verified boot. In this case, the wrong X.509 public key certificate is displayed for PPAR#0.
Workaround To check the public key certificate of a PPAR that is not PPAR#0, use the showvbootcerts(8) command.
RTI No. RTIF2-140808-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description After the occurrence of a component failure, you may fail to power off the physical partition (PPAR).
This phenomenon may occur when the following procedure is performed:
1. While the PPAR is being reactivated due to a component failure, the poweroff(8) command is executed without the -f option.

2. After the PPAR is powered off upon a PPAR reactivation failure due to a component failure, the poweron(8) command is executed to power on the PPAR.

3. The poweroff(8) command is executed without the -f option.
Workaround
Do not execute the poweroff(8) command while the PPAR is being reactivated due to a component failure.
[How to restore]
Execute the shutdown command from Oracle Solaris to power off the PPAR.
[Example]
# shutdown -y -g0 -i5
RTI No. RTIF2-140616-005
Model SPARC M10-4S
Description If you turn off the input power of the master XSCF (AC OFF) and then turn it on again (AC ON) when the power to the physical partition (PPAR) is off, error handling may fail due to the temporary absence of the master XSCF. In addition, the PPAR may remain abnormal so that you may be unable to power on the PPAR again.
You can determine the occurrence of this phenomenon by executing the showboards(8) command. If the value of "Pwr Conn Conf" displayed as the master XSCF PSB status is "n y n," this phenomenon has occurred.
[Example] If the master XSCF is BB#00
XSCF> showboards -a
PSB  PPAR-ID(LSB) Assignment  Pwr  Conn Conf Test    Fault
---- ------------ ----------- ---- ---- ---- ------- --------
00-0 00(00)       Assigned    n    y    n    Passed  Normal
01-0 01(00)       Assigned    y    y    n    Passed  Normal
Workaround There is no effective workaround.
[How to restore]
Turn off the input power to all SPARC M10-4S chassis that make up the system and then turn it on again.
RTI No. RTIF2-140507-010
Model SPARC M10-4S
Description In a system configuration with at least 3 BBs or a crossbar box, if the master/standby switchover occurs more than 256 times, the "SCF process down detected" error is detected by the slave XSCF, and XSCF "coremgrd" may cause a "process down."
Workaround Do not perform consecutive XSCF master/standby switchover.
[How to restore]
Reset the XSCF. The system will become usable.
RTI No. RTIF2-140507-012
Model SPARC M10-4S
Description
In a system with several SPARC M10-4S, if a crossbar box or the XSCF unit of a crossbar box is replaced after powering off all chassis and then the input power is turned on, the following error log may be registered.
Indispensable parts are not installed (OPNL).
Indispensable parts are not installed (FAN).
Indispensable parts are not installed (PSU).
Workaround When replacing a crossbar box, do so after turning off the input power (AC OFF) to only the crossbar box being replaced.
When replacing the XSCF unit of a crossbar box, execute the replacefru(8) command to do so.
Refer to the Fujitsu M10-4/Fujitsu M10-4S/SPARC M10-4/SPARC M10-4S Service Manual for replacing the crossbar box or the XSCF unit in the crossbar box.
[How to restore]
Turn off/on the input power (AC OFF/ON) of the newly installed crossbar box.
RTI No. RTIF2-140410-005
Model
SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If a hardware error is detected immediately after powering off or restarting the physical partition (PPAR), the PPAR power off or restart process may be stopped, and may not be completed.
To check whether this phenomenon has occurred, power off or restart the PPAR and then execute the showpparprogress(8) command. If the PPAR remains in the power on state and the power off process has not completed after at least one minute has passed, this phenomenon has occurred.
[Example of unsuccessful power off]
XSCF> showpparprogress -p 0
This PPAR is powered on.
Normally, when the PPAR power off completes, the power off sequence and PPAR state are as follows.
[Example of successful power off]
XSCF> showpparprogress -p 0
PPAR Power Off            PPAR#0 [1/3]
CPU Stop                  PPAR#0 [2/3]
PSU Off                   PPAR#0 [3/3]
The sequence of power control is completed.
Workaround There is no effective workaround.
[How to restore]
If the PPAR power supply remains in the power-on state 30 minutes after executing the showpparprogress(8) command, turn off the input power to all chassis and then turn it on again (AC OFF/ON).
RTI No. RTIF2-140409-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If you disconnect and then connect USB memory while the executed snapshot(8) command is collecting information into the memory, the following hardware error may be detected:
Msg: DMA timeout error Hard detected
At this time, the logical domain is continuously operated but the functions that access hardware (e.g., power on/off, monitoring function) no longer operate.
Workaround Do not connect and then disconnect the USB memory while information is being collected into the memory by the snapshot(8) command.
[How to restore]
Turn off the input power to the system and then turn it on again (AC OFF/ON).
RTI No. RTIF2-140409-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description An error log due to hardware is erroneously registered in the following cases.
- A watchdog timeout occurs due to a software factor

- XSCF RESET switch is pressed

- XSCF panic occurs due to firmware

[Example]
- Incorrect

Status: Alarm
FRU: /FIRMWARE,/MBU
Msg: SCF panic detected
- Correct

Status: Notice
FRU: /FIRMWARE,/MBU
Msg: SCF panic detected
Workaround There is no effective workaround.
Read the "Alarm" status as "Notice".
RTI No. RTIF2-140402-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The following special characters cannot be included in the e-mail address input field for the [Settings] - [Service] - [SMTP], [Settings] - [Email Reporting], [Settings] - [Audit], and [Settings] - [CoD Activation] menus on XSCF Web.
"!" "#" "$" "%" "&" "'" "*" "+" "/" "=" "?" "^" "'" "{" "|" "}" "~"
Workaround Use the setemailreport(8) command in the XSCF shell.
RTI No. RTIF2-140402-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When using XSCF Web in Internet Explorer, if you attempt to delete the second and subsequent User/Group settings of [Groups] and [View Access] of VACM in the [XSCF] - [Settings] - [Service] - [SNMP Security] menu, an error message is output and the deletion cannot be executed.
Workaround Execute the deletion by using XSCF Web in Firefox or the setsnmpvacm(8) command in the XSCF shell.
RTI No. RTIF2-140212-008
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When powering on, or rebooting a physical partition (PPAR), even if the process is stopped due to the failure of a component, the POWER LED of the operation panel keeps blinking. This problem does not occur while operating the system.
Workaround There is no effective workaround.
Blinking of the POWER LED on the operation panel is canceled if the physical partition (PPAR) is powered on when the process of powering on/restarting the physical partition (PPAR) is interrupted.
RTI No. RTIF2-140212-012
Model SPARC M10-4S
Description In a system configuration with at least 3 BBs or a crossbar box, if the XSCF master/ standby switchover occurs 60 times or more, a "process down" may occur on the slave XSCF and the slave XSCF may be reset.
Workaround There is no effective workaround.
The slave XSCF will be restored by the reset and the system can be used continuously after that.
RTI No. RTIF2-131213-012
Model SPARC M10-4S
Description After replacing SPARC M10 with the replacefru(8) command, diagnosis processing may not terminate properly.
[Example] The replacement of BB#2
Diagnostic tests for BB#2 have started.
Initial diagnosis is about to start, Continue?[y|n] :y
PSB#02-0 power on sequence started.
0.....30.....end

Initial diagnosis started. [7200sec]
0..... 30..... 60..... 90.....120.....150.....180.....210.....240.....

270.....300.....330.....360.....390.....420.....450.....480.....510.....

540.....570.....600.....630.....660.....690.....720.....750.....780.....

810.....840.....870.....900..end

Initial diagnosis has completed.
PSB power off sequence started. [1200sec]
0..... 30..... 60..... 90.....120.....150.....180.....210.....240.....

270.....300.....330.....360.....390.....420.....450.....480.....510.....

540.....570.....600.....630.....660.....690.....720.....750.....780.....

810.....840.....870.....900.....930.....960.....990.....1020.....1050.....

1080.....1110.....1140.....1170.....1200end

Failed to power off. Please check the FRU.
An internal error has occurred. Please contact your system administrator.
done
[Warning:030]
testsb failed.[c:cancel] :
Workaround There is no effective workaround.
[How to restore]
Re-execute the replacefru(8) command.
RTI No. RTIF2-130802-003
Model SPARC M10-4S
Description When you replace the XSCF unit of the crossbar box by using the replacefru(8) command, the command is completed normally, but the following error log may be registered. The suspected location indicated by this error log is incorrect.
SCF:Board control error (link failed)
Workaround Replace the XSCF unit of the same crossbar box by using the replacefru(8) command again. If you have turned off the input power (AC OFF) during the replacement work, disconnect and then connect all the XSCF BB control cables.
RTI No. RTIF2-130711-003
Model SPARC M10-4S
Description Before active replacement of the XSCF unit of the crossbar box is completed, the replacefru(8) command is completed normally.
Workaround When you use the replacefru(8) command to replace the XSCF unit, the following message may appear after you replace the XSCF unit. If it does, wait 10 minutes, and then enter "f".
The replacement of XBBOX#xx/XSCFU has completed normally.[f:finish] : 
RTI No. RTIF2-130305-023
Model SPARC M10-4S
Description If an error occurs in the DC-DC converter of a crossbar unit, "XB-XB interface link-up error." is erroneously registered instead of the correct error log of "LSI detected errors with power subsystem failure."
Workaround There is no effective workaround.
Check for power errors if the error log of "XB-XB interface link-up error" was registered.
Ignore the error log for "XB-XB interface link-up error" if a power error has occurred.