Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

This topic presents recommendations and considerations for different size BMC ProactiveNet environments that include data collection, event management, and impact management. Examine the guidelines for each environment to determine which size fits your requirements.

Note

In this environment, the resources are shared between the data collection, event management, and impact management functions. Therefore, assuming comparable hardware in each environment, this environment handles fewer attributes than a dedicated data collection environment, fewer events than a dedicated event management environment, and fewer configuration items than a dedicated impact management environment.

The systems require sufficient memory for the analytical engine component to perform all of the tasks quickly. Most data that it uses is cached in memory so that baseline and abnormality generation on virtually every attribute in the system can be done behind the scenes.

The sizing recommendations for data, event, and impact management are based on tests of a BMC ProactiveNet environment with an embedded Sybase ASA Database.

To view the characteristics of BMC ProactiveNet environments, see Hardware requirements.

Small environment

Consider the following guidelines when planning a small data collection, impact and event management environment:

  • In a small environment, you can collect and analyze from up to 15,000 monitor instances and up to 250,000 attributes.
    Use one BMC ProactiveNet Server and at least two 64-bit BMC ProactiveNet Integration Services as the data collectors. One 64-bit Integration Service can handle up to 7,500 monitor instances and 125,000 attributes.

    Note

    The BMC ProactiveNet Integration Service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

  • Distribute event correlation, deduplication, and normalization on BMC ProactiveNet Remote Cells.
  • Up to 25 concurrent users can be simultaneously logged in and accessing the BMC ProactiveNet Server.
  • If you collect data across networks or firewalls, consider using an Integration Service to minimize the number of connections to manage across the networks or firewalls.
  • (Sybase, only) To improve I/O throughput, use separate disks for the operating system on which BMC ProactiveNet Server is deployed, and the database. Ensure that each disk has its own disk controllers.
  • Configure BMC Atrium CMDB with automated or manual publish modes that send configuration items and relationships to the BMC ProactiveNet Server. For details, see BMC ProactiveNet Service Modeling and Publishing Guide and BMC ProactiveNet Command Line Interface Reference Guide.
  • BMC Atrium CMDB sends configuration items and relationships to the BMC ProactiveNet Server with automated and manual publish modes.

Medium environment

Consider the following guidelines when planning a medium data collection, impact and event management environment:

  • In a medium environment, you can collect and analyze from up to 50,000 monitor instances and up to 500,000 attributes.
    Use one BMC ProactiveNet Server and at least two 64-bit BMC ProactiveNet Integration Services as the data collectors. One 64-bit Integration Service can handle up to 25,000 monitor instances and 250,000 attributes.

    Note

    The BMC ProactiveNet Integration Service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

  • Distribute data collection on Integration Services so that the BMC ProactiveNet Server is dedicated to the primary server processes (analytical engine, object cache, and agent controller). The Self-Monitoring Service, which is automatically installed on the BMC ProactiveNet Server, collects metrics only about the server's performance.
  • If you expect the total number of attributes for the environment to grow beyond 500,000 attributes, use a large-environment deployment so that the system can accommodate growth smoothly.
  • You can deploy the Integration Service on a VM that meets the resource requirements.
  • Configure BMC Atrium CMDB with automated or manual publish modes that send configuration items and relationships to the BMC ProactiveNet Server. For details, see BMC ProactiveNet Service Modeling and Publishing Guide and BMC ProactiveNet Command Line Interface Reference Guide.
  • If you use the BMC PATROL Adapter for data collection, install the Integration Service on a dedicated computer.
  • Publish up to 10,000 configuration items at a time.
  • Configure the BMC Event Adapters on the BMC ProactiveNet Servers to send events. For details, see BMC ProactiveNet Installation and Configuration Guide and BMC Event Adapters User Guide.
  • Distribute event correlation, deduplication, and normalization on BMC ProactiveNet Remote Cells, which send this data to the BMC ProactiveNet Server.
  • BMC Atrium CMDB sends configuration items and relationships to the BMC ProactiveNet Server with automated and manual publish modes.
  • Install BMC Atrium CMDB on a dedicated computer. See BMC Atrium CMDB documentation for hardware requirements.

Large environment

Consider the following guidelines when planning a large data collection and event management environment:

  • In a large environment, you can collect and analyze from up to 100,000 monitor instances and up to 1.2 million attributes.
    Use one BMC ProactiveNet Server and five 64-bit BMC ProactiveNet Integration Services as the data collectors. One 64-bit Integration Service can handle up to 50,000 monitor instances and 500,000 attributes.

    Note

    The BMC ProactiveNet Integration Service on Solaris, whether 32-bit or 64-bit computer, cannot monitor more than 125,000 attributes.

  • Distribute data collection on Integration Services so that the server is dedicated to the primary server processes (analytical engine, object cache, and agent controller). The Self-Monitoring Service, which is automatically installed on the BMC ProactiveNet Server, collects metrics about only BMC ProactiveNet Server performance.
  • For optimum performance, minimize the number of monitors running on the BMC ProactiveNet Server's Self-Monitoring Service.
  • Configure each BMC ProactiveNet Server so that it contains an entire line of business, instead of spreading the monitoring across servers.
  • You can deploy the Integration Service on a VM that meets the resource requirements.
  • If you use the BMC PATROL Adapter for data collection, install the Integration Service on dedicated computers.
  • Publish up to 20,000 configuration items at a time.
  • Configure BMC Atrium CMDB with automated or manual publish modes that send configuration items and relationships to the BMC ProactiveNet Server. For details, see BMC ProactiveNet Service Modeling and Publishing Guide and BMC ProactiveNet Command Line Interface Reference Guide.
  • Install BMC Atrium CMDB on a dedicated computer. See BMC Atrium CMDB documentation for hardware requirements.
  • Install BMC ProactiveNet Remote Cells at each remote location. These remote cells collect events directly from the event sources, filter sympathetic events, and apply normalization and deduplication rules to other events. Only important events are propagated to the event manager of the BMC ProactiveNet Server.
  • Distribute event correlation, deduplication, and normalization on BMC ProactiveNet Remote Cells, which send this data to the BMC ProactiveNet Server.