Problems Resolved in XCP 2250
Problems Resolved in XCP 2250
The following table lists the problems resolved in XCP 2250.
| RTI No. | RTIF2-210209-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The "SCF process down detected" error may occur in some very rare cases. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201215-003 |
| Model | SPARC M10-4S |
| Description | Powering on three or more physical partitions (PPARs) at the same time may cause a power-on failure in some very rare cases. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201126-009 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that the initial diagnosis by POST detects an error and the system board (PSB) is degraded. Then, even after setting the mode switch on the operation panel to "Service" and turning on the input power again, you may be unable to cancel the degradation of the PSB. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201118-001 |
| Model | SPARC M10-4S |
| Description | In a system that has a physical partition (PPAR) with LSB number 15, the physical partition dynamic reconfiguration (PPAR DR) function may be used to incorporate a PSB into a PPAR. That incorporation may fail in some very rare cases. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201118-009 |
| Model | SPARC M10-4S |
| Description | If the master XSCF reboots during PSB diagnosis by the testsb or diagxbu command, the PSB being diagnosed may remain under diagnosis. |
| Workaround | There is no effective workaround. [How to restore] Turn off/on (AC OFF/ON) the input power to the system. |
| RTI No. | RTIF2-201117-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | It is possible to register an X.509 public key certificate in a format not supported by the verified boot function of the XSCF. This prevents such X.509 public key certificates from being displayed and enabled. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201117-005 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When the master XSCF reboots while the physical partition is powered off, some SPARC M10 units may not be powered off. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201117-010 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | If a serious failure occurs to a CPU, the Oracle VM Server for SPARC software may be unable to start even though the remaining CPUs can still operate. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-201109-014 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The control domain might panic due to send_mond_timeout, when XSCF slows down extremely. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-150514-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you execute the rebootxscf(8) command to reset an XSCF, "SCF panic detected" may be detected and the XSCF may stop. |
| Workaround | There is no effective workaround. [How to restore] Turn off the input power to the system and then turn it on again (AC OFF/ON). |
| RTI No. | RTIF2-150507-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | If the temperature of a part in a SPARC M10 system chassis or crossbar box rises, a high temperature part warning may in rare cases be registered even when the warning level has not been reached. |
| Workaround | There is no effective workaround. If a high temperature warning is registered, the system will automatically recover. This problem does not affect the system operation. |
| RTI No. | RTIF2-150507-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The "LINKCARD I2C error" error log may inadvertently be registered during firmware update for a PCI expansion unit. |
| Workaround | There is no effective workaround. Ignore this error log entry. The firmware update for the PCI expansion unit will end normally. |
| RTI No. | RTIF2-150227-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you connect a power cord of one of the power supply units (PSUs) in a redundant configuration right after disconnecting it, the event logs for power failure and power recovery may not be registered. In addition, if you repeat the operation of connecting the power cord of a PSU right after disconnecting it, "Input fail; AC: - ;" may appear in "Power Status" of PSU shown with the showhardconf(8) command even when the power cord is connected. |
| Workaround | Wait at least 10 seconds after you disconnect a power cord before connecting it again. [How to restore] If "Input fail; AC: - ;" appears in "Power Status" of the PSU shown with the showhardconf(8) command even when the power cord is connected, wait at least 10 seconds after you disconnect the power cord, and then connect it again. |
| RTI No. | RTIF2-150226-001 |
| Model | SPARC M10-4S |
| Description | Suppose you set the remote power management group with the setremotepwrmgmt(8) command when the remote power management function (RCIL) is used on a system configured with two or more SPARC M10-4S. If you execute the switchscf command on the master XSCF to switch between master and standby, remote power management may fail in the subsequent power supply operation. |
| Workaround | There is no effective workaround. [How to restore] Execute the rebootxscf(8) command to reset the standby XSCF. |
| RTI No. | RTIF2-150220-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the XSCF is reset due to any of the following while the physical partition (PPAR) is active, a break signal may be sent to the control domain of the PPAR. - rebootxscf(8) command execution - watchdog timeout occurrence due to a firmware factor - Panic occurrence due to a firmware factor - Pressing of RESET switch of XSCF This problem may occur even when you execute the setppartmode(8) command to set the break signal suppression. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-150218-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If an XSCF-LAN network is configured while an XSCF-LAN cable is not connected to an XSCF-LAN port, the XSCF-LAN may seem to be in the active state of "RUNNING". [Example] If no cable is connected to XSCF-LAN#1 XSCF> shownetwork -a bb#00-lan#0 Link encap:Ethernet HWaddr 00:00:00:12:34:56 inet addr: 192.168.11.10 Bcast: 192.168.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Omitted) bb#00-lan#1 Link encap:Ethernet HWaddr 00:00:00:12:34:57 inet addr:192.168.10.10 Bcast: 192.168.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 (Omitted) |
| Workaround | This state does not affect the system operation. Use it as is. |
| RTI No. | RTIF2-150129-001 |
| Model | SPARC M10-1 |
| Description | [1] If the input voltage drops, usually a power failure notification is issued and the physical partition is powered off. However, if the input voltage to the SPARC M10-1 drops instantaneously, no power failure notification is issued and the physical partition is powered off. [2] During the physical partition power-off due to the trouble in [1], if you execute the console(8) command to switch to the control domain console where you have entered a character or input a key, the following error log may be detected and the motherboard unit (MBU) may need to be replaced. MBC-CPU interface fatal error Check all the following five conditions are satisfied to see if the trouble in [1] occurs. - Any of the following error logs is registered: - MBU:SCF:failed to read/write interrupt mask register - MBU:SCF:failed to read/write active status register - Voltage out of range error - Oracle Solaris is not accessible via the network. - No power failure notification is issued. (*1) - The physical partition status display that you can check with the showpparstatus(8) command is not updated and indicates the physical partition is active (the status is other than "Powered Off"). - You can access the XSCF, but the execution result of the showlogs power command does not include "SCF Reset" indicating that the XSCF is reset. *1 If a power failure notification is issued, usually the following log is registered with the showlogs event command. PSU input power failure(/PSU#0) PSU input power failure(/PSU#1) In addition, the following error log is detected in many cases when the trouble in [1] occurs: failed to read/write extended active status register |
| Workaround | There is no effective workaround. If "MBC-CPU interface fatal error" is detected, replace the MBU. If "MBC-CPU interface fatal error" is not detected, turn off the input power supply and then turn it on again. |
| RTI No. | RTIF2-150126-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the XSCF is reset while the system is operating with the remote power management function enabled, the power of an external I/O device may be turned off incorrectly. |
| Workaround | Every time after the physical partition (PPAR) is powered on, disable the remote power management function with the RCIL, and then enable it again. This also applies when the PPAR is automatically powered on due to a power failure, power recovery, the auto power control system (APCS), RCIL, etc. [Example] XSCF> setremotepwrmgmt -c disable XSCF> setremotepwrmgmt -c enable Perform the following procedure when you cannot perform this workaround due to a system operation issue. - When two or more SPARC M10 systems are registered to the remote power management group, do not reset an XSCF at the same time as another SPARC M10 system's XSCF. - When only a single SPARC M10 system is registered to the remote power management group, perform either (1) or (2) below. (1) Disable only the power-off of the remote power management function. 1. Execute "setremotepwrmgmt -c disable" to disable remote power management. 2. Specify "0x01" for the Linkage value in the management file of remote power management. [Example] 1,1,0x01,00000000000000000000000000000011,0x01,0x00,,,10.20.300.40,0x20,aa:bb:cc:dd:ee:f0,,,,,,,,,, 1,2,0x10,00000000000000000000000000000022,0x01,0x00,,,10.20.300.41,0x20,aa:bb:cc:dd:ee:f1,,,,,,,,,, 3. Execute "setremotepwrmgmt -c config [file name]" to apply the management file. 4. Execute "setremotepwrmgmt -c enable" to enable remote power management. (2) Disable the remote power management function. 1. Execute "setremotepwrmgmt -c disable" to disable remote power management. 2. If the external I/O device is an ETERNUS, set the ETERNUS to LOCAL mode for operation. |
| RTI No. | RTIF2-150119-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The message " WARNING: Time of Day clock error: reason [Reversed by YYYY]" or "WARNING: Time of Day clock error: reason [Jumped by YYYY]" may appear on the OS console. |
| Workaround | There is no effective workaround. [How to restore] If you need accurate time while the NTP client is not set, restart Oracle Solaris so that it references the hardware time. Confirm the time after this restart. |
| RTI No. | RTIF2-141226-001 |
| Model | SPARC M10-4S |
| Description | If time synchronization of the master XSCF and the NTP server fails during master/standby XSCF switching, the XSCF time may shift and the ntpd may not start. If ntpd is not active, a message "NTP is unavailable." is output by executing the showntp -l command. Note that this problem does not occur if the NTP client setting of the XSCF and the NTP server setting are disabled. |
| Workaround | There is no effective workaround. [How to restore] If ntpd is not active when the NTP client setting of the XSCF or the NTP server setting is enabled, execute the rebootxscf(8) command to reset the XSCF. |
| RTI No. | RTIF2-141208-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Suppose that the audit system is configured so that writing to audit records stops temporarily when the audit trail reaches its full capacity. An XSCF shell or XSCF Web operation at this time may lead to an XSCF reset due to the mistaken detection of one of the following errors: "Hardware access error." or "SCF panic detected." This problem occurs even when the XSCF shell is automatically run regularly to monitor the logical domain status by using PRIMECLUSTER software. You can check the contents of the currently set audit system by using the showaudit(8) command. In the following example, "Policy on full trail" is "suspend," indicating that writing to the audit record has been set to stop temporarily. Also, "Audit space free" is "0," indicating that the audit trail has reached its full capacity. [Example] XSCF> showaudit all Auditing: enabled Audit space used: 4194304 (bytes) Audit space free: 0 (bytes) Records dropped: 0 Policy on full trail: suspend --- Omitted --- |
| Workaround | Execute the setaudit -p count command to configure the audit system to delete new audit records when the audit trail has reached its full capacity. (Default) [How to restore] Perform the following procedure. 1. Perform login authentication using the default user account. 2. Execute the restoredefaults xscf command. The audit log is erased. You can execute the setaudit command. 3. Execute the setaudit -p count command to configure the audit system to delete new audit records when the audit trail has reached its full capacity. (Default) |
| RTI No. | RTIF2-141111-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | On the SPARC M10-1/M10-4 or SPARC M10-4S in a single-chassis configuration, the contents of the scheduled operation setting for automatic power-on/power-off is lost and automatic power-on/ power-off becomes disabled. This occurs even when the PSU backplane (PSUBP) or PSU backplane unit (PSUBPU) and the microSD card are not replaced at the same time, as shown in the following procedure. 1. Turn off the input power (AC OFF) and replace PSUBP or PSUBPU. 2. Turn on the input power (AC ON) and start XSCF. 3. Turn off the input power (AC OFF) and replace the microSD card on the motherboard unit (MBU) or CPU memory unit lower (CMUL). Note that this problem occurs even if the microSD card is replaced first. |
| Workaround | After the first FRU is replaced, disable the scheduled operation and then enable it again to transfer the contents of the scheduled operation to the replacing FRU. Execute the following procedure. 1. Replace the first FRU. (step 1 in the Description) 2. Disable the scheduled operation. XSCF> setpowerschedule -a -c control=disable 3. Enable the scheduled operation again. XSCF> setpowerschedule -a -c control=enable 4. Execute step 2 and the subsequent steps in the Description. [How to restore] - If the dumpconfig(8) command is used to save the XSCF setting information, execute the restoreconfig(8) command and restore the XSCF setting information. - If the XSCF setting information is not saved, execute the setpowerschedule(8) command and reset the scheduled operation. |
| RTI No. | RTIF2-141111-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If any of the following events occur and the XSCF is reset, an incorrect error log may be registered. In addition, the XSCF time after the error occurrence time may be initialized to January 1, 1970. - XSCF panic - watchdog timeout - The RESET switch on the rear panel pressed The following two examples show incorrect entries registered in the error log and also error occurrence times that were initialized. [Example 1] Date: Jan 01 09:05:40 JST 1970 Code: 80002008-000e010000ff0000ff-018b00010000000000000000 Status: Alarm Occurred: Jan 01 09:04:56.276 JST 1970 FRU: /MBU Msg: Hardware access error. Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 [Example 2] Date: Jan 01 09:05:51 JST 1970 Code: 10000000-000e010000ff0000ff-010240020000000000000000 Status: Information Occurred: Jan 01 09:05:35.008 JST 1970 FRU: /MBU Msg: TWI access error Diagnostic Code: 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 0000 00000000 00000000 00000000 00000000 00000000 00000000 0000 |
| Workaround | There is no effective workaround. Do not press the RESET switch unless it is urgent and required. [How to restore] After powering off the physical partition (PPAR), turn off and on (AC OFF/ON) the input power to the system. By turning on the power again, the XSCF time is restored automatically. |
| RTI No. | RTIF2-140929-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | "NOTICE: Unable to get TX queue state!" is displayed mistakenly if Oracle Solaris is started in a system configured with Oracle Solaris kernel zones. |
| Workaround | There is no effective workaround. Ignore this message. |
| RTI No. | RTIF2-140929-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | In a system with the SPARC M10-1, SPARC M10-4, or SPARC M10-4S in a single-chassis configuration, the settings of the remote power management function (RCIL) are lost when the fixed microSD card in the motherboard unit (MBU) or CPU memory unit lower (CMUL) is replaced. |
| Workaround | There is no effective workaround. [How to restore] See the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 RCIL User Guide, and reconfigure RCIL. |
| RTI No. | RTIF2-140808-002 |
| Model | SPARC M10-4S |
| Description | When the showhardconf(8) command is executed after the input power is turned off and then on, information on the configuration of components installed on the system may not be recognized. |
| Workaround | There is no effective workaround. [How to restore] Execute the rebootxscf -a command to reset all XSCFs. |
| RTI No. | RTIF2-140407-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If [Ctrl] + [t] is pressed in response to the ok prompt that appears after starting OpenBoot PROM, the following trap related error message is output on the domain console of the logical domain. {0} ok ERROR: Last Trap: Fast Instruction Access MMU Miss TL: 1 %TL:1 %TT:64 %TPC:1056e6f20 %TnPC:1056e6f24 %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:183 %TPC:f0248e68 %TnPC:f0200c80 %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 --- ?? Called from (f0227228) at f0227240 0 (emit Called from (lf at f020c3c8 (lf Called from lf at f020c404 lf Called from crlf at f020c424 pop-base Called from (f0225fe0) at f0226024 pop-base Called from (f0225fe0) at f0226024 (f0225fe0) Called from (f0248350) at f024838c 7fffffffffffff98 80000000fecdaff8 (f02081dc) Called from (f0248350) at f024837c {0} ok |
| Workaround | There is no effective workaround. [How to restore] From the ok prompt, execute the reset-all command to restart OpenBoot PROM. {0} ok reset-all |
| RTI No. | RTIF2-140403-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you connect to the control domain console by executing the console(8) command on the XSCF serial terminal and then execute any of the following while the control domain console outputs a message, the "SCF process down detected" error may occur and the XSCF may be reset. - Entering "#" to disconnect the control domain console - Executing the console(8) command by specifying the -f option from another terminal to forcibly connect to the control domain console of the physical partition (PPAR) - Executing the switchscf(8) command to switch the master XSCF - Executing the rebootxscf(8) command to reset the XSCF |
| Workaround | Execute the console(8) command after connecting to the XSCF via telnet or ssh, or terminate the console(8) command after powering off the PPAR. |
| RTI No. | RTIF2-140227-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you execute the cfgadm command from a logical domain to use PCI hot plug (PHP) to disconnect a link card from the system, power supply to the link card will stop and "LINKCARD I2C error" will be inadvertently registered in the error log. |
| Workaround | There is no effective workaround. Ignore this error log entry. The system can operate continuously since the supply of power to link card has definitely stopped. |
| RTI No. | RTIF2-140212-013 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When powering on the physical partition (PPAR), the failure of a DIMM might register "CPU internal fatal error" for the following components: motherboard unit (MBU), CPU memory unit lower (CMUL), or CPU memory unit upper (CMUU). |
| Workaround | There is no effective workaround. If after replacing the MBU, CMUL or CMUU in question, the same error is registered again, replace all the DIMMs that are mounted on the MBU, CMUL and the CMUU. |
< Previous Page | Next Page >