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

Other Notes and Restrictions


Other Notes and Restrictions
Notes
  1. It may take a while for the service domain to start the virtual disk server (vds) or virtual switch (vsw). For this reason, at the time of guest domain boot, the wait time from the virtual disk/virtual network to vds or vsw is set as follows.
    - XCP 2221 or earlier: Maximum of 5 minutes

    - XCP 2230 or later: Maximum of 15 minutes

    If this wait time is exceeded, boot from the virtual disk/virtual network may fail.
    For example, with XCP 2230 or later, suppose multiple disks are configured for the OpenBoot PROM environment variable boot-device. Under this condition, it may take up to 15 minutes to switch the boot path from the virtual disk to the next disk, or the boot may fail if it takes more than 15 minutes.
  2. When the mode switch on the operation panel is set to Service mode, the power cannot be turned on by using the power switch on the operation panel. To turn on the power using the power switch on the operation panel, set the mode switch on the operation panel to the Locked mode position.
  3. To add the 64 GB memory, apply XCP 2090 or later.
  4. The maximum number of users who can concurrently connect to the XSCF via Telnet and SSH is as follows:
    - SPARC M10-1: 20 users

    - SPARC M10-4: 40 users

    - SPARC M10-4S (without crossbar box): 40 users

    - SPARC M10-4S (with crossbar box): 70 users

    If the maximum allowable number of users is exceeded, access is denied.
  5. XSCF-LAN is compliant with auto-negotiation. If you connect XSCF-LAN to a network device that is fixed to full-duplex mode, the XSCF-LAN communicates in half-duplex mode according to the IEEE 802.3 protocol. This may slow down the speed of network communication or cause communication error. Be sure to set auto-negotiation for network devices to which you connect XSCF-LAN.
  6. Configuring a memory mirror setting by using the setupfru(8) command should be done when the physical partition (PPAR) to which the target system board (PSB) belongs is powered off.
  7. To display a man page, set TERM=vt100 for the terminal software.
  8. When configuring a physical partition (PPAR), do not set a BB-ID that does not exist in the system as the PPAR-ID.
    For example, if BB-IDs 00 and 01 exist in the system, you can set 00 or 01 as the PPAR-ID. If you set 02 as the PPAR-ID, the PPAR with PPAR-ID 02 will not be able to start.
  9. Among the information displayed by executing the showhardconf(8) command, the PCI Express (PCIe) card information of the guest domain will be reflected after Oracle Solaris of the corresponding guest domain has started.
  10. As of XCP 2032, the default value for the power save operation set by the setpparmode(8) command is changed from "enabled" to "disabled."
  11. When you execute the testsb(8) or diagxbu(8) command, a PPAR-ID of "PPAR#30" that does not exist may appear in an error log suspected area. This indicates that an error was detected on the system board (PSB) while diagnosing. The output PPAR-ID does not have any meaning.
  12. When all the XSCFs in a physical partition (PPAR) are faulty, the control domain console function stops. This stoppage of the console function may affect the behavior of the syslogd daemon on the control domain. Therefore, if the XSCFs have failed when business application software that use system logs are operating on the control domain, the motherboard unit (MBU) or the CPU memory unit lower need to be replaced immediately.
  13. We recommend to connect the control domain console via the XSCF-LAN port.
    When a large amount of data is output by connecting to the control domain console via a serial port, the data may not be displayed properly.
  14. [SPARC M10-4S]
    The time taken for processing a command that displays the system configuration or status (such as the showhardconf(8) command, showboards(8) command, and showpparstatus(8) command) depends on the number of SPARC M10-4S chassis or crossbar boxes that compose the system.
  15. [SPARC M10-4S]
    For a system configured with multiple chassis, chassis BB#01 or XBBOX#81 may become the master XSCF first.
  16. [SPARC M10-4S]
    It may take more time to restart the physical partition when hardware fails, depending on the system configuration.
  17. If you add a SPARC M10-4S to the SPARC M10-4S on which XCP 2032 is installed, update to the latest firmware in advance.
  18. When you execute the setsnmpvacm(8) command with createview specified as the operand, you cannot set an access restriction using the OID mask of MIB. When you execute the setsnmpvacm(8) command with createview specified as the operand, do not use the OID mask of MIB.
  19. If a takeover IP address has been set, the UDP packet sender IP address and Agent Address for the SNMP Trap of SNMPv1 are different. The IP address assigned to each XSCF-LAN (physical IP address) is stored as the UDP packet sender IP address, while the takeover IP address (virtual IP address) is stored as the Agent Address.
  20. In the SPARC M10-4 or SPARC M10-4S with two CPUs installed, when I/O bus reconfiguration is enabled, the addition of a CPU memory unit upper (CMUU) to add two CPUs will change the device paths of the I/O devices used up until this time.
    Normally, disable the I/O bus reconfiguration function by leaving the default, false, specified for ioreconfigure. You can set ioreconfigure in the -m function option of the setpparmode(8) command.
    If you enable the I/O bus reconfiguration function by specifying true for ioreconfigure, it may be necessary to reinstall Oracle Solaris.
  21. With a logical domain running Oracle Solaris 11, updating to XCP 2050 or later allows you to have an increased maximum number of PCIe cards on one root complex (RC).
    To add a PCIe card after updating to XCP 2050 or later, perform the steps below in the control domain.
  1. This example assumes that two sets of configuration information currently in use, ldm-set1 and factory-default, are stored.
  1. 1. Confirm the logical domain configuration information saved to the XSCF.
