Checking ifHighSpeed is likely the easiest if you don’t already have syslog set up.
My 200G LAGs show ifHighSpeed=>200000, so it would be easy to check if it’s < 200000, or != 200000 depending on how you want to write the check.
|
Spencer J. Ryan| Manager, Technology and Infrastructure |
|
|
From: Brad Bendy via observium <observium@lists.observium.org>
Sent: Wednesday, March 22, 2023 6:57 AM
To: Observium <observium@lists.observium.org>
Cc: Observium <observium@observium.org>; Bryan Fields <Bryan@bryanfields.net>; Brad Bendy <brad.bendy@gmail.com>
Subject: [Observium] Re: Alerting if LAG member drops?
|
Caution: This is an external email. Do not open attachments or click links from unknown or unexpected emails.
|
Syslog should show it. Just have to verify the text when a member drops and send alert out
On Tue, Mar 21, 2023, 9:47 AM Bryan Fields via observium <observium@lists.observium.org> wrote:
I'm looking at an easy way to send an alert if a LAG member drops.
Running subscription Observium 22.12.12421 and talking a Juniper EX4500 switch.
My thought was to have a global check that looked for ifType = ieee8023adLag
and then if there was some way members changed, but I don't see a way to
detect/check for this. I don't think Observium has any graphing on the LAG
port members state. BTW, this would be a great thing to add to have viability
into LAG members at the ae level.
Perhaps checking if ifHighSpeed goes down?
Other than putting up check on the underlying interfaces manually, does anyone
have an idea on this?
Thanks,
--
Bryan Fields
727-409-1194 - Voice
http://bryanfields.net
_______________________________________________
observium mailing list -- observium@lists.observium.org
To unsubscribe send an email to observium-leave@lists.observium.org
|
You have received a message from the law firm Miller Canfield. The information contained in or attached to this electronic mail may be privileged and/or confidential. If you received this transmission and are not the intended recipient, you should not read this message and are hereby notified that any dissemination, distribution or copying of this communication and/or its attachments is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and delete or destroy the original and any copies, electronic, paper or otherwise, that you may have of this communication and any attachments. |
|
|