|
From: W.J.M. N. <Wim...@nl...> - 2011-08-15 08:35:54
|
Hello, in our Cisco-based network there is somewhere a source of broadcast or multicast traffic, which causes huge packet losses in the core of the network. This source is about once a week during a short period active. In order to find this source, a (temporary) template to measure and check the incoming multicast and broadcast packet rates is created. The template, shown in the attachment, exhibits one problem: it reports that the threshold value is undefined. Non-unicast packet rates above the yellow threshold do not result in a status change, which is consistent with the threshold value being undefined. The first part of the status message, as shown in a browser, is: <b>Non-unicast traffic rate:</b> Input rate alert thresholds: yellow=Undefined [p/s], red=Undefined [p/s] Output rate alert thresholds: None <table border=1 cellpadding=5> <tr><th>If name</th><th>Multicast rate in</th><th>Broadcast rate in</th><th>Multicast rate out</th><th>Broadcast rate out</th></tr> As far as I can tell the template definition is correct. A test run, with options "-1 -h <ASwitch>" did not show any errors or warnings. We are using Devmon r216. Has someone an idea of what is wrong? Is it perhaps caused by the fact that the OIDs for which a test is defined are used themselves in the computation of other OIDs in another test? Regards, Wim Nelis. ******************************************************************************************************* The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages. ******************************************************************************************************* |