Skip to main content

Problems Resolved in XCP 3030


Problems Resolved in XCP 3030
The following table lists the problems resolved in XCP 3030.
Table 3-18  Problems Resolved in XCP 3030
RTI No. RTIF2-210118-003
Model SPARC M12-2S
Description In a configuration with 16 physical partitions (PPARs), the power-on of all the PPARs at once may cause a power-on failure in some very rare cases.
Workaround There is no effective workaround.
RTI No. RTIF2-210118-004
Model SPARC M12-2, SPARC M12-2S
Description When you select the [XSCF] - [Logs] - [Console Log] menu from XSCF Web and display log information, the following error appears in a pop-up window and the screen returns to the login window.
Description Server Internal error or the page you visit does not exitst or has been
deleted! Sorry for any inconvenience!
Workaround There is no effective workaround.
Execute the showlogs command in the XSCF shell to check the console log.
RTI No. RTIF2-210118-005
Model SPARC M12-2, SPARC M12-2S
Description The console command may fail to connect to the control domain console.
Workaround There is no effective workaround.
Try again to connect to the control domain console.
RTI No. RTIF2-210118-006
Model SPARC M12-2, SPARC M12-2S
Description The showinterimpermit command cannot be executed with the fieldeng privilege.
Workaround Execute the command with any of the following user privileges.
platadm, platop, pparadm, pparmgr, pparop
RTI No. RTIF2-210118-007
Model SPARC M12-2S
Description If the restoredefaults -c factory command is executed when the master XSCF is XBBOX#80, the XSCF that executes the command will stop with "BOARD ERROR."
Workaround There is no effective workaround.
RTI No. RTIF2-210118-008
Model SPARC M12-1, SPARC M12-2S
Description Even when detected, some abnormal temperature changes in intake temperature are not registered in the event log.
Workaround There is no effective workaround.
RTI No. RTIF2-171013-002
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Security fixes.
(CVE-2016-6304, CVE-2016-2182, CVE-2016-2183, CVE-2016-6302, 
CVE-2016-6306, CVE-2016-6515, CVE-2017-3731, CVE-2016-7431,
CVE-2016-7429, CVE-2016-7433)
For details, see the Oracle website relating to the following:
Critical Patch Updates
Workaround Update the XCP firmware to XCP 3030 or later.
RTI No. RTIF2-170522-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description Booting from an external DVD drive may fail.
[Example of output message]
{0} ok boot /pci@8100/pci@4/pci@0/pci@8/usb@0/cdrom@6/disk@0 
 Boot device: /pci@8100/pci@4/pci@0/pci@8/usb@0/cdrom@6/disk@0 File and args:
  Can't open boot device 
Workaround To avoid this problem, perform the following procedure.
1. Stop OpenBoot PROM at the ok prompt.

2. Perform the following steps to change the OpenBoot PROM environment variable nvramrc.

a. Execute the nvedit command, and write nvramrc as shown below.

    {0} ok nvedit
    0: : patch-zero 0 to my-adr0 0 ;
    1: ' patch-zero ' 0 ' new-instance d# 28 + token@ (patch
b. Press the [Ctrl] + [C] keys to exit nvedit and return to the ok prompt.

c. Execute nvstore to save the edited contents.

    {0} ok nvstore
d. Check whether nvramrc was written correctly.

    {0} ok printenv nvramrc
    nvramrc = : patch-zero 0 to my-adr0 0 ;
                ' patch-zero ' 0 ' new-instance d# 28 + token@ (patch
    {0} ok
3. Set the OpenBoot PROM environment variable use-nvramrc? to true.

    {0} ok setenv use-nvramrc? true
    use-nvramrc? = true
4. Execute the reset-all command to restart OpenBoot PROM.

    {0} ok reset-all
 
After executing the reset-all command and the system stops at the ok prompt, boot from a DVD drive.
Example: Booting from a DVD drive connected to a front USB port
 {0} ok boot /pci@8100/pci@4/pci@0/pci@8/usb@0/cdrom@6/disk@0
 
To return the above setting described in [Workaround] to its original state, perform the following steps.
1. Stop OpenBoot PROM at the ok prompt.

2. Delete the set contents from the OpenBoot PROM environment variable nvramrc.

 a. Execute nvedit to delete ": patch-zero 0 to my-adr0 0 ;" and "' patch-zero ' 0 ' new-instance d# 28 + token@ (patch" from nvramrc. You can delete lines one by one by pressing the [Ctrl] + [K] keys twice at the beginning of a line.
  {0} ok nvedit

    0:
b. Press the [Ctrl] + [C] keys to exit nvedit and return to the ok prompt.

c. Execute nvstore to save the edited contents.

  {0} ok nvstore

d. Check whether the nvramrc setting was deleted correctly.

    {0} ok printenv nvramrc
    nvramrc =
    {0} ok
3. Set the OpenBoot PROM environment variable use-nvramrc? to false. If it has been set to true before the workaround was performed, this step is unnecessary.

    {0} ok setenv use-nvramrc? false
    use-nvramrc? = false
    {0} ok
