Skip to main content

Problems Resolved in XCP 2290


Problems Resolved in XCP 2290
The following table lists the problems resolved in XCP 2290.
Table 3-25  Problems Resolved in XCP 2290
RTI No. RTIF2-200910-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the input power is turned off (AC OFF) while the XSCF is starting up, only occasionally the XSCF may not start up when the input power is turned on (AC ON) again.
Workaround Do not turn off the input power while the XSCF is starting up.
If the XSCF reboots repeatedly due to a component failure, wait until the reboots stop before turning off the input power.
RTI No. RTIF2-160401-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Security fixes.
(CVE-2015-7547, CVE-2013-4786)
For details, see the Oracle website relating to the following: Critical Patch Updates
Workaround Update the XCP firmware to XCP 2290 or later.
To use the remote power management function, see "Notes on the Remote Power Management Function (RCIL)."
RTI No. RTIF2-160203-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When you set a string of 1017 or more characters in the OpenBoot PROM environment variable nvramrc, the following message appears, and the system may stop with the ok prompt displayed.
FATAL: free-memory: bad address.
ERROR: Last Trap: Memory Address not Aligned
TL:   1

%TL:1 %TT:34 %TPC:f0209020 %TnPC:f0209024
%TSTATE:4420001600 %CWP:0
   %PSTATE:16 AG:0 IE:1 PRIV:1 AM:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0
   %ASI:20  %CCR:44  XCC:nZvc   ICC:nZvc

%TL:2 %TT:60 %TPC:f0246b54 %TnPC:f0200680
%TSTATE:14420001400 %CWP:0
   %PSTATE:14 AG:0 IE:0 PRIV:1 AM:0 PEF:1 RED:0 MM:0 TLE:0 CLE:0 MG:0 IG:0
   %ASI:20  %CCR:44  XCC:nZvc   ICC:nZvc
 Omitted

{0} ok 
Workaround Confirm that a string of 1016 or less characters is set in nvramrc. Perform the following procedure at the ok prompt.
1. If the OpenBoot PROM environment variable auto-boot? is true, set it to false, and then execute the reset-all command to restart OpenBoot PROM.

2. Execute the nvedit command.

3. Edit the contents of nvramrc so that it contains a string of 1016 or fewer characters.

4. Execute the nvstore command to apply the contents of nvramrc.

5. Reset the OpenBoot PROM environment variable auto-boot?, and then execute the reset-all command to restart OpenBoot PROM. 
RTI No. RTIF2-160129-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When the showstatus command is executed, Status will display "Faulted" or "Degraded" for the faulty components of registered hardware failures in the error log. In some very rare cases, Status may incorrectly display "Deconfigured" instead.
[Example] After an Alarm-level memory failure is detected, "Deconfigured" instead of "Faulted" is displayed at Status.
XSCF> showlogs error
Date: Jan 1 00:00:00 JST 2016
    Code: 80002000-006e070069040000ff-019204110000000000000000
    Status: Alarm                  Occurred: Jan 1 00:00:00.000 UTC 2016
    FRU: /BB#0/CMUL/MEM#00A,/BB#0/CMUL
    Msg: DIMM initialization serious error

XSCF> showstatus
   BB#00 Status:Normal;
       CMUL Status:Normal;
*           MEM#00A Status:Deconfigured;
*           MEM#01A Status:Deconfigured;
*           MEM#02A Status:Deconfigured;
*           MEM#03A Status:Deconfigured;
Workaround There is no effective workaround.
Status is not correctly displayed with the showstatus command, but the faulty component has been degraded. Therefore, perform maintenance on the component.
RTI No. RTIF2-160129-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When you are maintaining a fan unit using the replacefru(8) command, the error log may show an incorrectly registered fan configuration error.
In this case, the showhardconf or showstatus command indicates that the system or chassis housing the fan unit under maintenance has degraded even though it has not actually degraded.
[Error message example]
Msg: FAN shortage
[Example] When the BB#00 fan was maintained
XSCF> showstatus
*  BB#00 Status:Deconfigured;
Workaround There is no effective workaround.
[How to restore]
Ignore this error log as it has no effect on the maintenance work.
After you finish maintaining the fan unit using the replacefru command, the chassis is no longer shown as degraded.
RTI No. RTIF2-160129-004
Model SPARC M10-4, SPARC M10-4S
Description When the CPU memory unit upper (CMUU) is removed, the number of CPU core resources displayed under "Installed" by the showcodusage command, or at "CPU Cores" and "Cores" by the showpparinfo command, is incorrect. Instead, it shows the number when the CMUU was mounted.
[Example] When the CMUU is removed from the SPARC M10-4, the number of CPU core resources is supposed to be 32 but is displayed as 64.
XSCF> showcodusage 
Resource In Use Installed CoD Permitted Status 
-------- ------ --------- ------------- ------ 
PROC          0        64            64 OK: 64 cores available
PPAR-ID/Resource In Use Installed Assigned 
---------------- ------ --------- -------------- 
0  - PROC             0        64       64 cores
1  - PROC             0         0        0 cores 
2  - PROC             0         0        0 cores 
3  - PROC             0         0        0 cores 
4  - PROC             0         0        0 cores 
5  - PROC             0         0        0 cores 
6  - PROC             0         0        0 cores 
7  - PROC             0         0        0 cores 
8  - PROC             0         0        0 cores 
9  - PROC             0         0        0 cores 
10 - PROC             0         0        0 cores 
11 - PROC             0         0        0 cores 
12 - PROC             0         0        0 cores 
13 - PROC             0         0        0 cores 
14 - PROC             0         0        0 cores 
15 - PROC             0         0        0 cores 
Unused - PROC         0         0       64 cores
Workaround There is no effective workaround.
RTI No. RTIF2-151124-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When you perform the following procedure, "Hypervisor Abort" occurs, and the logical domain may fail to start. If you try to start the PPAR again at this time, the PPAR is rebooted repeatedly, and the logical domain cannot be started. In addition, the logical domain configuration information cannot be restored.
1. Execute the dumpconfig command to save the XSCF setting information, including the logical domain configuration information.

