Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Expand all | Collapse all

Big Broadcast domain.

This thread has been viewed 4 times
  • 1.  Big Broadcast domain.

    Posted Oct 08, 2018 12:56 AM

    Hi,

      Finally, we are upgrading the LAN and we are going to use 3800 series Aruba switches. My question would be what is the downside of having a single big broadcast domain, let's say /17 for example. Some of the team members are not comfortable with big broadcast domain. Any input from the pros would be appreciated. 



  • 2.  RE: Big Broadcast domain.
    Best Answer

    MVP EXPERT
    Posted Oct 08, 2018 01:31 AM
    Keep it small as needed makes troubleshooting more easy. All broadcast traffic (and in some cases also multicast traffic without snooping) will floods to all clients.

    Possible l2 issue could be very hard to troubleshoot in big broadcast domains.

    Keep it small as you can, /24 /23 or max. /22 in most cases.


  • 3.  RE: Big Broadcast domain.

    EMPLOYEE
    Posted Oct 08, 2018 02:21 AM

    As your question is posted in the Wireless forum, it's not fully clear if you refer to wired or wireless clients in your question.

     

    If you connect a controller (that does broadcast filtering/conversion) with many wireless clients, you should, in general, take the subnet as large as possible. Check the Single VLAN Architecture for WLAN VRD for more information and backgrounds.

     

    In a pure-wired environment, I agree keeping the broadcast domains small (just a hundred or few hundred devices per VLAN) is considered best-practice for the reasons mentioned in the previous answer.