Problems Resolved in XCP 3070
Problems Resolved in XCP 3070
The following table lists the problems resolved in XCP 3070.
RTI No. | RTIF2-201106-001 |
Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
Description | The sun4v error report might be corrupted if multiple logical domains panic at the same time. |
Workaround | There is no effective workaround. |
RTI No. | RTIF2-190903-004 |
Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
Description | Security fixes. (CVE-2019-6111, CVE-2019-6109, CVE-2018-20685, CVE-2019-1559, CVE-2016-8610, CVE-2018-1000007, CVE-2018-18066, CVE-2018-18065, CVE-2018-12404, CVE-2018-12384, CVE-2018-7185) For details, see the Oracle website relating to the following: Critical Patch Updates |
Workaround | Update the XCP firmware to XCP 3070 or later. |
RTI No. | RTIF2-190902-003 |
Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
Description | Security fixes. (CVE-2018-16842) For details, see the Oracle website relating to the following: Critical Patch Updates |
Workaround | Update the XCP firmware to XCP 3070 or later. |
RTI No. | RTIF2-190725-001 |
Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
Description | After an XCP firmware update when the NTP client setting for the XSCF is enabled, the XSCF time may shift. If the physical partition power-on/off schedule has been set and a scheduled operation is performed, the operation time may shift as a result. This may cause the OS to not start at the specified time or to shut down at a time other than the specified time. |
Workaround | Update the XCP firmware to XCP 3070 or later. This problem does not occur while a firmware update to XCP 3070 or later is in progress. [How to restore] Using the showdate command or showntp -l command, confirm that the XSCF time has not shifted. If the XSCF time has shifted, reboot the XSCF with the rebootxscf -a command. [Example] Using the showntp -l command to check the time difference with the NTP server The following example shows an offset of -607086 ms (607 seconds). XSCF> showntp -l remote refid st t when poll reach delay offset jitter ============================================================================== *xxx.xx.xx.xx 192.168.yy.yy 6 u 42 64 377 0.191 -607086 81.767 127.127.1.0 .LOCL. 5 l 26h 64 0 0.000 0.000 0.000 |
RTI No. | RTIF2-190716-002 |
Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
Description | E-mail notification and notification through REMCS or SNMP trap are not provided when the input power to the power supply unit (PSU) of the PCI expansion unit is turned off. Likewise, if an error occurs in the primary circuit, no such notification is provided. Similarly, e-mail notification is not provided for some hardware failures in the PCI expansion unit. |
Workaround | There is no effective workaround that provides notification when the PSU input power for the PCI expansion unit is turned off or when the primary circuit has an error. Use notification through SNMP trap to monitor other hardware failures. |
RTI No. | RTIF2-170224-031 |
Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
Description | When the input power of a PCI expansion unit is turned off (AC OFF), an error log is registered but, notification through SNMP trap or REMCS is not performed. You can confirm that the input power of the PCI expansion unit has been turned off, in the execution results of the showlogs error command, like the following output log. Date: Mar 10 20:03:05 JST 2017 Code: 10000400-00d4000000ff0000ff-1100002a0000000000000000 Status: Information Occurred: Mar 10 20:03:00.905 JST 2017 FRU: /BB#0/PCI#8/PCIBOX#2003/PSU#0 Msg: AC FAIL Diagnostic Code: 00083230 30330000 0000 00080000 00000000 0000 00080000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 |
Workaround | There is no effective workaround. |
< Previous Page | Next Page >