Table of Contents

opReports 3.2.1

...

• Improves the QoS report by providing 'Standardised Quality of Service' on Cisco, Huawei, Juniper and Teldat devices insofar as these devices support QoS.
  • Teldat proprietary BRS is also interpreted as QoS insofar as BRS implements QoS;
  • opReports 3.2.0 does not have a dependency on any particular version of NMIS8;
  • NMIS8 modelling needs to be set up correctly for the Standardised QoS report to work correctly.
    The following files have been developed to assist in regard to NMIS modelling to support Standardised QoS:
    • These files are examples that should be reviewed and adapted as needed before implementation:
      • Plugin to support Huawei QoS devices at nmis8/conf/plugins/QualityOfServiceStattable.pm: QualityOfServiceStattable.pm
      • Common model file to support Huawei QoS devices at nmis8/models/Common-Huawei-cbqos.nmis: Common-Huawei-cbqos.nmis
        • QualityOfServiceStat
      • Example model file at nmis8/models/Model-HuaweiRouterAR2240-uses-common.nmis: Model-HuaweiRouterAR2240-uses-common.nmis
      • Plugin to support Juniper CoS devices at nmis8/conf/plugins/jnxCoStable.pm: jnxCoStable.pm
      • Common model file to support Juniper CoS devices at nmis8/models/Common-Juniper-jnxCoS.nmis: Common-Juniper-jnxCoS.nmis
        • Juniper_CoS
          • Please note that TotalDropPkts in this file is calculated as sum of jnxCosIfqTailDropPkts and jnxCosIfqTotalRedDropPkts as a 'calculate' example:
            • TotalDropPkts can be adapted to rather be only jnxCosIfqTotalRedDropPkts, or can be disabled completely by commenting out the entry
      • Common model file to support Teldat QoS and BRS at nmis8/models/Common-Teldat-cbqos.nmis: Common-Teldat-cbqos.nmis
        • TeldatQoSStat
        • TeldatBRSStat
      • Example model file at nmis8/models/Model-TeldatM1-uses-common.nmis: Model-TeldatM1-uses-common.nmis
      • Teldat QoS graph file at nmis8/models/Graph-TeldatQoSStat.nmis: Graph-TeldatQoSStat.nmis
      • Teldat BRS graph file at nmis8/models/Graph-TeldatBRSStat.nmis: Graph-TeldatBRSStat.nmis
      • Teldat graph file at nmis8/models/Graph-mem-proc-teldat.nmis: Graph-mem-proc-teldat.nmis
    • The following changes will also be needed in NMIS8:
      • nmis8/models/Common-database.nmis
        • add following two lines after 'QualityOfServiceStat' => '/nodes/$node/interface/hwqos-$index.rrd':
        • 'TeldatQoSStat' => '/nodes/$node/interface/tdqos-$index.rrd',
          'TeldatBRSStat' => '/nodes/$node/interface/tdbrs-$index.rrd',
      • nmis8/conf/Model-Policy.nmis
      • set Juniper_CoS => 'true' in 999 => {...} section
      • nmis8/models/Model.nmis
        • needs approporate entries for the Huawei and Teldat models to use their respective example models:
          • 'HuaweiRouterAR2240-uses-common' => 'AR2240'
          • 'TeldatM1-uses-common' => 'M1'
      • The following Juniper device settings need checking:
      • Edit each node and set 'CBQoS' to 'both' or 'out' then update each node
      • Update all device nodes affected by these changes
• Please read the known_reports_cache documentation:
  • Although the known_reports_cache has not changed since version 3.1.11, It is important to understand the benefits of applying the cache
    and that deleting reports via cronjob or commandline should be followed by a command to flush the known_reports_cache.

...

• Fixed bug where dos type files were not processed properly for Node Selection "from Node, Interfaces and Type List File (Upload).
• removed unused config items default_report_(from/to)
  
  

• load_availability_report (and thus load_groupedav_report) now honors undocumented and normally missing config option

  • opreports_availability_strict (default true):

    • if missing or 'true', then the normal behaviour for nodata-or-normal is used (ie. if reachability isn't present, it counts as nodata):

      • no data = 'down' when opreports_availability_strict=true

    • If set to 'false', then records with missing reachability but existing response time are fudged up so that the reachability = 100 (and loss = 0 if that's also missing) and therefore such a record does NOT count as nodata.

      • no data = 'up' when opreports_availability_strict=false

    • In both cases, if reachability is missing but response time is present, a debug3 about the inconsistency is logged. This applies to both availability report data and availability report graphs.
      
      

• node+intf regex now looks at Description as well as ifDescr not Description.

...