Problems Resolved in Versions Prior to XCP 2050
Problems Resolved in Versions Prior to XCP 2050
The following table lists the problems resolved in versions prior to XCP 2050.
| RTI No. | RTIF2-130612-001 |
| Model | SPARC M10-4S |
| Description | If the XCP firmware version is XCP 2041, XCP 2042, or XCP 2043, SPARC M10-4S cannot be replaced by using the replacefru(8) command in a system with more than one SPARC M10-4S. |
| Workaround | Perform cold replacement (replacement performed with the input power off) or update the XCP firmware version to XCP 2044 or later before performing replacement. |
| RTI No. | RTIF2-130516-005 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the showcodactivation(8) command is executed while data is being restored with the restoreconfig(8) or restorecodactivation(8) command, it may be impossible to display the execution results. If this occurs, the showcodactivation(8) command ends with a "codd internal error". |
| Workaround | To display the showcodactivation(8) command execution result, execute it after the execution of the restoreconfig(8) or restorecodactivation(8) command has completed. |
| RTI No. | RTIF2-130515-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | While the system is operating, the following events may occur: 1. The prtpicl command of Oracle Solaris no longer responds. 2. The display data (such as the XCP version) of prtpicl -v and prtdiag -v is not output as expected. 3. To /var/adm/messages, the warning message "PICL snmpplugin: cannot fetch object value" is output. 4. An XSCF CMDD process shutdown occurs and the XSCF is reset repeatedly such that it becomes unusable. At this time, system operation can be continued. |
| Workaround | There is no effective workaround. [How to restore] If event 1 occurs: Recover with the following procedure. 1. End the prtdiag command with [Ctrl] + [C]. 2. Wait about 30 minutes to allow an SNMP timeout to occur on the XSCF. 3. On the control domain, execute the svcadm command to restart the picl service. If event 2 occurs: Execute the command again. If results are displayed, the system can be operated continuously. If the state where results are not displayed as expected continues, check whether the XSCF is operating. - If the XSCF is operating, use the rebootxscf(8) command to reset the XSCF. - If the XSCF is not operating, turn off and then on the input power to the system (AC OFF/ON) to recover. If event 3 occurs: The system can be operated continuously because this is a temporary warning message. If event 4 occurs: Turn off the input power supply of the system, and then back on (AC OFF/ON) to recover. |
| RTI No. | RTIF2-130507-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | There is a case where a RAID volume cannot be recognized after a power failure occurred while using the hardware RAID function. |
| Workaround | Please run the activate-volume command at ok prompt to activate a hardware RAID volume. For details on the procedure, see "14.2.11 Re-enabling a Hardware RAID Volume" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide. |
| RTI No. | RTIF2-130417-001 |
| Model | SPARC M10-4S |
| Description | If the XSCF mounted in the crossbar box panics, it may be impossible to perform communication between the master XSCF and non-master XSCF. |
| Workaround | There is no effective workaround. [How to restore] If the event occurs, wait 15 minutes or longer, and then use rebootxscf -s to reset the master XSCF. |
| RTI No. | RTIF2-130416-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the PCI device in the I/O domain is deleted (ldm rm-io) or a PCI device is added (ldm add-io), hypervisor abort may occur when the I/O domain starts. |
| Workaround | To delete the PCI device in the I/O domain, delete all devices under the same route complex as that of the PCI device to be deleted (which have the same xxxx of /pci@xxxx) and then add the necessary devices again. Alternatively, do not assign multiple devices under the same route complex to a single I/O domain. |
| RTI No. | RTIF2-130415-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | In SPARC M10-4/M10-4S, if the firmware version is XCP 2031 or XCP 2032, the initial value of the following OpenBoot PROM environment variable differs from the default. Even if the setting was changed with the setpparparam(8) command in the XSCF shell or the setenv command from the OpenBoot PROM prompt, it will return to the original value. auto-boot? false diag-switch? true fcode-debug? true local-mac-address? false |
| Workaround | There is no effective workaround. Make a firmware update to XCP 2041 or a later version, and then set the value of the OpenBoot PROM environment variable again. |
| RTI No. | RTIF2-130410-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The power may not be turned on/off from the operation panel. |
| Workaround | If you power on from the XSCF shell, execute the poweron(8) command. If you power off from the XSCF shell, execute the poweroff(8) command. [How to restore] If this event occurs, power off the physical partition (PPAR) by using the poweroff -f command. |
| RTI No. | RTIF2-130410-005 |
| Model | SPARC M10-4S |
| Description | Executing the poweron -a command leads to the failure of power-on if more than one PPAR is powered on or more than one PPAR has failed in the system that has multiple physical partitions (PPARs). |
| Workaround | Specify the -p option to execute the poweron(8) command and turn on the power of each PPAR. [How to restore] If this event occurs, execute the poweroff -f command to forcefully power off the PPAR whose power has stopped being supplied during the middle of the power supply process. Then execute the poweron -p command to power on the PPAR. |
| RTI No. | RTIF2-130410-006 |
| Model | SPARC M10-4S |
| Description | If a crossbar box has failed in the system that satisfies all the following conditions, a crossbar box may be degraded and the operation may not be continued. - Two or more crossbar boxes are configured. - Multiple PPARs are configured. - Each physical partition (PPAR) is configured with multiple CPU memory units (CMUU/CMUL). |
| Workaround | There is no effective workaround. [How to restore] Execute the poweron -p command to power on the PPAR again whose power has been turned off due to an error in the crossbar box. |
| RTI No. | RTIF2-130410-007 |
| Model | SPARC M10-4S |
| Description | If you forcefully turn off the power of the physical partition using the poweroff -f command immediately after you powered on the physical partition, you may not be able to power on/off the physical partition after that. |
| Workaround | After powering on a PPAR, do not execute the poweroff -f command until the ok prompt is displayed. [How to restore] If you fail to forcefully turn off the power of a PPAR, power off the input power supply and then turn on the power again (AC OFF/ON). |
| RTI No. | RTIF2-130329-001 |
| Model | SPARC M10-4S |
| Description | During firmware updating in SPARC M10-4S, ALARM LED of the master chassis suddenly turns on and remains stopped, and the firmware updating may not complete. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-130329-002 |
| Model | SPARC M10-4S |
| Description | If the configuration has two or more crossbar boxes and the physical partition (PPAR) is configured not to use any crossbar box, you cannot disconnect the power supply from the operating panel. |
| Workaround | Disconnect the power by using the poweroff(8) command. |
| RTI No. | RTIF2-130329-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you power off the input power supply while the status of the physical partition (PPAR) is PowerOn (from the startup of Oracle Solaris to the completion of PowerOff), an SRAM serious error occurs in any of the SPARC M10-4S units in the PPAR when you next power on the input power supply, preventing you from powering on the input power supply. |
| Workaround | When you power off the input power supply, do so after disconnecting the PPAR power supply in advance and making sure that disconnection is complete. [How to restore] If any problem occurs, restore the configuration with the following procedure: 1. Save settings with the dumpconfig(8) command. 2. Initialize the system to the factory default with the restoredefaults -c factory command. 3. Confirm that the READY LED of the XSCF or XSCF unit is lit after performing AC OFF/ON. 4. Replace the CPU memory unit lower (CMUL) or the motherboard unit (MBU). 5. Execute the restoreconfig(8) command to restore the XSCF setting information. |
| RTI No. | RTIF2-130319-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | Immediately after the input power of the SPARC M10-4/M10-4S is turned on, "DMA timeout error Hard detected" may be detected. The CPU memory unit lower (CMUL) will be degraded if you start the logical domain with "DMA timeout error Hard detected" detected. |
| Workaround | There is no effective workaround. Before starting the logical domain, disconnect the input power supply and then power it on again. |
| RTI No. | RTIF2-130305-005 |
| Model | SPARC M10-4S |
| Description | In a system consisting of multiple SPARC M10-4S chassis, suppose an XSCF panic occurs on a SPARC M10-4S during diagnosis processing with the POST after physical partition (PPAR) power-on. Then, without continuing the power-on process, the PPAR may be powered off. |
| Workaround | There is no effective workaround. Make sure that the XSCF of each SPARC M10-4S is rebooted. Power on the PPAR again if they are rebooted. |
| RTI No. | RTIF2-130305-008 |
| Model | SPARC M10-4S |
| Description | If each physical partition (PPAR) is configured with one system board (PSB) in the system that has more than one SPARC M10-4S chassis and crossbar box, the power of the crossbar unit of a crossbar box is not stopped and the crossbar box is also powered on. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-130305-010 |
| Model | SPARC M10-4S |
| Description | Hypervisor Abort or OS PANIC may occur if all the PPARs are powered on using the poweron -a command in a system that has four or more SPARC M10-4S chassis units with multiple physical partitions (PPARs). |
| Workaround | Do not power on all the PPARs at the same time using the poweron -a command. Power on each PPAR using the -p option. |
| RTI No. | RTIF2-130305-021 |
| Model | SPARC M10-4S |
| Description | Immediately after starting the XSCF, the system board (PSB) may be recognized as "Unmount" and the addboard(8) command or the poweron(8) command may fail. |
| Workaround | Wait about 30 seconds after starting up the XSCF and check that the target PSB is mounted using the showboards(8) command. Then, execute the addboard(8) or poweron(8) command. |
| RTI No. | RTIF2-130305-024 |
| Model | SPARC M10-4S |
| Description | If you cycle the input power to a crossbar box in the state where a physical partition (PPAR) is powered on in the system that has the crossbar box, the following message may be output on the control domain console, and the power-on process of the PPAR may not be completed. WARNING: Unable to connect to Domain Service providers |
| Workaround | There is no effective workaround. [How to restore] If the power-on process of the PPAR is canceled, disconnect the power of the PPAR forcefully using the poweroff -f command. After that, reset all the XSCFs using the rebootxscf -a command or disconnect the input power supply of all the SPARC M10-4S chassis and then power on again. |
| RTI No. | RTIF2-130227-001 |
| Model | SPARC M10-4S |
| Description | If you collect a snapshot by specifying the -a option, "XSCF Kernel Panic" may occur due to the increased load on the master XSCF. |
| Workaround | If you collect a snapshot of the entire system, collect snapshots one by one by specifying a BB-ID of the SPARC M10-4S in the -b option and not the -a option. Perform this operation on all SPARC M10-4S. |
| RTI No. | RTIF2-130219-001 |
| Model | SPARC M10-4S |
| Description | The takeover IP address of an XSCF cannot be specified as a value for "IPAddress" or "SlaveAddress," which can be set in the management file for a remote power management group. |
| Workaround | Specify the IP addresses of XSCF-LAN#0 and XSCF-LAN#1 of the master XSCF and the standby XSCF for "IPAddress" and "SlaveAddress," respectively. |
| RTI No. | RTIF2-130219-005 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | If a failure occurs in a component in a physical partition (PPAR), the status of the PPAR in the SNMP MIB is not updated. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-130219-008 |
| Model | SPARC M10-4S |
| Description | If you turn on the input power supply to a SPARC M10-4S chassis while a physical partition (PPAR) is being powered on in a system that has multiple PPARs, the SPARC M10-4S chassis for which the input power supply is turned on may not be recognized by the master XSCF. |
| Workaround | Power on the input power supply to all the crossbar boxes and SPARC M10-4S chassis that compose the system before powering on a PPAR. |
| RTI No. | RTIF2-130215-001 |
| Model | SPARC M10-4S |
| Description | After the hardware initial diagnosis detects a system board (PSB) error as described in the following error log, the PSB may not be degraded but the physical partition (PPAR) may be reset repeatedly. Code: 40002000-003cff0000ff0000ff-02000e000000000000000000 FRU: /BB#x Msg: SB deconfigured (SB-SB access error) Code: 40002000-003cff0000ff0000ff-02000e010000000000000000 FRU: /BB#x Msg: SB deconfigured (not running) |
| Workaround | Disconnect the PSB where an error is detected from the PPAR configuration by using the deleteboard(8) command. |
| RTI No. | RTIF2-130215-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Even when policy is set to psb by the setpcl(8) command, a unit of resource to be degraded when an error occurs may not be a system board but Field Replaceable Unit (FRU). |
| Workaround | Disconnect the PSB where an error is detected from the PPAR configuration by using the deleteboard(8) command. |
| RTI No. | RTIF2-130212-001 |
| Model | SPARC M10-4S |
| Description | If the power save operation, which is set by the setpparmode(8) command, is "enabled," the following problems may occur. - A hang (heartbeat function) in a logical domain may be unable to be detected. - If the CPU core resources are reduced during system startup (while a physical partition (PPAR) is operating), the PPAR may be powered off. |
| Workaround | Set the power save operation to "disabled" by using the setpparmode(8) command. |
| RTI No. | RTIF2-130212-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When you check the domain status by using the showdomainstatus(8) command from the XSCF after executing the ldm add-spconfig command from Oracle Solaris, "Host stopped" is displayed for all domains, including the control domain. |
| Workaround | There is no effective workaround. Execute the ldm list-domain command from Oracle Solaris to check the domain status. |
| RTI No. | RTIF2-130212-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you execute the testsb(8) command to a system board (PSB) that is being diagnosed by the testsb(8) or diagxbu(8) command in a different session, the PSB that is being diagnosed may enter an abnormal state and become unavailable. |
| Workaround | Confirm that the PWR of the PSB to be diagnosed is "n" and that Test is not "Testing" by using the showboards(8) command before executing the testsb(8) command. If a PSB becomes unavailable, power off the entire system and then power it on again. |
| RTI No. | RTIF2-130130-001 |
| Model | SPARC M10-4, SPARC M10-4S |
| Description | If you turn on the AC when the system configuration has no CPU memory unit upper (CMUU), a "Hardware access error" error log is generated for CMUU. The same phenomenon occurs when you add or replace SPARC M10-4S. |
| Workaround | The error log is registered because no CMUU is mounted. So, ignore it. |
| RTI No. | RTIF2-130109-002 |
| Model | SPARC M10-4S |
| Description | If "Console path is switched" is registered in the event log of a system in which the physical partition (PPAR) consists of multiple system boards (PSBs), the PPAR-ID may have an invalid value. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-130109-005 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you use the replacefru(8) command to replace a power supply unit (PSU), "Indispensable parts are not installed (PSU)" may be registered in the event log. |
| Workaround | This is an error log that is registered because a PSU is removed. Ignore it. |
| RTI No. | RTIF2-130109-006 |
| Model | SPARC M10-4S |
| Description | If you change the setting information of the remote power management function while the standby XSCF is in failure or starting, the changed setting information may not be reflected in the standby XSCF even after the start of the standby XSCF is completed. If XSCF switching occurs in this state, the master XSCF after the switching may not be able to achieve remote power management based on the changed setting information. |
| Workaround | Disable the remote power management function, and then configure it again using the following procedure: 1. Execute the setremotepwrmgmt -c disable command to disable the remote power management function. 2. Save the management file, and then use the clearremotepwrmgmt(8) command to initialize the setting information. - If the standby XSCF is starting, execute the clearremotepwrmgmt(8) command after the start is completed. - If the standby XSCF is in failure, use the replacefru(8) command to replace the target FRU, and then execute the clearremotepwrmgmt(8) command. 3. After the start of the standby XSCF is completed, execute the setremotepwrmgmt -c config command to restore the setting information based on the saved management file. 4. Execute the setremotepwrmgmt -c enable command to enable the remote power management function. |
| RTI No. | RTIF2-130109-007 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If all physical partitions (PPARs) are stopped and you try to power on a PPAR, the PPAR may not be powered on without being registered in the error log. |
| Workaround | There is no effective workaround. Turn off the input power supply and turn it back on to all SPARC M10 system chassis and then try to power on the PPAR again. |
| RTI No. | RTIF2-121219-002 |
| Model | SPARC M10-4S |
| Description | Some chassis may not be recognized if all power cables are not connected within four minutes when connecting the power cables of the system that is composed of multiple SPARC M10-4S chassis. |
| Workaround | Make sure not to exceed four minutes to finish connecting all the power cables when the system is composed of multiple SPARC M10-4S chassis. Remove and connect the power cables of all the chassis again when there is a SPARC M10-4S chassis that is not recognized. |
| RTI No. | RTIF2-121219-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | While powering on/off the remote power management group, the showremotepwrmgmt(8) command may be abnormally terminated with the following message. Controller response timeout. |
| Workaround | Execute the showremotepwrmgmt(8) command again. |
| RTI No. | RTIF2-121219-005 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When a component with high temperature or low temperature at an air inlet is registered, the information on the second faulty component (the second suspect component) displayed in the FRU may not be correct. |
| Workaround | Ignore the information on the displayed second faulty component (the second suspect component). |
| RTI No. | RTIF2-121219-006 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | Replacement of the power supply unit (PSU) using the replacefru(8) command may fail with "Warning:005". |
| Workaround | Execute the replacefru(8) command again and replace the PSU. |
| RTI No. | RTIF2-121219-009 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If an error log indicating a fan failure, "Power-on failure" or "Power-off failure", is registered, other than the correct component may be displayed as the faulty FRU. |
| Workaround | If the failure is "Power-on failure" or "Power-off failure", and the faulty component is a fan, replace the following component. - For the SPARC M10-1 Motherboard unit (MBU) - For the SPARC M10-4/M10-4S PSU backplane unit |
| RTI No. | RTIF2-121219-010 |
| Model | SPARC M10-4S |
| Description | Error log "XSCF hang-up is detected" may be registered when the switchscf(8) command is executed. |
| Workaround | Ignore this error log entry. |
| RTI No. | RTIF2-121219-012 |
| Model | SPARC M10-4S |
| Description | When a SPARC M10-4S chassis is replaced using the replacefru(8) command, replacement of the SPARC M10-4S chassis may fail with "internal error" displayed. |
| Workaround | Use the following procedure to replace a SPARC M10-4S chassis by using the replacefru(8) command. 1. Enter "r" to replace the chassis in response to the message "Do you want to continue?[r:replace|c:cancel]" which is displayed after the replacefru(8) command is executed. 2. Replace the SPARC M10-4S chassis, and wait about 15 minutes after the input power of the chassis is turned on. 3. Execute the showlogs event command to display an event log. 4. Continue the replacement using either of the following methods. - If the event log displays "XSCF update is started" Wait until the "XCP update has been completed" log is registered. When "XCP update has been completed" is displayed, enter "f" in response to "Please select[f:finish]" and then continue the replacement by following the instructions displayed on the screen. - If the event log does not display "XSCF update is started" Enter "f" in response to "Please select[f:finish]" and then continue the replacement according to the instructions on the screen. |
| RTI No. | RTIF2-121219-013 |
| Model | SPARC M10-4S |
| Description | When a SPARC M10-4S chassis finds an error indicating that the XSCF cannot be started, not only an error log for the SPARC M10-4S chassis where the error occurred but also an error log regarding a cable connection error in a chassis that does not exist may be registered. |
| Workaround | Ignore the error log regarding a cable connection error registered for a SPARC M10-4S chassis that does not exist. |
| RTI No. | RTIF2-121219-014 |
| Model | SPARC M10-4S |
| Description | When cold replacement is performed (replacement performed while the input power is off) due to an error with BB#00, the setting information for the XSCF is deleted. |
| Workaround | To replace a SPARC M10-4S chassis due to an error in BB#00, use the replacefru(8) command. |
| RTI No. | RTIF2-121219-015 |
| Model | SPARC M10-4S |
| Description | When a SPARC M10-4S chassis is removed with the initbb(8) command, the information on the removed chassis remains without being completely deleted. |
| Workaround | To remove a SPARC M10-4S chassis, perform the cold removal (the chassis is removed by turning off the input power). |
| RTI No. | RTIF2-121219-016 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | An "internal error" may occur if the prtfru(8) command is executed while powering on/off or resetting the physical partition (PPAR). |
| Workaround | Wait for the power on/off or reset of the PPAR to complete and then execute the prtfru(8) command again. |
| RTI No. | RTIF2-121219-017 |
| Model | SPARC M10-4S |
| Description | If a SPARC M10-4S chassis is powered off after an error log is registered because a memory error occurred in BB#00 or BB#01, the same error log may be registered again. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-121219-018 |
| Model | SPARC M10-4S |
| Description | In a system in which two or more SPARC M10-4S chassis units constitute multiple physical partitions (PPARs), if you power on the PPAR after switching the master XSCF as a result of any of the following, error logs of "STICK does not start (CPU)", "STICK does not start (MBC)", or "STICK count up error" may be registered, causing degradation of the CPU memory units (CMUU/CMUL). - Performing firmware update - Detecting an XSCF failure - Executing the switchscf(8) command |
| Workaround | There is no effective workaround. After switching of the master XSCF is performed, power off the input power supply of all SPARC M10-4S chassis and power them on again, without powering on the PPAR. |
| RTI No. | RTIF2-121219-019 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When a PCI card is inserted to or removed from a PCI expansion unit, a number that is different from the relevant PCI card number (PCI#) is displayed in the log. In addition, when error log "PCICARD failed" is registered due to an error with the PCIe slot on the PCI expansion unit or the PCI card, a number other than that of the relevant PCI card number (PCI#) is displayed in the error log. |
| Workaround | Read it as the number obtained by subtracting one from the PCI number (PCI#) displayed in the log. |
| RTI No. | RTIF2-121206-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When starting the domain, the following error message may appear. Msg: PCI Express link not active |
| Workaround | Ignore this message if the showhardconf(8) command recognizes the PCI Express (PCIe) card. |
| RTI No. | RTIF2-121204-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The dynamic resource management software (ServerView Resource Orchestrator) sometimes fails to register a server to be monitored. |
| Workaround | There is no effective workaround. Register the server to be monitored again by the dynamic resource management software. |
| RTI No. | RTIF2-121204-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If a node of PRIMECLUSTER stops, node switching does not occur automatically. |
| Workaround | There is no effective workaround. Switch nodes manually in PRIMECLUSTER. |
| RTI No. | RTIF2-121204-003 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When you set or change OpenBoot PROM environment variables by using setenv or nvramrc of OpenBoot PROM, or by using the eeprom or ldm set-var command of Oracle Solaris, the setting or change may not be retained after power cycling of the system. |
| Workaround | After you update an OpenBoot PROM environment variable, execute the ldm add-config command to save the domain configuration information to the XSCF. |
| RTI No. | RTIF2-121204-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When you enable the auto boot function of the guest domain by using the setpparmode(8) command of the XSCF and then start the control domain and the guest domain simultaneously, you may encounter the situation where the following error message is recorded and Oracle Solaris cannot be started in the guest domain. Code: 20000000-00ffff0000ff0000ff-030000020000000000000000 Status: Notice Occurred: Nov 16 16:55:25.518 JST 2012 FRU: /UNSPECIFIED Msg: Boot process failed |
| Workaround | Use the XSCF setpparmode(8) to disable the autoboot function of the guest domain, and then start Oracle Solaris of the control domain. Then use the ldm start-domain command for Oracle VM Server for SPARC to start the guest domain. [How to restore] After stopping the guest domain with the ldm stop-domain command for Oracle VM Server for SPARC, execute the ldm start-domain command to start the guest domain. |
| RTI No. | RTIF2-121130-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If remote power management using RCIL is enabled and disabled, and then enabled again, remote power management of the ETERNUS DX80/DX90/DX410/DX440/DX8100/DX8700 S2 may not work. |
| Workaround | When you enable and disable remote power management using RCIL, reboot the XSCF. |
| RTI No. | RTIF2-121129-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | During operation of the XSCF firmware, a "system backup memory access error", which is an error in the PSU backplane (PSUBP), may be erroneously detected and registered in the error log. If this erroneous detection occurs during the start process of the physical partition (PPAR), the start of the PPAR may fail. Also, if it occurs during the collection of log information, the log information collection fails. In addition, a failure mark may be displayed on the PSUBP when the error is detected. If the failure mark is displayed on the PSUBP, the resources necessary for starting the PPAR are insufficient. Therefore, when start of the PPAR is requested, a log indicating that the start of the PPAR failed is registered in the power log. You can display the power log with the showlogs power command. |
| Workaround | If you find a log described in "Description," execute the showstatus(8) or showhardconf(8) command to check whether the failure mark is displayed on the PSUBP. - When the failure mark is not displayed on the PSUBP: No problem has occurred in the hardware. So, ignore the error log and continue the operation. - When the failure mark is displayed on the PSUBP: Clear the failure mark by using the following procedure. 1. Switch the mode switch on the operation panel to the Service mode position. 2. Power off and then on again the target SPARC M10 system chassis, and then reboot the XSCF. For the SPARC M10-4S, turn the power to every SPARC M10-4S chassis off and then on again. 3. After the XSCF has been rebooted, return the mode switch on the operation panel to its original position. If the same error recurs even after rebooting the XSCF, there is a possibility that the error has not been erroneously detected but that a PSUBP hardware failure has occurred. Ask your Fujitsu field engineer (service provider) to replace the PSUBP. |
| RTI No. | RTIF2-121129-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When you replace the CPU memory unit lower (CMUL) or motherboard unit (MBU), the XSCF user account information may be deleted. To recover the XSCF user account information, you need to use the restoreconfig(8) command to restore the information saved using the dumpconfig(8) command. |
| Workaround | After you have conducted the replacement, use the restoreconfig(8) command to restore the information saved using the dumpconfig(8) command, or set the XSCF user account information again. |
| RTI No. | RTIF2-121129-004 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The restoredefaults(8) cannot initialize the following information. The setting information remains as it is. - Time zone of the XSCF - Server certificate for HTTPS |
| Workaround | There is no effective workaround. Reset data with the settimezone(8), sethttps(8), and setssh(8) commands. |
| RTI No. | RTIF2-121113-001 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | After setting an invalid value for the user name with the setsmtp(8) command, you execute the setemailreport(8) command to send a test mail. Then the reply address shows that the mail has been successfully sent. |
| Workaround | There is no effective workaround. Even if it is displayed that the test mail has been successfully sent, it is not sent. |
| RTI No. | RTIF2-121113-002 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you execute the setaudit delete command and use the viewaudit(8) to display the audit log, some audit logs may not be deleted. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-121113-006 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you display the XSCF Web screen in another window or in another tab without using the XSCF Web menu, contents may not be normally displayed. |
| Workaround | For operation to display the XSCF Web screen, use the menu tree. |
| RTI No. | RTIF2-121113-007 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | While the XSCF is starting, a "process down," panic, or watchdog timeout occurs, which may cause the XSCF to be reset. |
| Workaround | Confirm that the XSCF is successfully started. If it is not started, turn off the power of the physical partition (PPAR), and then disconnect the input power supply to the system and back on again (AC OFF/ON). When turning off/on the input power, power off the system, wait at least 30 seconds, and then power on the system. If the XSCF does not start even after the system input power is cycled, replace the CPU memory unit lower (CMUL) or the motherboard unit (MBU). |
| RTI No. | RTIF2-121113-009 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | While the XSCF is running, a "process down," panic, or watchdog timeout occurs, which may cause the XSCF not to be rebooted after an XSCF reset. |
| Workaround | Confirm that the XSCF is successfully started. If it is not started, turn off the power of the physical partition (PPAR), and then disconnect the input power supply to the system and back on again (AC OFF/ON). When turning off/on the input power, power off the system, wait at least 30 seconds, and then power on the system. If the XSCF does not start even after the system input power is cycled, replace the CPU memory unit lower (CMUL) or the motherboard unit (MBU). |
| RTI No. | RTIF2-121113-011 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you execute the showsnmp(8) command, the following message may appear, which means that the snmp daemon has been terminated. Agent Status: Disabled |
| Workaround | Execute the showsnmp(8) command again to confirm that the snmp daemon is restarted. If "Agent Status: Disabled" remains displayed, execute the setsnmp enable command to restart the snmp daemon. |
| RTI No. | RTIF2-121113-014 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | The error message "/etc/redhat-release not found" appears while the XSCF is starting. |
| Workaround | Ignore this message. |
| RTI No. | RTIF2-121113-018 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When you replace a FRU with the replacefru(8) command, the message "configuration changed (...)" showing the configuration change may be registered more than once in the event log. |
| Workaround | Ignore the message that appears second time and later. |
| RTI No. | RTIF2-121113-019 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When the power supply of the physical partition (PPAR) is disconnected according to the power supply schedule, "-" may be displayed as the cause (Cause) in the power log. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-121113-021 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If time cannot be read accurately due to a failed clock in the XSCF board, an error showing a clock failure may not be recorded in the error log. |
| Workaround | There is no effective workaround. If the following message appears when you execute the poweron(8) command, the clock in the XSCF board has failed. Replace the XSCF board. Poweron canceled due to invalid system date and time. |
| RTI No. | RTIF2-121113-022 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If the operation panel has failed or is not connected, the XSCF cannot be started. |
| Workaround | Connect the operation panel. If the operation panel has failed, replace it. |
| RTI No. | RTIF2-121113-023 RTIF2-121113-028 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If a CPU failure occurs while Hypervisor is running, the physical partition (PPAR) is reset more than once, and restarting of the PPAR may take time. |
| Workaround | There is no effective workaround. |
| RTI No. | RTIF2-121113-025 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | When a CPU failure occurs, an error message showing degradation or offline on Oracle Solaris may not be output to Syslog. |
| Workaround | Use the showlogs(8) command to check a failure state on the XSCF. |
| RTI No. | RTIF2-121113-027 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | If you update the firmware and then upload XCP from XSCF Web without rebooting the XSCF, uploading of XCP will fail and the XSCF Web session will time out. |
| Workaround | If you update the firmware and then continue to upload XCP with XSCF Web, reboot the XSCF. |
| RTI No. | RTIF2-121113-031 |
| Model | SPARC M10-1, SPARC M10-4, SPARC M10-4S |
| Description | After creating an I/O domain to which the PCI card is assigned with Oracle VM Server for SPARC, turn on the power of the I/O domain. If you then stop it at the ok prompt, the configuration information of the PCI card may not be displayed with the showhardconf(8) command of the XSCF. |
| Workaround | Start Oracle Solaris of the logical domain to which the PCI card is assigned with Oracle VM Server for SPARC. |
< Previous Page | Next Page >