topic Re: Excessive Broadcast detected in Switches, Hubs, and Modems

Excessive Broadcast detected

PEI_1 — Wed, 11 May 2011 10:24:22 GMT

Hi,

How do I which ports have caused excessive broadcast to the LAN switches? The event logs on switches are showing excessive broadcast, Excessive CRC/misalignment...etc.

We were able to locate which ports were causing the loop by tracing all ports on each switch.

If we can identify the looping ports from the event logs, will be quicker.

Please advise.

Re: Excessive Broadcast detected

EckerA — Wed, 11 May 2011 11:18:04 GMT

well.. i always look at the webfrontend to trace where the loop is..the port utilization (non unicast) always gives a good hint..
hth
alex

Re: Excessive Broadcast detected

PEI_1 — Wed, 11 May 2011 23:25:32 GMT

Thanks. How soon would the indicator (color bar) be refreshed? If the broadcast stormed happened and cleared yesterday, would I still see the yellow bar (non-unicast) for those ports today?

Re: Excessive Broadcast detected

EckerA — Thu, 12 May 2011 03:56:20 GMT

No, you wouldn't. The colorbars are just that what happens at the moment.
hth
alex

Re: Excessive Broadcast detected

PEI_1 — Fri, 13 May 2011 10:06:50 GMT

Is there a way to see the bar status (non-unicast, unicast) with CLI? port status, port counter show cummulative counters from boot time, not the current status.

Re: Excessive Broadcast detected

EckerA — Fri, 13 May 2011 11:53:26 GMT

well..
not like the webfrontend, but at the cli
you have
show interface
show interface port-utilization
show interface brief
show interface config
show interface A1

hth
Alex

Re: Excessive Broadcast detected

PEI_1 — Sat, 14 May 2011 22:47:40 GMT

thanks

Re: Excessive Broadcast detected

pankajk — Mon, 19 Sep 2011 08:21:41 GMT

hi
is there any way to overcome excessive broadcast
even i am facing the same problem in my procurve switches

Tks
Pankajk