Just to clarify, ifup/ifdown events are generated for the switch, thus, you would set notifiers on the switch level.
In other words, ifdown on a switch will generate warning for that switch, not that port. The warning alert for that switch will tell you why the warning was generated listing the port in trouble. The trouble is that high CPU/memory levels on that switch will also generate a warning and send it to the same person. So what I'm saying is that you can't alert one person on CPU overutilization and a completely different person on ifdown. ---------------------------- Sent from my iMobile Le Jun 4, 2010 à 9:35 AM, "Randy Baker" <[email protected]> a écrit : > Hi: > > Thank you all for your responses. I only work part-time, sorry for > the slow response. The following is a collage of the various > responses you provided me, and my clairifications: > >> Is there a reason why you monitor all user ports in IM? >> What make are the switches, Randy? > > In Intermapper we are only interested in ports 49-53 on Dell 3448 > and 3548 switches. Ports 49-53 are uplink ports. Ports 1-48 are > not displayed on Intermapper, only the active uplinks on ports 49-53. > >> On Cisco switches, setting "no logging event link-status" on the >> uninteresting ports will eliminate >syslog messages when they >> change state. HP switches have a command that does much the same. > > Having checked to see if Dell has a similar command for these > switches, logging appears to be global and limited to act on one of > 8 severity levels 0-7, and I can globally exclude OIDs. > >> I usually only "display" the uplink ports. Ifdown generates a >> warning I believe and sends an >notification with the name of the >> port. >> Is that what you are asking? > > You are correct. I am trying to send a notifier on the uplink port > on an Ifup or Ifdown. When I am in edit mode and right click a port > I am monitoring, Status, Info and Flow windows are the only options, > no notifiers. > >> If Andrey's solution isn't viable in your case you can always set >> up a simple SNMP Comparison probe >to check ifStatus on the ports >> you care about and use either InterMapper's SNMP Trap notifier type >> >or a command-line notifier to generate an appropriate trap for >> Splunk. > > I am unable to set a probe on the port, at least from the method of > right clicking the object while in edit mode, there is no Set Probe > option. > > Thank you > Randy > Confidentiality Note: This e-mail, and any attachment to it, is intended to be confidential and might be legally privileged. It is intended solely for the use of the addressee. If you are not the intended recipient, you are hereby notified that reading, copying, disseminating or distributing this email is strictly prohibited. If you have received this e-mail in error, please immediately return it to the sender and delete it from your system. Thank you. > -----Original Message----- > From: [email protected] [mailto:InterMapper- > [email protected]] On Behalf Of Randy Baker > Sent: Thursday, June 03, 2010 12:58 PM > To: InterMapper Discussion > Subject: [IM-Talk] Notifiers per device port > > Hi: > > Unless I am overlooking something, it seems that you cannot put a > notifier on a switch port. > > The application I have for this feature is as follows: We typically > have multiple uplink ports per switch, so monitoring the device is > not completely effective. We are running Splunk to capture all > syslog events, and every time a user turns on or off their computer > we get messages indicating that a port is up or down. It would be > nice to no longer trap for ports up or down on the device as I > cannot discriminate as to what ports I want to watch. Ideally, I > would like Intermapper to detect the loss of only the uplink ports > to a switch and to send a SNMPT trap notification to Splunk to > record the event. > > If there is a way to do this, I would appreciate some pointers. > Otherwise, this would be a nice feature in future releases. > > Thank you > Randy Baker > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] > > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] > > > -- > This message was scanned by the Georgian College ESVA and is > believed to be clean. > > ____________________________________________________________________ > List archives: > http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ > To unsubscribe: send email to: [email protected] >
