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

Consult the following topics for guidance on when to deploy multiple BMC TrueSight Infrastructure Management Servers and best practices for deployment:

Multiple Infrastructure Management Server use cases

Multiple server use caseScenario
Capacity and scalability

When a single BMC TrueSight Infrastructure Management Server cannot scale to the requirements for data collection and event management, deploy additional Infrastructure Management servers to manage a portion of the environment for data collection and event management.

For information about how to size the environment, see Sizing and scalability considerations and best practices.

Physical deployment

When you have geographically dispersed data centers, secure zones, or environments with separate access controls.

Development, test, and production environments for agent deployment
Multitenancy

When you have multiple tenants requiring physical segregation of the data. Each Infrastructure Management server is associated with a single tenant only. A specific tenant is associated with the Infrastructure Management Server when the server is registered as a component with the Presentation Server. Each Presentation Server can support up to five tenants.

In a multiple Infrastructure Management server deployment, service providers can designate to which environments the tenants will have access by  registering a tenant for the Presentation Server supporting that environment.

Integrations to the Infrastructure Management server should be dedicated to the environment of the tenant associated with that server.

For information about setting up a multitenant environment, see BMC TrueSight Operations Management service provider and tenant deployment .

Multiple Infrastructure Management server deployment options

You use Central Monitoring Administration to manage BMC PATROL configuration across one or more Infrastructure Management Servers. Central Monitoring Administration is installed with the Presentation Server and launched from the TrueSight console. BMC recommends implementing one of the following architectural deployments for multiple Infrastructure Management servers:

 

Note

All BMC TrueSight Infrastructure Management Server versions must be the same in a single environment. The Infrastructure Management solution cannot support mixed versions of Infrastructure Management Servers and requires the same version of the Presentation Server with Central Monitoring Administration. For more information, see Infrastructure Management interoperability.

Multiple Infrastructure Management Servers connected a single Presentation Server with Central Monitoring Administration

The first option is to implement a single Presentation Server with Central Monitoring Administration for scenarios that require multiple Infrastructure Management Servers, such as multiple tenants or separate environments for development, test, and production.

Pros

  • Creating, testing, and deploying monitoring policies from test into production are very easy because you do not have to copy, export, or import any data. The application of policies to the development, test, and production environments is simply managed in the policy’s agent selection criteria.
  • This option requires fewer infrastructure nodes and components. Only a single  staging Integration Service host is needed, and only a single Central Monitoring Administration instance is used.

Cons

  • This option might not be supported in some sites where all the necessary connections in the development, test, and production or separate tenant environments are not available or allowed to be connected over the network.

  • Due to the powerful ease of use, it is easier for administrators to unintentionally apply policies to production. However, this possibility can be managed.

The following figure illustrates a typical high-level logical architecture for an Infrastructure Management deployment using multiple BMC TrueSight Infrastructure Management Servers connected to a single BMC TrueSight Presentation Server with Central Monitoring Administration.

High-level architecture for multiple-server deployment with a single Presentation Server and Central Monitoring Administration


In the single Central Monitoring Administration architecture, a single staging Integration Service node is used in the agent deployment process for all agents. All Infrastructure Management Servers leverage the single Central Monitoring Administration instance for managing the entire policy.

For the list of ports required in a multiple-server deployment, see Network ports.

Multiple Infrastructure Management Servers connected to multiple Presentation Servers with Central Monitoring Administration

The second option is to implement a separate Presentation Server and Central Monitoring Administration instance in each of the development, test, and production or tenant environments.

Pros

  • This option is supported in sites where all necessary connections in the development, test, and production or tenant environments are not available or allowed to be connected over the network.
  • The option supports policy management methods that help prevent administrators from making mistakes when applying policies to production.

Cons

  • Creating, testing, and deploying monitoring policies into production or across multiple tenant environments requires additional effort because you have to export and import policy data from development to the test environment and from test to the production environments.

  • Policies can get out of sync across development, test, and production environments if not managed properly. Keeping them updated is more of a manual process supported by the export/import utility.

  • This deployment requires additional infrastructure nodes and components. Development, test, and production environments must each have a dedicated staging Integration Service host and a dedicated instance of Central Monitoring Administration.

The following diagram illustrates the high-level architecture for multiple Central Monitoring Administration instances in the development, test, and production environments.

High-level architecture for multiple-server deployment with multiple Presentation Servers and CMA

In this architecture, each environment has its own dedicated Central Monitoring Administration instance and a staging Integration Service . All policy application between environments is supported by the policy export/import utility.

Exceptions requiring a Central Server deployment

In previous releases, the parent Infrastructure Management Server in a multiple-server deployment was known as the Central Server. In this release, the Central Server has been replaced by the Presentation Server for most deployments. However, a Central Server is still required for the following deployment use cases:  

For information on how to configure a Central Server, see  Configuring a BMC TrueSight Infrastructure Management multiple-server deployment.

Best practices for deploying Infrastructure Management

ComponentDeployment best practice
Administration console

Install and use the administration console on a host separate from the Infrastructure Management Server. Use the instance of the administration console that is installed with the Infrastructure Management Server for emergency use only. 

DatabaseReview the Considerations for selecting the database for the Infrastructure Management Server. If using an Oracle database, follow the Considerations and best practices for deploying the Oracle database.
Infrastructure Management Server
  • Install a BMC PATROL Agent and the BMC PATROL for BMC ProactiveNet Self Monitoring 1.1 knowledge module on the Infrastructure Management Server to monitor the Infrastructure Management Server externally. The Infrastructure Management Server includes in-built self monitoring; however, the Self Monitor KM provides a way to monitor the Infrastructure Management Server externally.
  • During installation of the Infrastructure Management Server, install the Infrastructure Management Self-Monitoring Service to monitor the health of all the components of Infrastructure Management. For more information, see Viewing the health of the Infrastructure Management components. For a description of this feature using a use case, see Detect problems using the automated self health monitoring capability.
  • Set up a separate event/notification path for external monitoring of the Infrastructure Management infrastructure so that you are not dependent on the infrastructure to generate and process alarms related to it being down or running in a degraded state.
Integrations and Impact Integration Web Services
Integration Service
  • Follow the Integration Service host deployment and best practices for event processing and propagation.
  • Determine the location of all PATROL Agents and the respective Integration Services. At least one Integration Service must exist for each network, and generally the Integration Service must be close to the PATROL Agents connecting to it. This requirement minimizes the number of connections to the Infrastructure Management Server and makes firewall management easier because there is one connection per Integration Service.

Tip

Develop a clear strategy for assigning the PATROL Agents to each Integration Service. The Infrastructure Management Server does not auto-balance the load between PATROL Agents and Integration Services, so the initial assignment is important. Although at least one Integration Service must exist per network, a convention based on name or function (or simple round-robin assignment) within the network is acceptable as long as you are consistent and avoid overloading any one Integration Service.

Staging Integration Service

Follow the Staging Integration Service host deployment and policy management for development, test, and production best practices.

All

Related topics

Staging Integration Service host deployment and policy management for development, test, and production best practices

Best practices webinars