Problems Resolved in XCP 2090
Problems Resolved in XCP 2090
The following table lists the problems resolved in XCP 2090.
| RTI No. | RTIF2-210209-005 |
| Model | SPARC M10-4S |
| Description | Update of the firmware in a system with a building block configuration may fail. |
| Workaround | There is no effective workaround. If the update fails, try the update again. |
| RTI No. | RTIF2-210104-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If "DIMM permanent correctable error" or "DIMM intermittent correctable error" occurs frequently in the error log, other errors may not be registered in the Fault Management log referenced in Oracle Solaris. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201127-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The SNMP manager cannot acquire the OID information of scfComponentNumber from the MIB definition file for XSCF expansion. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201127-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the XSCF stops due to an error, you may be unable to reboot the XSCF even by pressing the RESET switch on the rear panel. |
| Workaround | There is no effective workaround. [How to restore] Turn off the input power, and then turn it on again. |
| RTI No. | RTIF2-201126-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Depending on the set value for the XSCF-LAN IP address, communication using the Auto Service Request (ASR) function may not be possible. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201126-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | A "process down" may occur in XSCF Web when using Internet Explorer 10 in a Windows 8 environment. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201120-001 |
| Model | SPARC M10-4S |
| Description | A faulty XSCF BB control cable may lead to a poweroff command error, preventing power-off of the chassis whose cables have no problem. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201120-004 |
| Model | SPARC M10-4S |
| Description | Update of the firmware in a system with a building block configuration to XCP 2080 or earlier may fail, resulting in registration of the following in the error log. [Example] XSCF> showlogs error -v Date: Oct 19 17:56:59 JST 2013 Code: 10000000-00fcff0000ff0000ff-010210070000000000000000 Status: Information Occurred: Oct 19 17:56:53.144 JST 2013 FRU: /FIRMWARE Msg: Master switch synchronization timeout (SCF complete) Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 |
| Workaround | There is no effective workaround. [How to restore] Reboot all the XSCFs by using the rebootxscf -a command or XSCF Web, and then try to update the firmware again. |
| RTI No. | RTIF2-201109-021 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | A guest domain might not be booted after the ldm add-io command is executed for it. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-140617-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When the showhardconf -u command is executed on a system connected to a PCI expansion unit, the number of PCI cards installed on the PCI expansion unit is erroneously displayed as "11" (the maximum number of cards that can be installed). |
| Workaround | There is no effective workaround. To check information about the PCI cards installed in the PCI expansion unit, execute the showhardconf(8) command with no options. |
| RTI No. | RTIF2-140605-003 |
| Model | SPARC M10-4S |
| Description | Suppose that an XSCF failure occurs on one SPARC M10-4S chassis in a physical partition (PPAR) and the CHECK LED is on and the READY LED is off on the XSCF. If you attempt to power on this PPAR, the system erroneously judges that an error has occurred on every SPARC M10-4S chassis in this PPAR and you cannot power on the PPAR. |
| Workaround | There is no effective workaround. Follow the maintenance procedure for XSCF failures to replace the CPU memory unit lower (CMUL) on the faulty SPARC M10-4S chassis. |
| RTI No. | RTIF2-140605-004 |
| Model | SPARC M10-4S |
| Description | When you add or replace one SPARC M10-4S chassis (BB#00 or BB#01) or crossbar box chassis (XBBOX#80 or XBBOX#81), power control schedule settings for automatic power-on/off are not synchronized between the existing and additional/replacement chassis. If master/standby XSCF switching is performed in this state, automatic power-on/off is not performed because the power control schedule settings remain unavailable. |
| Workaround | There is no effective workaround. Execute the following procedure to synchronize power control schedule settings for automatic power-on/off between the master and standby XSCFs: 1. Execute the showpowerschedule -m list command to confirm that the power control schedule has been registered. If the power control schedule has not been registered, re-register it by using the addpowerschedule(8) and setpowerschedule(8) commands. 2. Execute the setpowerschedule -c control command to enable or disable the power control schedule. |
| RTI No. | RTIF2-140410-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If a CPU error occurs while powering on a physical partition (PPAR), an erroneous error log may be registered. This symptom can be confirmed by using the showlogs error -v command. If the result of the showlogs error -v command is "Msg: SP InternalError Occurred", and the first 4 bytes of the 5th line of the [Diagnostic Code] is "01920212", it corresponds to this symptom. [Example] XSCF> showlogs error -v Date: Nov 11 18:29:04 JST 2013 Code: 40000000-00fcff0000ff0000ff-0186ffff0000000000000000 Status: Warning Occurred: Nov 11 18:29:04.871 JST 2013 FRU: /FIRMWARE Msg: SP Internal Error Occurred Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 0007000b 02040002 00000000 00000000 01920212 00620000 0000 |
| Workaround | There is no effective workaround. [How to restore] Execute the showstatus(8) command to check whether a part has failed. A CPU whose [Status] is "Deconfigured" has failed. Follow the maintenance procedure to replace the FRU mounted on the CPU. [Example] When a "Deconfigured" CPU exists XSCF> showstatus BB#11 Status:Normal; CMUU Status:Normal; * CPU#0 Status:Deconfigured; |
| RTI No. | RTIF2-140410-006 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you execute the reset xir command immediately after starting Oracle Solaris or the ldmd service, "LDC Protocol info from PPAR (PPAR ID 0 : Domain Service Data Send Failed)" may be registered in the event log and a "process down" and reset may occur on the XSCF. |
| Workaround | There is no effective workaround. After XSCF is reset, execute the showlogs event command to confirm the event logs. Or, execute the showpparstatus(8) command to confirm that the physical partition (PPAR) was reset. If the physical partition has not been reset, execute the reset xir command again. |
| RTI No. | RTIF2-140303-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Response may become slow when using XSCF Web. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-131216-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The "XCP update is started." message is mistakenly displayed when the flashupdate -c check command is executed. |
| Workaround | There is no effective workaround. Ignore this message. |
| RTI No. | RTIF2-131213-006 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The "LDC Protocol info from PPAR (PPAR ID X : Domain Service Data Send Failed)" event log is registered on a running logical domain and shutdown of that logical domain may not be properly executed. |
| Workaround | There is no effective workaround. Either reboot the control domain or execute the rebootxscf -a command to reboot the XSCF. |
| RTI No. | RTIF2-131213-017 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Any of the following may occur while the XSCF is running. - Symptom 1 A "process down" occurs and the XSCF resets. - Symptom 2 The response of commands dealing with acquiring MIB information (get command, etc.) becomes slow. - Symptom 3 Execution of commands like showhardconf(8) takes time. Moreover, when the showhardconf(8) command is executed, the following message may be output and the command is terminated abnormally. "Cannot communicate with the other XSCF. Check the other XSCF' stat" - Symptom 4 The "SCF panic detected" error is produced and the XSCF is reset. - Symptom 5 Login to XSCF Web fails. However, login to the XSCF shell is possible. |
| Workaround | There is no effective workaround. [How to restore] - For symptoms 1, 2, and 4: The system can be recovered by resetting the XSCF. The system can be used after that. - For symptoms 3 and 5: Reset the XSCF with the rebootxscf(8) command. |
| RTI No. | RTIF2-131213-018 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the XSCF has disabled the NTP client setup, the time difference between the XSCF and the hypervisor of each physical partition (PPAR) is mistakenly updated, and the time of the logical domain may be misaligned after the PPAR is rebooted. |
| Workaround | Enable the NTP client setup of the XSCF by executing the setntp -s client -c enable command, and synchronize the XSCF with the upper-level NTP server. Otherwise, perform the following procedure. 1. Execute the showdateoffset(8) command before powering on or rebooting the PPAR and confirm the time difference between the XSCF and the hypervisor. 2. If the time difference is too large, execute the resetdateoffset(8) command with the PPAR in the stopped state in order to reset the time difference. 3. After powering on the PPAR, set the Oracle Solaris time again. |
| RTI No. | RTIF2-131213-020 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Due to the retry functionality of the XSCF, if any abnormality occurs in the recoverable backup memory inside the PSU backplane (PSUBP) more than three times, the XSCF regards it incorrectly as a fixed error. That may prevent the XSCF from starting. In such a case, the "REBOOT: COUNTER ERROR" message is displayed. |
| Workaround | There is no effective workaround. [How to restore] Re-execute power off and on. |
| RTI No. | RTIF2-131129-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | "Code" appears in memory information displayed by the showhardconf(8) command. If there is mounted memory whose last eight digits of "Code" begin with "00", execution of any of the following actions may result in incorrectly identified memory. The memory would have a value of 0 for both its "Code" and size. - Execute the restoredefaults factory command - Execute the initbb(8) command - Change the mounting point of memory [Example 1] XSCF> showhardconf : MEM#10B Status:Normal; + Code:ce8001M393B2G70QH0-YK0 0000-00511571; + Type:07; Size:16 GB;[Example 2] XSCF> showhardconf :* MEM#10B Status:Deconfigured; + Code:000000 0000-00000000; + Type: ; Size:0 GB; |
| Workaround | Apply the latest version of the XCP, and then execute power off and on. |
| RTI No. | RTIF2-131126-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that a system satisfying one of the conditions described in [Conditions] sets the remote power management function. If Oracle Solaris is running and one of the events mentioned in [Event] occurs, an external I/O device may be erroneously powered off. [Condition] - Multiple SPARC M10 systems are registered in the remote power management group, and the physical partitions other than those of the SPARC M10 system that resets the XSCF are powered off. [Event] - A firmware update was executed from the flashupdate(8) command and XSCF Web, and the XSCF was rebooted. - The XSCF was reactivated from the rebootxscf(8) command and XSCF Web, and the XSCF was rebooted - The XSCF was rebooted because of a failure. |
| Workaround | Apply either of the following countermeasures: - Before firmware update or XSCF reboot, execute the setremotepwrmgmt -c disable command to disable the remote power management function. Subsequently, update the firmware or reboot the XSCF. After the XSCF has been activated, execute the setremotepwrmgmt -c enable command to enable the remote power management function. - Disable the remote power management function with the setremotepwrmgmt -c disable command and then manually power on the external I/O device. |
| RTI No. | RTIF2-131126-002 |
| Model | SPARC M10-4S |
| Description | If one of BB#0/BB#01/XBBOX#80/XBBOX#81 is added or replaced, the synchronous processing of the CPU Activation key in the master/standby XSCF will fail. Subsequently, if the master and standby are switched, the CPU Activation key may be lost. This generates the following phenomena. [If the PPAR power is on] The PPAR power is powered off because of a CPU Activation violation. [If the PPAR power is off] PPAR power-on fails because there is an insufficient number of CPU Activations. |
| Workaround | After addition/replacement, the synchronous processing of the CPU Activation key is performed when the following is executed. - If the master/standby XSCF is not switched Execute the rebootxscf -a or addcodactivation(8) command from the master XSCF that requested addition/replacement. - If the master/standby XSCF has been switched Execute the switchscf(8) command to return the master XSCF to the pre-addition/replacement state. After that, execute the rebootxscf -a or addcodactivation(8) command. Note - Do not perform the following operations before restoring the master XSCF to its original state by executing the switchscf(8) command. If these operations are performed, it may be necessary to register the CPU Activation key again. - rebootxscf -a - addcodactivation(8) - deletecodactivation(8) - Input power off/on |
| RTI No. | RTIF2-131126-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When the firmware update of the PCI expansion unit and link card is complete, the firmware version of the PCI expansion unit is erroneously displayed. Specifically, "PCIBOX version" of the event log displays the pre-update version, while "last version" displays the post-update version. [Example] Version displayed after an update from 1120 to 1130 - Incorrect LINKCARD=1, bank=1, PCIBOX version=1120: last version=1130 - Correct LINKCARD=1, bank=1, PCIBOX version=1130: last version=1120 |
| Workaround | There is no effective workaround. Replace the version number. Moreover, update the XCP firmware to XCP 2090 or later. |
| RTI No. | RTIF2-131112-002 |
| Model | SPARC M10-4S |
| Description | Suppose that the system uses a crossbar box and contains two or more physical partitions (PPARs) each consisting of 2BB or more. In this system, if a hardware failure that affects all the PPARs occurs, the failed part is degraded such that the PPAR reactivation processing may fail, causing all the PPAR power supplies to remain turned off. |
| Workaround | There is no effective workaround. The failed parts are degraded. Power on the PPAR again. |
| RTI No. | RTIF2-131112-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the testsb(8), diagxbu(8), or flashupdate -c sync command is executed during the execution of the flashupdate(8) command, the error log "FMEM serious error" is registered, and the testsb(8), diagxbu(8), or flashupdate -c sync command may fail. |
| Workaround | Do not execute the testsb(8), diagxbu(8), or flashupdate -c sync command while the flashupdate(8) command is being executed. To confirm the completion of the flashupdate(8) command, execute the showlogs event command and then check for the following message. XCP update has been completed (XCP version=xxxx:last version=yyyy) |
| RTI No. | RTIF2-131112-008 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that the error log "SCF Diagnosis error on System backup memory" is registered, which is related to the PSU backplane (PSUBP) or XSCF interface unit (XSCFIFU). The FRU of the error log registered immediately after that error log may not be correct. In this case, any one of the following messages is displayed to indicate that the FRU PSUBP or XSCFIFU is not correct. Msg: SCF Diagnosis initialize RTC FRU: PSUBP or XSCFIFU Or Msg: SCF Diagnosis error on XXXX FRU: PSUBP or XSCFIFU XXXX indicates any of the following FRUs: CPU, L2 cache, SDRAM, RTC, SPI FMEM, NAND |
| Workaround | There is no effective workaround. Replace the FRU as follows. For SPARC M10-1: FRU: /MBU For SPARC M10-4: FRU: /BB#00/CMUL For SPARC M10-4S: FRU: /BB#xx/CMUL or FRU: /XBBOX#xx/XSCFU |
| RTI No. | RTIF2-131112-011 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the physical partition (PPAR) is powered on and then the ioxadm(8) command is executed before the power-on processing is complete, the error log "SCF process down detected" is registered, and the ioxadm(8) command may fail. |
| Workaround | Do not execute the ioxadm(8) command until the PPAR power-on processing is complete. You can check the progress of the PPAR power-on processing by executing the showpparstatus(8) command. If the "Running" message appears as a result of executing the showpparstatus(8) command, it indicates that the PPAR power-on processing has been completed. Once the PPAR power-on processing has been completed, execute the ioxadm(8) command again. |
| RTI No. | RTIF2-131112-012 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that the error log "FAN speed too high" is registered because of an excessive fan rotation count. Subsequently, if an event that changes the fan rotation speed occurs, the fan rotation speed may not be switched to the correct value and instead may be switched to level 5 (full speed). If an event that changes the fan rotation speed occurs, the following event logs are registered. However, the displayed fan rotation speed will not be correct. The actual fan rotation speed level is 5, which is full speed. - Low temperature was detected at air inlet. FANs are changed to speed (level-1) mode - Low temperature was detected at air inlet. FANs are changed to speed (level-2) mode - Middle temperature was detected at air inlet. FANs are changed to speed (level-3) mode - High temperature was detected at air inlet. FANs are changed to speed (level-4) mode - Air outlet temperature recovered from warning state |
| Workaround | There is no effective workaround. [How to restore] Replace the fan of the detected excessive rotation speed error. |
| RTI No. | RTIF2-131112-014 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the following mail server is being used and REMCS registration or REMCS environment setting is performed, a communication timeout with the mail server is detected, causing processing to fail. - Windows ExchangeServer - E-PORT - qmail |
| Workaround | After changing the mail server to be used to sendmail or postfix, perform REMCS registration or REMCS environment setting. If it is difficult to change the mail server, update the firmware to XCP 2090 or later. |
| RTI No. | RTIF2-131112-015 |
| Model | SPARC M10-4S |
| Description | If the initbb(8) or replacefru(8) command is executed, an event log stating "Change Master Failed" may be registered. |
| Workaround | There is no effective workaround. Ignore the event log. |
| RTI No. | RTIF2-131107-001 |
| Model | SPARC M10-4S |
| Description | If the XSCF BB control cable is faulty or loose or if an XSCF failure occurs, it may take several hours to disconnect or reset the power supply of the physical partition (PPAR) consisting of multiple SPARC M10-4S units. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-131023-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | OID of scfDomainInfoGroup is duplicated and defined in the MIB definition file for XSCF expansion. Therefore, any attempt to install the MIB definition file for XSCF expansion in the server management software (e.g., JP1/Integrated Management manufactured by Hitachi) may fail. |
| Workaround | Delete the line of text of the duplicated OID from the MIB definition file for XSCF expansion. Then, install the MIB definition file for XSCF expansion again. The line of text to be deleted is the one defining scfDomainInfoGroup containing "::= { scfMIBObjectGroups 14 }". [Example] For the MIB definition file for XSCF expansion (XSCF-SP-MIB_2050.mib), delete the following lines 3558 to 3566. -------------- 3558: scfDomainInfoGroup OBJECT-GROUP 3559: OBJECTS { 3560: scfDomainNumber, scfPPARId, scfDomainName, 3561: scfDomainStatus 3562: } 3563: STATUS current 3564: DESCRIPTION 3565: "A collection of objects providing PPAR information." 3566: ::= { scfMIBObjectGroups 14 } -------------- |
| RTI No. | RTIF2-130305-009 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that 129 or more IP addresses of the trap hosts are registered by the setsnmp addtraphost or setsnmp addv3traphost command. Then, executing the showsnmp(8) command displays each of the SNMPv1, SNMPv2, SNMPv2-inform, and SNMPv3 trap hosts, up to a maximum of 128 entries. Similarly, suppose that 129 or more entries are registered by the setsnmpusm create, setsnmpvacm creategroup, setsnmpvacm createview, or setsnmpvacm createaccess command. Then, executing the showsnmpusm or showsnmpvacm command displays no more than 128 entries for a user, view, group, and access. |
| Workaround | There is no effective workaround. When 129 or more data entries are registered by the setsnmp(8), setsnmpusm(8), or setsnmpvacm(8) command that does not end abnormally, the data entries have been registered successfully. |
| RTI No. | RTIF2-130219-003 |
| Model | SPARC M10-4S |
| Description | The following error log is registered if you remove an XSCF BB control cable when removing a SPARC M10-4S with the initbb(8) command or replace a SPARC M10-4S or an XSCF unit with the replacefru(8) command. Msg: Board control error (MBC link error) Msg: BB control cable detected unexpected Msg: XSCF hang-up is detected |
| Workaround | There is no effective workaround. Ignore the error log. |
| RTI No. | RTIF2-130219-007 |
| Model | SPARC M10-4S |
| Description | When you turn on the input power to a crossbar box or SPARC M10-4S after disconnecting it in a system having a building block configuration, "Board control error (MBC link error)" may be registered in the error log. In addition, a non-existing crossbar box or SPARC M10-4S may be displayed as a faulty unit. |
| Workaround | This error log is registered when you disconnect the input power supply. Ignore this error log entry. |
< Previous Page | Next Page >