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

Notes on the OpenBoot PROM


Notes on the OpenBoot PROM
  1. When security-mode in OpenBoot PROM environment variables is set to command or full, and at least 1 and no more than 8 viewable character strings are set for security-password, the OpenBoot PROM security mode is enabled and a password is required for executing commands or performing operations.
    For details, see "H.4 Behavior With the Security Mode Enabled" in the Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 System Operation and Administration Guide.
  1. When the XCP firmware is updated to XCP 2260 or later, information for CD-ROM and remote storage is added to OpenBoot PROM device aliases. To use added device aliases when the system operates with a logical domain configuration other than factory-default, perform the following procedure in the control domain after updating the XCP firmware to XCP 2260 or later.
  1. 1. Confirm the logical domain configuration information saved to the XSCF.

    The following example shows that two sets of configuration information (i.e., logical domain configuration information ldm-set1, which is currently in use, and factory-default) are stored.
# 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>.
# ldm set-variable fix_foo=true <ldom>
# ldm remove-variable fix_foo <ldom>
  1. 3. Save the updated configuration information for the logical domain again.

    Delete the stored ldm-set1 and then store the information again.
# ldm rm-spconfig ldm-set1
# ldm add-spconfig ldm-set1
  1. 4. Restart all logical domains.
  1. If you execute the sendbreak(8) command after the OpenBoot PROM banner appears but before OpenBoot PROM startup is completed, the following error message is output. In this case, the boot command cannot be executed.
    FATAL: OpenBoot initialization sequence prematurely terminated.
    In this case, set the OpenBoot PROM environment variable auto-boot? to false at the ok prompt, and then execute the reset-all command. When the OpenBoot PROM is restarted, set auto-boot? to true, and execute the boot command.
  2. When you use the setpparparam(8) command of the XSCF firmware to set an OpenBoot PROM environment variable, such as nvramrc, the maximum number of characters that can be set is 254.
    If you want to set a string of 255 or more characters in an OpenBoot PROM environment variable, such as nvramrc, do so in the OpenBoot PROM or Oracle Solaris environment. Note that, however, the maximum number of characters is 1024.
  3. The OpenBoot PROM device aliases disk and net are not created for Oracle VM Server for SPARC disks and logical domains to which no network is assigned. To execute disk boot or network boot by specifying the device alias disk or net, set the device aliases disk and net by using the OpenBoot PROM nvalias command.
  4. From XCP 2210 onward, at the time of starting up the OpenBoot PROM, the following message is output before the OpenBoot PROM banner is displayed.
NOTICE: Entering OpenBoot.
NOTICE: Fetching Guest MD from HV.
NOTICE: Starting additional cpus.
NOTICE: Initializing LDC services.
NOTICE: Probing PCI devices.
NOTICE: Finished PCI probing.
  1. Suppose the following: the OpenBoot PROM environment variable multipath-boot? is true; the boot -L command is executed to display boot environments (BEs) that, existing in the root pool, allow booting; and the number of a boot environment is selected from the displayed interactive menu. The system does not return to the ok prompt but restarts the OpenBoot PROM.
    The number of restarts depends on the OpenBoot PROM environment variable boot-device. The OpenBoot PROM restarts as many times as the number of configured devices, after which the message "ERROR: All device paths in boot-device have failed." is displayed and the ok prompt reappears.
    To avoid this problem, set the environment variable multipath-boot? of OpenBoot PROM to false before executing the boot -L command or execute the boot device_path -L command.
  2. Suppose you execute the boot command with no arguments while the OpenBoot PROM environment variable "multipath-boot?" is set to "false" and all attempted booting from the devices specified in the OpenBoot PROM environment variable "boot-device" fails. The message output to the domain console in such a case is changed from XCP 2250 as follows.
  1. - Message prior to XCP 2250
{0} ok boot
Boot device: disk File and args:

Can't open boot device

ERROR: boot-read fail

{0} ok
  1. Or
{0} ok boot
Boot device: disk File and args:

Can't locate boot device

ERROR: boot-read fail

{0} ok
  1. - Message XCP 2250 or later
{0} ok boot
No viable default device found in boot-device variable.

{0} ok
  1. In XCP 2070, the show-volumes command of OpenBoot PROM now displays "PhyNum". Also, the probe-scsi-all command now displays "VolumeDeviceName" and "VolumeWWID".

Top of Page