Skip to main content

Problems Resolved in XCP 2050


Problems Resolved in XCP 2050
The following table lists the problems resolved in XCP 2050.
Table 3-46  Problems Resolved in XCP 2050
RTI No. RTIF2-210209-007
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the XSCF reboots while Oracle Solaris is running, you may be unable to connect to the control domain console by executing the console command after the XSCF reboot.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-023
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description A logical domain might panic with BAD TRAP due to a logical domain channel (LDC) under heavy load.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-024
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description A logical domain might panic when the ldm remove-memory command is executed dynamically for it.
Workaround There is no effective workaround.
RTI No. RTIF2-201109-026
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Hypervisor might abort if the console paths change while the PPAR is starting up.
Workaround There is no effective workaround.
RTI No. RTIF2-131107-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the input power to the system is turned on, the XSCF is reset, or the XCP firmware is updated, the "SCF Diagnosis initialize RTC" error is erroneously detected, causing the following phenomena to occur.
- Symptom 1

The XSCF time may return to January 1, 1970.
- Symptom 2

The time difference between the XSCF and all physical partitions (PPARs) may become a value of 1.3 billion seconds or more. You can check this phenomenon by executing the showdateoffset(8) command, since the time difference between the XSCF and all the PPARs is displayed as a value of "1300000000 sec" or more.
XSCF> showdateoffset -a
PPAR-ID       Domain Date Offset 
00            1300000100 sec
01            1300000100 sec
 :
 :
15            1300000100 sec
- Symptom 3

When you reset the PPAR or power cycle the PPAR, the Oracle Solaris time may return to January 1, 1970.
Workaround There is no effective workaround.
Update to firmware version XCP 2050 or later.
[How to restore]
See "Restoration After Erroneous Detection of the "SCF Diagnosis initialize RTC" Error (RTIF2-131107-002)."
RTI No. RTIF2-131023-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the [Physical] bar is selected on the XSCF Web menu, PCI (excluding the link card) may appear to be abnormal (MMB_Warning).
Workaround There is no effective workaround.
Even if PCI (excluding the link card) is indicated as being abnormal (MMB_Warning), ignore it.
RTI No. RTIF2-130903-005
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description In the XSCF e-mail notification function, the following characters cannot be included in the local part or the domain part of the reply mail address which is sent by the setsmtp(8) command.
"!" "#" "$" "%" "&" "'" "*" "+" "/" "=" "?" "^" "_" "`" "{" "|" "}" "~"
Workaround Use reply mail addresses which do not include the characters shown by the description.
RTI No. RTIF2-130528-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description You cannot use the PCI hot plug (PHP) function to add a Quad Gigabit Ethernet card (SE1X7GQ2F) to a PCI Express slot of a PCI expansion unit.
Workaround This has been modified with XCP 2050 and SRU 11.1.6.4.0.

If XCP and SRU are not applied, you must stop the logical domain to which you want to add the PCI card before adding it.
[Precautions]
To resolve this problem when you have saved the configuration information of the logical domain and are operating the system with a configuration other than factory-default, you must reconstruct the logical domain configuration after update of the XCP firmware. For details, see "Reconstructing the Logical Domain (RTIF2-130528-001)."
RTI No. RTIF2-130516-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the XSCF load is high, the following warning message may be output, indicating the power supply unit (PSU) as a suspected location.
Insufficient FAN rotation speed
PSU voltage out of range error
PSU output current too high
PSU over temperature warning
Workaround There is no workaround.
This is a warning message, so you can operate it as it is. Ignore the message.
RTI No. RTIF2-130329-004
Model SPARC M10-4S
Description In a system with building block configuration, if the following operations are performed during power-on of the physical partition (PPAR), connection to the control domain console may not be possible.
1. The XSCF for any of the SPARC M10-4S units composing the PPAR is reset.

2. The master XSCF and standby XSCF are switched.

