Skip to main content

Contents

  1. Preface
  2. Chapter 1 Software Requirements
    1. Click XCP/Oracle Solaris and Required SRUs/Patches
    2.  How to Obtain XCP and Oracle Solaris SRUs/Patches/Oracle VM Server for SPARC
    3.  Web Browser
    4.  Software Supporting Remote Storage
    5.  Obtaining the SAS-2 Integrated RAID Configuration Utility
    6.  Existing XCP Firmware Versions and Support Information
  3. Chapter 2 XCP 2430-Related Information
    1.  Latest Information on XCP 2430
    2. Click Notes and Restrictions
    3.  XCP 2430 Problems and Workarounds
  4. Chapter 3 Information on Software
    1. Click Notes and Restrictions
    2. Click Problems With XCP and Workarounds
    3. Click Problems With Oracle Solaris and Workarounds
  5. Chapter 4 Information on SPARC M10-1 Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  6. Chapter 5 Information on SPARC M10-4 Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  7. Chapter 6 Information on SPARC M10-4S Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  8. Chapter 7 Information on the PCI Expansion Unit
    1.  PCI Expansion Unit Firmware Versions and Support Information
    2. Click Direct I/O Function for the PCI Expansion Unit
    3. Click Problems With the PCI Expansion Unit and Workarounds
  9. Chapter 8 Information on SPARC M10 Manuals

Problems Resolved in XCP 2332


Problems Resolved in XCP 2332
The following table lists the problems resolved in XCP 2332.
Table 3-23  Problems Resolved in XCP 2332
RTI No. RTIF2-170130-001
Model SPARC M10-1, SPARC M10-4, SPARC M10-4S
Description Even though the ldm add-spconfig command has been executed to save logical domain configuration information, the following may not be properly displayed during a live migration of a logical domain:
- The state of the moved logical domain to be displayed by the XSCF showdomainstatus command

- The state of the logical domain of scfDomainStatus in the XSCF extended MIB definition file


At this time, in an environment that uses the cluster software, the software tries to switch clusters if the interconnect of all the clusters fails. In that case, there may be double startup of a user application, and as a result, data inconsistency may occur.
[Example] After guest01 is moved from another SPARC M10 to the local SPARC M10 through live migration, the showdomainstatus command should display the Status of guest01 as Solaris running. However, it actually displays it as Host stopped.

XSCF> showdomainstatus -p 0 -y
Logical Domain Name Status
primary Solaris running
guest00 Solaris running
guest01 Host stopped

# ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -t-cv 4 1G 0.5% 3d 21h 7m
guest00 active -t--- 5000 8 1G 23% 10h
guest01 active -t--- 5001 8 1G 23% 20h
Workaround Before moving a guest domain from another SPARC M10 to the local SPARC M10 through live migration, reboot all the XSCFs connected to the local SPARC M10 by using the rebootxscf -a command.
The XSCFs must be rebooted every time a PPAR is powered off and on.
Reboot the XSCFs after powering off the PPAR but before performing a live migration.
If you turn the input power off and on when powering off and on the PPAR, you do not need to execute the rebootxscf -a command.
[How to restore]
After rebooting all the XSCFs connected to the SPARC M10 by using the rebootxscf -a command, perform a live migration to move the guest domain whose state is not displayed properly, or restart the guest domain.

Top of Page