2. Change the logical domain configuration information.

3. Specify the configuration information name before the change. Then, execute the ldm remove-spconfig and ldm add-spconfig commands to replace the current logical domain configuration information with the updated one and save it to the XSCF.

4. Execute the restoreconfig command to restore the XSCF setting information, including the logical domain configuration information, saved in step 1.

5. Start the physical partition (PPAR).
Workaround To restore the logical domain configuration information, perform the following procedure after step 4, instead of step 5 in [Description].
1. Start the PPAR with the factory-default configuration.

2. Restore the logical domain configuration information already saved to the XML file.

3. Execute the ldm add-spconfig command to save the logical domain configuration information to the XSCF.
RTI No. RTIF2-150914-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose you use any of the operations below to turn on the power to the physical partition (PPAR) when you use the flashupdate(8) command to update the firmware. An "FMEM serious error" error log may be registered, the motherboard unit (MBU) or CPU memory unit (lower) (CMUL) may be degraded, and the PPAR power-on processing and firmware update may fail.
- Power on using the operation panel power switch

- Issue the power on instruction with the remote power management function (RCIL)

- Issue the power on instruction with the auto power control system (APCS)
Workaround When you use the flashupdate(8) command to update the firmware, do not turn on the power to the physical partition (PPAR) using the power switch on the operation panel, RCIL, or APCS. Perform these operations after the firmware update is complete.
You can use the showlogs event command to check whether the firmware update is complete. If the firmware update is complete, the following message is output.
"XCP update has been completed (XCP version=xxxx:last version=yyyy)"
[How to restore]
Replace the motherboard unit (MBU) or the CPU memory unit (lower) (CMUL).
RTI No. RTIF2-150521-001
Model SPARC M10-4S
Description Suppose you have used the flashupdate(8) command to update the firmware with the power to the physical partition (PPAR) turned on. If you add a system board (PSB) by using dynamic reconfiguration, the following error log is registered, and the PSB may fail to be added.
Warning: /BB#x/CMUL:SCF:POST/OBP/HV data write error
Notice: /UNSPECIFIED:HYPERVISOR:DR failed
Also, the PPAR at the PSB add destination is reset.
Workaround Execute the version -c xcp -v command, and check the [CMU BACKUP] lines.
[Example]
XSCF> version -c xcp -v
BB#00-XSCF#0 (Master)
XCP0 (Reserve): 2260
CMU           : 02.25.0000 
     POST            : 3.9.0 
     OpenBoot PROM   : 4.36.1+2.10.0 
     Hypervisor      : 1.4.1
XSCF          : 02.26.0000
XCP1 (Current): 2260
CMU           : 02.25.0000 
     POST            : 3.9.0 
     OpenBoot PROM   : 4.36.1+2.10.0 
     Hypervisor      : 1.4.1
XSCF          : 02.26.0000
BB#01-XSCF#0 (Standby)
XCP0 (Reserve): 2260
CMU           : 02.25.0000 
     POST            : 3.9.0 
     OpenBoot PROM   : 4.36.1+2.10.0 
     Hypervisor      : 1.4.1
XSCF          : 02.26.0000
XCP1 (Current): 2260
CMU           : 02.25.0000 
     POST            : 3.9.0 
     OpenBoot PROM   : 4.36.1+2.10.0 
     Hypervisor      : 1.4.1
XSCF          : 02.26.0000
CMU BACKUP
#0: 02.26.0000
#1: ..
XSCF> 

Check the line where Current is displayed either for XCP0 or XCP1 on the PSB (BB#xx) where the PPAR is running. If the CMU firmware version shown on the next line after it ("CMU:02.25.0000" in the above example) is not the same as the CMU firmware version under [CMU BACKUP] ("#0: 02.26.0000" in the above example), update the XCP firmware to the CMU firmware version shown on the next line after Current while the PPAR is running.
If the CMU firmware versions are the same, you do not need to update the firmware. 

Afterward, regardless of whether the CMU firmware versions are the same, perform the following procedure in advance of any firmware update using the flashupdate(8) command while the PPAR is running.
1. Execute the switchscf(8) command to switch the master XSCF.

2. Execute the rebootxscf -a command to reset all XSCFs.

The above steps 1. and 2. are not necessary for a firmware update while the PPAR is stopped.