CricketGraphing

Generating the configuration for network Cricket graphing

The graphs are collected and plotted on salado, the net manager host. The configuration for the grapher is held in /project/cricket, owner by the 'cricket' user, whereas the CGI script itself is held in the default /var/www tree.

The naming in the graphs is auto-generated based on the port-name definitions in the router itself. So, to update the names alongside the interface numbers, forst update the running config of the router, and then run:

ssh cricket@salado
cd /project/cricket/deploy/cricket-config/
../cricket/util/genRtrConfig --snmpv2c -C public deel-man
cd ../cricket
./compile

and similarly for "nikopn-man", "sw-public-grid-01", "sw-public-sec-01", "sw-mngt-01" and even "opnstorage-sw-easteregg-01" (through the VLAN4 interconnect from deel to nikhef).

The graphs are generated every 5 minutes from crontab with

*/5 * * * *     /project/cricket/deploy/cricket/collect.sh > /dev/null 2>&1

and look at the results at http://salado.nikhef.nl/cgi-bin/grapher.cgi

Hooi-ei aggregated links

These configuration are generated by a simple perl script. Invoke with (untested):

perl ~/genhooiei.pl >> opnstorage-sw-easteregg-01/Defaults
cd /project/cricket/deploy/
./compile

Sources

All sources are kept in /project/cricket/src/:

-rw-r--r--  1 root    root 411265 Mar 28  2004 cricket-1.0.5.tar.gz
-rw-r--r--  1 root    root  47753 Aug 29  2007 genRtrConfig_1_5_50.tar.gz
-rw-r--r--  1 root    root 103555 Aug 13  2007 lzo2-2.02-3.el4.rf.i386.rpm
-rw-r--r--  1 root    root 352993 Feb  2  2007 openvpn-2.0.9-1.el4.rf.i386.rpm
-rw-r--r--  1 root    root  68407 Mar 19  2008 SNMP_Session-1.12.tar.gz

What About Hefrouter?

Also hef-router is now part of the aggregated monitoring infrastructure for routers at salado.

Formerly, statistics for hefrouter are kept at http://www.dutchgrid.nl/cgi-bin/grapher.cgi using legacy scripts and cronjobs on beerput.nikhef.nl (user netmon). The configuration is manually maintained by Paul.

Interventions

Changing the maximum scale of a dataset

Sometimes, gegRtrConfig incorrectly determined the maximum speed of an interface. In particular, a 10G interface may end up being a 4295MBps interface :-) To at least fix the rrd database, try something like:

rrdtool tune 10gigabitethernetX_Y.rrd -a ds0:1e+10 -a ds1:1e+10 -a ds2:1e+10 -a ds3:1e+10

in /project/cricket/deploy/cricket-data/NETWORK_DEVICE/.