Prime Infrastructure - alerting only trunk interfaces?

[hgans]

a very important NMS customization option is to decide which interfaces are important and which not for alerting...

How is this possible in PI?

I want to differentiate between important uplink ports and e.g. unimportant client ports - and as a consequence receive no emails for unimportant interfaces.

In LMS this was possible via Bluk jobs disabling monitoring for certain interfaces.

Is this possible in PI?

Thanks in advance!

BR.herwig

[Rob Johnson]

This is not currently available in current releases....

[hgans]

Thanks Rob for your prompt answer

I wonder how the "Port Group" Feature plays into the Alarming Part of PI.

What if I disable "Auto Monitoring" and create(design) port groups containing only important uplink ports...

Now if I receive a Interface down Trap from a Switch client port,

does PI still trigger an alert, despit I previously disabled "Auto Monitoring" in System Prefs?

Or in other words: Are Port Groups only used for performance monitoring or also used for alert notification?

[Steve Berglund]

Are there any updates for this? I dont want to have to go through all my switches and turn off snmp on interfaces.

        PI 2.0

[Martin Ostberg]

Any news on this. I'm running 3.0 right now and it really should be supported!

[tfetzer]

Having the same issue in PI 1.3.  Monitoring an access switch and only wish to monitor the uplink port.  Getting alarms everytime a pc gets turned off indicating that port is down on the device.  Any updates? 

Thanks.

[Steve Berglund]

I posted a thread similar for 2.0, but have not heard anything. The only way i know to get around this is to turn off SNMP on individual ports, but there's no way in hell i'm going through 200 switches manually.

I thought of creating a template, but i'd still have to do too much manual work that it wouldn't even be worth it.