JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle SuperCluster M6-32

Owner's Guide: Administration

search filter icon
search icon

Document Information

Using This Documentation

Product Documentation Library

Feedback

Understanding SuperCluster Software

Identify the Version of SuperCluster Software

SuperCluster Tools

Controlling SuperCluster M6-32

Cautions

Power On 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 Database

Shut Down the Storage Servers

Power Off the Storage Servers

Shut Down the LDoms

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)

OCM Overview

Access OCM Documentation

Monitoring the System With ASR

ASR Overview

ASR Resources

ASR Installation Overview

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

Tuning SuperCluster M6-32

ssctuner Overview

Monitor ssctuner Activity

View Log Files

Change ssctuner Properties and Disable Features

Install ssctuner

Enable ssctuner

Configuring CPU and Memory Resources (osc-setcoremem)

osc-setcoremem Overview

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)

Park Cores and Memory

Access osc-setcoremem Log Files

View the SP Configuration

Revert to a Previous CPU/Memory Configuration

Remove a CPU/Memory Configuration

Obtaining the EM Exadata Plug-in

Confirm System Requirements

Known Issues With the EM Exadata Plug-in

Configuring the Exalogic Software

Exalogic Software Overview

Prepare to Configure the Exalogic Software

Enable Domain-Level Enhancements

Enable Cluster-Level Session Replication Enhancements

Configuring Grid Link Data Source for Dept1_Cluster1

Fast Connection Failover

Runtime Connection Load Balancing

XA Affinity

SCAN Addresses

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

Enable SDP Support for JDBC

Monitor SDP Sockets

Create an SDP Listener on the IB Network

Administering Oracle Solaris 11 Boot Environments

Advantages to Maintaining Multiple Boot Environments

Create a Boot Environment

Mount to a Different Build Environment

Reboot to the Original Boot Environment

Create a Snapshot of a Boot Environment

Remove Unwanted Boot Environments

Administering DISM

DISM Restrictions

Disable DISM

Administering Storage Servers

Monitor Write-through Caching Mode

Shut Down or Reboot a Storage Server

Drop a Storage Server

Glossary

Index

Enable Cluster-Level Session Replication Enhancements

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:

  1. Ensure that managed servers in the Dept1_Cluster1 cluster are up and running.

    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

  2. Set replication ports for a managed server, such as WLS1.
    1. Under Domain Structure, click Environment and Servers.

      The Summary of Servers page is displayed.

    2. Click WLS1 on the list of servers.

      The Settings for WLS1 is displayed.

    3. Click the Cluster tab.
    4. In the Replication Ports field, enter a range of ports for configuring multiple replication channels.

      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.

  3. Create a custom network channel for each managed server in the cluster (for example, WLS1.
    1. Log in to the Oracle WebLogic Server Administration Console.
    2. If you have not already done so, click Lock & Edit in the Change Center.
    3. In the left pane of the Console, expand Environment and select Servers.

      The Summary of Servers page is displayed.

    4. In the Servers table, click WLS1 Managed Server instance.
    5. Select Protocols and then Channels.
    6. Click New.
    7. Enter ReplicationChannel as the name of the new network channel and select t3 as the protocol, then click Next.
    8. Enter the following information:
      • Listen address: 10.0.0.1


        Note - This is the floating IP assigned to WLS1.


      • Listen port: 7005

    9. Click Next, and in the Network Channel Properties page, select Enabled and Outbound Enabled.
    10. Click Finish.
    11. Under the Network Channels table, select ReplicationChannel, which is the network channel you created for the WLS1 Managed Server.
    12. Expand Advanced, and select Enable SDP Protocol.
    13. Click Save.
    14. To activate these changes, click Activate Changes in the Change Center of the Administration Console.
    15. Repeat the preceding steps to create a network channel each for the remaining managed servers in the Dept1_Cluster1 cluster. Enter the required properties, as described in this table.
      Managed Servers in Dept1_Cluster1
      Name
      Protocol
      Listen Address
      Listen Port
      Additional Channel Ports
      WLS2
      ReplicationChannel
      t3
      10.0.0.2
      7005
      7006 to 7014
      WLS3
      ReplicationChannel
      t3
      10.0.0.3
      7005
      7006 to 7014
      WLS4
      ReplicationChannel
      t3
      10.0.0.4
      7005
      7006 to 7014
      WLS5
      ReplicationChannel
      t3
      10.0.0.5
      7005
      7006 to 7014
      WLS6
      ReplicationChannel
      t3
      10.0.0.6
      7005
      7006 to 7014
      WLS7
      ReplicationChannel
      t3
      10.0.0.7
      7005
      7006 to 7014
      WLS8
      ReplicationChannel
      t3
      10.0.0.8
      7005
      7006 to 7014
  4. After creating the network channel for each of the managed servers in your cluster, click Environment-> Clusters.

    The Summary of Clusters page is displayed.

  5. Click Dept1_Cluster1. This is the example cluster to which you will deploy a web application at a later time.

    The Settings for Dept1_Cluster1 page is displayed.

  6. Click the Replication tab.
  7. In the Replication Channel field, ensure that ReplicationChannel is set as the name of the channel to be used for replication traffic.
  8. In the Advanced section, select the Enable One Way RMI for Replication option, and click Save.
  9. Activate changes, and restart the managed servers.
  10. Manually add the system property -Djava.net.preferIPv4Stack=true to the startWebLogic.sh script, which is located in the bin directory of base_domain, using a text editor as follows:
    1. Locate the following line in the startWebLogic.sh script:

      . ${DOMAIN_HOME}/bin/setDomainEnv.sh $*

    2. Add the following property immediately after the preceding entry:

      JAVA_OPTIONS="${JAVA_OPTIONS} -Djava.net.preferIPv4Stack=true"

    3. Save and close the file.
  11. Restart all managed servers.
    1. In the administration console, click Environment -> Servers.

      The Summary of Servers page is displayed.

    2. Select a managed server, such as WLS1, by clicking WLS1.

      The Settings for WLS1 page is displayed.

    3. Click the Control tab. Select WLS1 in the Server Status table. Click Start.
    4. Repeat these steps for each of the managed servers in the WebLogic cluster.
  12. Verify that multiple listening ports were opened in one of these ways:
    • Type the netstat -na command.

    • Check the managed server logs.