Problems Resolved in XCP 2260
Problems Resolved in XCP 2260
The following table lists the problems resolved in XCP 2260.
| RTI No. | RTIF2-150710-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Security fixes. (CVE-2014-3570, CVE-2014-3571, CVE-2014-3572, CVE-2014-8275, CVE-2015-0204, CVE-2015-0235) For details, see the Oracle website relating to the following: Critical Patch Updates |
| Workaround | Update the XCP firmware to XCP 2260 or later. |
| RTI No. | RTIF2-150622-001 |
| Model | SPARC M10-1 |
| Description | The following phenomena occur while a physical partition (PPAR) is powered on. 1. When an excessively low fan speed is detected, it is registered in the error log. If this error is detected multiple times, domain power-on will fail. 2. The fan speed level reaches level 5 (full speed), resulting in a noisy fan. One or no fan error is registered in the error log at this time. |
| Workaround | There is no effective workaround. [How to restore] Use either of the following procedures. - How to restore 1 Execute the replacefru(8) command for pseudo active replacement of all the fans (temporarily remove and then reinstall the fans). - How to restore 2 Turn off the power to the PPAR, and then disconnect and reconnect the input power supply of the system (AC OFF/ON). When turning off/on the input power, power off the system, wait 30 seconds, and then power on the system. Even after you have tried both of the above procedures, the fan may again rotate at the maximum speed with no reduction in noise. |
| RTI No. | RTIF2-150611-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | The fan speed may increase although the physical partition is powered off. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-150514-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you connect a PCI expansion unit to PCI slot #0 of a SPARC M10 system chassis and execute the prtfru(8) or snapshot(8) command, a "process down" may occur and the XSCF may be reset. Also, the physical partition is operating with two or more link cards connected to PCI slot #0 of a SPARC M10 system chassis, a "process down" may occur and the XSCF may be reset. |
| Workaround | - To execute the prtfru(8) command, connect the PCI expansion unit to a PCI slot other than #0. - To execute the snapshot(8) command, perform either of the following operations: - Connect the PCI expansion unit to a PCI slot other than #0. - Execute the snapshot(8) command without specifying the Full log set (-L F) option. [How to restore] Since the system is restored by resetting the XSCF, you can continue to operate the system. |
| RTI No. | RTIF2-150514-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the XCP version at dumpconfig(8) command execution is different from the XCP version at restoreconfig(8) command execution, a problem may occur. For details, see "Problems Related to RTIF2-150514-002." |
| Workaround | See "RTIF2-150514-002 Workarounds and How to Restore." |
| RTI No. | RTIF2-150514-004 |
| Model | SPARC M10-4S |
| Description | If you power on a physical partition or execute the diagxbu(8) command while the testsb(8) command is being executed, the testsb(8) command may terminate abnormally. |
| Workaround | There is no effective workaround. If the testsb(8) command terminates abnormally, execute the testsb(8) command again. |
| RTI No. | RTIF2-150507-002 |
| Model | SPARC M10-1, SPARC M10-4S |
| Description | The power supply units (PSUs) of the SPARC M10-1 or a crossbar box are in a redundant configuration. Suppose that you connect the power cord of PSU#0 (AC ON), and start an XSCF without connecting the power cord of PSU#1 (AC OFF). Once the READY LED of the XSCF is lit, the input power connection of PSU#1 is not recognized even if you connect the disconnected power cord of PSU#1 afterward. In this case, the Power_Status of PSU#1 is displayed as "Input fail; AC: - ;" by executing the showhardconf(8) command. |
| Workaround | When connecting the power cords of the PSUs, be sure to connect the power cords of all the PSUs at the same time. For SPARC M10-1, connect the cables within 5 minutes when the startup mode of the XSCF startup mode function is set to normal, or within 2 and a half minutes in fast mode. [How to restore] Perform either of the following operations: - Switch the mode switch on the operation panel to Locked or Service. - Select PSU#1 by executing the replacefru(8) command, and perform a pseudo replacement of the PSU. |
| RTI No. | RTIF2-150331-001 |
| Model | SPARC M10-4S |
| Description | If you update the firmware after importing a firmware file for a PCI expansion unit to the system by using XSCF Web, an "Operation was not successful." error is detected and the update may fail. |
| Workaround | There is no effective workaround. Use the getflashimage(8) command to import a firmware file for a PCI expansion unit to the system. Then, execute the ioxadm -c update command to update the firmware. |
| RTI No. | RTIF2-150331-002 |
| Model | SPARC M10-4S |
| Description | The serial number and part number of a link card connected to a chassis other than the master chassis are not displayed in the output results of the ioxadm -v list command. |
| Workaround | There is no effective workaround. To confirm the serial number and part number of the connected link card, directly check the link card. |
| RTI No. | RTIF2-150331-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The CPU utilization (system time: sys) of a CPU on the domain may reach 100% during while the XSCF is resetting. |
| Workaround | There is no effective workaround. No corrective action is required since CPU utilization returns to normal after the XSCF resetting is completed. |
| RTI No. | RTIF2-150313-001 |
| Model | SPARC M10-4S |
| Description | After updating the firmware with the flashupdate(8) command while the physical partition is powered on, if dynamic reconfiguration of PPARs is performed without first rebooting the PPAR in order to update the CMU firmware, the following error log may be registered: Warning: /BB#x/CMUL:SCF:POST/OBP/HV data write error |
| Workaround | When updating the firmware with the flashupdate(8) command while the physical partition is powered on, reboot the PPAR before performing dynamic reconfiguration of PPARs. Moreover, the error message when the problem occurs, may be ignored as it has no effect on the proper functioning of the system. |
| RTI No. | RTIF2-150305-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If an Oracle Solaris kernel zone has been created or started on any of the following domains, the guest domain or kernel zone enters the panic state: - Live-migrated guest domain - Guest domain in a physical partition (PPAR) from which a system board was deleted by dynamic reconfiguration (DR) of the PPAR The same phenomenon also occurs when you resume a suspended kernel zone. |
| Workaround | - Restart the guest domain before creating or starting the kernel zone. - If an Oracle Solaris kernel zone has been suspended, do not resume the kernel zone but instead start it with the -R option specified. [Example] guest# zoneadm -z kz000 boot -R [How to restore] Restart the PPAR that has the guest domain and the PPAR where the kernel zone has been resumed. |
| RTI No. | RTIF2-141031-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The self-authenticated certificate used by the HTTPS service will expire in 1 year, not 10 years. |
| Workaround | You can access XSCF Web even though the certificate has expired. Use the same certificate, create a certificate, or import a certificate with the sethttps(8) command. |
| RTI No. | RTIF2-140616-004 |
| Model | SPARC M10-4S |
| Description | When you execute the switchscf(8) command, XSCF master/standby switching may take time. As a result, the following error may occur: Master switch synchronization timeout. |
| Workaround | There is no effective workaround. If the current master XSCF differs from what you intended, re-execute the switchscf(8) command. |
| RTI No. | RTIF2-140407-001 |
| Model | SPARC M10-4S |
| Description | Suppose one version from XCP 2210 to XCP 2250 is applied to a SPARC M10-4S. On that SPARC M10-4S, the dumpconfig(8) and restoreconfig(8) commands cannot save/restore the PPAR DR feature setting values that were configured with the setpparmode -p ppar_id -m ppar_dr command. |
| Workaround | There is no effective workaround. Update the firmware to XCP 2260 or later. Save and restore the PPAR DR feature setting values in XCP 2260 or later. [How to restore] Perform the following procedure. 1. Execute the showpparmode(8) command to check whether the PPAR DR feature is enabled or disabled. 2. Execute the setpparmode(8) command to enable/disable the PPAR DR feature. [Example] Enabling the PPAR DR feature for PPAR#0 XSCF> setpparmode -p 0 -m ppar_dr=on [Example] Disabling the PPAR DR feature for PPAR#0 XSCF> setpparmode -p 0 -m ppar_dr=off |
| RTI No. | RTIF2-131213-010 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When the firmware of the PCI expansion unit is updated with the ioxadm -c update command, a "process down" may occur in the XSCF firmware. |
| Workaround | There is no effective workaround. Re-execute the ioxadm -c update command to update the PCI expansion unit firmware again. |
| RTI No. | RTIF2-130702-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | If the following applies, "I/O devices error detected" is detected at the time of PPAR power-on and control domain reboot: In SPARC M10-4/M10-4S, the CPU memory unit upper (CMUU) is added to a configuration that has been operated with only the CPU memory unit lower (CMUL) and false has been set as the IOreconfigure setting of the physical partition (PPAR). |
| Workaround | There is no workaround for errors that are detected at power-on after the addition. Making the following setting prevents the error detection that occurs every time the PPAR is powered on or the control domain is rebooted. 1. After starting Oracle Solaris, execute the ldm rm-io command to delete the PCIe root complex of the added CMUU from the configuration of the control domain. 2. Execute the ldm add-spconfig command to save the constructed logical domain configuration to the XSCF. |
Problems Related to RTIF2-150514-002
If the XCP version at dumpconfig(8) command execution is different from the XCP version at restoreconfig(8) command execution, a problem listed in Table 3-33 may occur.
| XCP Version Executing dumpconfig(8) Command | XCP Version Executing restoreconfig(8) Command | Problem Occurring | |
|---|---|---|---|
| (1) | 2092 or earlier | 2210 to 2221 | (a) |
| (2) | 2092 or earlier | 2230 to 2250 | (a) or (b) |
| (3) | 2210 to 2221 | 2230 to 2250 | (b) |
| (4) | 2210 to 2221 | 2092 or earlier | (c) |
| (5) | 2230 to 2240 | 2092 or earlier | (c) |
| (6) | 2250 | 2240 or earlier | (c) |
| (7) | 2260 | 2250 or earlier | (c) |
- Problem (a)
Physical partition fails to start and then the XSCF stops. - Problem (b)
Suppose XSCF setting information saved in XCP 2221 or earlier is used to restore the XSCF when recovery mode, which is supported in Oracle VM Server for SPARC 3.1 or later, is enabled. Since the physical partition starts with logical domain configuration information created with XCP 2221 or earlier, the command may fail to restore the logical domain configuration information, and the domain configuration may remain switched to the factory-default state.
This is because the recovery mode of the logical domain configuration information created with XCP 2221 or earlier is not enabled. Subsequently, even with the logical domain configuration information created again with XCP 2230 or later, the command may fail to restore the logical domain configuration information, and the domain configuration may remain switched to the factory-default state. - Problem (c)
The following error occurs.
[Example]
| XSCF> restoreconfig -u user https://... --- Omitted --- restoreconfig: could not verifying backup file.(...) |
RTIF2-150514-002 Workarounds and How to Restore
The RTIF2-150514-002 workarounds are as follows.
- For (1) to (3) in Table 3-33
Perform the following procedure.1. Execute the version(8) command to check the XCP version.2. Execute the flashupdate(8) command to update the firmware to the XCP version used when the XSCF setting information was previously saved by the dumpconfig(8) command.3. Execute the restoreconfig(8) command to restore the XSCF setting information.4. Execute the flashupdate(8) command to update the firmware again to the original XCP version checked in step 1. - For (4) to (7) in Table 3-33
There is no effective workaround.
The restore methods for RTIF2-150514-002 are as follows.
- For (1) to (3) in Table 3-33
Perform the following procedure.1. Execute the version(8) command to check the XCP version.2. Execute the flashupdate(8) command to update the firmware to the XCP version used when the XSCF setting information was previously saved by the dumpconfig(8) command.3. For a system configuration with multiple SPARC M10-4S units, execute the initbb(8) command to disconnect all slave chassis from the system.4. Execute the restoredefaults -c factory command to initialize the system to the factory default state.5. Turn off the input power to all SPARC M10 system chassis or crossbar boxes. Then, turn on the chassis or crossbar boxes again and confirm that the READY LED of the XSCF or XSCF unit is lit.6. Execute the restoreconfig(8) command to restore the XSCF setting information.7. Execute the flashupdate(8) command to update the firmware again to the original XCP version checked in step 1. - For (4) to (7) in Table 3-33
Perform the following procedure.1. Execute the version(8) command to check the XCP version.2. Execute the flashupdate(8) command to update the firmware to the XCP version used when the XSCF setting information was previously saved by the dumpconfig(8) command.3. Execute the restoreconfig(8) command to restore the XSCF setting information.4. Execute the flashupdate(8) command to update the firmware again to the original XCP version checked in step 1.
< Previous Page | Next Page >