primary# ldm list-spconfig
ldm-set1 [current]
factory-default
  1. 2. Execute the following commands on all of the logical domains, including the control domain.

    Specify the name of the logical domain for ldom.
primary# ldm set-variable fix_atu=true ldom
primary# ldm remove-variable fix_atu ldom
  1. 3. Save the updated configuration information for the logical domain again.

    Delete the stored ldm-set1 and then store the information again.
primary# ldm rm-spconfig ldm-set1
primary# ldm add-spconfig ldm-set1
  1. 4. Restart all logical domains.
  1. An XSCF user account name cannot be the same as an LDAP user name. In addition, an XSCF user account UID cannot be the same as an LDAP UID.
  2. When starting the OpenBoot PROM, even if an error is detected with the GFX 550e graphics card (TechSource, PCI Express Graphics Board), nothing may be output to the console.
    The problem can be confirmed from the following error log output with the showlogs error command, which registers the faulty component (suspect component) as "UNSPECIFIED".
  1. [Error message example]
XSCF> showlogs error
Date: MMM DD hh:mm:ss JST 2014
Code: 80000000-00ffff0000ff0000ff-030000010000000000000000
Status: Alarm Occurred: MMM DD hh:mm:ss.sss JST 2014
FRU: /UNSPECIFIED
Msg: I/O device error detected
  1. [SPARC M10-4S]
    If cold replacement is performed on a system with several SPARC M10-4S and crossbar boxes, the XSCF may not start. Perform one of the following procedures, according to the target components for cold replacement.
    ▪ When replacing crossbar boxes (XBBOX)

    Perform the following procedure.
    1. Turn off the input power (AC OFF) of the target XBBOX.
    2. Replace the XSCF unit (XSCFU).
    When performing this procedure, swap the microSD card in the old XSCF unit to the new XSCF unit, before replacing the XSCF unit itself.

    3. Turn on the input power (AC ON) of the XBBOX.
    ▪ Perform the following procedure when replacing the following components that are mounted on the crossbar box (XBBOX):

    In the following cases, replacement of the microSD card is unnecessary. For the maintenance procedure, see the Fujitsu M10-4/Fujitsu M10-4S/SPARC M10-4/SPARC M10-4S Service Manual.

    - XSCF unit (XSCFU), crossbar unit (XBU), XSCF interface unit (XSCFIFU), crossbar backplane unit (XBBP), fan backplane unit (FANBP), operation panel (OPNL), power supply unit (PSU), fan (FAN)

    ▪ Perform the following procedure when replacing SPARC M10-4S or CPU memory unit lower (CMUL):

    Execute the replacefru(8) command and then follow the maintenance menu to perform the replacement.
  2. [SPARC M10-4S]
    When maintenance is performed using either the replacefru(8) or addfru(8) command, terminate the command by entering the "c" option. In a system consisting of multiple SPARC M10-4S chassis, if the flashupdate(8) command is executed before the above command is terminated, automatic switchover to the master XSCF may not be performed after the firmware update is complete.
    [How to restore]
    After maintenance is completed using either the replacefru(8) or addfru(8) command, terminate the command by entering the "c" option. If switchover to the master XSCF is not performed after the completion of the firmware update, execute the switchscf(8) command on the master XSCF to switch over to the master XSCF.
  3. If an XSCF reset or switchover is performed while you are performing a setting-related operation from the XSCF shell or XSCF Web, the setting may not be saved on the XSCF. Use the XSCF shell or XSCF Web to confirm that the setting is saved after the XSCF reset or switchover has completed. If the setting is not saved, perform the setting again.
