Date: Thu, 28 Mar 2024 21:45:14 +0000 (UTC) Message-ID: <1251717074.3960.1711662314274@skald.opmantek.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3959_566004452.1711662314273" ------=_Part_3959_566004452.1711662314273 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
NMIS has been collecting CBQoS data from Cisco Devices for a very long t= ime, to produce the necessary charts, it is only required to sent some of S= NMP MIBS. For more detailed reporting now supported in opReports, it = is necessary to collect additional CBQoS MIBS. The full list of MIBS = supported for CBQoS collection after this patch is applied are:
PrePolicyByte
DropByte
PostPolicyByte
NoBufDropPkt
PrePolicyPkt
The graphs in NMIS and opCharts show the key pieces of Data above.
By default when we discover a Cisco router with CBQoS configured the sys= temhealth data will be populated with a table of interfaces on which CBQoS = is configured and which policy they are using. It will not start coll= ecting QoS statistics. The reason is:
CBQoS collection Control Consideration= s
When managing a network of devices typically the largest amount of data = or elements collected is the interface data. e.g. an average of 5 int= erfaces per device.
So - if you imagine that each interface had 5 CBQoS Class Queues per int= erface we now have 30 elements instead of the original 5. As you can = see we have pretty much increased the collection and storage by 5 fold = ;!! As such we want to be careful about which devices we want QoS sta= tistics collection enabled for.
To enable the collection of CBQoS statistics, in addition to the invento= ry data, we need to set one of the Nodes properties. For the Node in = NMIS use Edit Node then find the property CBQoS and change it from "none" t= o one of "input", "output" or "both".
If you are using imports or automation for your node properties then you= need to set the Nodes.nmis property to 'cbqos' =3D> 'both',
This can be done via the CLI Node admin:
admin/node_= admin.pl act=3Dset node=3D{nodename} entry.cbqos=3Dboth ##= (or input or output).
Download the nmis-8.4-cbqos.tar.gz patch= ; then copy the patch file to the server to be patched. It is easy to= process this file if you are the root user and the file is in the root use= r home directory which is /root
#Backup current N= MIS code and config including models DATE=3D`date "+%Y-%m-%d-%H%M"` cd /usr/local/nmis8 tar cvf ~/nmis8-backup-$DATE.tar ./admin ./bin ./cgi-bin ./conf ./install .= /lib ./menu ./mibs ./models #Make sure NMIS is working before you patch it. /usr/local/nmis8/bin/nmis.pl type=3Dcollect debug=3Dtrue node=3D<node to= test> #Get CP working right. (no prompts) unalias cp #Unarchive the NMIS tarball cd ~ tar xvf nmis-8.4-cbqos.tar.gz =20 # Patch the Code Base cd nmis-8.4-cbqos cp -r * /usr/local/nmis8
If there are no customisations to your CBQoS model files, copy the new o= nes over the old ones, or you will need to merge the differences manually.<= /p>
# Copy the model-= install files over the production files. cp /usr/local/nmis8/models-install/Common-cbqos-in.nmis /usr/local/nmis8/mo= dels/Common-cbqos-in.nmis cp /usr/local/nmis8/models-install/Common-cbqos-out.nmis /usr/local/nmis8/m= odels/Common-cbqos-out.nmis
# optionally audi= t your config /usr/local/nmis8/bin/nmis.pl type=3Daudit # fix your config /usr/local/nmis8/bin/nmis.pl type=3Dconfig # fix permissions /usr/local/nmis8/admin/fixperms.pl # test polling /usr/local/nmis8/bin/nmis.pl type=3Dcollect debug=3Dtrue node=3D<node to= test>