Understanding SuperCluster Software
Identify the Version of SuperCluster Software
Controlling SuperCluster M6-32
Powering Off SuperCluster M6-32 Gracefully
Shut Down the Oracle Solaris Cluster
Shut Down the Enterprise Controller (Ops Center)
Shut Down the OS on the Compute Servers
Shut Down the ZFS Storage Appliance
Power Off the Switches and Racks
Power Off SuperCluster M6-32 in an Emergency
Monitoring SuperCluster M6-32 (OCM)
Monitoring the System With ASR
Configure ASR on the Compute Servers (Oracle ILOM)
Configure SNMP Trap Destinations for Storage Servers
Configure ASR on the ZFS Storage Appliance
Configuring ASR on the Compute Servers (Oracle Solaris 11)
Enable the HTTP Receiver on the ASR Manager
Enable HTTPS on ASR Manager (Optional)
Approve and Verify ASR Asset Activation
Change ssctuner Properties and Disable Features
Configuring CPU and Memory Resources (osc-setcoremem)
Minimum and Maximum Resources (Dedicated Domains)
Supported Domain Configurations
Plan CPU and Memory Allocations
Display the Current Domain Configuration (osc-setcoremem)
Display the Current Domain Configuration (ldm)
Change CPU/Memory Allocations (Socket Granularity)
Change CPU/Memory Allocations (Core Granularity)
Access osc-setcoremem Log Files
Revert to a Previous CPU/Memory Configuration
Remove a CPU/Memory Configuration
Obtaining the EM Exadata Plug-in
Known Issues With the EM Exadata Plug-in
Configuring the Exalogic Software
Prepare to Configure the Exalogic Software
Enable Domain-Level Enhancements
Enable Cluster-Level Session Replication Enhancements
Configuring Grid Link Data Source for Dept1_Cluster1
Runtime Connection Load Balancing
Secure Communication With Oracle Wallet
Create a Grid Link Data Source on Dept1_Cluster1
Configuring SDP-Enabled JDBC Drivers for Dept1_Cluster1
Configure the Database to Support IB
Create an SDP Listener on the IB Network
Administering Oracle Solaris 11 Boot Environments
Advantages to Maintaining Multiple Boot Environments
Mount to a Different Build Environment
Reboot to the Original Boot Environment
Create a Snapshot of a Boot Environment
Remove Unwanted Boot Environments
Monitor Write-through Caching Mode
Use this procedure to register compute servers with Oracle Solaris 11 or Database Domains to the ASR Manager.
# svcs asr-notify
If you see this message:
svcs: Pattern ‘asr-notify' doesn't match any instances
then confirm that the asr-notify service is installed:
# pkg list asr-notify
If you see this message:
pkg list: no packages matching ‘asr-modify' installed
then install the asr-notify service:
# pkg install system/fault-management/asr-notify
Enter the svcs asr-notify command again to confirm that the asr-notify service is working.
If you see this message:
# svcs asr-notify STATE STIME FMRI online 16:06:05 svc:/system/fm/asr-notify:default
then the asr-notify service is installed and is working properly
# asradm register -e http://asr-manager-host:port-number/asr
Example:
# asradm register -e http://asrmanager1.mycompany.com:8777/asr
Screens are displayed asking for your Oracle Support account name and password. After entering your Oracle Support account name and password, a notification is displayed, indicating that your registration is complete:
Enter Orcle SSO User Name: Enter password: Registration complete.
# asradm list
Example output:
PROPERTY VALUE Status Successfully Registered with ASR manager System Id system-identification-number Asset Id asset-identification-number User username Endpoint URL http://asr-manager-host:port-number/asr
The registration of the ASR Manager is complete.
See Approve and Verify ASR Asset Activation for those instructions.