Just wondered what best practice is regarding the max number of devices per vlan. Our network uses a /20 mask which I think is too small . We have one particular vlan which contains 1120 devices (inc servers) and spans multiple switches. I've recommended we try not to add any more devices to this vlan and try and redesign the network so each switch stack is assigned one vlan.
Does anyone think we are heading for problmes if we continue with our present design?
Although this is not an definitive answer to your design question here are a few observations we reviewed when redesigning our network.
1. The larger the number of devices on a VLAN the higher the volume of broadcast traffic. Every device on the VLAN has to process that broadcast traffic which of course takes CPU cycles. Thus the local net that these devices are on becomes noisy. In this case less is better (at least to a point.)
2. The larger the VLAN in number of devices and pure geography of the network, then the larger the failure domain is. This means that any device that malfunctions on the at VLAN can negatively effect every other device sharing the same layer 2 domain. This makes it quite difficult to troubleshoot since you may be unsure where to start looking when a problem occurs. From our own experience this can be a very real, time-consuming issue.
Hope these brief comments provide you with further perspective.
I'll second the /24 size . This gives you 254 host addresses. This has worked for us for years in a very large corporate setting. Unless you have some real heavy users this should never be a problem . A /20 is wayyyyyyyyy too big imho .
I agree with the /24 subnet. In my situation, we segmented each floor by giving it a VLAN address. IN PAPER, each floor was given a /23 but each switches were configured with a /24. Should we require more IP Addresses, it's as easy as configuring another /24 secondary address.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
On a switched VLAN, even a /22 might be fine for your printers. This assuming all the traffic will be between GW and individual printers; should be little broadcast traffic.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...