This topic answers some Frequently Asked Questions (FAQs) about BMC ProactiveNet architecture and scalability.
The technology has also changed. Integration Service 9.5 comprises the Integration Service and the event cell. 9.5 BMC PATROL Agents do not communicate their data to a "BMC PATROL proxy server" any longer. PATROL Agents connect to the Integration Service and data is moved directly to the BMC ProactiveNet Server. Additionally, events can be sent to the Integration Service on the same port along with the performance data.
The cell on the BMC ProactiveNet Server is a Service Impact Management cell. For more information see BMC ProactiveNet Cell.
A correlation cell is a term referencing the type of event management work being done by the cell. Source cells normally perform actions that do not rely on evaluation with events from other sources. Correlation cells provide a common cell where events can be evaluated in context with other events.
Considering the Integration Service cell is the "entry point" or "source" cell for PATROL Agents, it is a best practice to perform message enrichment, deduplication here. Event management configuration KB content must be kept common across Integration Service cells where possible. Correlation cell rules allow for correlating across events that may originate separate communication paths (for example, across PATROL Agents from multiple Integration Service computers).
It depends on a number of factors (event volume, rules to be processed against, other resource constraints). It is best to install the correlation cell as a standalone cell allowing for the use of cell HA configuration.
Events reference the occurrence of availability and performance metric threshold breaches. Events can come from many sources. PATROL Agents normally detect and generate "availability" events that are sent to the BMC ProactiveNet Server, while "performance" events are raised in the BMC ProactiveNet Server based on threshold evaluations in the analytics process. For more information, see Event.
BMC PATROL central architecture is still supported and works with 9.5 PATROL Agents without any changes. Event forwarding in BMC PATROL must leverage the Integration Service. Doing so simplifies the required infrastructure and eliminates the requirement and configuration of one or more BMC Event Adapters.
The default port is 3183. This port can be changed. See Ports that can be configured after installation.
Yes. PATROL Agents version 3.8.50.01 and later pushed data to the Integration Service. In BMC ProactiveNet 9.5, the PATROL Agent pushes the data all the way to the BMC ProactiveNet Server (through communication managed by the Integration Service).
Some of the functions have migrated, but the migration is limited (for example, KM menu commands have not been migrated).
Oracle Standard Edition is supported. BMC ProactiveNet does not require partitioning. Other Oracle offerings are not required either; however, BMC recommends Data Guard to support Disaster Recovery.
RAC is not supported with Oracle Standard Edition. Oracle may also impose limitations on sockets based on the Oracle editions.
This depends on the size of the managed environment based on an architecture and scalability assessments. This is categorized based on small, medium and large environments. For Microsoft Windows running with i7 CPUs in a large environment, BMC recommends 4 CPUs, 24 GB RAM, 600 Gig of storage for the Oracle database. For more information, see Hardware requirements and Guidelines and tuning recommendations for BMC ProactiveNet Database.
Yes. The PATROL Agent first attempts to fill in the data gap using the cache and where required, uses the history files.
Yes. All trended data in BMC PATROL is now visible in the BMC ProactiveNet Operations Console. Attributes that are "availability" in nature, may be filtered from "storing" the data in the BMC ProactiveNet Server; however, BMC ProactiveNet supports graphing these attributes by querying the PATROL Agent for data. You can also see annotated data from BMC PATROL in the Operations Console. Text parameters in BMC PATROL are not visible in the BMC ProactiveNet UI.
Yes, the Integration Service computer acts as the "entry point" to the architecture. All sources of data and events must connect to an entry point. Some integrations may only leverage events into the architecture, but they must still connect to an Integration Server (for example, event only).
No, the use of the embedded Sybase database is restricted to installing the database as part of the BMC ProactiveNet Server.
Yes, the event management software is only installed once, but multiple cells may be created and run after the installation.
In general, attributes that are "availability" in nature generate events configured in the PATROL Agent and are passed to BMC ProactiveNet. Performance attributes are sent as data to the BMC ProactiveNet Server. The BMC ProactiveNet Server may then have thresholds that generate events based on the data received. These events may be in the form of Critical, Major, Minor, and so on or as abnormality events. Additionally, all trended data in BMC PATROL is visible in the Operations Console.
BMC PATROL architectures require RTServers. BMC ProactiveNet Central Monitoring Administration allows you to configure and manage agent and KM configurations. Your need to continue having a BMC PATROL Central Console environment will be driven by preferences and use cases benefited by its use. You may find that functional use cases are satisfied by BMC ProactiveNet. For example, you have the ability to run agent commands using the Query Agent window in the Operations Console. Annotation is also supported in BMC ProactiveNet attribute graphing. Parameter hierarchy from BMC PATROL is visible in BMC ProactiveNet. BMC PATROL text parameters are not visible.
Yes. Some BMC ProactiveNet customers use Oracle Exadata architectures.
Yes. Multiple instances of the Integration Service are supported. Installation of the cell components is required only once. Additional cells are created leveraging and configuring BMC Event Manager commands. Additional Integration Service instances can be installed on the same node as well. Installation of additional Integration Services provides a notation that cell components will be skipped during installation.
Policy filters instruct a PATROL Agent on what to send to the BMC ProactiveNet database and the event cell. By default, any KM that is configured and running sends all of its data and events configured in the PATROL Agent. Filtering provides "agent side" instructions to limit the information that the BMC ProactiveNet Server must store. Viewing is not restricted by policy filtering. You can graph an attribute that is filtered from sending its data to BMC ProactiveNet. For these attributes, the BMC ProactiveNet Server requests data from the PATROL Agent in real time.
Filtering configurations in monitoring policies suppress data from being streamed to the BMC ProactiveNet Server from the PATROL Agent. However, in the Operations Console, you can view an attribute that is filtered.
The maximum number of supported PATROL Agents is 900 on a large Integration Service host.
The staging Integration Service is installed in the same way as you install an Integration Service. You can then configure the Integration Service to be a staging Integration Service. BMC recommends that you edit the Integration Service installed with the BMC ProactiveNet Server and make it a staging Integration Service. A staging IS can be installed in any computer in which you install a normal Integration Service.
The staging Integration Service is used as a common initial place for newly installed PATROL Agents to enter the BMC ProactiveNet architecture. Staging policies can then decide which "production" Integration Service the PATROL Agent(s) must connect to going forward and optionally assign any agent tag(s) if required.
BMC recommends that you configure PATROL Agents to generate and forward events for "availability" parameters where sending data (0s and 1s) to the BMC ProactiveNet Server may not work. Performance parameters must be sent to BMC ProactiveNet as data only, allowing analytics to evaluate thresholds and generate intelligent events.
BMC provides comprehensive application response time monitoring with BMC End User Experience Management which integrates with BMC ProactiveNet. BMC also provides many metrics for application monitoring through BMC PATROL KMs. For a list of out-of-the-box KMs, see List of Monitoring Solutions and KMs in BMC ProactiveNet Performance Management.
Integration with BMC Remedy Service Desk is available only when you install the BMC ProactiveNet Server cell. If you want basic event to BMC Remedy integration, Integration with BMC Remedy Service Desk can be hosted by the correlation cell (or any standalone cell).
Not all of the BMC PATROL console functionality has been developed in BMC ProactiveNet yet, but some of the functionality does exist. In general, all configuration aspects are represented. Certain agent actions are also available. BMC ProactiveNet provides a Query Agent window which is similar (although not exactly the same) to the System Output window in BMC PATROL.
Yes. At a high level, Central Monitoring Administration replaces PATROL Configuration Manager. Some specific features of PATROL Configuration Manager do not exist in Central Monitoring Administration (for example, compare, reporting, and so on). Rule set development in Central Monitoring Administration includes policies and deployment of policies is much more controlled, automated, and easier in Central Monitoring Administration than PATROL Configuration Manager.
Use of the "merge" operation opens the doorway to having policies getting applied to an unknown agent configuration. There may be some limited cases where the merge operation is beneficial and some cases where in may even be required. This is an enhancement that will be considered.
Yes. BMC Impact Explorer can be used to access BMC ProactiveNet 9.5 cells.
BMC recommends that in BMC ProactiveNet 9.5, you use the Operations Console and not Impact Explorer. If you use Impact Explorer, you will have to register the cell(s) to BMC Event and Impact Manager 7.4.x IAS.
BMC plans to cover most (if not all) BMC PATROL Central Operator console capabilities of which you derive value from, in BMC ProactiveNet.
No new out-of-the-box reports have been added. Some reports that were based on outdated collectors have been removed. You can still create reports based on the attributes that you select.
Yes and that is the UI from which to manage event cells in BMC ProactiveNet 9.5.
Yes. You can modify the content of the data table but not the structure of the table.
Yes. Inheritance cannot be carried for the same application class defined in two or more policies (for example, one policy cannot select three services to monitor and another policy provide additional three services).
OS clustering is still required in BMC ProactiveNet 9.5 to support HA. For more information, see Installing BMC ProactiveNet in high availability mode and High Availability best practices.
No. Service impact is specific to rules and behavior of the Service Impact Management cell. Policies are focused on PATROL Agent configuration and/or monitoring the behavior of the BMC ProactiveNet Server. For more information, see BMC ProactiveNet Cell.
You can select to include or exclude the event management cell as part of the installation process. You can also exclude the cell if you are installing an additional Integration Service on a server in which an Integration Service already exists. The event management cell is installed once on a server. Additional instances are configured without running the installation file again.
Please communicate with your account team regarding any specific requests for information.
BMC PATROL Agents 9.5 can communicate with all the interfaces that it does today. A PATROL Agent that is configured to support Central Monitoring Administration policy configuration will give precedence to the policy configuration over any other tool instruction.
Policies allow even more control than manual adapters in earlier releases. In BMC ProactiveNet 9.5, you can filter at the application class, instance, and/or parameter levels. This filtering can include data, events, or both and can be applied at levels appropriate to what you want to view. For more information see, Configuring a monitor.
In general, a a single BMC ProactiveNet Server 9.5 can support 20000 devices, 250000 instances, and 1.7 million attributes (given the proper server resources, for example, 32 GB RAM, 8 CPUs). For more information, see Performance and scalability details for common deployments.
Central Monitoring Administration does not have in built policy versioning. BMC will provide an Import/Export utility in the near future so that customers can leverage their preferred source code control where desired. These capabilities will provide a means to create a "new" version of the policy, disable the old and enable the new. If an issue arose you could disable the new and re-enable the old policy.
The idea is to keep the workload on the BMC ProactiveNet Server cell reduced as much as possible with relation to enrichment of external event classes. You must add rules/classes to support events that present themselves to the BMC ProactiveNet Server cell for viewing. However, modify BMC provided rules and policies only after consulting BMC Support. The use of a correlation cell provides a step where customer specific rules can be applied to events prior to presenting them to the BMC ProactiveNet Server for viewing. Performing these limited workflows at this type of cell minimizes the need to publish these rules across many cells.
It is the same technology. The term "correlation" defines how the cell is used. An Integration Service cell is considered a source cell (feed directly by an event source, for example PATROL Agents) and as much standard processing as possible must be done at these cells. As events rise through the architecture, there are more events to be managed and rule processing must be limited to only those actions that require higher levels of functioning (for example, correlating with other events, configuration item (CI) enrichment, and so on).
A processing cell (for example, an Integration Service cell) provides basic event enrichment and handling that is usually common across "like" processing cells (for example, all PATROL Agent processing cells). A correlation cell usually has customer specific rules that can be applied to events prior to presenting the events to BMC ProactiveNet for viewing. Events at this cell may originate from any number of sources (BMC PATROL, SNMP, SCOM, and so on); performing these limited workflows at this type of cell minimizes the need to publish associated rules across many cells and supports correlating events from multiple domains.
BMC Impact Explorer 7.4.
No. Earlier versions of PATROL Agents are not compliant with Central Monitoring Administration. You must assign earlier PATROL Agent versions to the older Integration Service that they will be serviced through. For information about BMC ProactiveNet and PATROL Agent compatibility, see BMC ProactiveNet and BMC PATROL Agent compatibility.
The PATROL Agent has been updated for event configuration. You can enrich messages while configuring the PATROL Agent. This configuration can be managed in a policy. For details, see Configuring a BMC PATROL Agent.
Blackout policies in Central Monitoring Administration control PATROL Agent behavior. For external events, you can create a blackout policy using the Event Management Policies tab in the Administration Console.
Yes. Central Monitoring Administration does not support clustering staging Integration Services. It is important to note that clustering Integration Services create a comma separated list of Integration Services for the PATROL Agent. Because Central Monitoring Administration does not provide the staging Integration Service instruction to the PATROL Agent (this happens during the installation of the PATROL Agent), clustering may not be feasible. However, you can identify multiple Integration Services as staging Integration Services and when creating the PATROL Agent installation package, use a comma separated list of these Integration Services. The PATROL Agent then connects to the first one it finds available in the list.
No. However, an you must either use PATROL Configuration Manager or Central Monitoring Administration policies to manage a PATROL Agent, not both. Areas of agent configuration that are managed by policies override local configurations. In some instances, certain KMs may need to be configured outside of Central Monitoring Administration (for example, custom KMs not enhanced for Central Monitoring Administration policy control).
There are no changes in licensing.
A staging Integration Service allows you to automate the PATROL Agent to Integration Service configuration without sending data to the BMC ProactiveNet Server. It is used to automate which normal Integration Service or Integration Service cluster an agent must connect to. A staging Integration Service does not implement any monitoring policies.
Yes. This is supported with older Integration Service nodes integrated with BMC ProactiveNet 9.5. This does not apply to 9.5 Integration Service nodes and 9.5 PATROL Agents because there are no adapters. BMC ProactiveNet 9.5 includes manual synchronization in Central Monitoring Administration for older instances that were not initially included.
Yes. If the correlation cell is a standalone cell, it can be configured as a service impact management or an event management cell.
Impact Explorer 7.3.01 is not officially supported.
For information about the number of models a single BMC ProactiveNet Server can support, see Sizing charts for event and impact management. MOM and Enterprise use case implementations are intended to support environments where all service models can be configured in a single BMC ProactiveNet Server.
There are no changes to the prediction window.
Yes. The installation of a BMC ProactiveNet Server does not include the installation of Central Monitoring Administration. When you install a standalone BMC ProactiveNet Server, you have the option to install Central Monitoring Administration.
If you want to publish CIs to a cell, the cell must be a service impact management cell.
Yes. BMC ProactiveNet 9.5 ensures continuous communication between the Integration Service and the BMC ProactiveNet Server. For more information, see BMC ProactiveNet architecture with the integration of the BMC PATROL Agent. BMC ProactiveNet 9.5 also contains the ProactiveNet Health node that alerts on technology outages.
BMC PATROL data collection through the Integration Service nodes in earlier versions involved adapters that defined the data to be collected in the BMC ProactiveNet Server and the frequency of the data collection. These adapters have been completely eliminated in BMC ProactiveNet 9.5. In 9.5, BMC PATROL data is to the BMC ProactiveNet Server. This greatly simplifies the architecture and makes the process more resilient so that data is not lost during network interruptions or other outages. The PATROL agents now control what is sent upstream and the configuration for that is managed through filter settings in monitoring policies.
Generally 20,000. However, the number of agents is not the only limiting factor. For additional important details, see Sizing charts for data and event management.
It depends on the size of your environment. If your service models can be configured in a single BMC ProactiveNet Server, you must consider setting up the enterprise implementation as discussed in BMC ProactiveNet architecture best practices and integrate Atrium CMDB with only that server. If the size of your environment requires multiple BMC ProactiveNet Servers to support service modeling, you must integrate Atrium CMDB with the Child Servers.
Yes. For more information, see BMC Communities.
PATROL Configuration Manager in general is not required but may still be useful because it provides some capabilities that are not present in Central Monitoring Administration. For example, the ability to compare agents. If you use Central Monitoring Administration for configuration management, then use PATROL Configuration Manager to view configuration from agents. Do not use both to apply configuration to agents.
Can I use PATROL Configuration Manager instead of Central Monitoring Administration?
BMC recommends using Central Monitoring Administration in BMC ProactiveNet 9.5. Policy management provides operational benefits over the push/forget model of PATROL Configuration Manager. Central Monitoring Administration also has architectural improvements.
Yes. Events from other monitoring tools can be used for status change or impact change in service models.
SAN is preferred. BMC recommends a tier 1 SAN storage for production environments. For more information, see Hardware requirements.
Yes. BMC provides out-of-the-box integrations for some third party tools. For more information, see Event integration with supported third-party products and Data integration with supported third-party products.
For Microsoft SCOM, you must leverage the SCOM adapter for performance data. Event integration for SCOM is based on the Seamless integration. For more information see Adapter for SCOM. Zenoss integration is only event based unless you create a custom method for integrating performance data.
HA requires OS clustering in BMC ProactiveNet. HA is in-built and application specific to HA cells and Integration Service processes on the Integration Service hosts.
"MZ product" refers to the Market Zone product. Market Zone is a third party product developed to work with BMC solutions and is sold by BMC Software.
PATROL Agents 3.8.5 are supported. They must be integrated with an Integration Service version 9.0 or 8.6, and that with that Integration Service can connect to a 9.5 BMC ProactiveNet Server.
The BMC ProactiveNet database includes data views. If MSBI can fetch data from data views, it can be supported.
The BMC ProactiveNet Server does not include Microsoft SQL Server support.
5000 servers can be considered a medium environment sizing from purely a device count perspective. However, without considering all other scalability aspects, 5000 BMC PATROL managed servers cannot be considered medium environment.
Depending on how your business is set up, you can publish service models locally on the Child Servers, and view them centrally on the Central Server. Do not publish service models to a Central Server. However, you can publish service models to what is referred to as an "enterprise" implementation of the BMC ProactiveNet Server. This server is installed as a top tier BMC ProactiveNet Server. For more information about service models in a multiple server deployment, see Multiple-server deployment.
The Central Monitoring Administration UI has been redesigned and now includes a hyperlink approach for navigating within a single policy.
You can specify the sequence of event processing before it reaches the rate process. This includes customizations to events. Customization to events are removed by the rate process.
No. Earlier versions of PATROL Agents do not have the Integration Service streaming capability and they cannot connect to version 9.5 of the Integration Service. For events, older agents use a Notification Server if their version is earlier than 9.0. PATROL Agent versions 9.0.x can connect directly to an event management cell and forward events. For information about PATROL Agent and BMC ProactiveNet compatibility, see BMC ProactiveNet and BMC PATROL Agent compatibility.
Oracle versions 220.127.116.11.0 and 18.104.22.168.0.
The BMC ProactiveNet Server does not require Oracle partitioning. BMC ProactiveNet Performance Management Reporting requires Oracle partitioning in the latest release.
Yes. You must first apply the latest service pack and patches. For more information, see Upgrading BMC ProactiveNet Server 8.6.02.xx or 9.0.xx to 9.5.00 on Microsoft Windows.
No. Using Oracle does not increase the scalability of the solution. However, it does provide a nominal improvement in performance and supports better database resiliency.
BMC ProactiveNet Performance Management Reporting is included under the same license. The Reporting Studio option that supports creation of custom reports is an add-on license.
Yes. You can have multiple BMC ProactiveNet Servers in the same Oracle instance. Each server must have its own schema. For more information, see Configuring multiple BMC ProactiveNet Child Servers to connect to the same Oracle database.
The BMC ProactiveNet native adapter handles performance data. BMC recommends the Seamless integration for events. For more information, see Supported integrations with third-party products.
No. BMC ProactiveNet does not provide scripts or a method to migrate data from Sybase to Oracle.
The HA cell is not supported on the BMC ProactiveNet Server, but is supported on the Integration Service. You can also install remote HA cells for event visualization, including events propagated from BMC ProactiveNet Servers.
Not completely. BMC ProactiveNet supports operational multi tenancy where you can segregate access to data and operational activities based on user roles and permissions. There is no role-based access control for administrative activities. A user has either full administrative access or no administrative access. Also, there is no concept of segregated tenant accounts in BMC ProactiveNet.
No. A separate database user and schema is required per BMC ProactiveNet Server. BMC ProactiveNet Performance Management Reporting will support a single consolidated schema in the upcoming BMC ProactiveNet Performance Management Reporting 9.5 release.
BMC ProactiveNet is not FIPS compliant. For information about security capabilities, see Security.
No. The Seamless integration is from Seamless Technologies: http://www.bmc.com/products/product-listing/Seamless-Technologies-Event-Integration-for-BPPM.html
Because statistical data is streamed in near real time, the flash check functionality will not be needed. BMC ProactiveNet 9.5 also contains the Refresh Parameters menu option to force a collection outside of its normal timing.
The cell and the start and stop Integration Service processes have been separated to better support cell HA.
You will need only one Oracle instance for all BMC ProactiveNet Servers, and only one Oracle instance for BMC ProactiveNet Performance Management Reporting. This is a total of two instances, regardless of the total number of BMC ProactiveNet Servers. For more information, see Installing the BMC ProactiveNet Server on Microsoft Windows with Oracle as database and Configuring multiple BMC ProactiveNet Child Servers to connect to the same Oracle database.
No. In BMC ProactiveNet 9.5, PATROL Agents stream performance data all the way to the BMC ProactiveNet Server through the Integration Service nodes.
The correlation cell can be either located on an Integration Service or (if required) somewhere else. It is just a standard cell that is configured and used as a correlation cell. It is not a special installation.
The new streaming is only for data from PATROL Agents.
Yes. Any PATROL Agent earlier than 9.0 needs to leverage Bii4P. Also, the propagation of performance data requires using Integration Service 8.6 or 9.0 for older agents that connect to BMC ProactiveNet Server 9.5
A 4 GB RAM and 2 CPU Integration Service host can handle up to 900 PATROL Agents. For more information, see Sizing charts for data and event management.
No. Events are sent to only one destination. The destination must be an event management cell as recommend in BMC ProactiveNet architecture best practices. The cell can then send the events to multiple destinations.
Yes, all BMC KMs can be used through Central Monitoring Administration. Because KMs have their own release cycle, KMs are enabled as and when they are released.
BMC recommends that you have dedicated bandwidth and minimum latency; hence, the Internet is not recommended. However, BMC supports WAN connections and data compression is included to help manage WAN connections between the Integration Service nodes and the BMC ProactiveNet Server.
No. However, a policy is disabled by default. You must decide when to enable a given policy.
In BMC ProactiveNet 9.5, the BMC ProactiveNet Server does not make a connection with the PATROL Agents. The connection is between the PATROL Agents and the Integration Service. Central Monitoring Administration connections follow the same path and are perceived as a console connection by the PATROL Agent.
Yes. For more information, see Adapter for SCOM.
You can see the historical data that is collected from the Tools menu. If the PATROL Agent is sending only events, the data comes from the PATROL Agent in real time to populate the graph and this is a seamless process.
350,000 events per day. For more information see see Sizing charts for data and event management.
You can initiate PSL commands using the Query Agent command. This is not specifically designed to run scripts; however, with the correct syntax you can run small scripts. For a deep dive debug, you may still require a BMC PATROL console.
This has not changed much from earlier releases. The maximum load depends on many factors including the rules and policies that are enabled, types of events, and so on. In general, a single cell can support about 25 events per second. There may be more, but BMC recommends that you be conservative with this number. Note that events must be actionable messages.
No. It is in the roadmap for forthcoming BMC ProactiveNet releases.
Yes, there is a mapping which handles this relationship.
The Integration Service checks the communication automatically and alerts if it finds communication to be broken.
Central Monitoring Administration does not connect directly to agents. It connects through the agent controller on the BMC ProactiveNet Server(s). Policies are passed through the agent controller to the Integration Service nodes. The PATROL Agents initiate the connection to the Integration Service nodes and receive their policies. The default connection port for agents on the Integration Service is 3183. For information about ports, see BMC ProactiveNet ports. Also see the diagrams in BMC ProactiveNet architecture best practices for port numbers and connection requests.
As part of Central Monitoring Administration policy creation, you have complete control and filtering capabilities to specify the parameters, events, and data that you want to send to the BMC ProactiveNet Server. By default, KMs are not configured for monitoring until you create policies. Therefore, the related data is not collected till it is filtered out. You have to configure the monitoring policies before monitoring starts, and monitoring policies include filter configuration.
900 is the maximum number of PATROL Agents tested against a single Integration Service. However, agents do not maintain a connection to a staging Integration Service. They connect to the staging Integration Service, get their staging policy, and then immediately move to a production Integration Service. They do not reconnect to the staging Integration Service, so there no limit to the number of agents that a staging Integration Service can handle because the connection is transient.
BMC Remedy and xMatters do not integrate with Central Monitoring Administration. They integrate with the event and service impact management functions in BMC ProactiveNet. They can be integrated with any or all the BMC ProactiveNet Servers. The proper architecture for your environment must be reviewed by BMC Consulting Services.
Check with BMC Customer Support. BMC Customer Support covers governing when certain rules are applied to deal with Java rate process change issues.
BMC ProactiveNet can send SMTP emails natively. There is no in-built adapter for receiving emails as events. However this is planned in a future release and the method to support this is documented on BMC communities.
The out-of-the-box design is such that BMC Atrium Discovery and Dependency Mapping populates BMC Atrium CMDB and BMC ProactiveNet can be integrated into the same Atrium CMDB for service modeling. However, it is possible to populate data external from Atrium CMDB into BMC ProactiveNet for service modeling following processes developed by the field teams. This includes data from BMC Atrium Discovery and Dependency Mapping.
You can install the PATROL Agent manually. Central Monitoring Administration allows you to create a repository of silent installation packages that can be downloaded and run on the target servers to be monitored. For more information, see Creating and editing component installation packages.
No. Central Monitoring Administration does not deploy an installation package. You can create a silent installation package for the agents and KMs in but cannot deploy them using Central Monitoring Administration. You can use BMC Server Automation or any software distribution mechanism that you may have to deploy the silent install packages.
It is not required but it is a best practice. A staging Integration Service makes for easier agent deployment.
A staging Integration Service is not required if you know and configure the agent installation packages to contain the production Integration Service you want the agents to connect to. If you define the process and infrastructure so that each agent has the appropriate configuration for the Integration Service nodes, you do not have to use a staging Integration Service. The staging Integration Service is not mandatory. It is available to provide a central point to introduce agents to BMC ProactiveNet and to streamline the agent deployment process.
You must use a third party load balancer to load balance PATROL Agents across Integration Service nodes. You can also use a staging policy to apply tags to the PATROL Agents; however a load balancer eliminates the manual task of assigning tags for this purpose.
There are no known limitations. PATROL Agents connect and get reassigned to a production Integration Service immediately. In general, agents are assigned to the production Integration Service in less than a minute.
When you install a BMC ProactiveNet Server, a local Integration Service is installed by default. BMC recommends that the Integration Service be used as a staging Integration Service. Never use the Integration Service on the BMC ProactiveNet Server for data collection.
Yes. See Event integration with supported third-party products and Data integration with supported third-party products. BMC ProactiveNet can also consume data and events from third party sources for which there are no pre-built integrations. You have to configure customized integrations when pre-built integrations are not available.
Use Central Monitoring Administration to handle the application of monitoring configuration through monitoring policies. BMC Server Automation can handle the deployment and installation of agents and KMs. For more information, see Integrating with BMC Server Automation.
Yes you can use the Integration Service 9.5 on a BMC ProactiveNet Server that contains an earlier version of the Integration Service.
No. A staging Integration Service does not apply monitoring policies to the PATROL Agent. It only applies staging policies that contain final the Integration Service configuration and optionally tags for the PATROL Agent.
The PATROL Agent connects to the staging Integration Service based on the configuration in the agent installation package, the first time the agent starts. The staging Integration Service then applies a staging policy to the agent. The staging policy contains the final Integration Service that the agent then connects to. After the staging policy is applied, the agent connects to the final Integration Service and does not reconnect to the staging Integration Service. It does not reconnect to the staging Integration Service after a restart. If the agent were to be purged, it goes back to the staging Integration Service for reassignment.
Yes. If the location of the PATROL Agent connection is well defined and a staging Integration Service is not required, the PATROL Agent can just connect to the required production Integration Service.
There are no scalability recommendations except that you must not simultaneously connect to more than 900 nodes. For more information see, Sizing charts for data and event management.
Generally. Additionally, a staging policy can assign required tags to the PATROL Agent as part of the staging.
If the PATROL Agent cannot connect to the single Integration Service in the configuration list, it connects to the next one in the list. You can also use load balancers between the PATROL Agents and Integration Service nodes.
Reach out to the BMC Customer Support team. They have a new program called AMIGO (it is free) to help prepare customers for upgrades. https://communities.bmc.com/docs/DOC-28469
Central Monitoring Administration does not provide default monitoring configurations. This is being considered for the future.
MCxP has not changed in BMC ProactiveNet 9.5. The MCxP rule and class files in the KB define the BMC PATROL event structure and basic handling of BMC PATROL events.
Pairing Integration Services follows the same idea. Additionally, clustered Integration Services share a common HA cell for event high availability.
The PATROL Agent pushes data to the BMC ProactiveNet Server using the Integration Service to manage the conversation. The PATROL Agent initiates the connection to the Integration Service. The BMC ProactiveNet Server initiates the connection to the Integration Service.
Not exactly. The staging Integration Service does not process performance data or events. Its purpose is to apply staging policies. This depends on how you want to control initial agent connections into the Integration Service nodes as part of the deployment process and their production Integration Services. Using a staging Integration Service allows you to alter deployment behavior without the need to alter your standard agent installation packages.
The PATROL Agent buffers up to 30 minutes of data at the agent. This is the default setting. BMC recommends not increasing this setting. When the agent reconnects, the buffered data is sent to the BMC ProactiveNet Server and no data is lost.
You can integrate Atrium CMDB with a single Child Server or multiple Child Servers. Try to limit service models to a single Child Server if possible. Do not integrate the Central Server with Atrium CMDB.
No. PATROL Configuration Manager threshold rules are the absolute type. BMC ProactiveNet has absolute and signature thresholds that leverage baselines. Additionally the rule format stored in Central Monitoring Administration as policy content for thresholds has changed in comparison to the older rule format managed in PATROL Configuration Manager. However, PATROL Configuration Manager can be used to collect and view any rules at the agent, even if they come from a policy. Avoid trying to manage the same agent with PATROL Configuration Manager and policies.
BMC ProactiveNet does not have this capability. BMC ProactiveNet integrates with BMC Server Automation for easier deployments.
Yes. For more information, see Installing the BMC ProactiveNet Server in HA mode on Linux/Solaris.
BMC recommends that each Integration Service host have an event management cell installed. The cell includes a local database called mcdb. The cell must be configured as a HA cell. The PATROL Agent buffers events if the connection to the Integration Service is broken and/or the cell does not acknowledge the event being received. The cell also buffers events not sent to the BMC ProactiveNet Server.
Yes. However, they run active/active. For more information, see Installing the BMC ProactiveNet Integration Service in HA mode on Windows.
Yes. For more information, see Integrating with BMC Server Automation.
The Integration Service and MCxP are completely separate and do not conflict. Overall, MCxP defines event configuration for BMC PATROL events in the event management cell. The Integration Service receives performance data and events. The Integration Service forwards events to the local event management cell running on the same host with the Integration Service process. The MCxP rules and class files define the structure of BMC PATROL events in the cell and how BMC PATROL events are processed.
Yes, if needed to support PATROL Agents earlier than version 9.0. Leveraging Bii4P3 must be a temporary condition and Bii4P3 must not be used with PATROL Agents versions 9.0 or 9.5 (although technically they can be). BMC recommends upgrading to the more current versions of agents as soon as possible to leverage the related improvements.
There is no direct effect. Connections to the agents are handled via the certificate based path (level 2 by default). Central Monitoring Administration does not use Access Control Lists (ACLs) on PATROL Agents. Central Monitoring Administration connects to the agents through the Integration Service nodes. When multiple BMC ProactiveNet Servers are involved, Central Monitoring Administration communicates through the Child Servers to the respective Integration Service nodes and then to the agents. Access control is managed for the Query Agent functionality with the "Allow PATROL Agent operations" and "Allow trusted connection to PATROL Agents" permissions.
You need not install the Integration Service process if you are using BMC ProactiveNet only for event management. Third party events can be sent to event management cells directly. If you are using PATROL Agents and KMs for event detection, BMC recommends that you install the Integration Service and configure according to the best practices at BMC ProactiveNet architecture best practices so that events from PATROL Agents are sent to the Integration Services. This recommendation allows you to easily take advantage of trending performance Key Performance Indicators (KPI) data in BMC ProactiveNet. In event only Integration Service installations, it is best to ensure that the cells used have all the latest and correct event processing data classes and rules.
There is no way to restrict the number of active instances in BMC ProactiveNet.
Yes. PATROL Agents do not connect to Central Monitoring Administration. The connection is through the Integration Service. Central Monitoring Administration does not use ACLs on the PATROL Agent.
Technically yes, but BMC does not recommend it.
In general, do not cluster more than four Integration Service nodes. Create the cluster after you have added all the Integration Service nodes to Central Monitoring Administration. For more information, see Managing BMC ProactiveNet Integration Service clusters.
BMC ProactiveNet does not support multitenancy. You can configure various levels of visual separation and access control. However, this is different from true multitenancy.
There is no documentation dedicated to this scenario. In general, install the event management cells on the Integration Service hosts as explained in BMC ProactiveNet architecture best practices. Also check Performance and scalability recommendations.
The best practice is to leverage the event management cell on an Integration Service host. You can enable the SNMP trap adapter on the cell to receive SNMP traps as events. To do this, consider the Performance and scalability recommendations. If you plan to receive a very large number of SNMP traps, you must install an event management cell on a dedicated node to handle the volume. Never forward SNMP traps or raw events to the BMC ProactiveNet Server. For more information see, Managing BMC ProactiveNet events through SNMP traps.
There are limited use cases for the Administration Console in BMC ProactiveNet 9.5. Most operations that support multiple users have moved to Central Monitoring Administration. The Administration Console in BMC ProactiveNet 9.5 is used mostly for event management, cell configurations, and older third party adapter configurations.
No. BMC PATROL KM menu commands are not available in the BMC ProactiveNet consoles. However, you can use the Query Agent capability in Central Monitoring Administration to run PSL commands.
Yes. If you upgrade a previous version of BMC ProactiveNet that leveraged SNMP monitoring, it is supported. The old BMC ProactiveNet monitors (non-PATROL Agent monitoring) have been deprecated and are not available in BMC ProactiveNet 9.5. For more information, see Deprecated features in BMC ProactiveNet 9.5 and BMC PATROL Monitoring Solutions for deprecated monitors.
Yes, as long as the appropriate operating system, hardware, storage resources, and connectivity are allocated for it.
Yes. There are no changes regarding HA support for VMware. You can install as with earlier versions.
There is no specific documentation about this topic. In general, leverage the access control capability in BMC ProactiveNet to leverage user groups where appropriate groups are created per client. This type of configuration can vary from one customer to another and requires engaging BMC Consulting Services or other technical assistance to understand how access control works and what the limitations are.
The BMC PATROL Agent streams data to the BMC ProactiveNet Server and this data is stored in the BMC ProactiveNet Server in the same intervals and granularity as it is collected by the PATROL Agent. Therefore, data in the BMC ProactiveNet Server is based on the polling frequency set in the PATROL Agent for each specific KM collector running in the PATROL Agent.
Yes. The move is very quick and there is no missing data after the move.
Supported database versions that are documented are the versions that have been tested and supported. It is unlikely that a newer or earlier version of Oracle may not work; however these versions have not been tested. Do not use versions earlier than 11g.
No. The BMC ProactiveNet Server is the one location where cell HA is not supported.
Yes. See Viewing annotation details.
BMC ProactiveNet -based native monitors in BMC ProactiveNet 9.5 are deprecated and not available in a new 9.5 installation. If upgrade to BMC ProactiveNet 9.5, the deprecated monitors are available. For more information, see Deprecated features in BMC ProactiveNet 9.5 and BMC PATROL Monitoring Solutions for deprecated monitors.
Event management cells and Integration Services are independent of each other and do not conflict. You can set the order of how they move from one server to another.
Yes. This is supported as a cluster configuration in Central Monitoring Administration.
Yes. BMC ProactiveNet has been installed using VMware HA. The BMC ProactiveNet application is not VMware HA aware.
Yes. However, there have been HA deployments across data centers. The feasibility of this depends on hardware and network capabilities but it can be implemented.
Technically, you can do this if you use the p3adapter configuration with the Integration Service 9.0. This is possible because the p3adapter polls the agents. Though you can do this, BMC does not recommend this except for specific upgrade scenarios. PATROL Agents 9.5 does not stream data to the Integration Service 9.0.
BMC does not recommend this scenario. If you install the primary and secondary hosts in virtual guest systems, the guests must run on separate ESX Servers so that you have resiliency at the hardware level. If you install the primary and secondary hosts on the same ESX Server, they will both be unavailable if the ESX Server goes offline or if there is a hardware issue.
Yes. The the Monitor to Monitor KM is not needed on Integration Service 9.5 hosts and it will not monitor the Integration Service processes. The KM was designed for the older Integration Service processes. In-built self monitoring replaces the KM in version 9.5. You must also install a PATROL Agent and an OS KM on the Integration Service nodes so that you can monitor the Integration Service processes externally.
Yes. Only events and timers are synchronized.
Two, one for each BMC ProactiveNet environment that supports multiple BMC ProactiveNet Servers and one per BMC ProactiveNet Performance Management Reporting environment.
OS clustering can be configured to support basic application aware HA because failover can be triggered based on a process being down and so on. Additional details must be based on your requirements and environment.
Not necessarily. It depends on your plans for growth. Be sure to leave some buffer. BMC recommends at least 10%.