• State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 38 subscribers
  • Views 1249 views
  • Users 0 members are here
Options
Related
This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

How to monitor Burst data in interface.

krishnamishra0786

Use the below step that will help you - i used same is working fine emoticons_happy.png

  • Save a copy of the original SolarWinds.Interfaces.Collector.dll.config file to your local drive as a backup file, in case you need to roll back later.



  • SolarWinds strongly recommends that you only edit the SolarWinds.Interfaces.Collector.dll.config file as instructed. Any additional modifications may result in system performance issues or may create an error state.



  1. 1.     Log in to your Orion server.
  2. 2.     Go to C:\Program Files(x86)\SolarWinds\Orion\Interfaces\
  3. 3.     Open SolarWinds.Interfaces.Collector.dll.config in a text editor.
  4. 4.     Replace the following line:

<add key="ValidateCounters" value="True" />

with

<add key="ValidateCounters" value="False" />




  • Restart SolarWinds services. Refer to Start and stop Orion services.

 
Note - Same step you should apply on all additional poller including the additional web server.

  • 0

    This works great for monitoring circuits that are "burstable".  With many of our circuits, we have "purchased" a set amount of bandwidth but which are able "burst" over that set amount.
    To that end we monitor for the purchased amount but configure for the bust amount.

    Example - Circuit 10/100, The purchased amount is 10 meg of a 100 meg circuit.

    First the bandwidth on the device interface is set to 100 meg (the maximum burstable rate).

    Second the Custom Tx and Rx bandwidths are set within Orion for that interface to the "purchased" amount.

    pastedImage_3.png

    Third the change mentioned [<add key="ValidateCounters" value="False" />] is set on ALL the polling engines.

    With this set-up we are able to

    1) Track the amount of bustable bandwidth used (which we are of course we are billed for), but also this allows us to see if we need to increase the amount of purchased bandwidth

    2) Alerting on utilization over 100% - Bust is being used

    3) With netflow, we can see who and what is causing the overage.

    Prior to this setup we did not see the bust.  Now we are able to see the bust / overage utilization of a circuit and alert

    pastedImage_1.png

    So if you have an environment that has bustable circuits, I would suggest you looking into this type of setup.

SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 195,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.

SolarWinds Customer Success Center Certification Media Vault Link Accounts
About THWACK Blogs For Government Edit Settings Free Tools & Trials
Legal Documents Terms of Use Privacy California Privacy Rights Security Information
©2024 SolarWinds Worldwide, LLC. All Rights Reserved.