mikkydoos Posted July 21, 2021 Posted July 21, 2021 (edited) Hi all, hope you're good. Currently in the process of carving up a flat network into VLANS. I've identified the need for about 20 VLANS. The aim is to separate traffic from anything that doesn't need to to broadcast to anything else. IP addressing... to keep it simple for my headspace... I want VLAN10, VLAN20, VLAN30, VLAN40 etc and IP address segments to match. Apart from it being a waste of a million private IP addresses, for the sake of simplicity... any reason why I shouldn't use: /22 VLAN10 - 10.10.x.x VLAN20 - 10.20.x.x VLAN30 - 10.30.x.x Rather than... /22 VLAN10 - 10.10.1.x VLAN20 - 10.10.4.x VLAN30 - 10.10.8.x Yes there will be a huge number of networks kind of wasted but does it matter ? Single site with approx 1000 devices max. How do you guys do it for simplicity ? Cheers in advance Edited July 21, 2021 by mikkydoos
Zammo Posted July 21, 2021 Posted July 21, 2021 20 VLANs feels like quite a lot, not that it is the end of the world! But you can definitely give yourself extra headache with needless segregation Wired Wireless Guest BYOD Servers Internet CCTV Printing Services (door access etc) VOIP covers most things Are you also doing geographical? i.e AREA-B-CCTV, AREA-A-CCTV, AREA-C-CCTV....? 1
mikkydoos Posted July 21, 2021 Author Posted July 21, 2021 20 VLANs feels like quite a lot, not that it is the end of the world! But you can definitely give yourself extra headache with needless segregation Wired Wireless Guest BYOD Servers Internet CCTV Printing Services (door access etc) VOIP Its all of those but carving up the WiFi into separate SSIDs on their own VLAN.... Staff tablets/laptops, pupil laptops, pupil tablets, guest. Also...wired offices, IT rooms etc.
Chris_Cook Posted July 21, 2021 Posted July 21, 2021 (edited) Doesn't make a difference from a performance point of view. Its worth keeping things as logical as possible if you are doing lots of vlans. The only issue might be if your ISP has given you a block of IP addresses to use. Then you would need to stick within that or request more. Edit: Just saw you said /22. so removed a suggestion Edited July 21, 2021 by Chris_Cook 1
mikkydoos Posted July 21, 2021 Author Posted July 21, 2021 (edited) Doesn't make a difference from a performance point of view. Its worth keeping things as logical as possible if you are doing lots of vlans. no reason why you couldn't do 10.1.10.0, 10.1.20.0, 10.1.30.0 etc. The only issue might be if your ISP has given you a block of IP addresses to use. Then you would need to stick within that or request more. Using the 3rd segment with that mask (/22) would give me: 10.1.0.0 10.1.4.0 10.1.8.0 10.1.12.0 ISP is a thought... not relevant for now but maybe in the future. Good point!. Edited July 21, 2021 by mikkydoos
TriggerHappyUK Posted July 21, 2021 Posted July 21, 2021 (edited) Like said above. If it works for you, then anything is fine. We have about 15 VLANS for normal network: ISCSI Servers Switch Management Sysamin Access Points Authenticated Wireless Clients CCTV Authenticated Curriculum Desktops Printers Digital Signage VoIP Projectors Macs Hall AV PA System 10.1.10.X/24 10.1.15.X/24 etc... /22 for laptops and desktops We also split our BYOD up into: BYOD - Staff BYOD - Students BYOD - Guest BYOD - Sysadmin Edited July 21, 2021 by TriggerHappyUK
Chris_Cook Posted July 21, 2021 Posted July 21, 2021 sorry, I wasn't thinking straight. Your right on the subnets. You could use those numbers as you VLAN ids instead, but your original way is probably the clearest. As long as you leave clear documentation and label the VLANs on your switches, then the numbers aren't too critical.
FN-GM Posted July 21, 2021 Posted July 21, 2021 /22 is rather large. Is there waiting reason you’re not using /24?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now