Skip to main content

Problems Resolved in XCP 2080


Problems Resolved in XCP 2080
The following table lists the problems resolved in XCP 2080.
Table 3-42  Problems Resolved in XCP 2080
RTI No. RTIF2-210104-006
Model SPARC M10-4S
Description On the system connected to a crossbar box, suppose that the initbb command has been executed to disconnect the SPARC M10-4S chassis. Then, the showboards -a command is executed, and it may end abnormally with "Segmentation fault (core dumped)."
Workaround There is no effective workaround.
To end the command normally, execute the showboards command again.
RTI No. RTIF2-210104-008
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Excessive information may be registered in the audit log.
Workaround There is no effective workaround.
RTI No. RTIF2-201215-009
Model SPARC M10-4
Description The SPARC M10-4 model has no building block configuration. Nevertheless, XSCF Web displays the [Update LSB] and [Configure PSB] buttons in the [PPAR Configuration] menu as active buttons, making them executable.
Workaround There is no effective workaround.
On the SPARC M10-4 model, do not operate the [Update LSB] and [Configure PSB] buttons in the [PPAR Configuration] menu.
RTI No. RTIF2-201215-011
Model SPARC M10-4S
Description When an XSCF shell command such as the shownetwork command is used while the SPARC M10 chassis requiring maintenance is removed by the replacefru command, communication may end with an error. Also, "Maintenance" is not displayed as the status of the chassis requiring maintenance.
Workaround There is no effective workaround.
RTI No. RTIF2-201215-017
Model SPARC M10-4, SPARC M10-4S
Description If memory degradation occurs in multiple places at power-on of a physical partition (PPAR), there may be unintentional changes to factory-default, causing an Oracle Solaris boot failure.
Workaround There is no effective workaround.
RTI No. RTIF2-201127-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description When the power switch on the operation panel has been used to power on a physical partition (PPAR), the event log displays "Cancel from air conditioner" even if the wait time for air conditioning is not set.
Workaround There is no effective workaround.
RTI No. RTIF2-201126-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The following px driver failure may occur in Oracle Solaris. In such cases, the snapshot command, when executed, may detect a "process down" error and reboot the XSCF.
[Example]
17709858 Domain hangs while resuming I/O devices
Workaround There is no effective workaround.
RTI No. RTIF2-201126-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Executing the showpparinfo command with the -M option specified may change the order of displayed information.
Workaround There is no effective workaround. Do not use the -M option.
RTI No. RTIF2-201126-006
Model SPARC M10-4S
Description If the SPARC M10-4S for the BB-ID specified with the -b option is in the system board pool (SP) state, the following error occurs by executing the diagxbu command.
"An internal error has occurred. Please contact your system administrator."
Workaround There is no effective workaround.
RTI No. RTIF2-201126-010
Model SPARC M10-4S
Description When the replacefru command is executed to replace the CPU memory unit lower (CMUL) or XSCF unit (XSCFU), the replacement may fail with the following message displayed.
[Warning:018]
Diagnostics have failed because of a configuration error.
Please verify the configuration.
Workaround There is no effective workaround.
RTI No. RTIF2-140507-008
Model SPARC M10-4S
Description The testsb(8) command detects the "STICK Stop Register error (does not stop)" or the "STICK does not stop (CPU)" error message and may fail.
Workaround There is no effective workaround.
[How to restore]
Collect diagnosis information by executing the snapshot(8) command. After the collection is complete, turn off/on the input power (AC OFF/ON) of all the chassis of the SPARC M10 system, and then contact a field engineer.
RTI No. RTIF2-131126-006
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Suppose that the input power is turned off and on, or that the XSCF is reset. If an operation related to CPU Activation is performed for the first time using XSCF Web rather than the XSCF shell, it may fail. The procedure that fails is any of the following.
1. Perform any of the following on XSCF Web.

- From the [Settings] - [CoD Activation] menu, add the CPU Activation key.

- From the [Maintenance] - [Configuration Management] menu, save the XSCF setting information.

- From the [Maintenance] - [Configuration Management] menu, save/restore the CPU Activation key.

2. Execute the deletecodactivation(8) or setcod(8) command on the XSCF shell.
Alternatively, delete the CPU Activation key on XSCF Web.
Alternatively, change the assignment of the CPU Activation on XSCF Web.


Or
1. Perform any of the following on XSCF Web.

- From the [Settings] - [CoD Activation] menu, delete the CPU Activation key.

- From the [Settings] - [CoD Reservation] menu, release the assignment of the CPU Activation.

2. Log in to the XSCF shell or XSCF Web with another user account.

