Hi Kenneth, Recently there was a thread on this list regarding Interface-AlarmManagement via PolicyManager.
You can use a Port-Policy for this. First step is to write a search that finds the ports you want to disable the alarms on. If you're using the interface description then you need filter on the attribute ifAlias (0x11f7e). A basic search could look like this: <policy-search-criteria name="Search all ports to disable alarms"> <and> <attr-match match-type="equal-to" id="0x11ee8" value="15" /> <attr-match match-type="contains" id="0x11f7e" value"[SE]" /> </and> </policy-search-critera> This would grep all models with model_class Port and ifAlias containing [SE]. But this would mean Spectrum polls the ifAlias attribute on all port models. Depending on the number of interfaces you have in your network this can be a lot of load for the SS. If you're ablte to narrow down the search with internal attributes then I highly recommend that approach. In the next step you combine the search with the policy-setting "Disabled Port Monitoring/No Alarms" which ships as a default-setting. Be aware that since ifAlias is an external attribute, the policy will get enforced depending on the policy-reenforcement-interval which is usually 24h. So it can take up to 24h before alarms will get disabled on a port after your network-folks have configured the interface description. You can speed this up by setting the interval to the lowest value of 1h but this comes with a higher load on the SS. Hope this helps, Jan Operations Support Systems (OSS) EWE TEL GmbH Cloppenburger Straße 310 26133 Oldenburg E-Mail: [email protected] Internet: www.ewe.de Handelsregister Amtsgericht Oldenburg HRB 3723 Vorsitzender des Aufsichtsrates: Dr. Werner Brinker Geschäftsführung: Konrad Meier (Vorsitzender), Dirk Brameier, Ulf Heggenberger, Norbert Westfal -----Ursprüngliche Nachricht----- Von: Kenneth Kirchner [mailto:[email protected]] Gesendet: Freitag, 3. Juni 2011 06:01 An: spectrum Betreff: [spectrum] Policy Magic Guys, Is the policy manager capable of looking at the description on an interface and altering the monitoring characteristics? I was thinking about the adding a field on the end of an interface description like so: interface GigabitEthernet0/3 description Connection to WAN Router [SE] I would then write a policy for Spectrum so that if it detected an 'S' in the brackets at the end of the description, it would turn on all kinds of monitoring, but if it lacked an S, then it would turn off polling of that interface. I would do something equally clever in eHealth for the E, but that's another list. This would put the power of determining what to monitor in my Network folks hands via the device config and I would not have to make any manual changes to Spectrum models. Seems like there is always some stupid port that is used for testing and they don't want alarms from it. I don't want a ton of maintenance mode alarms hanging around either. Is this a pipe dream? Harder to implement than I would think? Stupid for other reasons? -Ken --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
