QoS Report

New in version 3.4.1 for NMIS8 and version 4.2.1 for NMIS9

QoS Report will generally not include interfaces in the report that have 'collect=false' set.
However,  from opReports versions 3.4.1 and 4.2.1, Standardised Quality of Service supported devices that do not support CBQoS will display interface QoS even though the interface has a setting of 'collect=false'.

New in version 3.3.0

Model and Vendor details are provided per node in the report.

Bold Introduction

The QoS report is intended to provide an overview of the Quality of Service configuration and utilisation of the selected nodes.

QoS Report will not include interfaces in the report that are disabled.


To assist in the assimilation of the data, a few simple rules have been applied to the statistics to assist with highlighting some possible problem areas.

Queue Drop

/path/to/omk/conf/opCommon.nmis config option opreport_rules/qos_droppkt (default 1) applies:
This condition indicates that a QoS Policy is being exceeded and packets in this class have been dropped. It may or may not be impacting applications, depending on how they handle packet loss. For example, HTTP will generally handle packet loss with no problems, while voice and video do not suffer packet loss very well at all.
  If an interface utilisation is greater than 0% input and 0% output;
  AND DropPkt is greater than opreport_rules/qos_droppkt (default 1) packet per second;
  THEN this class is highlighted yellow.

Class Under Utilised

/path/to/omk/conf/opCommon.nmis config option opreport_rules/qos_lowutil (default 1) applies:
This condition indicates that the QoS class was configured to be used for traffic, and there are VERY low levels of traffic in that class. It might be possible to update the QoS policy allocating some of this bandwidth to other classes.
  If an interface utilisation is greater than 0% input and 0% output;
  AND the Policy Percent is greater than 0 percent;
  AND PrePolicyUtil is less than opreport_rules/qos_lowutil (default 1) percent;
  THEN this class is highlighted yellow.

Class Utilisation Exceeding Policy

This condition indicates that QoS class was configured for a certain bandwidth and the traffic levels have exceeded the configured policy. This may not be a problem, depending on QoS configuration, traffic may be being forwarded or discarded, if necessary increase the bandwidth allocated to this class.
  If an interface utilisation is greater than 0% input and 0% output;
  AND PrePolicyUtil exceeds the classes configured bandwidth Percent;
  THEN this class is highlighted yellow.


A full report can be downloaded and viewed Here

Standardised Quality of Service - n
ew in version 3.2.0

The QoS report now provides '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/QualityOfServiceStattable.pm
        • copy from nmis8/install/QualityOfServiceStattable.pm
      • Common model file to support Huawei QoS devices at nmis8/models/Common-Huawei-cbqos.nmis
        • copy from nmis8/models-install/Common-Huawei-cbqos.nmis
        • QualityOfServiceStat
      • Example model file at nmis8/models/Model-HuaweiRouterAR2240-uses-common.nmis
        • copy from nmis8/models-install/Model-HuaweiRouterAR2240-uses-common.nmis
      • Plugin to support Juniper CoS devices at nmis8/conf/plugins/jnxCoStable.pm
        • copy from nmis8/install/plugins/jnxCoStable.pm
      • Common model file to support Juniper CoS devices at nmis8/models/Common-Juniper-jnxCoS.nmis
        •  copy from nmis8/models-install/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
        • copy from nmis8/models-install/Common-Teldat-cbqos.nmis
        • TeldatQoSStat
        • TeldatBRSStat
      • Example model file at nmis8/models/Model-TeldatM1-uses-common.nmis
        • copy from nmis8/models-install/Model-TeldatM1-uses-common.nmis
      • Teldat QoS graph file at nmis8/models/Graph-TeldatQoSStat.nmis
        • copy from nmis8/models-install/Graph-TeldatQoSStat.nmis
      • Teldat BRS graph file at nmis8/models/Graph-TeldatBRSStat.nmis
        • copy from nmis8/models-install/Graph-TeldatBRSStat.nmis
      • Teldat graph file at nmis8/models/Graph-mem-proc-teldat.nmis
        • copy from nmis8/models-install/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 appropriate entries for the Huawei and Teldat models to use their respective example models:
          • 'HuaweiRouterAR2240-uses-common' => 'AR2240'
          • 'TeldatM1-uses-common' => 'M1'
  • Since the QoS Report is a CBQoS Report, the following Node settings in NMIS need checking for Juniper, Huawei and Teldat compatible devices:
    • Edit each node and set 'CBQoS' to 'both' or 'out' then update each node
    • Update all device nodes affected by these changes
  • No labels