3. Execute the deletecodactivation(8) or setcod(8) command on the XSCF shell.
Alternatively, delete the CPU Activation key on XSCF Web.
Alternatively, change the assignment of the CPU Activation on XSCF Web.
Workaround To perform an operation related to the CPU Activation for the first time after the input power is turned off and on or after the XSCF is reset, execute it on the XSCF shell.
[How to restore]
Execute the rebootxscf(8) command to reset the XSCF. Then, execute the deletecodactivation(8) or setcod(8) command on the XSCF shell.
RTI No. RTIF2-131112-009
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the physical partition (PPAR) is powered on, the event log of "LDC Protocol info from PPAR (PPAR ID 0:Domain Service Data Send Failed)" is output. Moreover, after Oracle Solaris activation, "ldoms/ldmd:default failed: transitioned to maintenance" is output to the OS console. This may cause Oracle VM Server for SPARC to enter maintenance mode.
Workaround There is no effective workaround.
[How to restore]
Execute the rebootxscf -a command to reset all the XSCFs, and then reactivate the control domain. If restoration fails, execute the poweroff(8) and poweron(8) commands on the XSCF to power off and then power on the physical partitions (PPARs).
RTI No. RTIF2-131108-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description The warning message "WARNING: invalid vector intr: number 0x10001, pil 0x11000" may be output to /var/adm/messages.
Workaround Ignore this message.
RTI No. RTIF2-131023-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the XSCF is reset by the rebootxscf(8) or switchscf(8) command executed while the logical domain is either starting or stopped, the following problems may occur.
- If the showdomainstatus(8) command is executed, the logical domain state is not displayed properly.

- If the showlogs event command is executed, the log does not display notifications about the logical domain state.

- An SNMP Trap for notification of the state of the logical domain is not sent.
Workaround There is no effective workaround.
[How to restore]
To display the state of the logical domain properly, update it by reactivating the logical domain or other means.
RTI No. RTIF2-131023-004
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Even when an I/O failure is detected in the logical domain, the XSCF may not be notified of an error. For this reason, the I/O failure information in Fault Report to be displayed from the execution of Oracle Solaris fmdump command in logical domains is not displayed, even if the showlogs error command is executed.
Moreover, even if a CPU or memory error is detected in the XSCF, no notification may be sent to the logical domain. For this reason, Fault Report does not display the CPU or memory failure information to be displayed from the execution of the showlogs error command, even if the fmdump command is executed.
Workaround There is no effective workaround. 
If an I/O failure is detected in the logical domain, locate the failed portion from the display in Fault Report by executing the fmdump command, and perform maintenance on the failed part. If a CPU or memory failure is detected in the XSCF, perform maintenance according to the FRU displayed by executing the showlogs error command.
RTI No. RTIF2-131001-001
Model SPARC M10-4S
Description If the SPARC M10-4S or the crossbar box is disconnected with the initbb(8) command, and then all chassis are turned off and then on again with the XSCF BB control cable left connected, the chassis disconnected with the initbb(8) command will become the master chassis, and the XSCF settings will be initialized to the factory defaults.
Workaround Be sure to follow the procedure below when disconnecting the SPARC M10-4S and the crossbar box.
1. Execute the initbb(8) command to stop the target chassis.

2. Turn off the stopped chassis first and then disconnect the XSCF BB control cable.
RTI No. RTIF2-130307-001
Model SPARC M10-4S
Description If any SPARC M10-4S that is specified with the diagxbu(8) command is not implemented, the message "PSB#xx-0 is not installed." showing the PSB No. that represents the unimplemented SPARC M10-4S should appear. However, the PSB No. of the SPARC M10-4S which actually has been implemented may be erroneously output.
Workaround There is no effective workaround. 
Execute the showhardconf(8) command to check the status of the SPARC M10-4S to which the corresponding PSB No. is assigned. 
The SPARC M10-4S which has not been implemented is not displayed with the showhardconf(8) command. 
When the corresponding SPARC M10-4S is displayed, read the PSB No. in the message "PSB#xx-0 is not installed." as that of the unimplemented SPARC M10-4S that was specified when this command was executed.
RTI No. RTIF2-130305-018
Model SPARC M10-4S
Description An internal error may occur when performing "Diagnostic tests" when selecting "BB" with the replacefru(8) command or executing the testsb(8) command. If you check the error log at this time, you can see that "no PSB available in PPAR" was registered in "PPAR#30" when the internal error occurred.
Workaround An error occurred in the applicable SPARC M10-4S and the system board (PSB) is in an unavailable state. Check the error log and replace the SPARC M10-4S.
RTI No. RTIF2-130305-019
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Diagnosis continues even when an error occurred on the testsb(8) command and timeout occurs after a two-hour wait.
Workaround Execute the showboards(8) command in another session while executing the testsb(8) command to check the status of PSB to be diagnosed. An operation will fail if "Test" is set to other than "Testing" and "Pwr" is set to "n". In this case, cancel the testsb(8) command by pressing [Ctrl] + [C].
RTI No. RTIF2-121219-011
Model SPARC M10-4S
Description While the poweroff(8) command is in the process of powering off a physical partition (PPAR), if deleteboard -c unassign is executed for the system board that belongs to the PPAR, the PPAR may not be powered off.
Workaround After executing the poweroff(8) command, confirm that the status field of the relevant PPAR shows Powered Off by using the showpcl(8) command. Then, execute the deleteboard(8) command.