DX Unified Infrastructure Management

  • 1.  SNMPCollector Tips/Tricks/Suggestions for Smooth experience.

    Posted May 02, 2018 08:25 AM

    I am starting this discussion to hopefully get some advice/tips/tricks etc from others using the Probe in all different size environments, on changes or configuration updates that work for them and get the probe running smoother, more effective, and less chatty (less false positives) .

     

    One thing I noticed in our environment which is about 500 Network devices we run a discovery process every 24 hours. We have to though manually sometimes go in on devices and do a manual “Force Component Re-Discovery” to get updates/state changes of the device to take effect. Anyone else experience this and or come up with a fix?

    I was thinking if there was a way to cause this “Component Re-discovery once every hour or (whatever time variation you want) on each device maybe that would help take away some of the alarms we get when an interface has changed from UP to Down for example and the template does not apply properly so we miss alerts or vice versa.

     

    Looking forward to hearing others feedback, experiences, suggestions, etc.

     

    Thanks,


    Bob



  • 2.  Re: SNMPCollector Tips/Tricks/Suggestions for Smooth experience.

    Posted May 02, 2018 08:48 AM

    Could be a result of devices that are poor responders to snmp polling. Often setting the timeout down to around 5 and retries up to around 10 to 15 helps.



  • 3.  Re: SNMPCollector Tips/Tricks/Suggestions for Smooth experience.

    Broadcom Employee
    Posted May 02, 2018 08:11 PM

    Hi ,

    Are you already using below option 

    From SNMPcollector probe GUI change  the "hours between rediscovery". This triggers a "scheduled rediscovery.

     

    https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/snmpcollector-snmp-data-monitoring/snmpcollector-ac-configuration#snmpcollectorACConfiguration-ChangetheDiscoveryInterval

     

    Can also try the below custom solution 

    BAT - Force component Rediscovery for all SNMPC profiles

    https://communities.ca.com/docs/DOC-231173140-bat-force-compontent-rediscovery-for-all-snmpc-profiles



  • 4.  Re: SNMPCollector Tips/Tricks/Suggestions for Smooth experience.

    Posted May 07, 2018 08:11 AM

    Franklin,

     

    Currently we have setup in the UMP a discovery every day at 6:00 AM, however in the actual SNMPC probe we have to manually go and do a Query Discovery Server. The "hours between rediscovery" setting in the probe we are not using. If we use that and set it at say 24 hours is that the same as the UMP discovery process setup where we have it set to run every day at 6:00 AM, or will that setting also automatically do the query of the discovery server so that we do not have to manually do that each morning?

     

     

    The batch to force component re-discovery looks good, a question on that. As an example lets use this scenario that we run into a lot:

     

    We have a template that applied to all devices and at the interface level we have 2 rules for the interface template. The first rule is if admin status 1 and the second rule is if OperStatus not 2 than apply the interface template. In our case if an interface changes from up to down we get an alarm by design. If that interface is still down and alarming and we were to run a force component re-discovery than the interface is not going to pass the template check so than the template will not get applied so the interface would no longer be monitored is that not correct?

     

    I do realize that in this case we would still have the original alarm that would be alarming, however I would think than once the interface is brought back up we would have to run another component re-discovery is that correct? So that than once the interface is up the template would check its rules again and pass so than it could apply the template.



  • 5.  Re: SNMPCollector Tips/Tricks/Suggestions for Smooth experience.

    Broadcom Employee
    Posted May 07, 2018 08:09 PM

    Hi ,

    Hours Between Rediscovery: Enter the number of hours between component discovery updates.
    To turn off automatic discovery, set this value to 0.

     

    Note :there is no option to fix when this runs at a specific time .There is already idea for this feature

    https://communities.ca.com/thread/241762621-is-there-a-way-to-set-the-time-that-the-snmpcollector-probe-performs-the-automatic-re-discovery-of-devices-that-are-already-configured

     

    ->For your use case I believe running the batch script after fixing the issue of alarm i.e interface down might be required

    i.e  once the interface is up the template would check its rules again and pass so than it could apply the template.



  • 6.  Re: SNMPCollector Tips/Tricks/Suggestions for Smooth experience.

    Broadcom Employee
    Posted May 08, 2018 04:12 AM

    as franklin mentioned, when running force component rediscovery - existing templates are getting re-evaluated.