I’m considering enabling broadcast, multicast and unknown unicast rate limiting on a customer’s network ( core EAPs ring links ), this customer recently had a EAPs ring loop as the result of a card malfunction, this was devastating to the customer network.
Ultimately I would like to determine if this were to occur again, how can I mitigate against this enough to be able to manage the devices.
OSPF adjacencies are also formed across the EAPS rings, the implication here being the if the rate limits are set to low this will bring down the adjacencys.
So I have a number thoughts I would interested if this community would comment on
- In a loop situation OSPF control traffic will also be looped and rate limited, so does rate limiting provide any advantage at all ?
- How can I determine the correct level to set the limits ? I cannot afford a trial and error approach. The command "show port utilisation" only shows peak. Functionality would be improved here if I could see peak Muticast, and Peak Broadcast & peak unknown.
- Using SNMP, SNMP is able to report on multicast and broadcast. Now there are a number of values that can be read via SNMP, are these suitable to determine the values used by the rate limiters.
On some vendors it’s possible to place the rate limiters in to a "LOG only " and take no Action mode, does extreme have any similar functionality ?