Skip to main content

Problems Resolved in XCP 2350


Problems Resolved in XCP 2350
The following table lists the problems resolved in XCP 2350.
Table 3-18  Problems Resolved in XCP 2350
RTI No. RTIF2-201221-001
Model SPARC M10-1
Description If two or more fans or power supply units (PSUs) fail in a system with a connected PCI expansion unit, it may take a while to power on the physical partition (PPAR) next time.
Workaround Before powering on the PPAR, power off the input power supply and then power it on again.
RTI No. RTIF2-201215-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description An update to the XCP firmware may end with an error due to intermittent failure of the microSD card in the motherboard unit (MBU), the CPU memory unit lower (CMUL), or the XSCF unit (XSCFU). In such cases, subsequent CMU firmware updates may result in an error.
Workaround There is no effective workaround.
RTI No. RTIF2-201116-004
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description To restore XSCF setting information, the restoreconfig command may be executed when XSCF-LAN network settings are not configured, on a system with the remote power management function (RCIL) of the SPARC M12/M10 enabled. In such cases, the command may abnormally end with the error message "An internal error has occurred. Please contact your system administrator."
Workaround There is no effective workaround.
RTI No. RTIF2-201116-013
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description In a system using the remote power management function (RCIL) of the SPARC M12/M10, the restoreconfig command may be executed to restore the XSCF setting information on a system belonging to remote power management group 32. Then, the settings of the remote power management function cannot be restored.
Workaround There is no effective workaround.
RTI No. RTIF2-201110-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description In some very rare cases, the "NAND FMEM Fsck Error" error may be detected when the input power is turned off while the XSCF is starting.
Workaround There is no effective workaround.
RTI No. RTIF2-201110-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The PCI hot plug (PHP) function may be used to perform active maintenance on a PCIe card in a system with multiple PCI expansion units connected. In such cases, the connection of the PCI expansion units may not be recognized and displayed by executing the ioxadm -v list command.
Workaround There is no effective workaround.
This does not affect Oracle Solaris operation. Oracle Solaris can recognize the connections of the PCI expansion units.
RTI No. RTIF2-201109-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The root domain might panic when an I/O domain stops.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-003
Model SPARC M10-4, SPARC M10-4S
Description Hypervisor might abort if a logical domain stops after the CPU chip is degraded.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-005 
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description CPU performance counter (CPC) values are corrupted in Oracle Solaris kernel zones.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-006
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Intermittent parity errors in CPU registers might cause a reset hang.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-007
Model SPARC M10-4S
Description During dynamic deleteboard operation, the PPAR might reset due to RED State.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-008
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If live migration of a guest domain fails, logical domains on the physical partition as the migration source may panic or Hypervisor may abort.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-010
Model SPARC M10-4S
Description An incorrect TOD might be degraded when a TOD error occurs.
Workaround There is no effective workaround.
RTI No. RTIF2-171011-001
Model SPARC M10-4S
Description The dumpconfig(8) command may fail when firmware has been updated from XCP 2250 or earlier to XCP 2260 or later.
Workaround Execute one of the following XSCF commands:
- showremotestorage(8)

- snapshot(8)

- rebootxscf -a

RTI No. RTIF2-171011-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the XSCF shell is forcibly disconnected during execution of the showsnmp command, executed XSCF commands may in rare cases not respond.
After that, if XSCF commands do not respond many times, an XSCF panic and reboot occurs.
Workaround There is no effective workaround.
[How to restore]
Reboot all the XSCFs by executing the rebootxscf -a command.
If the executed rebootxscf -a command fails to reboot all XSCFs, perform the following:
- For a building block configuration
Shut down every Oracle Solaris instance and then turn off/on (AC OFF/ON) the input power to all chassis.

- For the SPARC M10-1, the SPARC M10-4, or the 1BB configuration with the SPARC M10-4S
Press the RESET switch of the XSCF, or shut down every Oracle Solaris instance and then turn off/on the input power (AC OFF/ON).
RTI No. RTIF2-171011-003
Model SPARC M10-1
Description If the DC-DC converter (DDC) mounted on the motherboard unit (MBU) fails, a power failure may be erroneously detected while the DCC failure is undetected.
Workaround There is no effective workaround.
Replace the MBU.
RTI No. RTIF2-171011-004
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description
- If the reporting function by REMCS is used, any of the following symptoms may very rarely occur if the XSCF is not rebooted for a long time.

- The power of the physical partition is not turned on.

- Reporting by REMCS is not conducted.

- A REMCS periodical connection timeout occurs.

