JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris 10 9/10 Release Notes
search filter icon
search icon

Document Information


1.  Installation Issues

2.  Oracle Solaris Runtime Issues

3.  System-Specific Issues

Dynamic Reconfiguration on Oracle's Sun Fire High-End Systems

Known Software and Hardware Bugs

GigaSwift Ethernet MMF Link Fails With CISCO 4003 Switch After DR Attach

Dynamic Reconfiguration on Oracle's Sun Fire Midrange Systems

Minimum System Controller Firmware

Known DR Software Bugs

Network Device Removal Fails When a Program Is Holding the Device Open (5054195)

Sun Enterprise 10000 Release Notes

System Service Processor Requirement

Dynamic Reconfiguration Issues

DR Model 3.0

DR and Bound User Processes

Network Device Removal Fails When a Program Is Holding the Device Open (5054195)

InterDomain Networks

OpenBoot PROM Variables

Dynamic Reconfiguration on Oracle's Sun Enterprise Midrange Systems

Supported Hardware

Software Notes

Enabling Dynamic Reconfiguration

Quiesce Test

Disabled Board List

Disabled Memory List

Unloading Detach-Unsafe Drivers

Self-Test Failure During a Connect Sequence

Known Bugs

Network Device Removal Fails When a Program Is Holding the Device Open (5054195)

4.  End-of-Software Support Statements

5.  Documentation Issues

A.  Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 9/10 Release

Sun Enterprise 10000 Release Notes

This section describes issues that involve the following features on the Sun Enterprise 10000 server:

Note - The Oracle Solaris 10 software can be run on individual domains within a Sun Enterprise 10000 system. However, the Sun Enterprise 10000 System Service Processor is not supported by this release.

System Service Processor Requirement

The SSP 3.5 software is required on your System Service Processor (SSP) to support the Oracle Solaris 10 software. Install the SSP 3.5 on your SSP first. Then you can install or upgrade to the Oracle Solaris 10 OS on a Sun Enterprise 10000 domain.

The SSP 3.5 software is also required so that the domain can be properly configured for DR Model 3.0.

Dynamic Reconfiguration Issues

This section describes different issues that involve dynamic reconfiguration on Sun Enterprise 10000 domains.

DR Model 3.0

You must use DR 3.0 on Sun Enterprise 10000 domains that run the Oracle Solaris OS beginning with the Solaris 9 12/03 release. DR model 3.0 refers to the functionality that uses the following commands on the SSP to perform domain DR operations:

You can run the cfgadm command on domains to obtain board status information. DR model 3.0 also interfaces with the Reconfiguration Coordination Manager (RCM) to coordinate the DR operations with other applications that are running on a domain.

For details about DR model 3.0, refer to the Sun Enterprise 10000 Dynamic Reconfiguration User Guide.

DR and Bound User Processes

For this Oracle Solaris release, DR no longer automatically unbinds user processes from CPUs that are being detached. You must perform this operation before initiating a detach sequence. The drain operation fails if CPUs are found with bound processes.

Network Device Removal Fails When a Program Is Holding the Device Open (5054195)

If a process is holding open a network device, any DR operation that would involve that device fails. Daemons and processes that hold reference counts stop DR operations from completing.

Workaround: As superuser, perform the following steps:

  1. Remove or rename the /rplboot directory.

  2. Shut down NFS services.

    # sh /etc/init.d/nfs.server stop
  3. Shut down Boot Server services.

    # sh /etc/init.d/boot.server stop
  4. Perform the DR detach operation.

  5. Restart NFS services.

    # sh /etc/init.d/nfs.server start
  6. Restart Boot Server services.

    # sh /etc/init.d/boot.server start

InterDomain Networks

For a domain to become part of an InterDomain Network, all boards with active memory in that domain must have at least one active CPU.

OpenBoot PROM Variables

Before you issue the boot net command from the OpenBoot PROM prompt (OK), verify that the local-mac-address? variable is set to false. This setting is the factory default setting. If the variable is set to true, you must ensure that this value is an appropriate local configuration.


Caution - A local-mac-address? that is set to true might prevent the domain from successfully booting over the network.

In a netcon window, you can use the following command at the OpenBoot PROM prompt to display the values of the OpenBoot PROM variables:

OK printenv

To reset the local-mac-address? variable to the default setting. use the setenv command:

OK setenv local-mac-address? false