1 2 Previous Next 27 Replies Latest reply: Jan 9, 2013 1:44 AM by Jonathan Coop RSS

How to Monitor Hardware using BMC Proactivenet Agent

pankajborale NameToUpdate

Hi Team,

 

          Let me know if you are aware of monitoring Hardware using BMC Proactivenet Agent based Architecture.

 

Thanks.

  • 1. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Suhrid Karthik

    There is no out of the box hardware monitoring provided by the PNet native monitors.

    Some suggestions:

    1. If your hardware monitoring parameters are available through SNMP/WMI - consider using the PNet SNMP, WMI Monitor Wizards to build your own custom hardware monitor.

    2. You can use Sentry solutions for Patrol and Portal and pull the data into ProactiveNet using Patrol proxy/BPM Portal adapter.

  • 2. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Edwin Vazquez

    Hi Suhrid,

    I have a customer with used Patrol KM for Sentry and they want migrate to PNET.

    Unfortunately does not use Portal as a compromise to solve the problem of sending information from Sentry to PNET.

    Investigating how to solve this problem, we review the issue of making a PSL to send information from Sentry to PNET, This is possible?

    Best Regards

    Edwin

  • 3. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Mirella Pellizzon

    Did you try to import the Km using Patrol Proxy and BMC PATROL adapter?

     

    You can do this in Pnet admin console.

     

    Any Patrol KM can be imported to Pnet. Portal is not a prerequisite.

     

    Regards

     

     

    Mirella Pellizzon

    Senior Software Consultant

    Enterprise System Management

    BMC Software do Brasil

     

    phone: 55.11.2183.6057

    mob: 55.11.9129.8876

     

    Rua Leopoldo Couto de Magalhaes Junior, 758 - 14 andar - Ed. New Century - Itaim Bibi

    Sao Paulo - SP - Brazil

    Zip 04542-000

  • 4. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Edwin Vazquez

    Thank you Mirella,

    I try this solution and let you know what happend whit my customer.

    Regards

    Edwin

  • 5. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Javier NameToUpdate

    Hi Panka,

     

    The solution to monitoring architecture and network devices is Entuity Network Monitoring (ENM - EYE Storm), you can see the follow link:

     

    http://www.bmc.com/products/product-listing/entuity-network-monitoring.html

  • 6. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Mirella Pellizzon

    Hi Javier,

     

    Eye doesn't monitor hardware specific metrics like fan, temperature etc. And if you want this also, I suggest you to use the Sentry family of products.

     

    http://www.bmc.com/products/product-listing/42911687.html

     

     

    Mirella Pellizzon

    Senior Software Consultant

    Enterprise System Management

    BMC Software do Brasil

     

    phone: 55.11.2183.6057

    mob: 55.11.9129.8876

     

    Rua Leopoldo Couto de Magalhaes Junior, 758 - 14 andar - Ed. New Century - Itaim Bibi

    Sao Paulo - SP - Brazil

    Zip 04542-000

  • 7. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Shweta Patil

    Hi Javier,

    Using Proactivenet if your hardware monitoring parameters are available through SNMP/WMI - than using the PNet SNMP, WMI Monitor Wizards you can monitor temperature, fan etc parameter.

     

    SNMP Monitor Defination.bmp

  • 8. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Jonathan Coop

    I have a Sun hardware monitoring KM that will work woth a PatrolAgent which makes use of ALOM or ILOM cards.

     

    Let me know if of interest.

     

    Jon

  • 9. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Javier NameToUpdate

    Just for information:

     

    This information appear in Release notes Version: 8.1.00 April 9, 2010, where PNET are no loger supported SNMP Trap Receiver monitors.

     

    Deprecated monitors
    The following monitors are no longer supported and will be removed from the BMC ProactiveNet Monitor Guide in a future release of the product:

    • Alteon
    • Cisco Interface Packets (Protocol 1)
    • Cisco Interface Packets (Protocol 2)
    • Cisco Local Director
    • Cisco Local Interface
    • Cisco Local Interface monitor (a network monitor)
    • Cisco Stack
    • Compaq
    • Compaq Disk
    • Compaq Health
    • Compaq System
    • Dell
    • Dell Disk
    • Dell Health
    • DHCP
    • Extreme Switch
    • Foundry Switch
    • Keynote Website Perspective
    • RADIUS
    • F5 BIG/IP
    • Frame Relay
    • Informix Query
    • RMON Interfaces
    • RMON2 Protocol
    • SNMP Trap Receiver monitors

    User Experience Transaction monitor

  • 10. How to Monitor Hardware using BMC Proactivenet Agent
    Gordon James

    Hi,

     

    I don't know whether you got any further with this. I'm looking to implement Pnet 8.6.02 and am currently using the Sentry Hardware KM 1.7.01.

     

    From how I've implemented the Sentry KM so far I have not used the STD:9/11 events it sends. Rather I use the STD:41 inbuilt recovery actions its sends whena fault is discovered or a threshold is breached. ( In fact I've filted them out completely).

     

    Therefore I would take the stance that data from the Sentry KM is event driven only ( like LOG scraping) and makes no sense in the BPPM data driven world. ( Am I wrong here ?).

     

    Somethings either broken or not. I CPU temperature breach will send a STD:41 event. ( THe Sentry KM sets many thresholds within the pconfig config upon discovery of each hardware object).

     

    THerefore I intend not to put Sentry KM into my Pnet IS data collector.

     

    Thoughts ?

     

    Gordon

  • 11. How to Monitor Hardware using BMC Proactivenet Agent
    Bertrand Martin

    Hi,

     

    Full disclosure: I work for Sentry, the developer of "Hardware Sentry KM".

     

    Hardware Sentry KM is not event-driven, quite the opposite: it actively polls the monitored systems to check the health of each component.

     

    When something bad happens (disk failure, temperature too high), a standard PATROL threshold is breached and an STD/11 event is generated. If you have imported your PATROL thresholds into ProactiveNet, you should get a native PNet alert automatically. You can also process the STD/11 event with BEM the very same way you would do with a BMC KM.

     

    In addition to the standard mechanism, Hardware Sentry KM triggers an additional STD/41 event with much more information about the actual problem, the faulty device and how to solve the problem. This event is actually configurable. In a PNet environment, I would recommend NOT using this STD/41 event and stick to the standard mechanism (as described above).

     

    Also, I strongly recommend that you use the latest version of Hardware Sentry KM (1.8.00) that has been released a few days ago:

    http://www.sentrysoftware.com/Products/Hardware_Downloads.asp

     

    This version better copes with BMC ProactiveNet.

     

    Hope this helps!

     

    Bertrand

  • 12. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Garland Smith

    Hello Bertrand,

     

     

     

    Would you mind offering some comments about SENTRY Monitoring Studio as

    well?

     

    Also, if there are any other SENTRY offerings in the PATROL/BPPM arena, I'd

    be interested

     

    in those as well.

     

     

     

    Thank you,

     

    Garland Smith

  • 13. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Gordon James

    Hi Bertrand. THanks for that up date.

     

    By event driven I meant that that I rely on the STD:41 events the Sentry KM sends to the PatrolAgents PEM and hence BII4Patrol into BEM. (Not the monitoring mechanism itself)

     

    Given that it provided the veiwer with a vast amount of information to the cause of the alert I decided to use these rather than the STD:9/11 parameter threshold beaches. Plus I didn't have to do any text enrichment in BEM

     

    I also found the Sentry KM incredibily noisey (1.7.00 admittedly). When a connector failed each "consumer" parameter of that connector went into alarm (such as discovered disks). causing message storms.

     

    As many of the parameters for Sentry KM (I am using the UCS config also) are "status" values (which I assume are boolean) then I still only see the benefit of using the STD:41 events and not the up/down values of the parameters themselves being recorded in BPPM.

     

    I will have a look at the 1.8. ( And I thought I was on top of things by deploying 1.7.01)

  • 14. Re: How to Monitor Hardware using BMC Proactivenet Agent
    Bertrand Martin

    Yeah 1.7.00 was quite noisy and had difficulties to cope with failures of the underlying instrumentation layers. This has been improved in both 1.7.01 and again in 1.8.00.

     

    There are several ways now to better handle a flaky hardware instrumentation layer:

    - change the "Alert after N times" value for the "Missing" parameters (done through a general KM Command, it's not a per instance settings, thank God)

    - disable the "Missing Device Alert" mechanism altogether (a component that is no longer discovered will simply be removed from the monitoring without any alert)

     

    Let us know if you have difficulties with this, it's always good to get feedback!

     

    Thanks!

    Bertrand

1 2 Previous Next