DFM HighDiscardRate

Unanswered Question
Mar 18th, 2009
User Badges:


We have since a few days email from DFM concerning HighDiscardRate error.

EVENT DESCRIPTION = HighDiscardRate::Component=PORT-192.168.x.x/10627 [Gi2/0/27] ;Type=ETHERNETCSMACD;InputPacketRate=8480.7 PPS;MinimumDiscardRate=8333.328;DuplexMode=FULLDUPLEX;OutputPacketRate=112.754166 PPS;DiscardThreshold=5;InputPacketDiscardPct=0.0 %;InputPacketDiscardRate=0.0 PPS;MaxSpeed=1000000000;OutputPacketDiscardRate=1.7895698E7 PPS;OutputPacketDiscardPct=1.5871289E7 %;

EVENT DESCRIPTION = HighDiscardRate::Component=PORT-192.168.x.x/10627 [Gi2/0/27] ;Type=ETHERNETCSMACD;InputPacketRate=8436.88 PPS;MinimumDiscardRate=8333.328;DuplexMode=FULLDUPLEX;OutputPacketRate=104.129166 PPS;DiscardThreshold=5;InputPacketDiscardPct=0.0 %;InputPacketDiscardRate=0.0 PPS;MaxSpeed=1000000000;OutputPacketDiscardRate=1.7895698E7 PPS;OutputPacketDiscardPct=1.7185892E7 %;

The traffic is still normal and is not affected by the strange 1.7185892E7% percentage !

Can anyone help ?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Wed, 03/18/2009 - 10:01
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

This is a known issue. Sometimes, due to the state of the object being polled, the utilization reaches an absurd value. This is one such example. This is being addressed in DFM 3.2 due out this summer.

In the meantime, assuming there isn't a counter bug on the device, removing the device from DFM, and re-adding it should allow DFM to resume proper management. You can also try unmanaging the affected interface(s) under DFM > Device Management > Device Details (don't forget to apply changes). Then remanage the objects.

MathieuJM_2 Wed, 03/18/2009 - 14:24
User Badges:

Thank you. I will try the workaround. I have forgot to mention that we run LMS 2.6. Not sure for the DFM version. Will the DFM 3.2 be available for LMS 2.6 ?

Joe Clarke Wed, 03/18/2009 - 14:34
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

No. DFM 3.2 will be part of LMS 3.2.


This Discussion