Table of Contents |
---|
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
This release requires updated licenses, please contact Opmantek Support to organise new licenses
...
- Model and Vendor details are provided per node in the report.
...
- where uptime is shorter than
uptime_shortest_days
(default 7); or - where uptime is longer than
uptime_longest_days
(default 365).
...
opReports 3.2.1
This version was released on 08 May 2020.
Highlights
This version:
- makes the following improvements:
- Interface Capacity Report:
- Adds Group column; and
- Adds Availability % column which provides Availability % per interface;
- Grouped Interface Capacity Report:
- Adds Availability % column which provides Availability % per interface;
- WAN Report:
- Adds Speed In and Speed Out columns which provide the applicable value per interface; and
- Adds Max Bandwidth In and Max Bandwidth Out columns which provide the applicable value per interface.
- Interface Capacity Report:
opReports 3.2.0
This major update of opReports was released on 21 February 2020.
Highlights
This version:
...
- 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
- Please note that TotalDropPkts in this file is calculated as sum of jnxCosIfqTailDropPkts and jnxCosIfqTotalRedDropPkts as a 'calculate' example:
- Juniper_CoS
- 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
...
- 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',
...
- set Juniper_CoS => 'true' in 999 => {...} section
...
- needs approporate entries for the Huawei and Teldat models to use their respective example models:
- 'HuaweiRouterAR2240-uses-common' => 'AR2240'
- 'TeldatM1-uses-common' => 'M1'
...
- Edit each node and set 'CBQoS' to 'both' or 'out' then update each node
...
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
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).
- where uptime is shorter than
- 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 fromuptime_shortest_days
to
uptime_longest_days
.
- Please read Generating Reports for generating on-demand reports: this new option is uptime_exceptions on that page.
- The Uptime Report now offers this new option which defaults to the original behaviour of only returning nodes according to opCommon configuration settings:
- New option 'Exceptions Report' (Default: true)
- QoS Report:
opReports 3.2.1
This version was released on 08 May 2020.
Highlights
This version:
- makes the following improvements:
- Interface Capacity Report:
- Adds Group column; and
- Adds Availability % column which provides Availability % per interface;
- Grouped Interface Capacity Report:
- Adds Availability % column which provides Availability % per interface;
- WAN Report:
- Adds Speed In and Speed Out columns which provide the applicable value per interface; and
- Adds Max Bandwidth In and Max Bandwidth Out columns which provide the applicable value per interface.
- Interface Capacity Report:
opReports 3.2.0
This major update of opReports was released on 21 February 2020.
Highlights
This version:
- Improves the QoS report by providing 'Standardised Quality of Service' on Cisco, Huawei, Juniper and Teldat devices insofar as these devices support QoS.
- 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.
- Although the known_reports_cache has not changed since version 3.1.11, It is important to understand the benefits of applying the cache
...