All -
I've written a brief guide on how we use the Custom Properties available in NPM to enhance and simplify our alerting. The example I use in the document is: how do you alert on one part of a port channel link going down when the port channel itself stays operational?
Any comments/amendments/suggestions are welcome.
Regards,
John Kelly
Cheers guys, glad people are finding it useful 
bluefunelemental: that one annoys me as well, it was a real PITA to go through all our edge ports and mark them as unplugged - the nice thing about using custom properties is that they can be added as a column in the Manage Nodes/Interfaces table so you can sort/pick based on the property as well. (Using standard interface descriptions in the switch config is a real helper as well: we started the description of all our Etherchannel Member links with "Member of" - simply typing this in search box lists them all).
No charge for re-use to members of a community like this 
Regards,
John
Cheers guys, glad people are finding it useful
bluefunelemental: that one annoys me as well, it was a real PITA to go through all our edge ports and mark them as unplugged - the nice thing about using custom properties is that they can be added as a column in the Manage Nodes/Interfaces table so you can sort/pick based on the property as well. (Using standard interface descriptions in the switch config is a real helper as well: we started the description of all our Etherchannel Member links with "Member of" - simply typing this in search box lists them all).
No charge for re-use to members of a community like this
Regards,
John
