Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Table of Contents

opReports 3.4.0

RELEASED 01 Oct 2020.

Upgrade Notes

The new upcoming release of opReports 3 will work on Opmantek's latest and fastest platform, however, the currently installed products are incompatible with this upgrade. 
To find out more about this upgrade please read: Upgrading Opmantek Applications

opReports 3.3.0

This version was released on 16 July 2020.

Highlights

(warning) This release requires updated licenses, please contact Opmantek Support to organise new licenses

  • makes the following improvements:
    • QoS Report:
      • Model and Vendor details are provided per node in the report.
    • Uptime Report:
      • New option 'Exceptions Report' (Default: true)

        • The Uptime Report now offers this new option which defaults to the original behaviour of only returning nodes according to opCommon configuration settings:
          • where uptime is shorter than uptime_shortest_days (default 7); or
          • where uptime is longer than uptime_longest_days (default 365).
        • When 'Exceptions Report=false', the Uptime Report provides a third column with the remainder of nodes that have an uptime to report,
          in other words, those with uptime from uptime_shortest_days to uptime_longest_days.

        • Please read Generating Reports for generating on-demand reports: this new option is uptime_exceptions on that page.

...

  • 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.

...