Oracle® Enterprise Manager Ops Center

Sizing and Performance

12c Release 3 (12.3.2.0.0)

E59962-04

June 2016

Oracle Enterprise Manager Ops Center Sizing and Performance, 12c Release 3 (12.3.2.0.0)

E59962-04

Copyright © 2015, 2016, Oracle and/or its affiliates. All rights reserved.

Primary Authors: Laura Hartman, Uma Shankar

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Related Documents

- Conventions

1 Introduction to Sizing and Performance

- About Oracle Enterprise Manager Ops Center

- Product Design and Resource Utilization

- Architecture

- Knowledge Base and Package Repository

- Enterprise Controller

- Proxy Controller

- Agent Controllers

- Product Design

- Enterprise Manager Ops Center's State Machine

- The Job Management System

- High Availability

- Related Resources for Product Architecture

2 Resource Utilization

- Use Patterns

- Use Pattern Categories

- Hardware Management

- Hardware and OS Provisioning

- Hardware, OS, and Update Management

- Hardware and OS Virtualization

- All Management Features

- Related Resources for Resource Utilization

3 Scaling and Performance Guidelines

- Introduction to Scaling and Performance

- Enterprise Controller Considerations and Requirements

- Changing the Database Fetch Size

- Proxy Controller Considerations

- Virtualization Controller Considerations

- Agent Controller Considerations

- Checking the Agent Controller Heap Usage

- Changing the Agent Controller Heap Size

- Maintaining Agent Access to Large Numbers of LUNs

- Management Repository Considerations

- Embedded Database

- Customer-Managed Database

- Network Considerations

- Storage Library Considerations

- Disk Considerations

- ZFS ARC Size Considerations

- Oracle VM Server for SPARC Provisioning Considerations

- ZFS Storage Appliance Considerations

- User Interface Considerations

- Disabling Automatic Asset Tree Expansion

- Disabling the Membership Graph

- Determine the Number of Asset Access Points

- Viewing the Access Point Count for Your Environment

- Viewing the Access Point List for Each Proxy Controller

- Viewing the Access Point Types for Each Proxy Controller

- Viewing All Access Point Data

- Viewing the Asset Count in the User Interface

- Related Resources for Scaling

4 Reference Systems

- Enterprise Controller

- Proxy Controller

A Report Service Configuration Properties

- Default Retention Periods

- Edit Report Service Properties

- Disable the Report Service

- Related Resources for Report Service Configuration

Index

Preface

The Oracle Enterprise Manager Ops Center Sizing and Performance provides sizing and deployment considerations to optimize Oracle Enterprise Manager Ops Center performance.

Audience

This document is intended for all administration users of Oracle Enterprise Manager Ops Center 12c Release 3 (12.3.1.0.0) software.

Related Documents

For more information, see the Oracle Enterprise Manager Ops Center Documentation Library at http://docs.oracle.com/cd/E59957_01/index.htm.

Oracle Enterprise Manager Ops Center provides online Help. Click Help at the top-right corner of any page in the user interface to display the online help window.

For the latest releases of these and other Oracle documentation, check the Oracle Technology Network at: http://www.oracle.com/technetwork/documentation/index.html#em

Conventions

The following text conventions are used in this document:

Convention

Meaning

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, code in examples, text that appears on the screen, or text that you enter.

1 Introduction to Sizing and Performance

This document provides an overview of the Oracle Enterprise Manager Ops Center software product design and includes what to consider when planning to deploy the software. It provides guidelines on how to effectively size an Oracle Enterprise Manager Ops Center environment, how to configure a scalable deployment for your datacenter and optimize performance.

The following topics are covered in this document:

- Resource Utilization

- Scaling and Performance Guidelines

- Reference Systems

About Oracle Enterprise Manager Ops Center

Oracle Enterprise Manager Ops Center provides a converged management solution for Oracle servers, storage, Oracle Solaris and Linux operating systems, zones, and Oracle VM Server for SPARC virtualization.