4. Execute the reset-all command to restart OpenBoot PROM.

    {0} ok reset-all
RTI No. RTIF2-170511-001
Model SPARC M12-1, SPARC M12-2, SPARC M12-2S
Description If a CPU failure or memory failure occurs, the OS on a logical domain using the faulty CPU or memory may hang.
Workaround There is no effective workaround.
RTI No. RTIF2-170224-048
Model SPARC M12-2S
Description In a system with a building block configuration, the following error log may be registered when the input power is turned on (AC ON) or the rebootxscf -a command is used.
XSCF data synchronization failed
At this time, the physical partition cannot be powered on.
Workaround There is no effective workaround.
Reboot all the XSCFs by using the rebootxscf -a command.
RTI No. RTIF2-170224-035
Model SPARC M12-2, SPARC M12-2S
Description If the setsnmp command tries to set enabled immediately after disabled was set, the "Agent enable failed" message may appear, and the command may fail.
This may cause the following phenomena.
1. If it is left as it is, the error log of "SCF panic detected" is registered and the XSCF is rebooted.

2. The setting has not been reflected, so if the showsnmp command is executed, it displays "Enabled" for "Agent Status" and "None" for "Enabled MIB Modules."

3. If the showsnmp command is executed, it displays "Enabled" for "Agent Status" and "SP MIB" for "Enabled MIB Modules." However, the setting has not actually been reflected, so rebooting the XSCF causes "None" to be displayed for "Enabled MIB Modules."

4. The setting has not been reflected, so when the showsnmp command displays "None" for "Enabled MIB Modules," the system using the cluster software detects the following error: "FJSVcluster: Error: DEV: 7240: Cannot connect to the XSCF."

  [Example] After the setsnmp command fails, the setting is not reflected.
  XSCF> setsnmp disable
  XSCF> setsnmp enable
  setsnmp: Agent enable failed
  XSCF> showsnmp
 
  Agent Status: Enabled
  Agent Port: 161
  System Location: System-Location
  System Contact: System-Contact
  :
  Status: Enabled
  Community String: public
 
  Enabled MIB Modules: None
  XSCF>
Similarly, this problem also occurs when the setsnmpusm command or setsnmpvacm command is executed to change the setting while the SNMP setting is enabled.
Workaround To change the setting to enabled after it was changed to disabled, wait at least 30 seconds, the minimum interval.
To change the setting with the setsnmpusm command or setsnmpvacm command, temporarily change the SNMP setting to disable, and then wait at least 30 seconds, the minimum interval.
[How to restore]
Temporarily set disable with the setsnmp command, and then wait at least 30 seconds, the minimum interval, to set enable.
Next, execute the showsnmp, setsnmpusm, or showsnmpvacm command to confirm that the setting has been reflected as expected.
RTI No. RTIF2-170224-043
Model SPARC M12-2, SPARC M12-2S
Description Normally, the occurrence of a memory configuration error is supposed to degrade all memory under the CPU. However, some memory has not been degraded. Powering on the PPAR at this time may register the non-degraded memory in an error log.
[Example] The MEM#02B memory has been unmounted but the MEM#xxA memory is not degraded.
XSCF> showstatus
   BB#00 Status:Normal;
       CMUL Status:Normal;
*           MEM#00B Status:Deconfigured;
*           MEM#01B Status:Deconfigured;
*           MEM#03B Status:Deconfigured;
*           MEM#04B Status:Deconfigured;
*           MEM#05B Status:Deconfigured;
*           MEM#06B Status:Deconfigured;
*           MEM#07B Status:Deconfigured;
 
[Example] Example of an error log
XSCF> showlogs error
Date: Nov 22 10:57:37 JST 2016
    Code: 40002000-004b830134110000ff-020014210000000000000000
    Status: Warning                Occurred: Nov 22 10:57:37.190 JST 2016
    FRU: /BB#0/CMUL/MEM#03A,/BB#0/CMUL
    Msg: Failed to find write cycle adjustment value
    Diagnostic Code:
        00000300 00000000 0000
        00000001 00000000 0000
Workaround Before powering on the PPAR, execute the showhardconf command and confirm that the memory is correctly mounted in accordance with memory mounting rules.
Remount any memory that is not correctly mounted.
[How to restore]
Remount the memory correctly in accordance with memory mounting rules.
With the mode switch in the Service mode position on the operation panel, turn on (AC ON) the input power to cancel the degradation of the memory registered with an error.
Execute the showstatus command to confirm that the memory is not degraded.
RTI No. RTIF2-170221-001
Model SPARC M12-2, SPARC M12-2S
Description The following error may be registered for a PCI slot that has a mounted Dual 10Gigabit Ethernet (10GBase-T) card when the physical partitions (PPARs) are started.
[Error message example]
FRU: /BB#0/PCI#3,/BB#0/CMUL
Msg: PCI Express link not active
Workaround When the device can be recognized from Oracle Solaris, ignore this error message.