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 describes considerations about your environment to help you determine which configuration options to use. The following topics are presented:

Considerations for BMC PATROL Agent and monitoring solution deployment

The following list presents considerations and guidelines for configuring the BMC PATROL Agent and monitoring solution deployment.

  • Leverage distribution software, such as BMC (BladeLogic) Server Automation, to deploy the monitoring solution packages. With a BMC ProactiveNet integration with BMC Server Automation, you can deploy BMC PATROL Agents and monitoring solutions with relevant configuration information, including the Central Monitoring Administration tag and the BMC PATROL Agent location. For details about BMC Server Automation integration with BMC ProactiveNet, see BMC ProactiveNet User Guide.
  • Specify the Central Monitoring Administration tag when you create a monitoring package (for details, see Creating and editing component installation packages), or specify the tag through the BMC BladeLogic Console. You can also use the BMC PATROL Agent pconfig command or PATROL Configuration Manager to set the tag, but if the recommendations are followed then those tools would not be necessary.
  • Monitoring solutions must expose the relevant metadata and conform to development guidelines to Central Monitoring Administration for configuration.
    • For a list of enabled monitoring solutions, see Monitoring solutions configurable through Central Monitoring Administration.
    • To create a custom monitoring solutions, see Building a PATROL Knowledge Module Developers Guide from the BMC Support website.
  • If you delete a monitoring policy, manually restart the BMC PATROL Agent. For example, if a BMC PATROL Agent has monitoring policies for OS and database, and you later decide to remove the OS, you need to restart the BMC PATROL Agent.

    For details, see the BMC PATROL Agent Reference Manual from the BMC Support website.

    To restart the BMC PATROL Agent using BMC PATROL Configuration Manager

    1. In PATROL Configuration Manager, select the agent.
    2. From the Tools menu, select Reinitialize Agent.

    To restart the BMC PATROL Agent using a pconfigcommand

    In a command window, run the pconfig +RESTART command with the following syntax:

    pconfig +RESTART [+verbose] [-port <portNumber>] [-host <hostName>] [-timeout <timeoutValue>]
    

Warning

If a BMC PATROL Agent is already configured through the PATROL Configuration Manager or through the Tools > Configure options in the BMC ProactiveNet Administration Console, and the agent is integrated with BMC ProactiveNet through the adapter for BMC PATROL, do not add a tag to that BMC PATROL Agent. Instead, continue managing the configuration for that BMC PATROL Agent through the PATROL Configuration Manager.

If you add a tag to the BMC PATROL Agent, configuration information might be overwritten. Duplicate instances will be created, conflicting monitor instances that were synchronized through PATROL Configuration Manager will be marked for deletion, and all historical data will be lost.

Monitoring policy configuration guidelines

Use the following guidelines and recommendations to configure monitoring policies in Central Monitoring Administration. For configuration details, see see Creating or editing a monitoring policy.

  • Avoid assigning the same tag to several different policies. Too many policies with the same tag make it difficult to determine the final configuration.
  • Consider the following performance factors when you configure monitoring policies:
    • Avoid policies that set thresholds for a large number of instances that are discovered by using regular expressions. If the threshold applies to all instances, BMC recommends using the global thresholds settings that are available through the BMC ProactiveNet Operations Console. Proliferation of instance thresholds could adversely affect the performance of the BMC ProactiveNet Child Servers.
    • Plan policy edits. Editing policies triggers a push of configuration on all the agents and the BMC ProactiveNet Child Servers (for server-side actions). For large environments, plan edits for policies in advance, and group together all the required changes rather than editing the policies multiple times for minor changes.
    • Combine all the actions for a specific tag in a single policy. Edits are more efficient and the final configuration is less confusing.
    • For BMC PATROL Agents with agent-level thresholds, which are set only from the BMC PATROL Console, do not set thresholds through monitoring policies to avoid duplication of processing.
  • Use the Copy baseline from device for environments that use VMs that are expected to have similar configuration with regards to the CPU, memory, and installed applications.
  • For the same monitor type with different versions of the monitoring solution, use the following guidelines:
    • If different versions have the same configuration settings, then use the latest version of the monitoring solution to configure the policies.
    • If different versions have different configuration settings, then create separate policies and separate tags for the different versions.

Performance considerations

The following list presents performance considerations for Central Monitoring Administration.

  • BMC ProactiveNet Central Server.
    • Do not monitor directly from the BMC ProactiveNet Central Server. Perform all monitoring from the BMC ProactiveNet Child Servers.
    • For performance considerations related to policies, see Monitoring policy configuration guidelines.
  • BMC ProactiveNet Child Servers. From the perspective of Central Monitoring Administration, the impact on the BMC ProactiveNet Child Servers is a function of the threshold configurations and the server-side actions. The guidelines given for configuration of the policies would ensure that the impact on the BMC ProactiveNet Child Servers is minimal.
  • Integration Services. Integration Services push configuration information to the BMC PATROL Agents. As long as the Integration Service is sized to handle the load of the data collection, no additional considerations are necessary from a Central Monitoring Administration perspective.

Security considerations

The information in this section is specific to Central Monitoring Administration. A list of ports required for data collection and other configuration is available the BMC ProactiveNet Installation and Configuration Guide.

  • Firewall Considerations.
    • Port 3183 (default) is required for communication between the BMC ProactiveNet Central Server and the Integration Services distributed across the environment. The connection is initiated by the Central Server.
    • Port 8093 (default) is required for communication between BMC ProactiveNet Child Servers and Central Monitoring Administration. The connection is initiated by the BMC ProactiveNet Child Server.
    • Certain actions, such as registration of the BMC ProactiveNet Child Servers and using the REST Web Services, require access to web services on the Central Server. Port 80 or 443 needs to be accessible on the Central Server from the BMC ProactiveNet Child Servers or the client machines invoking the APIs.
  • Access Control. Central Monitoring Administration is only accessible to users who are assigned the Access to Central Admin permission. After permission is available to the user, the user can create policies which impact any of the objects in the entire deployment. Only give this permission to "Super Admin" users to limit the exposure to a minimal set of users. For details, see Granting user access to Central Monitoring Administration.

High-availability and disaster recovery considerations

Other than following the BMC ProactiveNet Server high-availability and disaster recovery considerations, no special considerations are necessary from a Central Monitoring Administration perspective.

For details, see the high-availability installation instructions in BMC ProactiveNet Installation and Configuration Guide, and the disaster recovery guidelines.