Problems Resolved in XCP 2240
Problems Resolved in XCP 2240
The following table lists the problems resolved in XCP 2240.
| RTI No. | RTIF2-210209-004 |
| Model | SPARC M10-4S |
| Description | Immediately after the XSCF starts, the showboards command, etc. may not be correctly displayed. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201118-002 |
| Model | SPARC M10-1 |
| Description | If the input power is turned off immediately after changing the startup mode of the XSCF startup mode function with the xscfstartupmode command, the setting might not be reflected. |
| Workaround | After executing the command, wait at least 35 seconds before turning off the input power. |
| RTI No. | RTIF2-141208-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | After a "CPU fatal error" occurs, the time required for a physical partition (PPAR) restart may be 6 to 30 minutes longer than usual. The required restart time varies depending on the number of mounted PCIe cards. If many PCIe cards are mounted, the following error may be mistakenly detected. - On a SPARC M10-4S system with a 2BB or larger configuration SRAM data error - On a SPARC M10-1/M10-4 system Timeout of Reset Watch. PPARID 0 |
| Workaround | There is no effective workaround. [How to restore] - If "SRAM data error" has been detected Replace the component at the suspected location indicated by the error log. After that, update the XCP firmware to XCP 2240 or later. - If "Timeout of Reset Watch. PPARID 0" has been detected Update the XCP firmware to XCP 2240 or later. |
| RTI No. | RTIF2-141203-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | In some rare cases, "CPU Internal Serious error" might occur. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-141113-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Security fixes. (CVE-2014-3566) For details, see the Oracle website relating to the following: Critical Patch Updates |
| Workaround | Update the XCP firmware to XCP 2240 or later. |
| RTI No. | RTIF2-141110-001 |
| Model | SPARC M10-4S |
| Description | The ldm command of Oracle VM Server for SPARC may not display correct CPU utilization and the dynamic resource management (DRM) may not work correctly on large domain systems where 150 domains or more exist. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-141106-001 |
| Model | SPARC M10-1 |
| Description | Any of the following errors related to abnormal temperature may be erroneously registered. - Temperature out of range error - High temperature at SW In these error logs, the first two bytes of the second field in [Code:] has the value of "0013". |
| Workaround | There is no effective workaround. Ignore this message because there is no impact on system operation. |
| RTI No. | RTIF2-141031-003 |
| Model | SPARC M10-4S |
| Description | After the system board is deleted by dynamic reconfiguration of physical partitions (PPAR DR), I/O devices on I/O domain may not work, or root domain or I/O domain may cause a panic. |
| Workaround | There is no effective workaround. [How to restore] If I/O devices does not cause a panic after physical partitions (PPAR DR), reboot the I/O domain. |
| RTI No. | RTIF2-141031-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Hypervisor Abort may occur if all of cores are degraded on the primary domain. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-141020-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When using the ASR function and an abnormality occurs with the fan unit in the PCI expansion unit or the SPARC M10 system chassis, the following incorrect fault telemetry is sent to ASR Manager. - An error in the fan unit of a PCI expansion unit is sent as an error in the fan unit of a SPARC M10 system chassis. - An error in the fan unit of a SPARC M10 system chassis is sent as an error in the fan unit of a PCI expansion unit. [Example] Error in a fan unit of the SPARC M10 system chassis - Incorrect message ID: device.fan.toofast_pcibox - Correct message ID: device.fan.tooslow This problem occurs when the four bytes from the beginning of the third field of [Code:] at execution of the showlogs error command are any of the following. 01911026, 01911027, 01911028, 01911029, 0191102a, 0191102b [Example] Error in fan unit of PCI expansion unit - Incorrect message ID: device.fan.tooslow - Correct message ID: device.fan.toofast_pcibox This problem occurs when the four bytes from the beginning of the third field of [Code:] at execution of the showlogs error command are any of the following. 1100002E, 1100002F |
| Workaround | There is no effective workaround. When the four bytes from the beginning of the third field of [Code:] are in [Example] in [Description] at execution of the showlogs error command, take action by interpreting the message to be correct. |
| RTI No. | RTIF2-141016-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | AC input power may be incorrectly determined to have a mix of 100 V and 200 V if any of the power supply units (PSU) in redundant configuration triggers an AC input error, and then power loss/recovery repeats in a short time. Consequently, though system operation may continue when power is recovered, two PSUs are degraded with the "PSU shortage (power off started)" message displayed and the system stops. |
| Workaround | There is no effective workaround. Replace the PSU where the power loss/recovery was detected. |
| RTI No. | RTIF2-140715-001 |
| Model | SPARC M10-1 |
| Description | In the SPARC M10-1, if the power supply unit (PSU) has a redundant configuration and the power cable connected to one of the power supply units is pulled out, a PSU error may be erroneously detected, and the SPARC M10-1 chassis CHECK LED (amber) may go on. At this time, executing the showlogs error command outputs the "Msg: PSU failed" log entry. |
| Workaround | There is no effective workaround. [How to restore] Use either of the following procedures. - How to restore 1 If any physical partition (PPAR) on the SPARC M10-1 is running, power off the PPAR (AC OFF). Then, disconnect both SPARC M10-1 power cables. Then, wait 30 seconds before reconnecting the cables (AC ON). - How to restore 2 Perform pseudo active replacement of the PSU in which the error has been detected (temporarily remove the PSU and then reinstall it). When performing pseudo replacement of the PSU, use the replacefru(8) command. Note that the fieldeng privilege is required to execute the replacefru(8) command. |
| RTI No. | RTIF2-140711-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that the NTP client setting for the XSCF is enabled and Oracle Solaris has been kept active for a long time. Then, powering off and then powering on the physical partition (PPAR) may cause the Oracle Solaris time to shift. |
| Workaround | There is no effective workaround. Note - To update the firmware from XCP 2232 or earlier to XCP 2040 or later, in which this problem has been resolved, see "RTIF2-140711-001 Additional Information." [How to restore] Execute the following procedure to start Oracle Solaris in single user mode and set the time. 1. Execute the poweroff(8) command to power off the PPAR. 2. Execute the showpparstatus(8) command to confirm that the status is "Powered off," indicating that the PPAR has been powered off. 3. Set the OpenBoot PROM environment variable auto-boot? to "false." XSCF> setpparparam -p PPAR-ID -s bootscript "setenv auto-boot? false" 4. Execute the poweron(8) command to power on the PPAR. 5. Execute the console(8) command to connect to the control domain console and display the ok prompt. 6. Start Oracle Solaris in single user mode. {0} ok boot -s 7. Execute the date command to set the Oracle Solaris time. [Example] Setting of 18:30:00 on June 27, 2014 # date 0627183014.00 # date 0627183014.00 |
| RTI No. | RTIF2-140710-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | After you replace a motherboard or CPU memory unit lower (CMUL), the XCP firmware version should differ from the pre-replacement version. Nevertheless, the message "XCP version of XSCF and Back-Panel mismatched!" that should appear at the time of login to the XSCF is not displayed. |
| Workaround | There is no effective workaround. [How to restore] When replacing a component, execute the following procedure: 1. Before replacement, execute the version(8) command to check the XCP version. [Example] XSCF> version -c xcp BB#00-XSCF#0 (Master) XCP0 (Current): 2051 XCP1 (Reserve): 2051 2. After replacement, execute the version(8) command to check the XCP version again. 3. If the XCP versions before and after replacement do not match, execute the flashupdate(8) command to update the firmware. [Example] Updating to XCP 2052 XSCF> flashupdate -c update -m xcp -s 2052 |
| RTI No. | RTIF2-140616-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If a problem occurs with the microSD card on the XSCF or the XSCF unit, you may not be able to access data in the restored XSCF. This may cause the output of the error message "An internal error has occurred. Please contact your system administrator." when any of the following commands is executed. After that, the command terminates abnormally. initbb(8) resetdateoffset(8) setpciboxdio(8) setpowercapping(8) setpparmode(8) setpparparam(8) setservicetag(8) In addition, the following command execution terminates normally but the setting information is not reflected in the system. addboard(8) deleteboard(8) setpcl(8) setupfru(8) This problem also occurs when you perform the setting on XSCF Web. |
| Workaround | There is no effective workaround. [How to restore] Replace the following part. - SPARC M10-1 PSU backplane (PSUBP) - SPARC M10-4/M10-4S PSU backplane unit (PSUBP) - SPARC M10-4S (with crossbar box) XSCF interface unit (XSCFIFU) |
| RTI No. | RTIF2-140523-001 |
| Model | SPARC M10-1 |
| Description | In the event of an instantaneous power failure lasting 11 ms or more, the CHECK LED on the operation panel will remain on after recovery, and the XSCF may not start. Therefore, even if the system is set to automatically start after recovery, it may not actually start automatically. |
| Workaround | There is no effective workaround. [How to restore] After turning off the input power, wait at least 10 seconds before turning it on again. |
| RTI No. | RTIF2-140515-001 |
| Model | SPARC M10-1 |
| Description | In order to configure the XSCF startup mode function, after changing the startup mode with the xscfstartupmode(8) command or setting the operation panel mode switch to "Locked" or "Service," if the rebootxscf(8) command is executed to reset the XSCF, the new startup mode gets enabled. However, under normal circumstances, the configuration of the startup mode is not enabled when XSCF is reset using the rebootxscf(8) command. It is enabled only when the input power of the system is turned off/on (AC OFF/ON). This state can be confirmed with the xscfstartupmode -d command as follows. [Example] When startup mode is set to "fast" after setting the operation panel mode switch to "Locked" XSCF> xscfstartupmode -d Setting Mode: normal Current Mode: normal XSCF> xscfstartupmode -m fast XSCF> rebootxscf -a XSCF> xscfstartupmode -d Setting Mode: fast[need AC OFF/ON] Current Mode: fast However, the correct result will be that the "Current Mode" be "normal" like the following: XSCF> xscfstartupmode -d Setting Mode: fast [need AC OFF/ON] Current Mode: normal |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-140507-013 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Even if two default gateways are set up using the setroute(8) command, connection from other networks is possible only on either XSCF-LAN#0 or XSCF-LAN#1. |
| Workaround | Out of the XSCF-LAN#0 and XSCF-LAN#1 gateways, make one of their IP addresses available for connection. |
| RTI No. | RTIF2-140314-001 |
| Model | SPARC M10-1 |
| Description | Suppose XCP 2210 is applied to a SPARC M10-1. In that SPARC M10-1, if an internal component failure occurs in a Type B motherboard unit (MBU), it may be not detected, the following may be registered many times in the error log. - Voltage problem within MBU FRU: /MBU Msg: Critical low voltage error Or - Fan rotation problem FRU: /FAN#x,/MBU Msg: FAN speed too low |
| Workaround | There is no effective workaround. [How to restore] Replace the MBU. |
| RTI No. | RTIF2-140227-001 |
| Model | SPARC M10-4S |
| Description | When the crossbar boxes are powered on (AC ON) for the first time, "SCF panic detected" or "XSCF hang up is detected" may be registered in the error log when the XSCF starts. |
| Workaround | There is no effective workaround. [How to restore] Perform the following procedure. 1. Confirm that all crossbar boxes and SPARC M10-4S are displayed by the showhardconf(8) command. 2. Perform AC OFF/ON on all crossbar boxes and SPARC M10-4S. 3. Check the master XSCF with the showbbstatus(8) command. If XBBOX#81 had been switched to master XSCF, use the switchscf(8) command to make XBBOX#80 the master XSCF. |
| RTI No. | RTIF2-130305-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you reconnect the input power cable soon after it is unplugged, the error log of PSUs detect 100 V and 200 V at AC inputs indicating that an error in the configuration of the input power supply may be registered. - XCP 2041 or later Wrong PSU is installed - XCP 2032 or earlier PSUs detect 100 V and 200 V at AC inputs |
| Workaround | There is no effective workaround. Ignore this error log entry. |
RTIF2-140711-001 Additional Information
This problem (RTIF2-140711-001) has been resolved for XCP 2240 and later versions. However, the Oracle Solaris time may shift if a physical partition is started up immediately after updating the firmware from XCP 2232 or earlier to XCP 2240 or later.
To synchronize the time, see "Notes on the Logical Domain Time."
To synchronize the time, see "Notes on the Logical Domain Time."
< Previous Page | Next Page >