Problems Resolved in XCP 3050
Problems Resolved in XCP 3050
The following table lists the problems resolved in XCP 3050.
| RTI No. | RTIF2-210118-012 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | An update to the XCP firmware may end with an error due to intermittent failure of the SD card in the motherboard unit (MBU) or XSCF unit (XSCFU), so subsequent CMU firmware updates may result in an error. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-210118-013 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | Multiple executions of the reset command and showsnmp command may take a while. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-210118-014 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | If the SD card in the motherboard unit (MBU) or 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-210118-015 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| 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 M12-1, the SPARC M12-2, or the 1BB configuration with the SPARC M12-2S 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-210118-016 |
| Model | SPARC M12-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-210118-017 |
| Model | SPARC M12-2S |
| Description | The component tree in [Logical Tree] on the [Logical] bar of XSCF Web displays PSBs redundantly. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-210118-018 |
| Model | SPARC M12-2S |
| Description | Due to a crossbar box failure, the Reset event log of the physical partition (PPAR) may not be registered even if a Fatal reset is perfomed in the PPAR to automatically restore the system. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-180525-002 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | Security fixes. (CVE-2017-1000254, CVE-2015-3144, CVE-2015-3145, CVE-2015-3153, CVE-2015-3236, CVE-2015-3237, CVE-2016-0755, CVE-2016-3739, CVE-2016-5419, CVE-2016-5420, CVE-2016-5421, CVE-2016-7167, CVE-2016-7141, CVE-2016-8615, CVE-2016-8616, CVE-2016-8617, CVE-2016-8618, CVE-2016-8619, CVE-2016-8620, CVE-2016-8621, CVE-2016-8622, CVE-2016-8623, CVE-2016-8624, CVE-2016-9586, CVE-2017-7407) For details, see the Oracle website relating to the following: Critical Patch Updates |
| Workaround | Update the XCP firmware to XCP 3050 or later. |
| RTI No. | RTIF2-180220-001 |
| Model | SPARC M12-1 |
| Description | After a physical partition (PPAR) is powered on, the Dual 10Gigabit Ethernet card (10GBase-T) may not be recognized. [Error message example] XSCF> showlogs error Date: Nov 06 13:05:58 JST 2017 Code: 40002000-0019ff002e110000ff-020024350000000000000000 Status: Warning Occurred: Nov 06 13:05:58.901 JST 2017 FRU: /MBU/PCI#2,/MBU Msg: PCI Express link not active |
| Workaround | There is no effective workaround. [How to restore] Power off the physical partition (PPAR) and power it on again. |
| RTI No. | RTIF2-180220-002 |
| Model | SPARC M12-1 |
| Description | showhardconf may not properly display the Subsystem_Vendor-ID or Subsystem-ID of the graphics card. [Display example: showhardconf] XSCF> showhardconf: PCI#2 Name_Property:pci; + Vendor-ID:104c; Device-ID:8231; + Subsystem_Vendor-ID:0000; Subsystem-ID:0000; + Model:;: |
| Workaround | Ignore this message because there is no impact on system operation. |
| RTI No. | RTIF2-180214-001 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | In a system where 64 GB DIMMs are mounted, powering on a physical partition (PPAR) may cause a diagnosis failure with either of the following entries output to the error log. Date: Nov 14 07:12:58 JST 2017 Code: 40002000-004b870134110000ff-020014260000000000000000 Status: Warning Occurred: Nov 14 07:12:58.317 JST 2017 FRU: /BB#0/CMUL/MEM#04B,/BB#0/CMUL Msg: Window size is too small (read VrefDQ training) Date: Oct 24 16:48:46 JST 2017 Code: 40002000-004b870134110000ff-020014240000000000000000 Status: Warning Occurred: Oct 24 16:48:46.655 JST 2017 FRU: /BB#0/CMUL/MEM#05A,/BB#0/CMUL Msg: Address not found (PRBS access) This symptom occurs when any of the following work has been performed: - Adding a 64 GB DIMM (including changes to a 64 GB DIMM to expand capacity) - Adding a CPU module (CPU memory unit upper (CMUU)) with 64 GB DIMMs mounted - Adding a SPARC M12-2S with 64 GB DIMMs mounted, into a building block configuration Note - This symptom also occurs when 64 GB DIMMs are moved to the current system from another system. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-170626-002 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | When only the host node (SPARC M12) loses power and then recovers, the ETERNUS power is turned off once. At this time, the ETERNUS power stays off even after the power to the physical partition (PPAR) is turned on. This may occur when the remote power management function (RCIL) is enabled on the SPARC M12 system connected to the ETERNUS. |
| Workaround | There is no effective workaround. If the ETERNUS power is off, turn off and on the PPAR again to recover. |
| RTI No. | RTIF2-170224-051 |
| Model | SPARC M12-1, SPARC M12-2, SPARC M12-2S |
| Description | If the poweroff -f command is executed while the physical partition (PPAR) is restarting, the next execution of the poweron command may cause an error that does not allow the PPAR to be powered on. [Example] The PPAR cannot be powered on. XSCF> poweron -p 0 PPAR-IDs to power on :00 Continue? [y|n] :y 00 : Not powering on : An internal error has occurred. Please contact your system administrator. |
| Workaround | Before executing the poweroff -f command, use the showpparprogress command to check the status of the target PPAR. If "PPAR reset" is displayed at this point, it means that the target PPAR is restarting. The PPAR restart is completed by the time that "The sequence of power control is completed." appears. Until this message appears, do not execute the poweroff -f command. If "This PPAR is powered on." or "This PPAR is powered off." appears, the PPAR has not been restarted. [Example] The PPAR restart has completed. XSCF> showpparprogress -p 0 PPAR reset PPAR#0 [ 1/13] : CPU Start PPAR#0 [13/13] The sequence of power control is completed. XSCF> [How to restore] Turn off the input power to the system, wait 30 seconds, and then turn it on again. (AC OFF/ON) |
< Previous Page | Next Page >