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)
Register Compute Servers With Oracle Solaris 11 or Database Domains to ASR Manager
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
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
You can enable session replication enhancements for managed servers in a WebLogic cluster to which you will deploy a web application at a later time.
Note - If you are using Coherence*web, these session replication enhancements do not apply. Skip these steps if you use the dizzyworld.ear application as described in Chapter 8, “Deploying a Sample Web Application to and Oracle WebLogic Cluster” in the Oracle Fusion Middleware Exalogic Enterprise Deployment Guide at: http://docs.oracle.com/cd/E18476_01/doc.220/e18479/deploy.htm
To enable session replication enhancements for Dept1_Cluster1, complete the following steps:
Refer to Section 5.16 “Starting Managed Servers on ComputeNode1 and ComputeNode2” of the Oracle® Fusion Middleware Exalogic Enterprise Deployment Guide at: http://docs.oracle.com/cd/E18476_01/doc.220/e18479/create_domain.htm#BABEGAFB
The Summary of Servers page is displayed.
The Settings for WLS1 is displayed.
For example, replication channels for managed servers in Dept_1_Cluster1 can listen on ports starting from 7005 to 7015. To specify this range of ports, enter 7005-7015.
The Summary of Servers page is displayed.
Listen address: 10.0.0.1
Note - This is the floating IP assigned to WLS1.
Listen port: 7005
|
The Summary of Clusters page is displayed.
The Settings for Dept1_Cluster1 page is displayed.
The Summary of Servers page is displayed.
The Settings for WLS1 page is displayed.
Type the netstat -na command.
Check the managed server logs.