Monday, June 9, 2014

BPPM 9.5 Quick Start - Part 10: PATROL agent installation and configuration

There are several ways to deploy large number of PATROL agents including creating silent installation package using CMA, using RSCD agents in BMC Server Automation (BSA), and using old PATROL Distribution Server.  But if you just need to install a few PATROL agents in a development environment to understand how BPPM 9.5 works, you can just use PATROL installer to install each PATROL agent interactively.

To get PATROL data and events into BPPM server, the first step in PATROL configuration is to specify its data and event destinations.  Since BPPM 9.5 allows you to send both PATROL data and events to the same port on integration service node (ISN), your typical pconfig setting would be:

"/EventSetup/Configuration/Format" = { REPLACE = "BiiP3" },
"/EventSetup/Configuration/Key" = { REPLACE = "mc" }
"/EventSetup/Configuration/ForwardEventsToIS " = { REPLACE = " Yes " }
"/AgentSetup/integration/integrationServices"={REPLACE="tcp:ISN1:3183,tcp:ISN2:3183"} 

where ISN1 and ISN2 are host names for the first ISN and second ISN in high-availability cluster.

If you don't want to send PATROL events to the same port as PATROL data, you can still use what you had in BPPM 9.0 by replacing
"/EventSetup/Configuration/ForwardEventsToIS " = { REPLACE = " Yes " }
with
"/EventSetup/Configuration/EventCells" = { REPLACE = "ISN1/1828,ISN2/1828" }

Once the above configuration is in PATROL agent, you will see  all PATROL agents linked with their ISNs in CMA GUI display.

Next, you will need to add tags to PATROL agent configuration. Here is the format for a tag in pconfig

"/AgentSetup/Identification/Tags/TAG/<tag_name>" = {REPLACE = "Tag description"}

For example, you may want to define a tag for Windows OS base monitoring.  You will have the following variable in pconfig:

"/AgentSetup/Identification/Tags/TAG/WinBase" = {REPLACE = "Windows OS Base Monitoring"}

where 'WinBase' is the tag name you created, and it has to match a tag specified in a CMA policy in order to receive the configurations contained in that CMA policy.  "Windows OS Base Monitoring" is a description you give to this tag, and it does not have to match anything.

When the tag in PATROL agent pconfig matches the tag in a CMA policy, CMA will push all its configurations contained in that policy to PATROL agent immediately.  Whenever any configuration is updated in a policy, all PATROL agents with matching tags will receive the same update immediately.  No PATROL agent restart is needed.








4 comments:

  1. HI Willa,

    Is there any possiblilty/option to install a Patrol agent 9.5 in target server from BPPM CMA console 9.5 directly like other installation type(using standard installer loggin to that specific server,publishing server etc ) .
    i can see only options to create a package. nothing like to deploy on the end server directly by entering the ip/hostname.

    ReplyDelete
  2. Subramanyam,

    I am not aware of direct installation option from BPPM 9.5 CMA. That is why BMC is selling BMC Server Automation (BSA) to use its RSCD agents for PATROL agent deployment. The old PATROL Distribution Server should still work and it is free.

    Thanks!
    Willa

    ReplyDelete
  3. Hi Willa,

    We have BPPM 9 and want to install bppm agents. Do we need to install patrol agents or can we use the bppm agent to start our basic monitoring. How can i manage BPPM agents? do i still need the CMA? Appreciate your feedback.

    ReplyDelete
  4. Nusrath,

    You will need to install PATROL agents to use BPPM 9 as recommended by BMC. The native ProactiveNet agents are either on limited support or no longer supported by BMC. CMA is for managing PATROL agents only.

    Thanks!

    Willa

    ReplyDelete