if you have many users vlan numbers will not be enough to use one per user, so if you have one site it is good to use vlan per service and if you have many sites and all those sites connect to common broadcast domain you will have problem with broadcast traffic between sites so you can use vlan per service per site (ex. Site 1 and date = vlan 11, site 15 and voice = vlan 152).
if I have a network infrastructure to provide triple-play services and I want to separate traffic using vlan per service. There will be DSLAM for example to concentrate users at the access Layer, and then it will route traffic to the Agregation layer. The question is if I want a VLAN per service (3 in this case) I will need just 3 vlans? or I should take any other variables in order to know the total number of vlans that I need ?
Actually this is a small project for triple-Play services...so I must decide how many VLANs I should provide per DSLAM.
According to the text I've read it would be a good practice to have 1 VLAN per service and I would be answering my own question :=) but I don't know if I should consider more variables..for example if additionally I need a VLAN per site??
With 1660 users per site, I would look at separating out the users into departments then subnet them out. Then do the same thing for all the different services. Separate out the VLANS per service per department or closet/building location. Also, I would look into a routed design to help eliminate STP and check the timers of the routing protocol to best practices from Cisco.
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 custome...