If you can find a common element like name or get the network's team to add a common code to the ifdescr then it's rather simple to then create an ignore port gc modify event rules to not alert on port down for that gc. However that does require cooperation. More complex is a list of servers at point x then work out which ports connect to them via the relationship model. A bit of coli should do it. Then use that list as your gc to then use for event rule changes. Also maybe some sanm work depending on how other alarms are needed On 2/02/2016 4:35 AM, "Schneider Christian" <[email protected]> wrote:
> Hi, > > I know we had this in the past but did not find my notes on that. Here is > the challenge: > > Many many switches and routers in the Landscape which produce link-down > alarms if the connected server on a switch-port is going down. As we are > running the network, we are not interested if the server guys are playing > around with the servers and would like to not getting a link-down alarm. > > Any hints? > > Kind regards, > > Christian Schneider > Enterprise Service Specialist > > 4-tune GmbH > Sägereistrasse 33 > CH-8152 Glattbrugg > > Mob +41 79 418 45 42 > Tel +41 71 930 07 00 > Fax +41 71 930 07 01 > Mail [email protected] > > www.nexellent.ch > www.4-tune.ch > > > > > > > > > > - --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]