- The error message "An internal error has occurred." appears when an XSCF command is executed, and the command fails.
Workaround Reboot all of the XSCFs by executing the "rebootxscf -a" command.
At that time, it is not necessary to power off the physical partition.
RTI No. RTIF2-171011-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the motherboard unit (MBU), the CPU memory unit lower (CMUL), or a microSD card in the XSCFU fails, the CPU Activation key backup information on the PSU backplane (PSUBP) may also be deleted.
This may make it impossible to register the CPU Activation key again.
Workaround There is no effective workaround.
[How to restore]
If the CPU Activation key cannot be registered again, execute the restoredefaults -c xscf command. Then, after the XSCF stops, turn off the input power (AC OFF).
After that, turn on the input power (AC ON) again, and register the CPU Activation key again.
RTI No. RTIF2-170626-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If only the host node (SPARC M10) loses power, the power of the ETERNUS is turned off when the power of the host node recovers. At this time, the power of the ETERNUS is not turned on even when the power of the physical partition (PPAR) is turned on.
This may occur when the remote power management function (RCIL) is enabled on the SPARC M10 system with the ETERNUS connected.
Workaround There is no effective workaround.
If the power of the ETERNUS is not turned on, turn off and on the PPAR again to recover.
RTI No. RTIF2-170428-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Even when XCP firmware has been updated, the old XCP firmware version before the update may be displayed under the following cases:
- The [VERSION] button on XSCF Web is selected.

- The prtdiag -v command is executed on Oracle Solaris.

In this case, the correct XCP firmware version is displayed after the XSCF is rebooted, however, the following message appears at each XSCF login.
"XCP version of XSCF and Back-Panel mismatched!"
Workaround There is no effective workaround.
[How to restore]
Update the firmware again.
To update the firmware with the flashupdate command, specify the -f option.
RTI No. RTIF2-170405-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose you close the browser before finishing the collection of a snapshot from XSCF Web and then you execute the snapshot command to collect a snapshot on the XSCF shell. The newly executed command ends normally but no log was collected in the snapshot.
Workaround To collect a snapshot after you close the browser while collecting a snapshot from XSCF Web, collect it from XSCF Web again or wait about an hour after closing the browser to execute the snapshot command.
RTI No. RTIF2-161205-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description During firmware update for a PCI expansion unit, the "LINKCARD I2C error" error log may inadvertently be registered immediately after the start of the update.

Nov 27 19:28:26 M10-1 Event: SCF:LINKCARD update is started (LINKCARD=9, bank=1,PCIBOX version=1210: last version=1180)
Nov 27 19:28:29 M10-1 Warning: /BB#0/PCI#9/LINK:SCF:LINKCARD I2C error
Workaround There is no effective workaround.
Ignore the "LINKCARD I2C error" error log that is registered immediately after the start of the update.
The firmware update for the PCI expansion unit will succeed.
RTI No. RTIF2-150702-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose you attempt to execute the dumpconfig(8) command to save XSCF setting information, and then execute the restoreconfig(8) command to restore the XSCF setting information in the same chassis or other chassis. In this case, some settings may not be saved/restored or may be excessively restored on other chassis.
The following settings are not saved/restored in the same chassis or other chassis.
- Setting values for power operation at power recovery, set with the setpowerschedule -c recover command

- Setting values for enabling/disabling ASR function, set with the setservicetag(8) command

- Setting values for configuring a remote power management group, changing its settings, and enabling/disabling the remote power management function for the group, set with the setremotepwrmgmt(8) command


The following settings are excessively restored on the same or other chassis.
- Information on the time difference between the XSCF and the hypervisor of each physical partition (PPAR)
Workaround There is no effective workaround.
[How to restore]
Perform the following procedure.
1. Before saving the XSCF setting information with the dumpconfig(8) command, confirm the following settings.

- Setting for power operation at power recovery(recover mode)

[Example] Not powering on at power recovery
XSCF> showpowerschedule -a -m state
PPAR-ID schedule member recover mode
------- -------- ------ ------------
0       enable   4      off
- ASR function (Service Tag) enable/disable setting

[Example] Enabled
XSCF> showservicetag
Enabled
 
- Remote power management group settings

- Saving configuration and setting changes

[Example] Saving management file to ftp server when registering one remote power management group
XSCF> getremotepwrmgmt -G 1 ftp://server[:port]/path/file
- Remote power management function enable/disable setting

[Example] Enabled
XSCF> showremotepwrmgmt
[Remote Power Management Group#01 Information]
Remote Power Management Status :[Enable]
--- Omitted ---

2. Execute the dumpconfig(8) command to save the XSCF setting information.

3. Execute the restoreconfig(8) command to restore the XSCF setting information.

4. After restoring the XSCF setting information with the restoreconfig(8) command, execute the command below to implement a reset using the setting values confirmed in step 1.

- Restoring the setting for power operation at power recovery

[Example] Not powering on at power recovery
XSCF> setpowerschedule -a -c recover=off
 

- Restoring the ASR function (Service Tag) enable/disable setting

[Example] Setting enable
XSCF> setservicetag -c enable
 

- Restoring configuration and setting changes of the remote power management group and the enable/disable setting of the remote power management function

[Example] Restoring setting information based on management file saved to FTP server
(1) If there are other hosts included in the remote power management group, disable the remote power management function for the hosts.

XSCF> setremotepwrmgmt -c disable
(2) Restore the management file of the remote power management group.

XSCF> setremotepwrmgmt -c config "ftp://server[:port]/path/file"
(3) Enable the remote power management function. If you have disabled other hosts, enable them, too.

XSCF> setremotepwrmgmt -c enable
5. Power on the physical partition, and synchronize Oracle Solaris time with the NTP server or adjust the time with the date(1) command.