topic EOS - S-Series: Sending Trap if broadcast suppression limit is reached in ExtremeSwitching (EOS)

EOS - S-Series: Sending Trap if broadcast suppression limit is reached

M_Nees — Sat, 18 Mar 2017 15:48:00 GMT

Is it possible that s-series (or K or 7100) are send an traps if the broadcast supression threshold value is reached ?

I do that with all my EXOS stuff and what using the same mechanism with EOS.

Regards

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

Bastian_Sprotte — Sat, 18 Mar 2017 16:29:00 GMT

Matthias,
that is not supported in EOS, as this is an MAC chip function and the MAC chip will not alert the OS about the condition. We had reviewed the option to poll these counters internal, but decide the NMS will poll the counter per SNMP and an Flexview is available.
We have no plans to add that function to EOS as i know.
regards
Bastian
-

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

M_Nees — Sat, 18 Mar 2017 16:29:00 GMT

Thanks a lot for that further explanation.

Regards

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

M_Nees — Sat, 18 Mar 2017 16:29:00 GMT

Hi Bastian,

thinking twice about that limitation. I think there will be surely a solution for EOS that these systems are able to sending traps if the limit was exceeded. (i think checking threshold exceeding within EOS OS in a fixed intervall was enough).

My customer and i have huge problems to use a common configuration although we have only extreme networks gear (no other vendor). Over the time it is unavoidable to have EOS and EXOS staff in the same network.

But it is sometimes very hard because these two OSes does not offer the same feature or sometimes have opposed concepts.

So from my side it will be very usefull to enhance EOS in this way to offer the same mechanism like EXOS. S / K / 7100 are still update to date switching HW.

Regards,
Matthias

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

Erik_Auerswald — Sat, 18 Mar 2017 16:29:00 GMT

Hello Matthias,

EOS provides this functionality already, it is called CoS-based flood control. See e.g the documentation or some GTAC Knowledge articles like Network being flooded with Multicast packets causing Network outages and How To Clear CoS Flood Violation on S-Series. There is an article on The Hub as well, Purpose of the 'cos flood-ctrl' command set.

This feature is available on the SecureStacks and similar as well, not only on S/K/7100. Even the old N-Series provided this feature.

If you use CoS-based flood control to limit multicast frames, you should ensure to use a recent enough firmware containing the fix for the issue N/S/K Series : COS Flood Control for multicast traffic drops BPDUs and affects Spanning Tree behavior.

In contrast to the simple broadcast limiters, CoS-based flood control can be used to individually limit broadcast, multicast, and unknown unicast frames. In this regard it is similar to Cisco's Traffic Storm Control. [Cisco IOS cannot limit unknown unicast frames, the Traffic Storm Control unicast limit affects all unicast frames. Cisco NX-OS can limit unknown unicast frames using the same configuration commands as Cisco IOS. ExtremeEOS correctly limits unknown unicast frames if told to do so.]

The EXOS equivalent would be rate-limit flood. See How to Rate Limit Multicast or Broadcast Flooded traffic on EXOS as well.

Thanks,
Erik

[Edited to add some links]

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

M_Nees — Sat, 18 Mar 2017 16:29:00 GMT

Hi Eric,
thanks a lot for the valueable advice - this was excactly what i (my customers) needs!

I will try that.

Thanks also to give me the advice regarding the EOS firmware. That a topic at my current installation.

Let 's configure and run better networks ;-))

Regards

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

Erik_Auerswald — Mon, 20 Mar 2017 14:13:00 GMT

Hello Matthias,

if you use the CoS-based flood control instead of the basic broadcast limiter (set cos port-config flood-ctrl), you can use set cos port-resource flood-ctrl to send a sylog message, a trap, or disable the port if the configured threshold is reached. You need to enable CoS (set cos state enable) to actually use this feature.

Thanks,
Erik

RE: EOS - S-Series: Sending Trap if broadcast suppression limit is reached

PeterK — Tue, 18 Jul 2017 13:31:00 GMT

Is there a way to only notify via syslog or trap when broadcast limit threshold is reached and not to act/drop frames?

When I understand right "set cos port-resource flood-ctrl" does not have this option...