Skip to main content

Problems Resolved in XCP 2210


Problems Resolved in XCP 2210
The following table lists the problems resolved in XCP 2210. 
Table 3-38  Problems Resolved in XCP 2210
RTI No. RTIF2-210104-010
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When a snapshot has been collected in XSCF Web, in some very rare cases, a "process down" may occur and the XSCF may reboot.
Workaround There is no effective workaround.
RTI No. RTIF2-201126-007
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The set IP address of the NTP server may contain "127.127" or "0.0". In such cases, the showntp command, when executed, does not display the set IP address.
Workaround There is no effective workaround.
RTI No. RTIF2-201126-008
Model SPARC M10-4, SPARC M10-4S
Description If an error occurs in the power supply of the CPU memory unit upper (CMUU), the error may be erroneously detected in the CPU memory unit lower (CMUL).
Workaround There is no effective workaround.
RTI No. RTIF2-201120-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When a hardware error occurs, a BB-ID that does not exist in the system may be registered for the FRU in the error log, and excessive entries may be registered in the error log.
Workaround There is no effective workaround.
Ignore this error log entry.
RTI No. RTIF2-201120-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If a CPU failure occurs, a "process down" may occur and the XSCF may reboot.
Workaround There is no effective workaround.
RTI No. RTIF2-201119-003
Model SPARC M10-4S
Description If there is a problem with a crossbar cable connection when the diagxbu command is executed, the specified crossbar box may not be powered off but remain powered on even after the diagnosis ends.
Workaround There is no effective workaround.
RTI No. RTIF2-201119-004
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When using XSCF Web in Internet Explorer, you are unable to add the following power schedules from [Settings] - [Power Schedule] menu:
- "special" is selected for a one-shot power schedule.

- "holiday" is selected for a pause of scheduled operation.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-018
Model SPARC M10-4S
Description Hypervisor might abort when dynamically performing the deleteboard operation after an I/O has been deleted or added.
Workaround There is no effective workaround.
RTI No. RTIF2-140605-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If either of the following events occurs, the ttydm process may fail, causing the XSCF to be reset:
- The console(8) command is executed to connect to the control domain console after one of the following events occurs: A large amount of data is output to the screen of the domain console and the console(8) command terminates when the XSCFs for multiple SPARC M10-4S chassis are reset.

- The console(8) command is executed to forcibly connect to the control domain console.

If the ttydm process fails, the following error log is registered:
[Example]
XSCF> showlogs error -v
Date: Dec 01 22:08:13 JST 2013
    Code: 20000000-00fcff00b0000000ff-010400010000000000000000
    Status: Notice                 Occurred: Dec 01 22:08:04.886 JST 2013
    FRU: /FIRMWARE,/XBBOX#80/XSCFU
    Msg: SCF process down detected
    Diagnostic Code:
       00000000 00000000 0000
       50000000 00000000 0000
       00000000 00000000 0000
       74747964 6d2e3239 37302e62 7a320000
       00000000 00000000 0000
If the first five bytes on the fourth line in [Diagnostic Code:] are "747479646d", the ttydm process has failed.
Workaround There is no effective workaround.
[How to restore]
- For a system that consists of multiple SPARC M10-4S chassis

 By executing the console(8) command after XSCF resetting, which causes master/standby XSCF switching, you can connect to the control domain console.

- For the SPARC M10-1, SPARC M10-4, or SPARC M10-4S in a single-chassis configuration

 By executing the console(8) command after XSCF resetting, you can connect to the control domain console.
RTI No. RTIF2-140507-019
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If Firefox 26 is used in an environment with XSCF firmware older than XCP 2210, the frame of the pop-up window appears with a thick black line.
Workaround Ignore the thick black frame.
RTI No. RTIF2-140507-020
Model SPARC M10-4S
Description If the master XSCF is switched to the standby state just after executing the poweroff -f -p -n command (n: partition number), the following message is registered in the error log, displayed by the showlogs error command.
Msg: SCF process down detected
Workaround There is no effective workaround.
This symptom has no effect on the system operation.
RTI No. RTIF2-140410-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description An XSCF NTP server function may be used as the platform for a DDoS attack (CVE-2013-5211).
Workaround Update the XCP firmware to XCP 2210 or later.
RTI No. RTIF2-140410-007
Model SPARC M10-4S
Description When setting the takeover IP address (virtual IP address) for the XSCF network, the XSCF-LAN IP address (physical IP address) needs to be set for both the master and standby XSCFs. Otherwise, the takeover IP address setting may not be reflected after the setting is applied and the XSCF is reset.
Workaround Set the XSCF-LAN IP address (physical IP address) of both master and standby XSCFs and then set the takeover IP address.
RTI No. RTIF2-140407-007
Model SPARC M10-4S
Description After a degraded system board is replaced using the replacefru(8) command, the replacement system board is diagnosed using the replacefru(8) command menu or the testsb(8) command. The diagnosis fails if all of the following conditions are met.
- Physical partition (PPAR) consists of multiple system boards and the PPAR power is on.

