Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Release Notes Oracle Solaris 10 8/11 Information Library |
Auto Registration Feature of Oracle Solaris
How to Enable or Modify Auto Registration
Before or During an Installation or Upgrade
After an Installation or Upgrade
How to Disable Auto Registration
Live Upgrade and Oracle Solaris Zones
Using Live Upgrade With a Zone Root on a ZFS File System
Upgrading a Trusted Extensions System That Is Configured With Labeled Zones
Patching Miniroot on SPARC and x86 Compatible Machines
Oracle Solaris Data Encryption Supplement on Oracle Solaris 10 Releases
x86: Systems With an elx or pcelx NIC Fail Network Configuration
Default Size of /var File System Might Be Inadequate
x86: Do Not Upgrade Hewlett-Packard Vectra XU Series Systems With BIOS Version GG.06.13
SPARC: Older Firmware Might Need Boot Flash PROM Upgrade
x86: Failure of BIOS Device Utility Prevents Installation or Upgrade From Succeeding (6362108)
Cannot Create an Oracle Solaris Flash Archive When a Non-Global Zone Is Installed (6246943)
x86: Sun Java Workstation 2100Z Might Panic When Booting From Oracle Solaris 10 DVD (6214356)
x86: Serial Consoles on Some Sun Fire Systems Do Not Work (6208412)
Jumpstart Installation Fails on Machines Attached to a SAN (7072761)
ZFS Root System Might Hang When Swapping to zvol (6898318)
Installing an Oracle Solaris ZFS Flash Archive (6889459)
Some Asian Locales Cannot Be Used for JumpStart Installation (6681454)
PRODRM Has Problems Deleting prodreg Entry for Trusted Extensions (6616592)
Upgrade Detailed Patch Analysis Panel Not Scrollable (6597686)
x86: Invalid /sbin/dhcpinfo Error During Installation (6332044)
x86: System Fails to Boot After JumpStart Installation (6205478)
SPARC: All Types of M-Series Machines Might Encounter Slight Performance Degradation (7058265)
lucreate Command Fails on Systems That Do Not Have the SUNWzoneu Package (7061870)
The iscsi/initiator Service Might End in Maintenance State After Upgrade (6976602)
Issues With a DSR Upgrade With Zones (6616788)
Trusted Extensions Upgrade Issues (6616585)
System Cannot Communicate With ypbind After an Upgrade (6488549)
Upgrade Fails on Systems With Zones That Have Been Installed But Not Booted
Device ID Discrepancies After an Upgrade From the Solaris 9 9/04 OS
Additional Related Locales Might Be Installed
3. Oracle Solaris Runtime Issues
4. End-of-Software Support Statements
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 8/11 Release
This section provides general information such as behavior changes in the Oracle Solaris 10 8/11 release.
The Auto Registration feature was new in the Oracle Solaris 10 9/10 release.
A new Auto Registration screen has been added to the interactive installer to facilitate registering your system using your Oracle support credentials. Installations and network installations made by using the JumpStart feature of Oracle Solaris require a new auto_reg keyword in the sysidcfg file to control settings during the installation.
With Auto Registration, during the initial reboot after you install or upgrade your system, service tag data about your system is automatically communicated through the existing service tag technology to the Oracle Product Registration System. This data about your system is used, for example, to help Oracle enhance customer support and services. You can learn about service tags at http://www.oracle.com/technetwork/server-storage/solaris/oracle-service-tag-faq-418684.html.
By registering with your support credentials using one of the registration options, you can inventory your systems and the major software components installed on them. For instructions on tracking your registered products, see https://inventory.sun.com/inventory/decommission_faq.html. See also My Oracle Support.
You can choose to send your service tag data to the Oracle Product Registration System anonymously. An anonymous registration means that the data sent to Oracle has no link to the name of a customer. You can also choose to disable Auto Registration.
Auto Registration is enabled by default. Auto Registration uses support credentials and proxy information that you provide before, during, or after an installation or upgrade of an SPARC or x86 based system.
You can add the new auto_reg keyword to your sysidcfg file prior to an automatic installation or upgrade, such as network installations or JumpStart installations.
During an interactive installation or upgrade, the installer asks you to provide your support credentials, or to register anonymously.
You can use a new Live Upgrade command option to provide your support credentials and proxy information, or to register anonymously, during a Live Upgrade. For more information about the Live Upgrade feature of Oracle Solaris, go to My Oracle Support.
Note - If you are working with a flash archive that is based on at least the Oracle Solaris 10 9/10 release, Auto Registration is enabled by default. The means of providing Auto Registration credential and proxy information depends on which installation or upgrade method is used with the archive.
After an installation or upgrade, a privileged system administrator can use the regadm command to administer Auto Registration and to manage a service tag inventory.
You have the following options for disabling Auto Registration on a SPARC based system or x86 based system, thus preventing data transmission to the Oracle Product Registration System.
If you are performing an automatic installation or upgrade, for example, if you are using the JumpStart program, you can disable Auto Registration prior to the installation or upgrade as follows:
Before you begin the installation or upgrade, edit the sysidcfg file to add the auto_reg keyword to the file.
auto_reg=disable
Proceed with the installation or upgrade.
(Optional) After the installation has completed and the system reboots, verify that the Auto Registration feature is disabled.
# regadm status Solaris Auto-Registration is currently disabled
Begin an interactive installation or upgrade.
During the interactive installation or upgrade, the installer prompts you to select an automatic reboot. Do not select the option to automatically reboot after the installation or upgrade. You need to disable Auto Registration prior to rebooting the system.
After the installation is complete but before rebooting the system, open a terminal window as follows:
For a GUI installation, right-click to open a terminal window.
For a text installation, press the exclamation point (!) to open a terminal window.
At the command line, remove the /a/var/tmp/autoreg_config file.
Reboot the system.
# reboot
Prior to performing a Live Upgrade operation, open a text editor and create a file that contains the following Auto Registration information:
autoreg=disable
Save this file.
Point to this file when you run the luupgrade command.
luupgrade -k /path/filename
For further information about Auto Registration, see the following resources.
Table 2-1 Auto Registration Documentation
|
On an x86 platform, after installing the Oracle Solaris 10 8/11 OS or upgrading to the Oracle Solaris 10 8/11 OS, you must install the following security patches.
145081–04 or later.
119901–11 or later.
The patches are available at My Oracle Support.
Starting with the Oracle Solaris 10 9/10 release, Oracle Solaris 10 9/10 Installation Guide: Solaris Flash Archives (Creation and Installation) includes instructions about how to create a flash archive recovery image that can be used to restore a system to its default factory condition. See Creating and Using a Disaster Recovery Image in Oracle Solaris 10 9/10 Installation Guide: Solaris Flash Archives (Creation and Installation). This chapter provides the simplest instructions to create a flash archive (FLAR) image that can be loaded onto the target system to recover from a failed disk drive.
The Oracle Solaris 10 8/11 release is tested on all supported Oracle systems running the latest combinations of the following:
BIOS and ILOM
SPARC firmware, OBP, and Hypervisor
For best results using the Oracle Solaris 10 8/11 release, upgrade your BIOS/firmware to the latest release listed in the matrix at http://www.oracle.com/technetwork/systems/patches/firmware/release-history-jsp-138416.html.
The following are the minimum and recommended memory requirements for the Oracle Solaris 10 8/11 release.
For UFS root file systems:
Minimum: 1.5 GB
Recommended: 1.5 GB or more
For ZFS root pools:
Minimum: 1.5 GB
Recommended: 1.5 GB or more for overall ZFS performance
Note - You need at least 16 GB of disk space.
You can upgrade to Oracle Solaris 10 8/11 by using the standard upgrade process or by using Live Upgrade. For more information about Live Upgrade, see My Oracle Support.
To upgrade to the Oracle Solaris 10 8/11 release from a release earlier than the Solaris 8 OS, first upgrade to any of the releases in the following list. Then, upgrade to the Oracle Solaris 10 8/11 release.
SPARC: You can upgrade to Oracle Solaris 10 8/11 on SPARC based systems from the following major releases:
Solaris 8 OS
Solaris 9 OS
Oracle Solaris 10 OS
x86: You can upgrade to Oracle Solaris 10 8/11 on x86 based systems from the following major releases:
Solaris 9 OS
Oracle Solaris 10 OS
The Oracle Solaris 10 8/11 release has been tested for compatibility with previous releases in line with the Oracle Solaris compatibility guarantee. This means that applications, including third-party applications, which adhere to the Oracle Solaris published ABI will work without modification on the Oracle Solaris 10 8/11 release.
Your system might run both an Oracle Solaris OS and other products that are not part of the Oracle Solaris software. These products might be supplied by either Oracle or another company. If you upgrade this system to the Oracle Solaris 10 release, make sure that these other products are also supported on the Oracle Solaris 10 OS. Depending on the status of each of these products, you can choose one of the following options:
Verify that the existing version of the product is supported on the Oracle Solaris 10 software.
Install a new version of the product that is supported on the Oracle Solaris 10 release. You might need to remove the previous version of the product prior to upgrading to the Oracle Solaris software. See the product documentation for more details.
Remove the product prior to upgrading to the Oracle Solaris 10 software.