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

Configure SNMP Trap Destinations for Storage Servers


Note - Do not attempt to copy and paste commands that span across multiple lines from this section. Manually type commands that span across multiple lines to ensure the commands are typed properly.


Perform this task on each storage server:

  1. Log in as celladmin on the storage server.
  2. On the storage server, add SNMP trap destinations:

    # cellcli -e “alter cell snmpSubscriber=(host ='ASR-Manager-name-or-IP-address',port=162,community=public,type=asr)”

    Single quotes are required around the ASR-Manager-name-or-IP-address entry. These are the element definitions for the command above:

    • host='ASR-Manager-name-or-IP-address' – The ASR Manager hostname can be used when DNS is enabled for the site. If DNS is not running, the IP address is preferred, but the ASR Manager hostname can be used if the entry is added to the /etc/hosts file.

    • type=asr – Specifies the ASR Manager as being a special type of SNMP subscriber.

    • community=public – The required value of the community string. This value can be modified to be a different string based on your network requirements.

    • port=162 – The SNMP port. This port value is site dependant. It can be configured as a different port based on network requirements, or it might need to be changed for ASR to work correctly in a managed environment.

  3. Ensure that Oracle ILOM auto-activation occurred

    This confirms that the network and Oracle ILOM are set up correctly.

    # asr list_asset

    Example:

    IP_ADDRESS     HOST_NAME       SERIAL_NUMBER   ASR       PROTOCOL   SOURCE
    ----------     ---------       -------------   ---       --------   -----
    10.60.40.105   ssc1cel01       1234FMM0CA      Enabled   SNMP       ILOM
    10.60.40.106   ssc1cel02       1235FMM0CA      Enabled   SNMP       ILOM
    10.60.40.107   ssc1cel03       1236FMM0CA      Enabled   SNMP       ILOM
    10.60.40.117   ssc1cel01-ilom  1234FMM0CA      Enabled   SNMP,HTTP  EXADATA-SW
    10.60.40.118   ssc1cel02-ilom  1235FMM0CA      Enabled   SNMP,HTTP  EXADATA-SW
    10.60.40.119   ssc1cel03-ilom  1236FMM0CA      Enabled   SNMP,HTTP  EXADATA-SW
    • If all Oracle ILOMs for the storage servers are in the list, go to Step 5.

    • If Oracle ILOMs are not in the list, go to Step 4.

  4. On the ASR Manager, activate the Oracle ILOMs of the storage servers:

    # asr activate_asset -i ILOM-IP-address

    or

    # asr activate_asset -h ILOM-hostname


    Note - If the last step fails, verify that port 6481 on the Oracle ILOM is open. If port 6481 is open and the step still fails, contact ASR Support.


  5. Activate the Exadata OS side of the ASR support:

    # asr activate_exadata -i host-management-IP-address -h host-management-hostname -l ILOM-IP-address

    or

    # asr activate_exadata -i host-management-IP-address -h host-management-hostname -n ILOM-hostname

  6. Ensure that all storage servers are visible on the ASR Manager.

    # asr list_asset

    You should see both the Oracle ILOM and the host referenced in the list, with the same serial number, as shown in this example:

    IP_ADDRESS     HOST_NAME       SERIAL_NUMBER   ASR       PROTOCOL   SOURCE
    ----------     ---------       -------------   ---       --------   -----
    10.60.40.105   ssc1cel01       1234FMM0CA      Enabled   SNMP       ILOM
    10.60.40.106   ssc1cel02       1235FMM0CA      Enabled   SNMP       ILOM
    10.60.40.107   ssc1cel03       1236FMM0CA      Enabled   SNMP       ILOM
    10.60.40.117   ssc1cel01-ilom  1234FMM0CA      Enabled   SNMP,HTTP  EXADATA-SW
    10.60.40.118   ssc1cel02-ilom  1235FMM0CA      Enabled   SNMP,HTTP  EXADATA-SW
    10.60.40.119   ssc1cel03-ilom  1236FMM0CA      Enabled   SNMP,HTTP  EXADATA-SW
  7. On the storage server, validate the configuration:

    # cellcli -e “list cell attributes snmpsubscriber”

  8. On the storage server, validate the SNMP configuration:

    # cellcli -e “alter cell validate snmp type=asr”

    The MOS contact receives an email as confirmation.

  9. Repeat these instructions for every storage server in your SuperCluster.
  10. Go to the next configuration task.

    See Configure ASR on the ZFS Storage Appliance.