Skip to main content

Problems Resolved in XCP 3130


Problems Resolved in XCP 3130
The following table lists the problems resolved in XCP 3130.
Table 3-10  Problems Resolved in XCP 3130
RTI No. RTIF2-230919-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description If the ETERNUS enters maintenance mode and then is manually powered on without the use of the remote power management function (RCIL), the ETERNUS may in rare cases be powered off when maintenance mode is canceled.
This problem may occur when all of the following is true:
- RCIL is set between multiple host nodes and the ETERNUS in the configuration

- RCIL is enabled on at least one host node

- While all host nodes are powered off, the XSCF network is temporarily disconnected by, for example, an XSCF reboot on some host nodes

This problem does not occur while the host nodes are in operation.
Workaround To power on and perform maintenance on the ETERNUS without using RCIL, disable RCIL on all host nodes before beginning the work.
After finishing the work, restore the original RCIL settings on all the host nodes.
RTI No. RTIF2-230919-003
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description An attempt with the password command or XSCF Web to set a password for an XSCF user account may fail, and the "Operation failed" error message may be output.
[Example]
XSCF>password nuser
Password: **************
password: Operation failed
XSCF>
Workaround If the "Operation failed" error message is output, change the password value and set the password again.
RTI No. RTIF2-230919-005
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Security fixes.
(CVE-2021-43527, CVE-2022-4450)
For details, see the Oracle website relating to the following:
Critical Patch Updates
Workaround Update the XCP firmware to XCP 3130 or later.
RTI No. RTIF2-211015-003
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description If the XSCF is rebooted or the input power is turned on when the NTP client setting for the XSCF is enabled, the XSCF time may shift in rare cases.
As a result, powering on a physical partition may cause the logical domain time to shift.
After this XSCF time deviation occurs, event log output will show that the XSCF time and NTP server time have been successfully synchronized. After that, by executing the showntp -l command, you can check whether XSCF and NTP server time synchronization has stopped.
[Example] Output in the event log when the time has been successfully synchronized, and output by the showntp -l command when time synchronization has stopped
XSCF>showlogs event
Date Message
May 11 14:55:45 JST 2021 NTP service found NTP server to synchronize.
XSCF>showntp -l
NTP is unavailable.
Workaround There is no effective workaround.
After rebooting the XSCF and confirming that the XSCF time is normal, start Oracle Solaris in single user mode and set the correct time.