DX Unified Infrastructure Management

 View Only
  • 1.  SNMPCollector Polling Interval

    Posted Nov 13, 2017 10:27 AM



    We were experiencing some major database growth for UIM and after some troubleshooting we found out that the biggest disk space consumers and also the tables with the most writes were those connected to the following QOSs:




    Do you know what is the default polling interval for them? Is it the 300 s value found in Raw Config?

    I was thinking about changing the polling interval to reduce used space.


    Thank you!

  • 2.  Re: SNMPCollector Polling Interval
    Best Answer

    Broadcom Employee
    Posted Nov 13, 2017 12:25 PM

    Hi Marius,


    That is the correct parameter, however, there is a little bit more to it.

    Please reference the link below:

    snmpcollector Theory of Operations - CA Unified Infrastructure Management Probes - CA Technologies Documentation 

  • 3.  Re: SNMPCollector Polling Interval

    Broadcom Employee
    Posted Nov 14, 2017 09:25 AM

    This question is tracked in a support case.

  • 4.  Re: SNMPCollector Polling Interval

    Posted Nov 20, 2017 01:46 PM

    There are a couple of ways to attack this probably. 


    1. Don't monitor all interfaces. Now this is way easier said then done. Comparing Spectrum to UIM is like comparing apples to oranges but Spectrum does a great job identify upstream interfaces and in turn makes it really easy to only monitor those interfaces. UIM is not as mature as Spectrum in this space at the moment so you have to try to use the template filters to try to get the job done.


    2. Adjust the data retention for those particular QOS tables. If you are storing less raw data then your table will shrink. You have to determine what is the absolute minimum amount of interface raw data you can live with. 


    Something else you could also look into is how many days worth of data do you have in those tables. If you are using data_engine to perform your data-rollup it is worth taking a look at. I work for a MSP and we have a TON of data. What we found is that the data-rollup job was failing when it hit the interface data tables. By the time we caught it we had at least double the days worth of data as what we set in our retention period. Hopefully that isnt your issue but that is something to look for.