5 Replies Latest reply on Oct 6, 2008 12:10 PM by DLI-Alford

    Monitoring Total Errors on a Router Interface

       Hi,

       I'm having a little trouble setting up some alerts for my company.  The way that we want to setup the monitoring and alerts for interface errors, CRCs, etc. is not in/out errors in the past hour or 24, but total errors since counters have been cleared (these are all cisco routers/switches).  So far with NPM I've been able to setup the monitoring that I needed with little trouble, however I'm not sure if there is a way to do custom polling like this, since my needs have been fairly basic so far (up and down alerts, running reports, etc).  Any help would be appreciated.  Thanks.

       

      -Garrett
       

        • Re: Monitoring Total Errors on a Router Interface
          HemiTruck

          how often are you clearing the counters?


          and how many errors are you looking to trigger at? (how big of a delta)

            • Re: Monitoring Total Errors on a Router Interface

              Well, we usually try to address any issues with the errors as soon as we see them and then clear the counters to have a fresh look, so generally we don't clear them until after we find a problem.  We would like the trigger to go off as soon as they start accumulating, but I would say after 100 coming in is more realistic so we don't have so many alerts.

               

                • Re: Monitoring Total Errors on a Router Interface
                  aLTeReGo

                  I think the issue you'll face creating Universal Device Pollers for this purpose is that the Cisco "clear counters" command does not reset the SNMP counters, just the counters you see via the CLI. The only way to clear the SNMP counters on a Cisco switch that I'm aware of, is to reboot the switch.


                  Even if that wasn't the case this could be done using the Universal Device Poller, but it would be a total pain in the ass to setup. For instance, if you wanted to monitor receive errors for interface 5 on a Cisco 3750 switch, you'd need to create a UDP to monitor OID 1.3.6.1.2.1.2.2.1.14.10005. To monitor transmit errors on the same interface, you'd need to create a UDP for OID 1.3.6.1.2.1.2.2.1.20.10005. As you can see this doesn't scale real well. For a 48 port switch you would need 96 UDPs to capture the information you're trying to collect.

                  • Re: Monitoring Total Errors on a Router Interface
                    HemiTruck

                    ok this told me what I wanted to hear.


                    You want to know as soon as they start building up.


                    If you trigger based on the last hour this will give you the alert you want.


                    so set your trigger for >100 errors  in last hour and i am pretty sure you will get the results you want.  Becasue this will trigger the moment that the count goes over 100 and not wait till the top of the hour if that was what you were worrying about.


                    Did this for all Ethernet interfaces for the Net Engineers and they are able to find mismatch duplexes and bad fiber SLPs really fast