Skip to main content

Problems Resolved in XCP 3040


Problems Resolved in XCP 3040
The following table lists the problems resolved in XCP 3040.
Table 3-17  Problems Resolved in XCP 3040
RTI No. RTIF2-210209-008
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
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-210118-009
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
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-210118-010
Model SPARC M12-2S
Description If the physical partition dynamic reconfiguration (PPAR DR) function is used to incorporate a PSB into a PPAR when master/standby XSCF switching occurs, the incorporation may fail.
Workaround There is no effective workaround.
RTI No. RTIF2-210118-011
Model SPARC M12-2S
Description If the addboard command is executed when the physical partition dynamic reconfiguration (PPAR DR) function is used to incorporate a PSB into a PPAR, the "An internal error has occurred" error may occur and the incorporation may fail.
Workaround There is no effective workaround.
RTI No. RTIF2-201106-002 
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description The root domain might panic when an I/O domain stops.
Workaround There is no effective workaround.
RTI No. RTIF2-201106-003 
Model SPARC M12-2, SPARC M12-2S
Description Hypervisor might abort if a logical domain stops after the CPU chip is degraded.
Workaround There is no effective workaround.
RTI No. RTIF2-201106-005 
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description CPU performance counter (CPC) values are corrupted in Oracle Solaris kernel zones.
Workaround There is no effective workaround.
RTI No. RTIF2-201106-006 
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Intermittent parity errors in CPU registers might cause a reset hang.
Workaround There is no effective workaround.
RTI No. RTIF2-170801-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
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 this time, it is not necessary to power off the physical partition.
RTI No. RTIF2-170801-002
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Even when the XCP firmware has been updated, the old XCP firmware version before the update may be displayed for the following cases:
- The [VERSION] button on XSCF Web is selected.

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


In either case, the new 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-170508-006
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description The error log with a "LINKCARD I2C error" may inadvertently be registered during firmware update for a PCI expansion unit.
Workaround There is no effective workaround.
Ignore this error log entry.
The firmware update for the PCI expansion unit will succeed.
RTI No. RTIF2-170428-002
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Suppose you close the browser prematurely while collecting a snapshot from the XSCF Web and then execute the snapshot command to collect a snapshot on the XSCF shell. The newly executed command terminates normally but logs are not collected in the snapshot.
Workaround To collect a snapshot after you close the browser while collecting a snapshot from the XSCF Web, collect it from the XSCF Web again or wait about an hour after closing the browser to execute the snapshot command.