• September 25, 2020, 02:03:45 AM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: broadcast-limit for procurve equip  (Read 7487 times)

0 Members and 1 Guest are viewing this topic.

Offline jbabio

  • Rookie
  • **
  • Posts: 2
    • john babio
broadcast-limit for procurve equip
« on: September 01, 2013, 07:43:50 PM »
From my understanding, you broadcast limit the older switches as a whole and newer switches by port. The percent I am using is 10 beings I read both 5 and 30 are numbers people have used. So my question is at how many different points do you limit the broadcast? Here is a sample layout:

L2switch => L2switch => L2switch => L3 Core switch.

I have limiting on each l2 switch and on the core fiber uplink port I also have broadcast-limit 10. Does this sound correct?


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 3842
    • michaelfmcnamara
    • Michael McNamara
Re: broadcast-limit for procurve equip
« Reply #1 on: September 04, 2013, 08:46:24 PM »
The value to use is specific to your network... some folks have broadcast and multicast applications so the rate will differ. I would suggest you enable it everywhere... smaller values on your edge ports, larger values on uplinks/downlinks/trunks where you aggregate multiple VLANs, etc.

Good Luck!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline jbabio

  • Rookie
  • **
  • Posts: 2
    • john babio
Re: broadcast-limit for procurve equip
« Reply #2 on: September 04, 2013, 09:21:11 PM »
Thanks Michael,
Interestingly enough, the 2650, 2625, 2608 switches only allow a single global value. So if it actually does a per port value based on this number then the uplinks being gig at 10% which is 100Mbps. The newer switches allow for a per port value. I can't imagine that kind of broadcasting going on even with dhcp requests. All traffic is always destined for the internet because its the resident hall network. The macbooks hammer away at ports and access points with multicast. I have some older HP 420 access points that don't handle igmp and when an apple connects the NMS alerts me it goes up and down. When you turn on broadcast and multicast limiting on the AP the drop of the grid.

I do BPDU guard and loop guard on the edge ports, I minimize management accessibility from only certain subnets, and I turn off auto/admin-edge ports where switch trunks and AP's connect. I could prob do port-security, dhcp-snooping, and DAI. Not much time at the moment.

The value to use is specific to your network... some folks have broadcast and multicast applications so the rate will differ. I would suggest you enable it everywhere... smaller values on your edge ports, larger values on uplinks/downlinks/trunks where you aggregate multiple VLANs, etc.

Good Luck!