Restrictions
  1. The -c wait option of the setpowerupdelay(8) command is not supported.
  2. At this point in time, the no-mem setting in the -s option of the setpcl(8) command is not supported.
  3. Alive check function between the XSCF and a Hypervisor is not supported. Alive check function between the XSCF and a Hypervisor cannot be enabled/disabled even by using the setpparmode(8) command.
  1. To use a user account managed with the Lightweight Directory Access Protocol (LDAP), Active Directory, and the LDAP over SSL service, the available characters for the user account name for XSCF login are lowercase alphabetic characters, numbers, the hyphen (-), the underscore (_), and the period (.). The name is a combination of up to 31 characters. Uppercase alphabetic characters cannot be used. The first character of the name must be a lowercase alphabetic character.
    Even though you can log in using a user account name not fitting the above description, your commands may not work normally. For this reason, use the above-described user account name.
  1. [SPARC M10-4S]
    Suppose that the XSCF was switched while connecting to the control domain console in a SPARC M10-4S that is composed of more than two chassis. In that case, if an attempt has been made to reconnect the control domain console to the switched master XSCF, a connection to the control domain console may not be established until all the SPARC M10-4S chassis have been restarted.
    If all XSCFs have not been rebooted due to an error in the XSCF, establish a connection to the control domain console again. Replace a failed XSCF or CPU memory unit lower (CMUL) if a connection cannot be established to the control domain console.
  2. [SPARC M10-4S]
    In a SPARC M10-4S that is composed of more than two chassis, if all XSCFs have not been rebooted due to an error in an XSCF, the poweroff(8) and reset(8) commands may not be executed normally.
    To disconnect the power of a physical partition (PPAR), login to the control domain of the PPAR and execute the shutdown command on Oracle Solaris. Then, disconnect the power of the PPAR using the poweroff -f command on the XSCF firmware. The reset(8) command cannot be used in this state.
  3. Replacement of a crossbar box using the replacefru(8) command is not supported at present. For details on how to replace a crossbar box, see "Restrictions on Replacing a Crossbar Box" in "Chapter 6 Information on SPARC M10-4S Hardware."
  4. Addition of a crossbar box using the addfru(8) command is not supported at present. For details on how to add a crossbar box, see "Restrictions on Adding Expansion Rack 2" in "Chapter 6 Information on SPARC M10-4S Hardware."
  5. [SPARC M10-4S]
    When the poweron(8) command powers on all the physical partitions (PPARs) in a system that has more than one PPAR, the startup time taken by power-on of a specified PPAR is even longer than the time taken by batch power-on, which is specified by -a.
  6. [SPARC M10-4S]
    If showhardconf -M is executed, it may not be possible to display one screen at a time if both of the conditions below are met. Do not execute showhardconf -M.
    - System configured with 2BB or more

    - One or more SPARC M10-4S units are subject to an XSCF reset by the rebootxscf(8) command, so they cannot communicate.
  7. [SPARC M10-1]
    If XCP 2070 or earlier firmware is updated while the physical partition (PPAR) is powered on, the logical domains may stop.
    Be sure to execute firmware update when the physical partition (PPAR) is powered off. For details on this problem, see "RTIF2-131004-001" in "Problems Resolved in XCP 2070."
  8. The user privileges of XSCF user accounts are managed with the LDAP server specified in the setldap(8) command or in [XSCF] - [Settings] - [User Manager] - [LDAP] on XSCF Web. If the version being used is XCP 2271 or earlier, the privileges cannot be configured from [XSCF] - [Settings] - [User Manager] - [Account] on XSCF Web.
    Set user privileges with the setprivileges(8) command from the XSCF shell prompt.
  9. Neither the deleteuser(8) command nor the [Settings] - [User Manager] - [Account] menu on XSCF Web can delete the user account of a user who is logged into the XSCF via SSH, Telnet, or XSCF Web. Any attempt to do so will result in an error. To delete the target user account, use the who(1) command or the [Settings] - [User Manager] - [Account] menu on XSCF Web to confirm that the user account is not logged in to the XSCF, and then delete it.
    Likewise, neither the deleteuser(8) command nor the [Settings] - [User Manager] - [Account] menu on XSCF Web can delete a user account for which the SNMP setting has been made with the setsnmp(8), setsnmpusm(8), or setsnmpvacm(8) command or the [SNMP] or [SNMP Security] menu on XSCF Web. Any attempt to do so will result in an error. Before deleting the user account, execute the rebootxscf -a command to reset all the XSCFs.

Top of Page