3. The XSCF of the SPARC M10-4S that was reset in 1. is reset again.
Workaround There is no effective workaround. 
Reset the master XSCF using the switchscf(8) command.
RTI No. RTIF2-130329-006
Model SPARC M10-4S
Description If the XSCF of the SPARC M10-4S belonging to the physical partition (PPAR) in operation is rebooted due to a panic or watchdog timeout while the master XSCF and the standby XSCF are restarting simultaneously, connection to the control domain console may not be possible. 
Workaround There is no effective workaround. 
Power off the PPAR by using the poweroff -f command, and then power it on again.
RTI No. RTIF2-130319-002
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Before power-off of the physical partition (PPAR) completes in a SPARC M10-4S, suppose you cycle the input power to the SPARC M10-4S or a crossbar box and power on the PPAR again. Then, the PPAR in operation may be powered off if the master XSCF is switched with the switchscf(8) command, firmware update, or failure.
Workaround If you power off the PPAR before powering off the input power supply of the SPARC M10-4S or crossbar box, check that power-off of the target PPAR and SPARC M10-4S is complete, by using the showboards(8) and showlogs power commands. Then, power off the input power supply of the SPARC M10-4S or crossbar box.
RTI No. RTIF2-130319-003
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description If the shutdown -i5 command and power-off command compete for power-off of the PPAR when the former is executed in the control domain or the latter is executed from the ok prompt while power-off of the physical partition (PPAR) is performed with the poweroff(8) command, "SCF:PPAR issued power-off request (PPARID X)" may be registered many times.
Workaround Ignore the registered event log, because the PPAR has been normally powered off.
RTI No. RTIF2-130305-016
Model SPARC M10-4S
Description Timeout may occur if the XCP firmware version of a SPARC M10-4S or crossbar box is updated using the flashupdate -c sync command.
Workaround Execute the flashupdate(8) command by specifying the -f option to re-update the XCP firmware for all SPARC M10-4S or crossbar boxes.
RTI No. RTIF2-130219-002
Model SPARC M10-4S
Description When maintaining SPARC M10-4S with a slave XSCF, if you incorrectly connect the standby XSCF and the slave XSCF with an XSCF connection cable, the maintenance is considered to have finished normally without detecting the error.
Workaround After switching between the master XSCF and the standby XSCF by using the switchscf(8) command, execute the testsb(8) command to the target slave XSCF. The incorrect connection with the XSCF connection cable is detected and an error log is issued.
Reconstructing the Logical Domain (RTIF2-130528-001)
To resolve this problem when you have saved the configuration information of the logical domain and are operating the system with a configuration other than factory-default, you must reconstruct the logical domain configuration after update of the XCP firmware through the following procedure:
  1. Check the current configuration information of the logical domain stored on the XSCF.
    This example assumes that the name of the saved logical domain configuration information is config1.
XSCF> showdomainconfig -p 0
20xx-yy-zz hh:mm:ss
PPAR-ID     :0
Booting config
(Current)  :config1
(Next)     :config1
--------------------------------------------------------------

Index       :1
config_name :factory-default
domains     :1
date_created:-
--------------------------------------------------------------

Index       :2
config_name :config1
domains     :2
date_created:'20xx-yy-zz hh:mm:ss'
  1. Set a dummy variable and then clear it for all logical domains.
    Execute the following commands for all logical domains.
primary# ldm set-variable fix-php=true ldom
primary# ldm remove-variable fix-php ldom
  1. Save the changed configuration to the XSCF to replace the current configuration information.
    In this example, the name of the current configuration information is replaced with config1.
primary# ldm remove-spconfig config1
primary# ldm add-spconfig config1
  1. Restart all logical domains.
Restoration After Erroneous Detection of the "SCF Diagnosis initialize RTC" Error (RTIF2-131107-002)
[How to restore]
  1. If phenomenon 1 occurs:
    - Case 1

    If the Oracle Solaris time has returned to January 1, 1970, execute the setdate(8) command to set the XSCF time again. In this case, the XSCF is rebooted. After that, power cycle the PPAR. After this, the XSCF is reset. After that, power on the PPAR.

    - Case 2

    If the Oracle Solaris time is other than January 1, 1970, contact a field engineer. In this case, do not execute the resetdateoffset(8) of setdate(8) command on the XSCF.

    - Case 3

    If the PPAR power is off, power on the PPAR. After that, check the Oracle Solaris time, and perform the above case 1 or case 2.
  2. If phenomenon 2 occurs:
    - Case 1

    If the Oracle Solaris time has returned to January 1, 1970, it is necessary to initialize the time difference between the XSCF time and Hypervisor on all of the PPARs. Stop all the PPARs, and execute the resetdateoffset -a command to clear the time difference.

    - Case 2

    If the Oracle Solaris time is other than January 1, 1970, contact a field engineer. In this case, do not execute the resetdateoffset(8) of setdate(8) command on the XSCF.

    - Case 3

    If the PPAR power is off, power on the PPAR. After that, check the Oracle Solaris time, and perform the above case 1 or case 2.
  3. If phenomenon 3 occurs:
    If phenomenon 1 or 2 also occurs, perform its [How to restore] action first.
    Set the Oracle Solaris time again.