The software provides system administrators with a comprehensive solution including change and configuration management, firmware and OS patching, bare metal and VM provisioning, hardware telemetry (“phone home"), performance management, integrated diagnostics, and automatic tuning.

This chapter contains the following topics:

- Product Design and Resource Utilization

- Architecture

- Product Design

- High Availability

- Related Resources for Product Architecture

Product Design and Resource Utilization

Oracle Enterprise Manager Ops Center is designed to scale from small installations up through large installations. To scale, you must deploy key components of the product architecture appropriately to meet the requirements. You should be familiar with the following key components:

- Browser user interface. Ops Center provides a rich interface inside a browser. The user interface heavily leverages JavaScript and AJAX technology to provide a highly dynamic and asynchronously updating user view.

- Enterprise Controller. The Enterprise Controller is the core component of Ops Center, it provides a centralized place where management information is stored and from which operations are initiated. The browser user interface connects into a standard API that the Enterprise Controller provides.

- A Management Repository. The management repository is based on an Oracle Enterprise Edition Database and provides a permanent storage location for all management data used by the Enterprise Controller. In this release the management repository can either be co-located in the same operating system instance as the Enterprise Controller or deployed onto an external database server.

- Proxy Controller. The Proxy Controller is designed to be distributed throughout the networks. It provides proxy capabilities for operations that must be logically located close to the targets due to network considerations, such as OS provisioning activities. It also provides a fan out for minimizing network load, proxy load balancing, and failover. Using this technology, you can configure proxies to see the same assets and can load balance traffic and provide a failover model between proxies.

- Agent Controllers. Agent Controllers provide monitoring and update capabilities for the host operating system. Specialized agents support basic and virtualization control virtualization technology. When an asset is agent-managed, the agent gathers information for the Enterprise Controller. The VC Agent Controller is for virtualization technology, such as zones and logical domains. This agent manages the logical domains that run on the Control Domain and the zones that run on the logical domains.
You have the option to not install an agent on a host, referred to as agentlessly managed. The management functionality is limited without the agent.

Architecture

Oracle Enterprise Manager Ops Center is designed to provide increased scalability, high availability and optimized performance in large, distributed data centers. The architecture is scaled as your organization grows. The Enterprise Controller, Proxy Controllers, Agent Controllers, and user interface are the major architectural components. They are supported by the Knowledge Base, which is hosted by Oracle and accessed through the Internet. This architecture lets you customize your deployment for the size and network topology of your organization by varying the placement of the Proxy Controllers and use of Agent Controllers.

Oracle Enterprise Manager Ops Center, downloads information from the Knowledge Base and Package Repository to the Enterprise Controller, which stores the information along with basic management tools, such as the profiles and plans. At least one Proxy Controller distributes the Enterprise Controller's work. Secure network connections between all components transfer control commands and data. For operating systems, Agent Controllers provide update capabilities, management and monitoring, and control of virtualization environments. Agent Controllers are required for Oracle Solaris 9 and 10 and Linux catalogs. Oracle Solaris 9 and Oracle Solaris 10 boot environment management also requires an agent-managed operating system.

Figure 1-1 shows the relationship between the browser console, Enterprise Controller, Proxy Controller, and multiple Agent Controllers. See the Related Resources for Product Architecture section for details on the communication direction, protocol and port, and the purpose for each level of communication.

Figure 1-1 Oracle Enterprise Manager Ops Center Architecture

Knowledge Base and Package Repository

The Knowledge Base and Oracle Solaris 11 Package Repository store metadata about Oracle Solaris and Oracle Linux operating system components. The metadata includes patch dependencies, standard patch compatibilities, withdrawn patches, and rules for download and deployment.

Oracle Enterprise Manager Ops Center is configured to connect to Oracle Corporation sites for updated metadata for operating systems. However, you can configure the product software without a direct connection to these sites.

Enterprise Controller

The Enterprise Controller is the central server for Oracle Enterprise Manager Ops Center. All operations, or jobs, are initiated from the Enterprise Controller.

The Enterprise Controller manages firmware and operating system images, plans, profiles, and policies. The Enterprise Controller relies on a database of asset data and site customizations. The database is a local embedded database or a remote customer-managed Oracle Enterprise Edition database that is accessible on the network to the Enterprise Controller. Include the Enterprise Controller in an active-standby High Availability configuration to increase the availability of the Oracle Enterprise Manager Ops Center software.

The Enterprise Controller connects to the Internet to get access to contract information, to create service requests, and to download updates, Oracle Solaris images, and updates to the product software itself. When an update is requested, the Enterprise Controller retrieves the software from the Knowledge Base, package repository, or vendor. This default mode of operation is called Connected mode.

If your site policy does not permit an Internet connection, you can operate the software in Disconnected mode. In this mode, you must load and maintain the Knowledge Base and package repository data and updates in the Enterprise Controller. For Oracle Solaris and Oracle Linux operating systems, Oracle Enterprise Manager Ops Center provides a script that you run on a system that is connected to the Internet to retrieve the contents of Oracle's Knowledge Base or Oracle Solaris 11 Package Repository and then you upload the baselines and updates to the Enterprise Controller.

Proxy Controller

Proxy Controllers distribute the operation load and provide fan-out capabilities to minimize network load. The Proxy Controller can also be used to provide a network presence behind a firewall or to provide access to a private network.

A Proxy Controller links the managed assets to the Enterprise Controller and performs operations that must be located close to the managed assets, such as operating system provisioning. Proxy Controller performs management operations on assets and reports the results to the Enterprise Controller. The actions required to manage, provision, and update assets are handled as a queue of jobs.

You must have at least one Proxy Controller. When you install the Enterprise Controller, a Proxy Controller is automatically installed on the same system. To enhance performance and scalability, the preferred method is to install the Proxy Controllers on separate machines.

Most sites benefit from using multiple Proxy Controllers. The following are some reasons for using multiple Proxy Controllers:

- Some assets are in remote locations and you want to maintain performance.

- You anticipate creating multiple jobs to run concurrently.

- Some assets are behind a firewall and need their own Proxy Controller.

- To provision Oracle Solaris 10 or Linux with ISO boot, you will need a local Proxy Controller. To provision Oracle Solaris 11 SPARC or Oracle Solaris 10 SPARC with Solaris Flash archive, you can use WAN boot to provision the operating system on a wide area network.

- You can designate a Proxy Controller for the Management Network and another Proxy Controller for the Data Network.

Agent Controllers

Physical and virtual Oracle Solaris and Oracle Linux operating systems require agent software to perform many functions, such as creating update reports, creating and using system catalogs, and managing Oracle Solaris 9, 10 and 11 boot environments. Some monitoring and Analytics data also require an agent-managed operating system. However, you can use many of the monitoring and management features without installing an Agent Controller on the operating system.

The Agent Controller is a lightweight Java software that identifies the asset and responds to Proxy Controller. When an operating system is agent-managed, the agent receives the command from its Proxy Controller, performs the required action, and notifies the Proxy Controller of the results. When an operating system is agentlessly managed, the Proxy Controller uses SSH (Secure Shell protocol) to perform tasks and to monitor the operating system. You can change the method of managing an operating system asset.

Hardware management does not require the Agent Controller. Instead, a Proxy Controller runs commands on the hardware system and reports the results to the Enterprise Controller.

Product Design

To fully understand the best approach to a deployment, it is important to understand how the product uses resources and under what use conditions.

Ops Center provides such a wide range of potential use cases that it is difficult to provide an accurate and simple answer about how far a particular product deployment can scale.

Ops Center is designed around two key design models:

1. A distributed state machine. Maintains the information about all of the managed assets and what can be done to the assets under Enterprise Manager Ops Center's control. This state machine is incremented by discovering new assets, adding new services or metrics to the machine or creating new logical groups of assets. The state machine size is decreased by deleting assets. Each modification of a variable, for example a CPU utilization measure, causes a change in the state machine.

2. An asynchronous job dispatch system. All actions that are requested through the Ops Center console are dispatched asynchronously through the system. The job system has a throttle that prevents the overloading of the system and manages queues of pending jobs.

Enterprise Manager Ops Center's State Machine

Enterprise Manager Ops Center's state machine is maintained in a combination of memory and database. As the managed environment of assets increase, so will the resource utilization (mostly in terms of memory required) of the system.

The diagram above shows a simple deployment of Enterprise Manager Ops Center. Each component of Enterprise Manager Ops Center manages part of the state machine. A basic Agent will add the asset information for the operating system being managed and insert all of the relevant metrics, data, and operations that are supported as part of a discovery action. This part of the state machine is then pushed up to the Proxy Controller, which manages the part of the state machine for all of the assets it is managing and ultimately up to the Enterprise Controller, which can see the entire state machine.

The state machine imparts the highest load on the managed systems during discovery actions. Every part of the system is involved, beginning with the initial location of the asset by way of network requests to the addition of the asset into the state machine, through to the propagation and automated correlation of the new asset in the Enterprise Controller.

Steady state operation of the state machine involves the changing of metrics on the assets themselves. For example, an operating system's asset will have metrics showing network I/O utilization; these are sampled periodically by the Agent from the operating system and updated into the state machine on the Agent. The Agent caches to the state machine, per policy updates, and then sends the updates up to the Proxy Controller. The Proxy Controller follows a similar process up to the Enterprise Controller. The network load in steady state is very low because only changes to metrics are sent and connection management caching is in place to reduce the SSL handshake overhead between the tiers.

The browser user interface reflects a view of the state machine. Assets and their relationships as they exist in the state machine are displayed in the navigation panels, details of the assets are displayed in the center panels and actions associated with the assets are displayed in the Action panel. The Enterprise Controller manages the translation of data from the state machine into a form the browser can display. Viewing different assets or asset groups can place a processing load on the Enterprise Controller. Each user performing these actions in parallel will increase the processing load on the Enterprise Controller. In addition, a small amount of memory is dedicated to each user session.

The Job Management System

The job management system performs actions that are requested by the user. The job management system is completely asynchronous and active jobs are capped and queued to manage resource utilization by the entire Ops Center system.

Depending on the particular action, job actions can run on the agent, the Proxy Controller, or the Enterprise Controller, or a combination of all three. For example, an OS provisioning job is managed from the Proxy Controller that is managing the system that is the target of the action. The Proxy Controller will run the majority of the processes during such an action and will impart the majority of the CPU load that is used during such an action.

The Agent Controller on the hosting operating system executes the software patch install on the operating system. The agent performs all of the requests required to fulfill the required action and imparts a minor CPU load on the host through job completion.

High Availability

The design for a High Availability (HA) architecture must consider all single points of failure, such as power, storage, and network connectivity in addition to the software.

See the Related Resources for Product Architecture section for configuration options for high availability.

Related Resources for Product Architecture

For more information about managing an Enterprise Controller HA configuration, see the Oracle Enterprise Manager Ops Center Administration Guide.

The Oracle Enterprise Manager Ops Center Ports and Protocols Guide provides details on the communication direction, protocol and port, and the purpose for each level of communication.

2 Resource Utilization

This chapter describes how different use patterns affect resource utilization.

This chapter includes the following sections:

- Use Patterns

- Use Pattern Categories

- Related Resources for Resource Utilization

Use Patterns

Enterprise Manager Ops Center is designed to support an increasing number of administration and management actions.

Each type of action and management analysis impacts resource utilization on the underlying systems that support the Enterprise Manager Ops Center deployment. The management features that are used throughout a deployment will greatly affect the resource utilization and the demands of Enterprise Manager Ops Center on its host systems. It is therefore critical to understand the types of management activities to be conducted by Enterprise Manager Ops Center, as this will greatly affect the number of assets a deployment can manage.

Which services are enabled is often related to the Enterprise Manager Ops Center deployment model. For example, deploying an Agent to an Oracle Solaris 10 OS system will automatically enable virtualization management for Oracle Solaris Zones, which in turn increases the size of the state machine for that particular managed asset.

Use Pattern Categories

To simplify deployment, the following five use patterns are identified and compared:

- Hardware Management: Management of server and chassis hardware through Enterprise Manager Ops Center.

- Hardware and OS Provisioning: Management of server and chassis hardware and the ability to provision operating systems to the managed hardware.

- Hardware, OS, and Update Management: Management of hardware, operating systems and deploying software updates to the operating systems.

- Hardware and OS Virtualization: Management of hardware, operating systems, and virtualization features of Oracle Solaris 10 and 11.

- All Management Features

Hardware Management

Hardware management is performed from the Proxy Controller through the systems management Ethernet port on the servers or chassis. In this mode the majority of the utilization occurs at the proxy, which is responsible for performing initial discovery of the hardware and subsequent polling of the hardware for status and configuration changes.

Network sessions are initiated directly from the Proxy Controller to the hardware using specific server and chassis-type protocols that include, IPMI, SSH and SNMP.

Hardware management has a relatively low resource impact on the Enterprise Manager Ops Center host OS. The largest impact is on the network traffic emanating from the Proxy Controller to the target servers and the Proxy Controllers should be scaled appropriately.

Hardware and OS Provisioning

Agents are not deployed for OS provisioning or pure hardware management, as no operating systems are being managed. OS provisioning is an action taken on managed servers and is executed primarily from the Enterprise Manager Ops Center Proxy Controller. The number of OS provisioning jobs that can occur in parallel is metered by the job management system, but OS provisioning does impart a greater load on the infrastructure.

Hardware, OS, and Update Management

This mode applies to Oracle Solaris 8, Oracle Solaris 9, and Linux-managed operating systems. Oracle Solaris 10 and 11 operating systems implicitly enable virtualization management. In this use pattern, Agents are deployed to the managed operating systems and update / software provisioning jobs can be completed. This increases the size of the state machine, as operating systems and their configuration are modeled and made available to the update and monitoring capabilities of Enterprise Manager Ops Center.

Hardware and OS Virtualization

Oracle Solaris 10 and 11 Management adds in sophisticated virtualization management for Oracle Solaris Zones and Oracle VM Server for SPARC. Managing these virtualization features involves exposing significantly greater operating system configuration and metrics to the state machine. This will increase the memory utilization at the Enterprise and Proxy Controller tiers. Oracle VM Manager for x86 requires the deployment of an Oracle VM Server x86 management environment. This does not add as much load as the Oracle Solaris technologies as the Oracle VM management infrastructure is managing much of the scale load.

All Management Features

Using all management features of Enterprise Manager Ops Center will place the largest resource utilization burden on Enterprise Manager Ops Center's host infrastructure. It is recommended that you only configure and use the co-located Proxy Controller for small installations or test environments. For any moderate sized or larger production environment, deploy one or more remote Proxy Controllers.

Related Resources for Resource Utilization

Our documentation library includes installation guides, an administration guide, reference materials, and examples to guide you through Oracle Enterprise Manager Ops Center. The documentation library is located at http://docs.oracle.com/cd/E59957_01/index.htm.

For end-to-end examples, see the workflows and how to documentation in the library. For deployment tasks, go to http://docs.oracle.com/cd/E59957_01/nav/deploy.htm and for operate tasks go to http://docs.oracle.com/cd/E59957_01/nav/operate.htm.

The Oracle Enterprise Manager Ops Center Command Line Interface Guide contains information about the command-line interface.

For current discussions, see the product blog at https://blogs.oracle.com/opscenter.

3 Scaling and Performance Guidelines

Many factors can affect the resources used by Oracle Enterprise Manager Ops Center, and ultimately its ability to scale to manage large deployments.

This chapter includes the following sections:

- Introduction to Scaling and Performance

- Enterprise Controller Considerations and Requirements

- Proxy Controller Considerations

- Virtualization Controller Considerations

- Agent Controller Considerations

- Management Repository Considerations

- Network Considerations

- Storage Library Considerations

- Disk Considerations

- ZFS ARC Size Considerations

- Oracle VM Server for SPARC Provisioning Considerations

- ZFS Storage Appliance Considerations

- User Interface Considerations

- Determine the Number of Asset Access Points

- Related Resources for Scaling

Agent Controller Considerations

By default, the Agent Controller heap size is set to 1 GB. If an Agent Controller is not being used for virtualization, you can reduce this heap size to save resources on the managed system. If you later want to use such a system for virtualization, you should increase the heap size.

You can run the OCDoctor script with the --troubleshoot option to check the current heap usage.

An Agent Controller requires a minimum of 512 MB of RAM.

Checking the Agent Controller Heap Usage

You can check the current heap usage on an Agent Controller system using the OCDoctor.

1. Log in to the managed system.

2. Run the /var/opt/sun/xvm/OCDoctor/OCDoctor.sh script with the --troubleshoot option. An analysis of the current Agent Controller heap usage is displayed.
For example, on a system using over 90% of its heap size:

WARNING: Agent heap stats: configured: 1024MB  max. usable: 980MB  currently used: 925MB  percentage used: 94%
WARNING:
WARNING: The heap usage is above 90% of the maximum usable size!
WARNING:
WARNING: To increase the maximum allowed heap size, you could use e.g. the following command:
WARNING:
WARNING: /var/opt/sun/xvm/OCDoctor/toolbox/changeXmxValue.sh 2048 m agent
WARNING:

On a system using less than 10% of its heap size:

INFO: Agent heap stats: configured: 1024MB max. usable: 980MB currently used: 41MB percentage used: 4%
INFO:
INFO: The heap usage is below 5%.
INFO:
INFO: If desired, you can reduce the maximum allowed heap size by running e.g. the following command:
INFO:
INFO: /var/opt/sun/xvm/OCDoctor/toolbox/changeXmxValue.sh 256 m agent
INFO:

Changing the Agent Controller Heap Size

You can use the OCDoctor's /var/opt/sun/xvm/OCDoctor/toolbox/changeXmxValue.sh script to change an Agent Controller's heap size.

1. Log in to the managed system.

2. Run the /var/opt/sun/xvm/OCDoctor/toolbox/changeXmxValue.sh script to specify the new heap size.
For example, to set the heap size to 256 MB:

/var/opt/sun/xvm/OCDoctor/toolbox/changeXmxValue.sh 256 m agent

Maintaining Agent Access to Large Numbers of LUNs

When working with agents that access several thousand LUNs, the timeout for fetching all the LUNs can be exceeded.

If the storage tab of an agent does not display all the LUNs, verify that the agent is able to see the LUNs by logging onto the agent system and running the following command: #mpathadm list lu

If this command lists the expected LUNs, but these LUNs do not appear in the storage tab of the agent, create a file /opt/sun/n1gc/etc/xvmluinfo.properties on the agent system. In this file, add the following line: timeout=1000

Storage Library Considerations

If you are using Dynamic Storage Libraries containing thousands of LUNs (a few thousand LUNs), in some cases not all LUNs are retrieved correctly.

If some LUNs are not displayed in the dynamic library, open the proxy logs in the /var/cacao/instances/scn-proxy/logs directory and check for the following message: "unable to fetch storage element info.”

If this message exists in the logs, this situation may be resolved by opening the /opt/sun/n1gc/lib/XVM_PROXY.properties file, changing the value of the storage.driver.pagination.size property to 100, and restarting the proxy. Allow some time for the LUNs to be fetched.

ZFS ARC Size Considerations

In some Oracle Solaris 11 configurations, ZFS ARC can consume all available memory even when it should be released. You can limit the size of the ZFS ARC cache to prevent this issue.

Use this formula to determine the recommended ZFS ARC cache size:

ZFS ARC cache = (Physical memory - Enterprise Controller heap size - Database memory) x 70%

Once you have the size, you can set it by changing the value of the zfs_arc_max property in a system file. On Oracle Solaris 11.0 or 11.1, edit the /etc/system file. On Oracle Solaris 11.2 or higher, edit the configuration file in the /etc/system.d directory.

Oracle VM Server for SPARC Provisioning Considerations

If you plan to provision multiple Oracle VM Server for SPARC guests in parallel, the default number of threads configured by the pkg depot may be too low to manage all of the jobs. You can avoid this issue by increasing the number of threads configured by the depot to 500.

ZFS Storage Appliance Considerations

When discovering and managing a ZFS Storage Appliance, Ops Center can work with one of two drivers: a StorageConnect driver (which uses the StorageConnect API to communicate with the appliance) or an OpsCenter Driver (which mostly uses the RESTful API and also some SSH API). In the ZFS appliance discovery profile, you select which driver is used.

When the ZFS appliance is serving a large amount of shares (typically a few thousand LUNs) then using the StorageConnect API frequently fails. This can be verified by observing the string "list index out of range" in the logs on the proxy. The proxy logs are located in the /var/cacao/instances/scn-proxy/logs directory.

In such a case, using the OpsCenter driver often helps. If the discovery failed when using the StorageConnect driver and the above string appears in the logs, you can try to edit the discovery profile to use the OpsCenter driver, and re-discover the appliance. Alternatively, if the appliance was discovered using StorageConnect, you can "Switch Driver" to the OpsCenter driver from the actions pane.

Note:
The OpsCenter driver can only work with ZFS appliances with version 2013.1.2 or above.

User Interface Considerations

In environments with large numbers of assets, the automatic display of the asset hierarchy in the navigation pane and the display of the membership graph showing the relationship between managed assets can cause the user interface to respond slowly. You can disable the automatic asset tree expansion and the membership graph to improve performance.

Disabling Automatic Asset Tree Expansion

You can disable automatic asset tree expansion. The asset tree in the navigation pane will not be automatically expanded.

1. Log in to the user interface.

2. In the upper right section of the UI, click Setup.

3. Under My Preferences, select User Interface Preferences.

4. Under the Display Preferences heading, an option for displaying nodes in the asset tree is displayed. Select Collapsed.

5. Click Submit.

Disabling the Membership Graph

You can disable the membership graph. The membership graph will not be displayed for selected assets.

1. Log in to the user interface.

2. In the upper right section of the UI, click Setup.

3. Under My Preferences, select Membership Graph Preferences.

4. Deselect the Show Graphs option.

5. Click Submit.

Introduction to Scaling and Performance

You can scale Oracle Enterprise Manager Ops Center to accommodate a variety of environments. However, the size and layout of your environment can effect the number of Enterprise Controllers and Proxy Controllers that you require. The scaling guidelines provided here are based on the use of an external repository and are minimum required parameters.

For sizing purposes, the following are defined as assets:

- Servers, including the service processor and operating system

- Switches

- Storage devices

- Non-global zones

- Logical domains

- Chassis

- Oracle SPARC Enterprise M-Series chassis

- Oracle SPARC Enterprise M-Series domains

- Oracle Exadata Storage Server X2-2 cells

See Determine the Number of Asset Access Points for how to run a script on the Enterprise Controller to determine the number and type of assets on each Proxy Controller and the total number of assets on the Enterprise Controller.

Enterprise Controller Considerations and Requirements

Consider the following factors when selecting a platform for the Enterprise Controller:

- System: The Enterprise Controller has many parallel executing processes and a multi-core system will significantly improve performance. There are some processes that are by their nature single threaded and benefit from higher clock speed. It is recommended to choose a process that is both multi -core and has a high single thread CPU speed.

Note:

Do not install the Enterprise Controller on a hardened system. The installation will complete successfully, but you will encounter several issues when you use the software.

- Memory: The core JVM machine consumes memory and its resource utilization will increase with the number of assets being managed. If the Java virtual machine is forced into virtual memory, then Enterprise Manager Ops Center performance will reduce significantly.

- Database: A database is present in Ops Center and a high performing disk I/O is important in the implementation. Generally, disk striping or the use of a well configured high performing file system with such features built in, such as ZFS, is highly recommended. See Management Repository Considerations for information on database sizing.

- Operating system: While not a scaling issue, the system must be running on a version of Oracle Solaris 11 if you plan on using Oracle Enterprise Manager Ops Center to manage Oracle Solaris 11 Operating Systems or virtualized environments, or if you plan on discovering and managing Oracle SuperCluster and other Oracle engineered systems. Because Oracle SuperCluster uses Oracle Solaris 11, you must install your Enterprise Controller on Oracle Solaris 11 if you plan to manage Oracle SuperCluster.

Note:

It is recommended that you use Oracle Solaris 11.2 or higher for the Enterprise Controller operating system.

- Network: Start-up times of the Enterprise Controller can be minimized by ensuring that the network link to the repository is as low latency as possible. The start-up process involves a large number of queries as the state machine is being built. It is recommended that a 10 GigE connection be available between the Enterprise Controller and Management Repository.
For a remote customer-managed database, set up the network according to the Oracle database networking setup defined in the Oracle Server Installation Guide. See the Related Resources for Scaling section for more information about database requirements. See Management Repository Considerations for more information on database considerations.

An Enterprise Controller can manage up to 3,000 mixed assets including hardware, operating systems, virtualization technologies, and other assets. Deployments above 1,000 assets might require you to tune your Java Virtual Machine (JVM) heap size.

An Enterprise Controller system must meet the following minimum requirements:

- Oracle SPARC or x86 platform that is running a supported Oracle Solaris or Linux OS, such as Oracle Solaris 11

- 200 GB of disk space
Memory Settings

- 12 GB if the Enterprise Controller uses an embedded database

- 6 GB if the Enterprise Controller uses a customer-managed database

- Swap space for embedded database

- Equal to physical memory if the physical memory is less than 16 GB

- 16 GB if the physical memory is greater than 16 GB

- Swap space for remote database

- 12 GB minus the amount of physical memory (swap is required if this number is <=0)

Changing the Database Fetch Size

In large environments, the default database fetch size can be too small, causing the Enterprise Controller to start slowly. If your Enterprise Controller is slow to start, you can increase the fetch size in the user interface.

1. Expand the Administration section in the Navigation pane, then click Enterprise Controller.

2. Click the Configuration tab.

3. Select EC Manager from the Subsystem menu.

4. Edit the persistent.cached.manager.ec.connection.prefetch.size variable.
A value of 10,000 is sufficient for most large environments. Do not increase the variable beyond 30,000.

5. Restart the Enterprise Controller.

Proxy Controller Considerations

Consider the following factors when selecting a platform and environment for the Proxy Controller:

- Operating system: To provision and update Oracle Solaris 11 operating systems, the Enterprise Controller and Proxy Controller must be installed on at least Oracle Solaris 11.1 operating system.

- Global or non-global zone: If the assets being managed are Oracle Solaris 11, you can configure the Proxy Controllers in a global or non-global zone. Otherwise, install the Proxy Controllers in global zones. A Proxy Controller includes the capability to perform OS provisioning, which is not supported by Oracle Solaris 10 non-global zones.

- Network I/O: If the Proxy Controller is supporting Operating System provisioning then it is recommended that the Proxy Controller should be utilizing GigE network cards or higher.

Consider installing additional Proxy Controllers, beyond the minimum requirements, in environments with the following characteristics:

- Remote datacenters: If some of your assets are in a remote location, installing a Proxy Controller in that location can reduce network latency and cache Oracle Enterprise Manager Ops Center content closer to the assets.

- Deployment through firewalls: If you have firewalls between your Enterprise Controller and some managed assets, having a Proxy Controller near the assets can simplify deployment and management.

- High Availability: Installing additional Proxy Controllers gives you the ability to migrate assets between Proxy Controllers for maintenance or if a Proxy Controller fails.

- Virtualization: If you intend to manage virtualization technologies like Oracle VM Servers for SPARC, additional Proxy Controllers help handle the added asset and job load.

The software is supported on a wide variety of hardware, operating systems, and virtualization technologies. See the Oracle Enterprise Manager Ops Center Certified Systems Matrix for a list of certified systems.

Each Proxy Controller can manage up to 500 assets. Installing additional Proxy Controllers beyond the requirements is beneficial in some environments.

A Proxy Controller system must meet the following minimum requirements:

- Oracle SPARC or x86 platform that is running a supported Oracle Solaris or Linux OS, such as Oracle Solaris 11

- 1.5 GB of disk space

- 6 GB Swap space

- 8 GB Memory

- 2 GB Java Heap size, defined by -Xmx in the java-flags

It is generally recommended that you use proxy fan out as it makes sense in the network to be deployed. For example, OS provisioning capabilities are often restricted to a network subnet.

Changing the resource configuration of the system will affect the numbers, as will more complex mixing of the services across the deployment.

Virtualization Controller Considerations

An agent on an Oracle Solaris Zone Virtualization Controller installed on a system with one (1) processor and 128 GB of memory can manage with a good level of performance:

- 50 non-global zones with one (1) filesystem configured on each non-global zone.

- 15 non-global zones with 20 filesystems configured on each non-global zone.

An agent on an Oracle VM Server for SPARC Virtualization Controller installed on a system with one (1) processor and 128 GB of memory can manage, with a good level of performance, 20 logical domains with 25 disks (LUNs) configured on each domain.

For both configurations described above, the agent deployment time will take less than one hour and the restart time will be about 15 minutes. The CPU consumption of the agent should not exceed 5 percent.

Management Repository Considerations

Oracle Enterprise Manager Ops Center stores product data in an Oracle Database Enterprise Edition database. This database can be an embedded database installed on the same system as the Enterprise Controller, or a customer-managed database that is accessible to the Enterprise Controller system. Run the OCDoctor to check for basic database requirements.

A backup feature enables you to back up your environment. The backup feature supports an embedded or customer-managed database. If you are using a customer-managed database, you can also back up the database schema using the existing backup and recovery processes implemented by your database administrator.

Note:

If you plan to implement high availability for the Enterprise Controller, you must use a customer-managed database.

Use the following sizing guidelines to estimate the maximum size of the database based upon the number of assets managed:

- Operational Data: 74 megabytes (MB) per asset.

- Reporting Data: 166 MB per asset. Steady state is reached at 180 days when using the default rollup schedule. USERS tablespace (Reporting) is required when report attributes are enabled. Use one of the following methods to change the size of the reporting data:

- Customize the amount of attributes shown in the Enterprise Controller.

- Stop the report service, which will stop generating report data in the database.

See Report Service Configuration Properties for more information about the report service.

- UCE Data: 4 gigabytes (GB) needed for 10 channels. 12 GB additional for disconnected mode. You will generally need 400 megabits (Mb) for each additional channel. In some cases, you might need up to 600 Mb for a channel.
Oracle Solaris and Linux operating system updates and provisioning use UCE data. A channel, or UCE channel, is a supported Oracle Solaris or Linux operating system distribution, such as an Oracle Solaris 10 on a SPARC platform.

- Schema Backups: Each backup dump requires 40% of Enterprise Manager Ops Center Schema Size on the database server in the OC_DUMP_DIR directory location.

- Embedded, or Ops Center Local, database: A maximum of seven (7) copies of the backup are kept online.

- Customer managed database: The database administrator must manage the Oracle Enterprise Manager Ops Center dump directory backup content.

- Archival: An embedded database does not run in archive mode. For a remote database running in archive mode, the size of the archive is set according to the redo logs size.

Table 3-1 shows the estimated database size for when 1000 assets and 100 assets are managed and 10 UCE channels are configured in connected mode.

Table 3-1 Estimated Database Size

Use Pattern

Size for 1000 Assets (MB)

Size for 100 Assets (MB)

SYSTEM tablespace

1000

1000

UNDO tablespace

2750

275

SYSAUX

1200

1200

USERS tablespace (Operational)

100000 (100 GB)

10000 (10 GB)

USERS tablespace (Reporting)

230000 (230 GB)

23000 (23 GB)

USERS tablespace (UCE)

4000

4000

TEMP

2000

200

TOTAL DB Size

340950

39675

Spaced Reserved for Backups

954660

103600

The database size also depends on your retention policy of gathered data. The default retention is 180 days for a 24 hour sample.

Embedded Database

When using an embedded (Ops Center local) database, the Enterprise Controller system must meet the requirements for an Oracle Database Enterprise Edition installation. You can improve the embedded database performance by using the following configuration:

- Use the ZFS filesystem as your underlying database

- Set the redo log files to a block size of 8K

- Set the logbias=throughput

Separating the redo logs onto a separate zpool (a different underlying disk) will further improve the embedded database performance.

On Oracle Solaris 10 1/13 systems and Oracle Solaris 11 SRU 7.5 or later systems, the embedded database is Oracle Database 12c. Oracle Database 12c uses the Optimized Shared Memory (OSM) model of Oracle Solaris to implement Automatic Memory Management. OSM allows dynamic resizing of System Global Area (SGA) without restarting the instance.

On Oracle Solaris 10 systems prior to Oracle Solaris 10 1/13 and Oracle Solaris 11 SRU 7.5, Dynamic Intimate Shared Memory (DISM) allows a database to dynamically extend or reduce the size of the shared data segment. The embedded database is configured to use a minimum of 12 GB RAM using DISM (TOTALMEMORY in the response file.)

See the Related Resources for Scaling section for information about local database requirements.

Customer-Managed Database

You can use a customer-managed, or remote, Oracle database with Oracle Enterprise Manager Ops Center.

A remote database system must use a supported Oracle Database version. See the Related Resources for Scaling section for a list of supported database versions.

The network connection to the remote database should have a low latency.

Note:

If you are implementing high availability, the remote database system must be accessible for all of the Enterprise Controller nodes.

The recommended database memory size is 12 GB.

The following are the minimum initialization parameters to use when you create the database:

- open_cursors=1000

- pga_aggregate_target=0

- processes=500

- recyclebin=OFF

- sga_target=0

See the Related Resources for Scaling section for detailed database requirements.

Network Considerations

When using a remote database, the network connection to the remote database should have a low latency.

For Ethernet connectivity, it is recommended that the network you are planning to use to conduct OS provisioning across be 1/10GB capable.

If your site uses VLAN, a best practice is to create a separate VLAN for management networks.

Disk Considerations

In a mirror setup, you need two (2) disks with following minimum disk space:

- In the active and running boot environment:

- /var: 85GB for the Enterprise Controller and Proxy Controller run time

- /: 30GB for the Enterprise Controller and Proxy Controller install and data

- Enterprise Controller Libraries

- 15 GB for the EC library

- 45 GB for the Oracle Solaris 11 Software Update Library

- 5 GB per channel for the Linux, Solaris 8-10 Software Update Library

- Database
See Table 3-1 for database sizing. The following is an example estimated database size for 400 assets: 160 GB for the database plus 400 GB reserved for backups

Sufficient storage disk space is critical in optimizing performance.

The following configurations are applicable for a SPARC platform:

- The OS disk configuration is on a Fibre Channel hardware RAID.

- The Oracle Enterprise Manager Ops Center data is on a Fibre Channel hardware RAID.

The following are recommended disk configurations:

- Place the /var/opt/sun/xvm directory on a different set of disk spindles from the operating system. Do not co-mingle with the OS.

- Use at least 4 spindles in the hardware RAID cache configuration.

- Place the OS on multiple spindles with hardware RAID cache. If the hardware does not allow this with internal drives, then boot from SAN

The Proxy Controller software is considered relatively lightweight and, in all but the extreme scale cases, does not require a dedicated system.

The following configurations are applicable for SPARC platforms:

- The OS disk configuration is on a Fibre Channel hardware RAID.

- The Oracle Enterprise Manager Ops Center data is on a Fibre Channel hardware RAID.

Determine the Number of Asset Access Points

An access point is a connection between a managed asset and the Enterprise Controller through a Proxy Controller. The number of access points for the Enterprise Controller and for each Proxy Controller provides more accurate scaling information than the number of assets.

A single managed asset can have one or more access points, depending on how many Proxy Controllers are managing it. For example, if an Oracle VM Server for SPARC control domain's operating system is managed by one Proxy Controller while a hosted logical domain's operating system is managed by another Proxy Controller, the Enterprise Controller has two access points for that asset.

The OCDoctor utility includes a script, AssetCount.sh, that you can run on the Enterprise Controller to get the current access point count for the Enterprise Controller and each Proxy Controller, including a breakdown of the type of assets on each Proxy Controller.

When the OCDoctor utility is run with the --troubleshoot option, it performs an access point count. If the results of this count indicate that the Enterprise Controller or Proxy Controllers are approaching or beyond the maximum recommended number of assets, the output will include a warning.

When you run the ./OCDoctor.sh --collectlogs command on the Enterprise Controller, the current access point count is included in the output. The current access point count can be useful when troubleshooting an issue.

The following methods can be used to view the access point count:

- Viewing the Access Point Count for Your Environment

- Viewing the Access Point List for Each Proxy Controller

- Viewing the Access Point Types for Each Proxy Controller

- Viewing All Access Point Data

- Viewing the Asset Count in the User Interface

Viewing the Access Point Count for Your Environment

You can view the total number of access points managed by the Enterprise Controller, as well as a categorized count of the access points managed by each Proxy Controller. Run the following command on the Enterprise Controller:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh standard

For example:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh standard
EC 72
Proxy Assets Zones Ldoms OVMGuests Servers Storages Switches ExadataCells MSeriesChassis MSeriesD
-------------------------------------------------------------------------------------------------
pc4   32     5     25    0         2       0        0        0            0              0
pc1   28     0     26    0         2       0        0        0            0              0
pc0   12     2     4     0         6       0        0        0            0              0
Use option '-v' to see additional notes on the counting algorithm.

Viewing the Access Point List for Each Proxy Controller

You can view a list of the access points of each type that are managed by each Proxy Controller. The output first provides the total number of access points on the Enterprise Controller, then for each Proxy Controller provides the total number of access points, the number of access points of each type, and the user-friendly name for each asset.

The output for this command can be very long in a large environment.

Run the following command on the Enterprise Controller:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh machine

For example:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh machine
EC 72
Proxy 32 pc4
Zones 5 S11zone101 S11zone102 S11zone100 S11zone103 S11zone104
Ldoms 25 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ...
OVMGuests 0
Servers 2 10.187.70.169 pc4
...
Proxy 28 pc1
Zones 0
Ldoms 26 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ...
OVMGuests 0
Servers 2 10.187.70.171 pc1

Viewing the Access Point Types for Each Proxy Controller

You can view a count of the access points for each Proxy Controller in three categories: Agent Controllers, Agentless assets, and service processors.

Run the following command on the Enterprise Controller:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh agent

For example:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh agent
EC 72
Proxy Agents Agentless SPs
--------------------------
pc4   25     2         0
pc1   1      1         0
pc0   5      5         5
Use option '-v' to see additional notes on the counting algorithm.

Viewing All Access Point Data

You can view all access point data, including the results of the standard, machine, and agent options.

Run the following command on the Enterprise Controller:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh all

For example:

# /var/opt/sun/xvm/OCDoctor/toolbox/AssetCount.sh all
EC 72
Proxy Assets Zones Ldoms OVMGuests Servers Storages Switches ExadataCells MSeriesChassis MSeriesD
-------------------------------------------------------------------------------------------------
pc4   32     5     25    0         2       0        0        0            0              0
pc1   28     0     26    0         2       0        0        0            0              0
pc0   12     2     4     0         6       0        0        0            0              0

Proxy Agents Agentless SPs
--------------------------
pc4   25     2         0
pc1   1      1         0
pc0   5      5         5

Proxy 32 pc4
Zones 5 S11zone101 S11zone102 S11zone100 S11zone103 S11zone104
Ldoms 25 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ...
OVMGuests 0
Servers 2 10.187.70.169 pc4
...
Proxy 28 pc1
Zones 0
Ldoms 26 stdldom21 stdldom34 stdldom36 stdldom22 stdldom45 stdldom47 ...
OVMGuests 0
Servers 2 10.187.70.171 pc1

Use option '-v' to see additional notes on the counting algorithm.

Viewing the Asset Count in the User Interface

You can view the asset count through the user interface.

1. Select the Administration section in the Navigation pane.

2. Select the Enterprise Controller.

3. Click the Asset Counter tab in the center pane.
The Asset Counter tab contains a table for the Enterprise Controller with the total number of each type of asset and a table that shows the number of assets managed by each Proxy Controller .

Figure 3-1 Asset Counter Tab

4. (Optional) If you are interested in the number of asset of a specific Proxy Controller, select the Proxy Controller from the Administration section in the Navigation pane and then click the Asset Counter tab.

The number represents the number of access points reported by each Proxy Controller.
You can refresh the display by selecting Run Asset Counter Job in the Action pane. If the Enterprise Controller has just been installed, or if new assets have recently been added, you can use this action to update the count.

Related Resources for Scaling

For more information, see the Oracle Enterprise Manager Ops Center Documentation Library at http://docs.oracle.com/cd/E59957_01/index.htm.

See the Oracle Enterprise Manager Ops Center Installation for Oracle Solaris Operating System Guide or the Oracle Enterprise Manager Ops Center Installation for Linux Operating Systems Guide for information about local database requirements.

See the Oracle Enterprise Manager Ops Center Administration Guide for more information about the OCDoctor, including tuning and troubleshooting options. The OCDoctor will print a WARNING if the Asset Count of an EC or Proxy has reached or exceeded the maximum recommended value.

See the Oracle Enterprise Manager Ops Center Certified Systems Matrix for a list of supported Oracle Database versions.

See the Oracle Database Enterprise Edition documentation at http://www.oracle.com/technetwork/database/enterprise-edition/documentation/index.html for detailed database requirements.

For current discussions, see the product blog at https://blogs.oracle.com/opscenter.

4 Reference Systems

Scalability figures are based on systems that run an Oracle Solaris 11.2 operating system. Memory access is affected by DIMM count and placement, therefore these configurations include the maximum number of DIMMs of lowest density available to achieve the best possible memory access times.

Any departure from the stated specifications might have a measurable effect on the overall performance and scalability of the reference configurations.

This chapter includes the following sections:

- Enterprise Controller

- Proxy Controller

Enterprise Controller

The following are the minimum reference system specifications for the Enterprise Controller to support up to 3,000 assets. This reference system assumes that Oracle Solaris 11 and one other Oracle Solaris OS will be used.

Note:

If you are using Oracle VM Server for SPARC, it is recommended to use version 3.1.1 or higher.

- CPU count: 8 virtual processors (as seen by psrinfo -pv)

- CPU speed: 2.6Ghz

- Disk: 200 GB

- Swap:

- Double the physical memory if the physical memory is less than 16 GB

- 16 GB if the physical memory is greater than 16 GB

- Memory:

- 24 GB if the Enterprise Controller uses the embedded database

- 16 GB if the Enterprise Controller uses a customer-managed database

The following is the 8 drive configuration reference storage for Internal or FC/SAN Storage:

- Volume 1: OS root, swap, and dump:

- Hardware RAID 10 (1+0) for redundancy and performance

- 4 x 300 GB Disks @ 10,000 RPM

- 600 GB Volume, 600 GB LUN (whole Volume)

- Volume 2: Enterprise Manager Ops Center Shared Data and Local Libraries:

- Hardware RAID 10 (1+0) for redundancy and performance

- 4 x 300 GB @ 10,000 RPM

- 600 GB Volume, 600 GB LUN (whole Volume)

Proxy Controller

The following are the reference system specifications for the Proxy Controller to support from 350 to 450 assets, as defined in Proxy Controller Considerations:

Note:

If you are using Oracle VM Server for SPARC, it is recommended to use version 3.1.1 or higher.

- CPU count: 4 virtual processors (as seen by psrinfo -pv)

- CPU speed: 2.6 Ghz (or above)

- Memory: 8 GB

The following is the reference (6 drive configuration) storage Internal or FC/SAN Storage:

- Volume 1: OS root, swap, and dump:

- ZFS mirror for redundancy

- 2 x 300 GB Disks @ 10,000 RPM

- 300 GB Volume, 300 GB LUN (whole Volume)

- Volume 2: Enterprise Manager Ops Center Shared Data and Local Libraries:

- Hardware RAID 10 (1+0) for redundancy and performance

- 4 x 300 GB @ 10,000 RPM

- 600 GB Volume, 600 GB LUN (whole Volume)

A Report Service Configuration Properties

You can tune the report service retention periods or disable the report service to improve performance.

The following information is covered:

- Default Retention Periods

- Edit Report Service Properties

- Disable the Report Service

- Related Resources for Report Service Configuration

Default Retention Periods

The report service writes to the database every 1000 samples and retains the information for a defined amount of time.

The following are the default retention periods:

- Daily samples (collected every 5 minutes): 5 days (repsvc.daily-samples-retention-days)

- 1 hour samples (weighted average of daily samples for one hour): 21 days (repsvc.1hour-samples-retention-days)

- 12 hour samples (weighted average of daily samples for 12 hours): 42 days (repsvc.12hours-samples-retention-days)

- 24 hour samples (weighted average of daily samples for 24 hours): 180 days (repsvc.24hours-samples-retention-days)

You can tune the report service to write to the database of samples. By default a write is made every 1000 samples. For larger deployments, you might want to increase the number from 1000 samples to a larger sample size.

Edit Report Service Properties

You can configure the retention periods to change the number of days that data is retained, or you can disable the roll up of data.

Perform the following steps to disable the report service:

1. Expand Administration in the Navigation pane.

2. Select the Enterprise Controller.

3. Click the Configuration tab.

4. Select Report Service from the Subsystem menu.

Figure A-1 Report Service Configuration Properties

5. You can edit the following property values:

- To edit the number of days that data is retained, edit the number in the Value field for the sample-retention-days properties.

- To increase the sample size, edit the number in the epsvc.saves-bt-commits field. Larger deployments might want to increase the sample size from the default size of 1000.

- To disable the roll up of data, set the 1 hour samples, 12 hour samples, and 24 hour samples retention times to 0.

6. Click Save to save your changes.

Figure A-2 Save Configuration Property Values

7. Stop and restart the Enterprise Controller.

a. As root, log in to the Enterprise Controller system.

b. Use the ecadm command with the stop subcommand to stop the Enterprise Controller.

c. Use the ecadm command with the start subcommand to start the Enterprise Controller.
See the Related Resources for Report Service Configuration section for more information about viewing and changing the Enterprise Controller status and command options.

Disable the Report Service

You can disable the report service, which will stop adding report data in the database.

Note:

Disabling the report service disables the logging of all monitoring values into the database. The analytics feature, which displays graphs and charts of asset attributes, is disabled. Any feature that depends on monitoring data is also disabled.

Perform the following steps to disable the report service:

1. Go to the /opt/sun/n1gc/lib directory.

2. Edit the XVM_SATELLITE.properties file.

3. Remove the comment from the following line: report.service.disable=true.

4. Stop and restart the Enterprise Controller.

a. As root, log in to the Enterprise Controller system.

b. Use the ecadm command with the stop subcommand to stop the Enterprise Controller.

c. Use the ecadm command with the start subcommand to start the Enterprise Controller.
See the Related Resources for Report Service Configuration section for more information about viewing and changing the Enterprise Controller status and command options.

Related Resources for Report Service Configuration

See the Oracle Enterprise Manager Ops Center Administration Guide for more information about viewing and changing the Enterprise Controller status and command options.

Index

A  C  D  E  H  K  M  N  O  P  R  S  U  V  Z

A

- Access points

- counting assets 1

- Agent Controllers 1

- Architecture 1

- Asset management

- counting 1

- Assets

- counting 1

- definition 1

- determining the number of 1

- maximum supported 1

C

- Counting assets 1

D

- Database

- considerations 1

- customer-managed 1

- embedded 1

- local 1

- remote 1

- sizing 1

- Database configuration

- local 1

- remote 1

- Disk considerations 1

E

- Enterprise Controller

- database 1

- disk space 1

- Java Heap size 1

- memory 1

- minimum requirements 1

- network 1

- operating system 1

- platform considerations 1

- requirements 1

- sizing 1

- swap space 1

- system 1

H

- Heap size 1

K

- Knowledge Base and Package Base Repository 1

M

- Management repository

- considerations 1

N

- Network considerations 1

O

- OCDoctor 1

- Oracle VM Server for SPARC 1

P

- Proxy Controller

- disk space 1

- Java Heap size 1

- multiple 1

- network I/O 1

- operating system 1

- platform 1

- platform considerations 1

- requirements 1

- sizing 1

- swap space 1

- zones 1

R

- Related Resources

- Resource utilization 1

- scaling 1

- Remote database

- sizing 1

S

- Sizing

- Enterprise Controller 1

- local database 1

- Proxy Controller 1

- remote database 1

- SSH (Secure Shell protocol) 1

U

- Use pattern

- Hardware, OS, and update management 1

- Hardware and OS provisioning 1

- Hardware and OS virtualization 1

- Hardware management 1

- Manage all 1

- Use Pattern 1

V

- Virtualization considerations 1

Z

- Zones 1

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2017, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.