Problems Resolved in XCP 2330
Problems Resolved in XCP 2330
The following table lists the problems resolved in XCP 2330.
| RTI No. | RTIF2-201221-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Diagnostics may fail due to a microSD card failure. At the same time, if an intermittent USB-SSD failure occurs in the PSU backplane (PSUBP) or the XSCF interface unit (XSCFIFU) of the crossbar box, the XSCF may not be able to start. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201116-016 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | "XSCF self diagnosis warning detection" should be provided as notification of a Warning level error, but is registered at the Notice level and not provided as notification. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201109-011 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Devices assigned to an I/O domain might not be available. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-161129-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | With XCP 2290 or later, Hypervisor may abort after perform a live migration on a guest domain running Oracle Solaris 11.2 or later. |
| Workaround | There is no effective workaround. After a guest domain is moved by a live migration, reboot the guest domain as soon as possible, or restart (stop and start) the PPAR. |
| RTI No. | RTIF2-161108-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you boot/reboot logical domains after a certain period of time elapsed from physical partition (PPAR) power-on, the boot/reboot fails and the system stops at the ok prompt. This problem does not occur in a boot/reboot from an internal disk or USB device. The problem occurs in a boot/reboot from any of the following devices: - Virtual disk (*1), virtual network, virtual HBA, and F160/F320 card *1 This also holds true for cases where an internal disk is used as a virtual disk. This problem happens during the time period described below. - The first period is the 15-minute period after the elapse of "24 days, 20 hours, 16 minutes, and 23.648 seconds" from physical partition (PPAR) power-on. Each subsequent period is the 15-minute period after the elapse of a multiple of time of "49 days, 17 hours, 02 minutes, and 47.296 seconds." (15-minute period on the 25th day and then the 75th day, 125th day, 175th day, and so on at an interval of approximately 50 days) [Example] Period of 15 minutes from 24th day, 20 hours, 16 minutes, and 23.648 seconds to (same day and hour) 31 minutes and 23.648 seconds Period of 15 minutes from 74th day, 13 hours, 19 minutes, and 10.944 seconds to (same day and hour) 34 minutes and 10.944 seconds [Example of failure] Oracle Solaris is booted from guest domain virtual network on SPARC M10-1 SPARC M10-1, No Keyboard Copyright (c) 1998, 2016, Oracle and/or its affiliates. All rights reserved. OpenBoot 4.38.5, 14.0000 GB memory available, Serial #xxxxxxxx. [ 2.19.0 ] Ethernet address xx:xx:xx:xx:xx:xx, Host ID: xxxxxxxx. WARNING: /virtual-devices@100/channel-devices@200/network@0: Unable to connect to virtual switch No viable default device found in boot-device variable. Evaluating: {0} ok |
| Workaround | There is no effective workaround. [How to restore] After system stops with the ok prompt and the elapse of 15 minutes, execute the boot command. |
| RTI No. | RTIF2-161108-003 |
| Model | SPARC M10-4S |
| Description | In a system configuration with two crossbar boxes, logs may be registered with the wrong BB-ID if an "XB detected fatal clock failure" error or XB internal fatal error" error occurs. [Example] BB-ID of "Code:" shows correct value "01", but BB-ID of "FRU" shows incorrect value "0". XSCF> showlogs errorDate: May 16 08:49:52 JST 2016 Code: 80002100-0076110000ff0000ff-050067003013015f000000000 Status: Alarm Occurred: May 16 08:49:35.147 JST 2016 FRU: /BB#0/XBU#1 Msg: XB detected fatal clock failure |
| Workaround | There is no effective workaround. After executing the showlogs error command, identify the faulty components and replace them based on the value of "Code:" indicating the suspected location. |
| RTI No. | RTIF2-161012-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Virtual function (VF) may be unusable if you forcibly stop (e.g., ldm stop-domain command with -f option) the I/O domain to which the VF of the 10Gigabit Ethernet card is assigned. |
| Workaround | When stopping the I/O domain to which the VF is assigned, use the shutdown command. [How to restore] After clearing the Fault Report of the appropriate VF with the fmadm command on the I/O domain with the VF assigned, as well as on the root domain providing physical function (PF) of the VF, stop and start the I/O domain and the root domain with the shutdown command. |
| RTI No. | RTIF2-161012-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | In the I/O domain to which the 10Gigabit Ethernet card and the like are assigned, Oracle Solaris may hang when Oracle Solaris is booting. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-160912-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | When a root complex other than BB#0/CMUL fails, the FRU of the PCI access error, which is displayed by the XSCF command showlogs error, may not be displayed properly. |
| Workaround | There is no effective workaround. [How to restore] When a root complex fails, identify the failure location and replace the failure part according to the result displayed by the showstatus(8) command of the XSCF as shown below. Note - Do not identify the failure location and perform maintenance according to the FRU of PCI access error displayed by the showlogs error command of the XSCF and the output result of the fmdump/fmadm command of Oracle Solaris. [Example] When the root complex of BB#01/CMUU/CPU#1 fails XSCF> showstatus BB#01 Status:Normal; * CMUU Status:Degraded; * CPU#1 Status:Degraded; |
| RTI No. | RTIF2-160616-001 |
| Model | SPARC M10-1 |
| Description | In a system with two PCI expansion units connected, you may be unable to identify the connection of a PCI expansion unit from the XSCF by executing the ioxadm -v list command after the physical partition (PPAR) is powered on. However, you may be able to identify it from Oracle Solaris or OpenBoot PROM on the physical partition. In this case, with the connection unidentified, it is not possible to perform active replacement of a LINK card or the fan unit or power supply unit of the PCI expansion unit. The settings are reset to the factory default and the logical domain may not be able to start if the system operates with a logical domain configuration. |
| Workaround | There is no effective workaround. Power off the physical partition (PPAR) and power it on again. |
| RTI No. | RTIF2-160606-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the reset command is executed while the physical partition (PPAR) is powered off, "no PSB available in PPAR" is registered in the error log at the PPAR power-on time, and PPAR power-on fails. |
| Workaround | Do not execute the reset command while the physical partition (PPAR) is powered off. Execute the rebootxscf command to reboot the XSCF or turn off the input power of the system if the error log of "no PSB available in PPAR" is registered after executing the reset command. |
< Previous Page | Next Page >