Skip Navigation Links | |
Exit Print View | |
Installing Oracle Solaris 11.1 Systems Oracle Solaris 11.1 Information Library |
Part I Oracle Solaris 11.1 Installation Options
1. Overview of Installation Options
Part II Installing Using Installation Media
2. Preparing for the Installation
System Requirements for Live Media and Text Installations
Preparing a Boot Environment for Installing Multiple Operating Systems
Guidelines for Partitioning a System Prior To Installation
Guidelines for Partitioning a System During an Interactive Installation
x86: Setting Up Partitions During an Interactive Installation
Setting Up VTOC Slices During a Text Installation
Ensuring That You Have the Proper Device Drivers
How to Use the Oracle Device Detection Tool
5. Automated Installations That Boot From Media
6. Unconfiguring or Reconfiguring an Oracle Solaris instance
Part III Installing Using an Install Server
7. Automated Installation of Multiple Clients
8. Setting Up an Install Server
10. Provisioning the Client System
11. Configuring the Client System
12. Installing and Configuring Zones
13. Running a Custom Script During First Boot
15. Troubleshooting Automated Installations
Part IV Performing Related Tasks
A. Working With Oracle Configuration Manager
In this Oracle Solaris release, during an interactive installation, you will be prompted to configure the Oracle Configuration Manager and the Oracle Auto Service Request utilities for your installed system if those services are going to be installed on your system.
Oracle Configuration Manager sends periodic data to the Oracle support organization describing a system's software configuration.
Oracle Auto Service Request sends data to the Oracle support organization when a Fault Management Architecture (FMA) event occurs, indicating a hardware or software issue.
Note - All Data is transmitted in secure mode.
When performing an interactive installation, you have the following options.
The default Support Registration installer panel provides an anonymous registration address. If you use this anonymous address or another email address with no password, anonymous system configuration will be uploaded to the Oracle support organization. But, because you did not provide your My Oracle Support login information, My Oracle Support will not receive any of your identifying customer information when information is sent about the installed system's configuration.
You can replace the anonymous email address in the Support Configuration panel with your My Oracle Support login ID and add your My Oracle Support password. Use this option if you want to see your customer information in My Oracle Support and receive security updates. With this option, Oracle Auto Service Request will also be started.
When customer configuration data is uploaded on a regular basis, customer support representatives can analyze this data and provide better service. For example, when you log a service request, the support representative can associate the configuration data directly with that service request. The customer support representative can then view the list of your systems and solve problems accordingly.
If you delete the anonymous email address in the Support Configuration panel and leave that field blank, Oracle Configuration Manager will be started in a disconnected mode. No data will be sent to My Oracle Support. In this mode, the Oracle Configuration Manager can still be manually activated in order to send data. For example, if you are asked by a tech support person to provide data on your system, you could manually use Oracle Configuration Manager to provide that data.
Unless Oracle Configuration Manager is in disconnected mode, during the first reboot, an Oracle Configuration Manager service runs and attempts to register the system with the registration server. If this registration succeeds, an upload of the configuration information is performed. Also, upon successful registration, an internal scheduler is started. Thereafter, configuration data is uploaded under control of the scheduler. On subsequent reboots, configuration data is not sent as part of service startup. The service recognizes that the system is already registered and simply launches the scheduler. Scheduling may be tuned by using /usr/sbin/emCCR. See the emCCR(1M) man page and the Oracle Configuration Manager Installation and Administration Guide.
Regardless of whether you chose to allow the registration, you can still choose to register or re-register your system later with the Oracle Configuration Manager in order to facilitate future support.
You may choose to register or re-register in situations such as the following:
You previously registered anonymously.
You previously disconnected Oracle Configuration Manager.
The My Oracle Support credentials could not be validated when they were entered because Oracle could not be contacted. For example, automatic registration was unable to complete due to a network proxy requirement.
You can register or re-register by using the configCCR utility (/usr/sbin/configCCR) in interactive mode. For example, run the following command to remove existing configuration specifications:
# /usr/lib/ocm/ccr/bin/configCCR -r
Then, run the following command to manually configure Oracle Configuration Manager:
# /usr/lib/ocm/ccr/bin/configCCR -a
After completing registration, you can enable the service as follows:
# svcadm enable system/ocm
Once the service is enabled, the Oracle Configuration Manager client will be restarted when the system is rebooted.
For further information about Oracle Configuration Manager and Oracle Auto Service Request, see the following:
configCCR(1M) man page
Oracle Configuration Manager Installation and Administration Guide
Oracle Auto Service Request documentation at http://www.oracle.com/asr