- Some system boards in the PPAR are stopped through degradation.
Workaround Use either of the following procedures to replace a system board and execute diagnosis.
1. Before replacing the system board, execute the deleteboard(8) command to change the system board state to system board pool (SP).

2. After completing system board replacement and diagnosis, execute the addboard(8) command to assign the system board to the PPAR again.

Or
1. After powering off the PPAR, execute system board replacement and diagnosis.

[How to restore]
After executing the deleteboard(8) command to change the system board state to system board pool (SP) or after powering off the PPAR, redo the system board diagnosis.
RTI No. RTIF2-140303-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description In some very rare cases, the XSCF does not start after performing AC OFF/ON.
Workaround There is no effective workaround.
Contact a field engineer if this symptom occurs.
RTI No. RTIF2-140221-002
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)" message is registered while logical domains are running and the "WARNING: ds@x: ds_handle_recv: invalid message length, received xxx bytes, expected xxx" message is displayed on the control domain console.
Workaround There is no effective workaround.
Reset the XSCF with the rebootxscf -a command. After that, execute the svcs command on the control domain to restart the picl, fmd, and ldmd services.
RTI No. RTIF2-140212-001
Model SPARC M10-4S
Description In a configuration with several SPARC M10-4S chassis (system boards), a system board in a physical partition has been degraded due to failure. Afterward, in an attempt with the replacefru(8) command to replace the system board, the system board is recognized as running, and the replacement attempt fails with the following error message:
[Warning:028]
BB#XX cannot be replaced because the PSB in the BB that you indicated is running.
Similarly, an attempt to initialize the degraded system board with the initbb(8) command fails with the following error message:
Hardware error occurred by initial diagnosis.
This symptom occurs if the system board is in the following state, when the showhardconf(8) or the showboards(8) command is executed:
[Example]
In case PSB#01-0 (BB#01) has been degraded.
XSCF> showhardconf
 :
* BB#01 Status:Deconfigured;
 :
XSCF> showboards -a
PSB  PPAR-ID(LSB) Assignment  Pwr  Conn Conf Test    Fault
---- ------------ ----------- ---- ---- ---- ------- --------
01-0 00(01)       Assigned    n    n    n    Passed  Faulted
Workaround After removing the degraded system board from the physical partition with the deleteboard(8) command, execute either the replacefru(8) or the initbb(8) command to replace or remove the system board.
[Example]
XSCF> deleteboard -c unassign 01-0
After replacing the system board, assign the system board to the physical partition using the addboard(8) command and follow the maintenance procedures to add it in the physical partition.
[Example]
XSCF> addboard -c assign -p 0 01-0
RTI No. RTIF2-140212-010
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the [Ctrl] + [C] keys are pressed partway through the execution of the setsnmp(8), setsnmpusm(8), or setsnmpvacm(8) command, SNMP cannot be set up using the above commands after that. In such a case, the error message "configuration being changed by another user" may be displayed.
Workaround There is no effective workaround.
RTI No. RTIF2-140212-015
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the version(8) command is executed after replacement of the CPU memory unit lower (CMUL), XSCF unit (XSCFU) or motherboard unit (MBU), the Current bank and Reserve bank are incorrectly displayed.
[Example]
- Before replacing CMUL

  XSCF> version -c xcp
  BB#00-XSCF#0 (Master)
  XCP0 (Reserve): 2210
  XCP1 (Current): 2210
- (Wrong) After replacing CMUL

  XSCF> version -c xcp
  BB#00-XSCF#0 (Master)
  XCP0 (Reserve): 2210
  XCP1 (Current): 2210
- (Right) After replacing CMUL

  XSCF> version -c xcp
  BB#00-XSCF#0 (Master)
  XCP0 (Current): 2210
  XCP1 (Reserve): 2210
