Guest

Preview Tool

Cisco Bug: CSCuo49635 - invalid traffic numbers inserted from plan files skew graphs

Last Modified

Nov 14, 2014

Products (1)

  • Cisco MATE Live

Known Affected Releases

5.6

Description (partial)

Symptom:
invalid traffic numbers inserted from plan files skew graphs

Conditions:
This is a regression from 5.4.  In a very few plan files which Cox uses, some traffic measurements contain large negative numbers which throws off aggregate calculations and makes graphs unreadable for specific time periods.  I will attach a few plan files which show this.  The 5.4 ml_insert_plan tool replaces negative traffic numbers with null.  MATE Design similarly displays negative traffic numbers as n/a.  mate_convert shows the negative numbers.  An excerpt from a Cox plan file, using mate_convert:
<NetIntIfMeasurements>
Node    MeasType        NetIntIndex     Interface       Queue   OutOctets_avg   OutOctets_samples       InOctets_avg    InOctets_samples        OutPackets_avg  OutPackets_samples      InPackets_avg   InPackets_samples       InErrors_avg    InErrors_samples        OutDiscards_avg OutDiscards_samples     OutOctetDiscards_avg    OutOctetDiscards_samples
172.17.248.1    Rate    625                     18614.4957424239        18614.4957424239        6283.22422550568        6283.22422550568        2179446.31610517        2179446.31610517        1567793.79852711        1567793.79852711        0.0     0       0.0     0
172.17.249.35   Rate    615                     -16001624.268465        -16001624.268465        -16041788.8898604       -16041788.8898604       -2006680465894.04       -2006680465894.04       -2006685581733.39       -2006685581733.39       0.0     0       0.0     0

In Cox's case, the plan files are from March 14, 2013.  On 3/14, a few plan files had this problem across many interfaces.  I have not checked all plan files.  The plan files are version 5.3.

The collector is incorrect in generating plan files with negative traffic numbers.  This is a separate issue.  Hopefully already fixed.

This problem is severe for customers wishing to migrate older data to ml6+ w/Informix using ml_insert_plan.  There is probably a
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.