Skip to main content

Contents

  1. Preface
  2. Chapter 1 Latest Information
    1.  Latest Information
    2.  Revision Information
  3. Chapter 2 Software Requirements
    1. Click Supported Firmware and Oracle Solaris Versions
    2.  Web Browser
    3.  Software Supporting Remote Storage
    4.  XCP and Oracle Solaris Version Supporting Power Aware Dispatcher Function
    5.  How to Obtain XCP and Oracle Solaris SRU/Patch/Oracle VM Server for SPARC
    6. Click Notes on Memory
    7. Click Notes on Mixing Different Hardware
    8.  Obtaining the SAS-2 Integrated RAID Configuration Utility
  4. Chapter 3 Information on XCP
    1. Click Latest Information on XCP
    2.  XCP Firmware Versions and Support Information
    3. Click Notes and Restrictions
    4. Click Problems With XCP and Workarounds
  5. Chapter 4 Information on Oracle Solaris
    1. Click Notes and Restrictions
    2. Click Problems With Oracle Solaris and Workarounds
  6. Chapter 5 Information on SPARC M12 System Hardware
    1. Click Notes and Restrictions
    2.  Problems With Hardware and Workarounds
  7. Chapter 6 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
  8. Chapter 7 Information on SPARC M12 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, a maximum of 15 minutes is set as the wait time of a guest domain until vds or vsw starts.
    If this wait time is exceeded, boot from the virtual disk/virtual network may fail.
    For example, when multiple disks are set for the OpenBoot PROM environment variable boot-device, it may take up to 15 minutes to switch the boot path from the virtual disk to the next disk. Or, if it takes more than 15 minutes, boot may fail.
  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 the power on in Service mode, execute the XSCF poweron command. 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. The maximum number of users who can concurrently connect to the XSCF via Telnet and SSH is as follows:
    - SPARC M12-1: 20 users

    - SPARC M12-2: 40 users

    - SPARC M12-2S (without crossbar box): 40 users

    - SPARC M12-2S (with crossbar box): 70 users

    If the maximum allowable number of users is exceeded, access is denied.
  4. 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 a communication error. Be sure to set auto-negotiation for network devices to which you connect XSCF-LAN.
  5. 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.
  6. 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.
  7. When you execute the testsb(8) or diagxbu(8) command, a PPAR-ID of the "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. Ignore the output PPAR-ID.
  8. 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 XSCF unit (XSCFU) need to be replaced immediately.
  9. 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.
  10. [SPARC M12-2S]
    The time taken for processing a command that displays the system configuration or status depends on the number of SPARC M12-2S units or crossbar boxes that configure the system. Such commands include the showhardconf(8) command, showboards(8) command, and showpparstatus(8) command.
  11. [SPARC M12-2S]
    It may take more time to restart the physical partition when hardware fails, depending on the system configuration.
  12. When you execute the setsnmpvacm(8) command specifying createview as the operand, you cannot set an access restriction using the OID mask of MIB. When you execute the setsnmpvacm(8) command specifying createview as the operand, do not use the OID mask of MIB.
  13. 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.
  14. The device path of the I/O device that has been used changes if the CPU memory unit upper (CMUU) is expanded to add one CPU when I/O bus reconfiguration is enabled in the SPARC M12-2 or SPARC M12-2S with one CPUs installed.
    As for ioreconfigure that can be set by the -m function option of the setpparmode(8) command, leave it as the default, false, and disable the I/O bus reconfiguration function.
    If you enable the I/O bus reconfiguration function by specifying true to ioreconfigure, it may be necessary to reinstall Oracle Solaris.
  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.
  1. [SPARC M12-2S]
    When maintenance is performed by either the replacefru(8) or the addfru(8) command, terminate the command using the "c" option. If the flashupdate(8) command is executed before the above command is terminated in a system consisting of multiple SPARC M12-2S units, automatic switchover to the master XSCF may not be executed after the firmware update completes.
    [How to restore]
    After maintenance is completed using either the replacefru(8) or the addfru(8) command, use the "c" option to terminate the command. If switchover to the master XSCF is not performed after the completion of firmware update, execute the switchscf(8) command on the master XSCF to switch over to the master XSCF.
  2. If XSCF reboot or switchover is performed while you are performing an operation on the setting by using 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 reboot or switchover has completed. If the setting is not saved, perform the setting again. If the setting is not saved, perform the setting again.
  3. [SPARC M12-2S]
    If active replacement of the XSCF unit (XSCFU) fails due to a FRU failure or the like, do not leave the XSCFU disconnected.
    That would disable hardware monitoring of the SPARC M12 (PSB) where the XSCFU is mounted, possibly affecting system operation.
    Prepare another FRU, and replace the XSCFU again.
    If you cannot immediately replace it again, perform the following procedure.
    1. Shut down Oracle Solaris on the PPAR of the target PSB.

    2. Forcibly power off the PPAR of the target PSB.

    3. Turn off (AC OFF) the input power to the target PSB.

    4. Disconnect the target PSB from the PPAR.
Restrictions
  1. The -c wait option of the setpowerupdelay(8) command is not supported.
  2. At present, no-mem, which is set with 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 M12-2S]
    Suppose that the XSCF was switched while connecting to the control domain console in the SPARC M12-2S in a configuration with two or more chassis. Then, the connection to the control domain console may not be established until all the SPARC M12-2S chassis have been restarted if an attempt has been made to reconnect the control domain console to the switched master XSCF.
    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 M12-2S]
    If all the XSCFs have not been rebooted due to an error in an XSCF in the SPARC M12-2S in a configuration with two or more chassis, the poweroff(8) and reset(8) commands may not be executed normally.
    To power off a physical partition (PPAR), log in to the control domain of the PPAR and execute the shutdown command on Oracle Solaris. Then, power off the PPAR by 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 (Only for SPARC M12-2S)" in "Chapter 5 Information on SPARC M12 System Hardware."
  4. Addition of a crossbar box using the addfru(8) command is not supported at present.
  5. [SPARC M12-2S]
    If you power on all physical partitions (PPARs) in a system that has more than one PPARs with the poweron(8) command, the startup time taken when specifying power-on of the PPAR is longer than the time taken for batch power-on by specifying -a.
  6. [SPARC M12-2S]
    When showhardconf -M is executed, it may not be possible to display one screen at a time if both of the conditions below are met. Under these conditions, do not execute showhardconf -M.
    - System configured with 2 BBs or more

    - One or more SPARC M12-2S units are subject to an XSCF reboot by the rebootxscf(8) command, so they cannot communicate.
  7. 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 of XSCF Web. Any attempt to do so will result in an error. Before deleting the user account, execute the rebootxscf -a command to reboot all the XSCFs.

Top of Page