Workaround There is no effective workaround.
It will not affect the system as it is only a problem with the command output.
[How to restore]
Re-execute the flashupdate(8) command.
RTI No. RTIF2-140212-017
Model SPARC M10-4S
Description After the SPARC M10-4S or a crossbar box (XBBOX) is removed with the initbb(8) or replacefru(8) command, the XSCF network (host and domain names, SSCP, IP address, routing, name server) is set up and the applynetwork(8) command is executed. Then, if the "An internal error has occurred. Please contact your system administrator" error message is output, the XSCF network parameters do not reflect the above settings.
Workaround There is no effective workaround.
[How to restore]
After re-connecting or replacing the removed SPARC M10-4S or XBBOX, set up the XSCF network again.
RTI No. RTIF2-140212-018
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description In the REMCS customer information input screen, if any of the following two-byte characters are input in the two-byte input field, input error message may be output.
- The leading character corresponds to A1xx of the EUC code.

- The trailing character corresponds to xxA1 of the EUC code.
Workaround Do not input the two-byte characters that cause this error at the beginning or end of a character string.
RTI No. RTIF2-140212-019
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When turning on the input power, the voltage reading of the power supply unit (PSU) fails and the PSU error "Hardware access error" may be mistakenly detected and the PSU is degraded.
Workaround There is no effective workaround.
[How to restore]
Ignore this error log entry. To release the PSU from the degraded state, turn off the input power and turn it on again.
RTI No. RTIF2-140212-020
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When hot-swapping a fan, if the fan is installed right after removing it, hot-swapping may fail.
Workaround When replacing a fan, after removing it, wait at least 10 seconds before installing one.
RTI No. RTIF2-140212-023
Model SPARC M10-4, SPARC M10-4S
Description If CPU failures like the following occur on a SPARC M10-4/M10-4S where a CPU memory unit lower (CMUL) and a CPU memory unit upper (CMUU) is mounted, when starting a physical partition (PPAR) the "Hypervisor Abort" error occurs and the PPAR cannot be used anymore.
- In the SPARC M10-4,

if all the CPUs mounted on the CMUL are degraded.

- In the SPARC M10-4S,

if all the CPUs mounted on the CMUL on all the chassis that configures the PPAR, are degraded.
Workaround There is no effective workaround.
Replace the CMUL on which the failed CPUs are mounted.
RTI No. RTIF2-140212-024
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description After executing the ldm add-spconfig or ldm set-spconfig command in Oracle Solaris, if the OpenBoot PROM environment variable auto-boot? is changed, the set value does not show up when the XSCF showpparparam(8) command is executed. The value that existed before the ldm add-spconfig or ldm set-spconfig command was executed is displayed.
This symptom occurs when the following procedures are done in the following sequence.
1. Start the physical partition (PPAR).

2. Execute the ldm add-spconfig command from the control domain of the running PPAR to save logical domain configuration information. Or, execute the ldm set-spconfig command from the control domain of the PPAR to specify the name (config-name) of the logical domain configuration information that will be used at the next PPAR start time.

3. From Oracle Solaris on the control domain, execute "eeprom auto-boot?=xxxx" to change the environment variable of OpenBoot PROM. or, change the OpenBoot PROM environment variable from the OpenBoot PROM itself.
Workaround There is no effective workaround.
However, the value itself has been enabled. Check the value of the OpenBoot PROM environment variable "auto-boot?", which will be used at the next PPAR start time, not from the XSCF but from Oracle Solaris on the control domain or from OpenBoot PROM.
RTI No. RTIF2-140212-025
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description With the SPARC M10-4/M10-4S, suppose that all the I/Os on the CPU memory unit lower (CMUL) in one of chassis composing a physical partition (PPAR) cease working. Or with the SPARC M10-1, suppose that all the I/Os on the motherboard unit (MBU) cease working. Then, if you power on the PPAR without replacing the failed components, hypervisor startup will be aborted or Oracle VM Server for SPARC will enter the "suspended" state after Oracle Solaris startup. Any of the following has occurred when all I/Os cease working.
- I/O power supply has failed.

- All PCI Express root complex have failed.

