LACP Member Monitoring/Speed Mismatch Alert Suggestion
Hi all,
i would like ask all of you if someone knows a good solution how to trigger a speed mismatch against the configured link speed. I give you an example:
Bundle-Ether1 has a port description of "Core: device [40Gbit] {abc} (notes)". So the bundle should have 40Gbit and I want now to create an alert to trigger a speed mismatch if a member goes down, then Bundle-Ether1 will report its updated speed i.e. 30Gbit and this should be compared and trigger somehow.
Mit freundlichem Gruß Stadtwerke Norderstedt
Denis Klimek
Professional Network Engineer IP-Systemtechnik
Tel: 040 / 521 04 - 1049 Mobil: 0151 / 652 219 06
dklimek@stadtwerke-norderstedt.demailto:dklimek@stadtwerke-norderstedt.de www.stadtwerke-norderstedt.dehttp://www.stadtwerke-norderstedt.de/
Like I already said on Jira, this is an interesting issue, and I think one that's worth solving.
I'm not sure what the best strategy for solving it is though. Would we just be interested in notifying when an interface has /decreased/ in speed? Or do we care about specific speeds?
adam. On 2018-03-26 13:05:09, Klimek, Denis dklimek@stadtwerke-norderstedt.de wrote: Hi all, i would like ask all of you if someone knows a good solution how to trigger a speed mismatch against the configured link speed. I give you an example: Bundle-Ether1 has a port description of "Core: device [40Gbit] {abc} (notes)". So the bundle should have 40Gbit and I want now to create an alert to trigger a speed mismatch if a member goes down, then Bundle-Ether1 will report its updated speed i.e. 30Gbit and this should be compared and trigger somehow. Mit freundlichem Gruß Stadtwerke Norderstedt Denis Klimek Professional Network Engineer IP-Systemtechnik Tel: 040 / 521 04 – 1049 Mobil: 0151 / 652 219 06 dklimek@stadtwerke-norderstedt.de [mailto:dklimek@stadtwerke-norderstedt.de] www.stadtwerke-norderstedt.de [http://www.stadtwerke-norderstedt.de/]
Yes I know that you’ve reply already on Jira, but you’ve told me to use the mailing list for this. If you like can close/delete the Jira ticket ☺
Regarding the solution:
I think the best solution would be to convert the “configured” speed into a common unit i.e. bits into the sql database. Currently observium is copy&pasting the value from [] i.e. 40Gbit to the port_descr_speed field. If that would be converted into bits like 40000000000 than we could compare it against the “ifSpeed” field ☺ And based on that we can create custom alerts with simple eq, le compare methods.
I also tried to look into the IEEE8023-LAG-MIB to find a solution, but it looks like that our Cisco devices have a bad implementation of this MIB set ☹
Mit freundlichem Gruß Stadtwerke Norderstedt
Denis Klimek
Professional Network Engineer IP-Systemtechnik
Tel: 040 / 521 04 – 1049 Mobil: 0151 / 652 219 06
dklimek@stadtwerke-norderstedt.demailto:dklimek@stadtwerke-norderstedt.de www.stadtwerke-norderstedt.dehttp://www.stadtwerke-norderstedt.de/
Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong Gesendet: Montag, 26. März 2018 15:08 An: observium@observium.org Betreff: Re: [Observium] LACP Member Monitoring/Speed Mismatch Alert Suggestion
Like I already said on Jira, this is an interesting issue, and I think one that's worth solving.
I'm not sure what the best strategy for solving it is though. Would we just be interested in notifying when an interface has /decreased/ in speed? Or do we care about specific speeds?
adam.
On 2018-03-26 13:05:09, Klimek, Denis <dklimek@stadtwerke-norderstedt.demailto:dklimek@stadtwerke-norderstedt.de> wrote: Hi all,
i would like ask all of you if someone knows a good solution how to trigger a speed mismatch against the configured link speed. I give you an example:
Bundle-Ether1 has a port description of "Core: device [40Gbit] {abc} (notes)". So the bundle should have 40Gbit and I want now to create an alert to trigger a speed mismatch if a member goes down, then Bundle-Ether1 will report its updated speed i.e. 30Gbit and this should be compared and trigger somehow.
Mit freundlichem Gruß Stadtwerke Norderstedt
Denis Klimek
Professional Network Engineer IP-Systemtechnik
Tel: 040 / 521 04 – 1049 Mobil: 0151 / 652 219 06
dklimek@stadtwerke-norderstedt.demailto:dklimek@stadtwerke-norderstedt.de www.stadtwerke-norderstedt.dehttp://www.stadtwerke-norderstedt.de/
Yeah, we were just discussing this as a possibility. It'd require a bit of rejigging of the existing port polling and alerting code, though.
I think it might be easier after future planned changes to alerting.
adam. On 2018-03-26 14:10:21, Klimek, Denis dklimek@stadtwerke-norderstedt.de wrote: Yes I know that you’ve reply already on Jira, but you’ve told me to use the mailing list for this. If you like can close/delete the Jira ticket J Regarding the solution: I think the best solution would be to convert the “configured” speed into a common unit i.e. bits into the sql database. Currently observium is copy&pasting the value from [] i.e. 40Gbit to the port_descr_speed field. If that would be converted into bits like 40000000000 than we could compare it against the “ifSpeed” field J And based on that we can create custom alerts with simple eq, le compare methods. I also tried to look into the IEEE8023-LAG-MIB to find a solution, but it looks like that our Cisco devices have a bad implementation of this MIB set L Mit freundlichem Gruß Stadtwerke Norderstedt Denis Klimek Professional Network Engineer IP-Systemtechnik Tel: 040 / 521 04 – 1049 Mobil: 0151 / 652 219 06 dklimek@stadtwerke-norderstedt.de [mailto:dklimek@stadtwerke-norderstedt.de] www.stadtwerke-norderstedt.de [http://www.stadtwerke-norderstedt.de/] Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Adam Armstrong Gesendet: Montag, 26. März 2018 15:08 An: observium@observium.org Betreff: Re: [Observium] LACP Member Monitoring/Speed Mismatch Alert Suggestion Like I already said on Jira, this is an interesting issue, and I think one that's worth solving. I'm not sure what the best strategy for solving it is though. Would we just be interested in notifying when an interface has /decreased/ in speed? Or do we care about specific speeds? adam. On 2018-03-26 13:05:09, Klimek, Denis <dklimek@stadtwerke-norderstedt.de [mailto:dklimek@stadtwerke-norderstedt.de]> wrote: Hi all, i would like ask all of you if someone knows a good solution how to trigger a speed mismatch against the configured link speed. I give you an example: Bundle-Ether1 has a port description of "Core: device [40Gbit] {abc} (notes)". So the bundle should have 40Gbit and I want now to create an alert to trigger a speed mismatch if a member goes down, then Bundle-Ether1 will report its updated speed i.e. 30Gbit and this should be compared and trigger somehow. Mit freundlichem Gruß Stadtwerke Norderstedt Denis Klimek Professional Network Engineer IP-Systemtechnik Tel: 040 / 521 04 – 1049 Mobil: 0151 / 652 219 06 dklimek@stadtwerke-norderstedt.de [mailto:dklimek@stadtwerke-norderstedt.de] www.stadtwerke-norderstedt.de [http://www.stadtwerke-norderstedt.de/]
Hi Adam,
Have you had a chance to implement changes to alerting and port polling to make this check work ?
On Mon, Mar 26, 2018 at 10:14 AM, Adam Armstrong adama@observium.org wrote:
Yeah, we were just discussing this as a possibility. It'd require a bit of rejigging of the existing port polling and alerting code, though.
I think it might be easier after future planned changes to alerting.
adam.
On 2018-03-26 14:10:21, Klimek, Denis dklimek@stadtwerke-norderstedt.de wrote:
Yes I know that you’ve reply already on Jira, but you’ve told me to use the mailing list for this. If you like can close/delete the Jira ticket J
Regarding the solution:
I think the best solution would be to convert the “configured” speed into a common unit i.e. bits into the sql database.
Currently observium is copy&pasting the value from [] i.e. 40Gbit to the port_descr_speed field. If that would be converted into bits like 40000000000 than we could compare it against the “ifSpeed” field J
And based on that we can create custom alerts with simple eq, le compare methods.
I also tried to look into the IEEE8023-LAG-MIB to find a solution, but it looks like that our Cisco devices have a bad implementation of this MIB set L
Mit freundlichem Gruß
Stadtwerke Norderstedt
*Denis Klimek*
Professional Network Engineer
IP-Systemtechnik
Tel: 040 / 521 04 – 1049
Mobil: 0151 / 652 219 06
dklimek@stadtwerke-norderstedt.de
www.stadtwerke-norderstedt.de
*Von:* observium [mailto:observium-bounces@observium.org] *Im Auftrag von *Adam Armstrong *Gesendet:* Montag, 26. März 2018 15:08 *An:* observium@observium.org *Betreff:* Re: [Observium] LACP Member Monitoring/Speed Mismatch Alert Suggestion
Like I already said on Jira, this is an interesting issue, and I think one that's worth solving.
I'm not sure what the best strategy for solving it is though. Would we just be interested in notifying when an interface has /decreased/ in speed? Or do we care about specific speeds?
adam.
On 2018-03-26 13:05:09, Klimek, Denis dklimek@stadtwerke-norderstedt.de wrote:
Hi all,
i would like ask all of you if someone knows a good solution how to trigger a speed mismatch against the configured link speed. I give you an example:
Bundle-Ether1 has a port description of "Core: device [40Gbit] {abc} (notes)". So the bundle should have 40Gbit and I want now to create an alert to trigger a speed mismatch if a member goes down, then Bundle-Ether1 will report its updated speed i.e. 30Gbit and this should be compared and trigger somehow.
Mit freundlichem Gruß
Stadtwerke Norderstedt
*Denis Klimek*
Professional Network Engineer
IP-Systemtechnik
Tel: 040 / 521 04 – 1049
Mobil: 0151 / 652 219 06
dklimek@stadtwerke-norderstedt.de
www.stadtwerke-norderstedt.de
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong -
Klimek, Denis -
Vlad Kratsberg