Skip to main content

Problems Resolved in XCP 3090


Problems Resolved in XCP 3090
The following table lists the problems resolved in XCP 3090.
Table 3-8  Problems Resolved in XCP 3090
RTI No. RTIF2-200805-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Security fixes.
(CVE-2019-11477, CVE-2019-11478, CVE-2019-11479, CVE-2018-3693)
For details, see the Oracle website relating to the following:
Critical Patch Updates
Workaround Update the XCP firmware to XCP 3090 or later.
RTI No. RTIF2-200528-002
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Wrong PCI INTx interrupt control may cause logical domains to panic.
Workaround There is no effective workaround.
RTI No. RTIF2-200518-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description When a snapshot is collected with USB memory specified as log save destination, collection will end normally but without a log collected in the snapshot.
The problem when this USB memory is specified as the data save destination also occurs with the following XSCF commands or XSCF Web operations:
- dumpconfig, dumpcodactivation, getremotepwrmgmt, or showcodactivationhistory command

- Configuration Backup/Restore on the [Maintenance] - [Configuration Management] menu

- CoD Activation History on the [Settings] - [CoD Activation] menu
Workaround Check the collected file size in the USB memory. If the size is 0, collect data by executing the XSCF command or XSCF Web operation again.
RTI No. RTIF2-200518-003
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Suppose an XSCF user account managed with the Lightweight Directory Access Protocol (LDAP), Active Directory, and the LDAP over SSL service is used to log in to XSCF Web. If the user account name contains a period ".", login fails with the following message displayed.

System Error!
Unknown system error,please contact the administrator.
Workaround There is no effective workaround.
RTI No. RTIF2-200515-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Depending on the combination of memory type and size, the following error log is registered during memory diagnostics when a physical partition (PPAR) is powered-on after memory was replaced.
[Example]
XSCF> showlogs error
Date: Oct 07 06:30:48 JST 2017
   Code: 80002100-014e830134210000ff-150410040010002800f00000
   Status: Alarm                Occurred: Oct 07 06:29:55.240 JST 2017
   FRU: /BB#0/CMUL/MEM#06A,/BB#0/CMUL
   Msg: DIMM address bus fatal error
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)
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)
Workaround There is no effective workaround.
RTI No. RTIF2-200423-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description After Oracle Solaris startup, the following errors may be detected.
XSCF> showlogs error -V
Date: xxx xx xx:xx:xx xxx xxxx
    Code: 40000000-00a20400480400a204-12bb00000000000000000000
    Status: Warning               Occurred: xxx xx xx:xx:xx.xxx xxx xxxx
    FRU: xxxxxxxxxxxxx
    Msg: PCI access error
    Diagnostic Code:
       00000200 00000000 0000
       00000100 00000000 0000
       00000200 00000000 0000
       00000000 00000000 00000000 00000000
       00000000 00000000 0000
    Diagnostic Messages
        IO-FaultReport:
        TIME                 UUID
        xxx xx xx:xx:xx      xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
        MSG-ID
        xxxxxxxxxxxxx
If one of the following is indicated in FRU, it corresponds to this problem.
/BB#0/CMUL,/BB#0/CMUU
 /BB#0/CMUL
 /BB#0/CMUU
 /MBU
If one of the following is indicated in MSG-ID, it corresponds to this problem.
PCIEX-8000-YJ
 
Workaround There is no effective workaround.