From: W.J.M. N. <Wim...@nl...> - 2011-05-10 13:19:07
|
Hello, > Is there a way to ignore an interface based on text in the alias? The > docs show: > > The exceptions file is contains rules which are only applied > against repeater type data aliases. > > An example of a exceptions file is as follows: > > -<start file>----------------------------- > > ifName : alarm : Gi.+ > ifName : ignore : Nu.+|Vl.+ > > -<end file>------------------------------- > > You can see that each entry is on its on line, with three > fields separated by colons. The first field is the primary > data alias that the exception should be applied against. The > second field is the exception type, and the third field is > the regular expression that the primary alias is matched > against. Exception regular expressions (unlike non-numeric > thresholds) ARE anchored, and thus need to match the primary > oid EXACTLY. > > > What I would like to do is have the interface ignored if the text of the > alias (description) has something like "NEW TURNUP","NOT LIVE" or > "DECOM" . > > The folks that do the port provisioning load the configs and the port > will be left in a down state. This keeps the Xymon display red for the > router. How are other folks handling this? Or is it as simple as an > exception using the "ifAlias" oid in the exceptions file? > We achieve something like that by using a script which generates amongst others the Devmon configuration. That script periodically checks the status of all network equipment and also the status of all networkports. The interfaces to be skipped are put into the Devmon configuration in the Xymon hosts.cfg configuration file: 0.0.0.0 SomeSwitch # DEVMON:except(all;ifName;i:Gi0/1|Gi0/2) Moreover, in the templates, the exceptions file we do not use the keyword 'ignore', only the keyword 'only'. In this way both selections will be applied. ( An 'except' in the Xymon hosts-file overrules an 'ignore' in the template.) Regards, Wim Nelis. ******************************************************************************************************* The NLR disclaimer (http://www.nlr.nl/emaildisclaimer) is valid for NLR e-mail messages. ******************************************************************************************************* |