- All PCI switches have failed. 
Workaround There is no effective workaround.
[How to restore]
In the case of the SPARC M10-4S/M10-4, replace the CMUL on which the I/O has failed.
In the case of the SPARC M10-1, replace the MBU on which the I/O has failed.
RTI No. RTIF2-140122-001
Model SPARC M10-4S
Description When a PCI expansion unit is connected to a logical system board whose LSB number is equal to or greater than 01 (LSB#01), if the direct I/O feature is enabled for the PCI expansion unit, the PCI expansion unit may not be recognized by the logical domain.
Workaround If the PCI expansion unit is not recognized, reboot the logical domain.
RTI No. RTIF2-131218-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description While the Solaris OS is running, if the physical partition is reset due to the output of the "Hypervisor Abort" message on the OS console, the state of Oracle VM Server for SPARC may change to maintenance mode at the next reboot of the physical partition.
Workaround There is no effective workaround.
[How to restore]
Reboot the control domain only.
If the state of Oracle VM Server for SPARC does not become "online", execute the rebootxscf -a command to reset all the XSCFs and then check the state of Oracle VM Server for SPARC once again. If the state has not yet become "online", once more reboot the control domain only.
RTI No. RTIF2-131213-001
Model SPARC M10-4S
Description In a system configuration with at least 3 BBs or a crossbar box, when the XSCF master/standby switchover is executed due to some abnormality on the master XSCF, the master XSCF may fail to switch over to the standby XSCF and start up as another master XSCF. Due to this, the system seems to contain two master XSCFs. Normal behavior of a system is not guaranteed when there are two master XSCFs in the system.
This state can be confirmed by a lighted MASTER LED at the rear panel of two chassis.
Workaround There is no effective workaround.
[How to restore]
The system can be operated normally when the number of master XSCFs automatically returns to one after a few minutes.
If the number of master XSCFs does not return to one even after 15 minutes, press the RESET switch at the rear panel of all existing SPARC M10 systems and crossbar boxes. The system can be operated normally after that.
RTI No. RTIF2-131213-004
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose the PPAR DR function is enabled/disabled on XSCF Web when PPAR-DR(Current) or PPAR-DR(Next) is selected from the [PPAR Operation] - [PPAR Mode Configuration] menu and [Configure] is clicked. Then, the wrong dialog box appears, and the PPAR DR function cannot be changed to disabled/enabled.
Workaround Execute the XSCF setpparmode(8) command to enable/disable the PPAR DR function.
RTI No. RTIF2-131213-008
Model SPARC M10-4S
Description In a system configuration with at least 3 BBs or a crossbar box, after XSCF switchover occurs due to some problems on the master XSCF while the addboard -c configure command is running, the deleteboard(8) command executed on the new master XSCF may not respond. This symptom occurs if two master XSCFs exist on a system after a master/standby switchover of XSCFs. (Reference: RTIF2-131213-001)
This state can be confirmed by a lighted MASTER LED at the rear panel of two chassis.
Workaround There is no effective workaround.
[How to restore]
Execute the deleteboard(8) command when the number of master XSCFs automatically returns to one after a few minutes.
If the number of master XSCFs does not return to one even after 15 minutes, press the RESET switch at the rear panel of all existing SPARC M10 systems and crossbar boxes. Execute the deleteboard(8) command after that.
RTI No. RTIF2-131213-009
Model SPARC M10-4S
Description If the addboard(8) or deleteboard(8) command is executed using the DR feature,
addition or removal of system boards using the DR feature may fail, displaying the message "Failed to evacuate board resources."
Workaround Re-execute the addboard(8) or deleteboard(8) command.
If it fails again, either reboot the control domain or reboot the XSCF with the rebootxscf –a command. After that, re-execute the addboard(8) or deleteboard(8) command of the DR feature.
RTI No. RTIF2-131213-021
Model SPARC M10-4S
Description The timeout error log "Timeout detected during unconfiguration of PSB#xx-x." may be registered and an abnormal termination may occur when a system board (PSB) is removed by the deleteboard(8) command of the DR feature. In such a case, the showboards(8) command shows that the status of all the Pwr/Conn/Conf of the system board (PSB) is "y".
Workaround There is no effective workaround.
[How to restore]
Reboot all the XSCFs by executing the rebootxscf -a command.
RTI No. RTIF2-131212-001
Model SPARC M10-4S
Description If there is a physical partition (PPAR) whose LSB number is 01 or larger, the showlogs error command either does not show the "I/O device error detected" log even if I/O errors occur, or the FRU in the "I/O device error detected" message is mistakenly displayed.
Workaround There is no effective workaround.
RTI No. RTIF2-131126-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The [Physical] or [Logical] tree displayed in the menu frame is not updated even if you click the [Refresh] button of the masthead frame on XSCF Web.
Workaround Click the [Physical] or [Logical] tab of the menu frame to redisplay the tree.
RTI No. RTIF2-130801-002
Model SPARC M10-1, SPARC M10-4
Description If a DIMM failure occurs, a configuration error is erroneously detected and the following event log is registered.
SCF:DIMM configuration error on PSB#xx-0
Workaround There is no effective workaround.
Ignore this event log.
Using the maintenance procedure for DIMM failures, turn off the input power to the SPARC M10 system chassis in which the failed DIMM is mounted, replace the DIMM, and then turn on the power. These steps will remove the configuration error and failure.