14 Replies Latest reply: Jul 21, 2012 8:16 AM by amrit tandon RSS

New Proactivenet agent problem

MarkSaunders

I have been tasked with setting up a new Proactivenet agent to use for our internal monitoring. We currently have one agent already which was set up by a consultant to monitor a customers servers.

 

I have created the new agent and it is happliy monitoring my PC as a test. I have a problem with connecting it to the Proactivenet server. On the admin console it is added to Advanced Options -> Agent and showing as connected. When I go to add the adaptor I can connect and start the integration service agent configuration but this has no monitor information trying to click next gives a ERROR: No Monitors Found!!! message.

 

Im guessing that I have missed some network access but I cannot figure out whereas all the ports I know about 3181/2/3 and 12124 all seem to be open in the right places.

  • 1. Re: New Proactivenet agent problem
    Alexandr Shubin

    Can you provide us with few screenshots please?

     

    You have no PATROL Agents registered in this Integration Service.

     

    Check PAgent configuration: Integration->IntegrationService = tcp:<is-agent-hostname>:3183

  • 2. Re: New Proactivenet agent problem
    MarkSaunders

    Sure

     

    Here Patrol Central on the new RSM showing a monitored device.

    new pnet agent 1.JPG

     

    When doing configure Integration service (Our integration port is 3182)

     

    new pnet agent 2.JPG

     

    The monitored machine is not included in the list

     

    new pnet agent 3.JPG

    new pnet agent 4.JPG

    When going through adapters add adapter this ends with a

     

    new pnet agent 5.JPG

    When setting up the agent the pproxsrv service did not get added in I had to add this afterwards from the command line

     

    pproxsrv.exe -install -p 3182

  • 3. Re: New Proactivenet agent problem
    Alexandr Shubin

    You have no PATROL Agents registered in this Integration Service.

     

    Check PAgent configuration: Integration->IntegrationService = tcp:<is-agent-hostname>:3183

     

    When you do above steps you should see something like this:

     

    26.03.2012-18-50-22-2200.jpg

     

    Agents listed here:

    with port 3182 - IS Pronet Agent

    3181 - Patrol Agents.

     

    So, you need to register PAgents through IS or add them manually.

  • 4. Re: New Proactivenet agent problem
    MarkSaunders

    With our existing pronet agent when new patrol agents are deployed all we have to do is push out a rule to the agent to set the integration port 3183,3185 or 3187 and they get added into the agent profile.

     

    How do I go about registering/adding the agents if it needs to be done another way ?

  • 5. Re: New Proactivenet agent problem
    MarkSaunders

    Thank you for the help in the pointer to the integration service. I have removed and reinstalled the agent including the integration service as part of the install rather than trying to add it afterwards and this now all seems to be working.

  • 6. Re: New Proactivenet agent problem
    przemyslaw.mantaj@wolainfo.com.pl

    Hi, I have similar problem but when I trying to add both manual or during installation process, patrol agent still doesn't communicate with Remote Agent (proxy) on port 3183. Could you help me resolve the problem? Maybe patrol agent doesn't support RHEL 5.7?

     

    I have done integration with windows patrol agent and everything is ok. The problem is unix patrol agent (rhel) with PNet Proxy (windows).

     

    Przemek

  • 7. Re: New Proactivenet agent problem
    Alexandr Shubin

    Once again - please, provide us with more info!

     

    Some screenshots would be nice.

     

    And again - 3183 - Integration service port.

     

    PORT Scheme:

     

    Source                 Port                    Destination                   Port

     

    PatrolAgent          Any       =>         BPPM Agent (IS)          3183

    BPPM Agent        Any       =>         PatrolAgent                  3181

     

     

    Рисунок1.png

  • 8. Re: New Proactivenet agent problem
    przemyslaw.mantaj@wolainfo.com.pl

    in PCM I added integrationServices parameter with proper value:

    integrationServices.jpg

     

    OMW9 is Remote Agent (PNet Proxy):

    proxy1.jpg

    I see only one patrol agent on windows machine. There should be another patrol agent on unix system.

    proxy2.jpg

     

    There isn't any firewall problem. On remote agent there isn't any established port to patrol agent:

     

    C:\Users\Administrator>netstat -an | find "318"

      TCP    0.0.0.0:3182           0.0.0.0:0              LISTENING

      TCP    0.0.0.0:3183           0.0.0.0:0              LISTENING

      TCP    127.0.0.1:50293        127.0.0.1:3182         TIME_WAIT

      TCP    192.168.11.105:3182    192.168.11.105:49516   ESTABLISHED

      TCP    192.168.11.105:3182    192.168.11.105:49817   ESTABLISHED

      TCP    192.168.11.105:3182    192.168.11.208:57002   ESTABLISHED

      TCP    192.168.11.105:3182    192.168.11.208:57006   ESTABLISHED

      TCP    192.168.11.105:3182    192.168.11.208:64968   ESTABLISHED

      TCP    192.168.11.105:3183    192.168.11.65:50169    ESTABLISHED

      TCP    192.168.11.105:49516   192.168.11.105:3182    ESTABLISHED

      TCP    192.168.11.105:49813   192.168.11.11:3182     ESTABLISHED

      TCP    192.168.11.105:49817   192.168.11.105:3182    ESTABLISHED

     

     

    On patrol agent (unix) there isn't any established port to remote agent:

    [root@oml9 log]# netstat -an | grep 318

    tcp        0      0 0.0.0.0:3181                0.0.0.0:*                   LISTEN

    udp        0      0 0.0.0.0:3181                0.0.0.0:*

     

     

    Przemek

  • 9. Re: New Proactivenet agent problem
    Alexandr Shubin

    PA version is...? And can you please check DUMP AGENT CONNECTION in IS Configuration?

  • 11. Re: New Proactivenet agent problem
    Alexandr Shubin

    Upgrade agent to 8.5.00 (or 3.7.50?)

     

    BMC Performance Manager PATROL-based

    -Data flows from PATROL Agents to Integration Service (formerlycalled PATROL proxy) to BPPM Server

    -With PATROL 3.8.50 or later Agent

    §Automatic registration with Integration Service connects Agentto BPPM server by a simple PCONFIG setting

    §Automated device and monitor creation:

    Create devices in BPPM

    Create monitors automatically (no need for Add Monitor Wizard)

  • 12. Re: New Proactivenet agent problem
    Garland Smith

    Automated Workflow requires 3.8.50 or higher version of PATROLAgent.

    The logic to communicate with Integration Service on port 3183 is not

    available in earlier PATROLAgent versions.

     

    Garland Smith

  • 13. Re: New Proactivenet agent problem
    przemyslaw.mantaj@wolainfo.com.pl

    You are right, after upgrade agent to 3.8.50 connection is established. Thanks for help.

     

    Przemek

  • 14. Re: New Proactivenet agent problem
    amrit tandon

    The same happened in our ENV today, we have 3 integration service, automatic creation of adapters is set to false for all. We have created manual adapters for all integration service.

    We restarted BPPM Server(8.6.02.02) and Integration Service(8.6.02.02) after downtime and found that one integration service was unable to collect data from PATROL Agent.

     

    **When trying to see-->Tools--->Configure-->Integration Service, found that no PATROL Agent can be seen connected. Earlier there were about 250 Server under monitoring for the same IS

    **Checked all the ports, everything is open.

    **Checked netstat -an | find "ESTA" | find "3181"-----> All Patrol Agent seem to have established connection with IS.

    **When trying to edit adapter i end with error ERROR: NO MONITORS FOUND

     

    Need suggestion,