2 Replies Latest reply on Feb 2, 2010 9:08 AM by pyro13g

    Problem with Discards Today


      I have this one regarding:


      Interfaces with Errors+Discards greater than 1000 Today


      I have an interface showing 73,729 receive error for the day.  When you look at the chart for the interface, it's visually obvious that the number is wrong.  I dumped the chart data in excel and the total is really 226809 which matches the total I get from another monitoring system I fired up to check it.

      On another note, might to think about converting discards to percent of packets to add some better context to the possible impact.  I was surprised to see errors in a separate table from Interface Traffic_Details.

        • Re: Problem with Discards Today
          I have a similar issue. Interface discards on my ASA are incrementing by thousands per hour. After a call into Cisco I was advised that the total input discards as a percentage of total input packets was less than 1% and within normal ASA operating standards.

          I'd like to see errors and discards represented as percentage instead of a flat number.
            • Re: Problem with Discards Today

              All those type of thresholds in NPM need changed to reflect context better.  1000 errored packets out of 10,000 is bad, out of 100,000 I don't care. 

              But there is a gotcha with discards.  Packets discarded due to QoS on a CISCO Router are represented in in/out discards.  So you also need to know that a QoS policy is applied to the interface.

              Since the QOS-CBP-TARGET MIB isn't supported on most of the routers, you have to handle the MIBs with the QoS info in a special way to find out what Policies apply to what interface.  Then, when the router is rebooted, you have to rediscover all of it because the Indexes are never reused after a reboot.