Storm Control

[RebusCom]

Seeking clarification:

On viewtopic.php?f=6&t=2233 it's stated:

Keefe007: Does storm control look inside VLANs?
Eric Stern: Storm control is based on the number of packets on a physical interface and so is not affected by VLANs.
Keefe007: It is by port though - not total on switch correct?
Eric Stern: Its actually total on the switch.

Yet if I pose a question to Grok, I get the following:

Q: So it measures excess pps on all ports in the aggregate but can take action on just the offending port not all ports in the aggregate?

A: No, storm control on Netonix switches measures ingress packets per second (pps) individually on each physical port or interface, not as a combined aggregate across multiple ports (such as in a Link Aggregation Group or LAG). When the configured pps threshold for broadcast, multicast, or unicast traffic is exceeded on a specific port, the switch drops only the excess packets of that traffic type on the affected port, without impacting other ports—even if they are part of the same LAG. The feature is applied to physical interfaces, so in a LAG setup, each member port operates independently for storm control purposes.

Please reconcile. I'm wanting to tune the storm control on our switches without getting overly aggressive with it. We do utilize LAG (and VLANS) on some switches and other than the thread above I see mention elsewhere on the forum that all ingress is monitored together, no outbound, again implying the entire switch, not per port.

[sirhc]

storm control on Netonix switches measures packets per second (pps) individually on each physical port or interface, not as a combined aggregate across multiple ports (such as in a Link Aggregation Group or LAG).

Correct, it looks at each physical port separately.