I have worked with Vlans for another company that used a different Vlan for every department and then had a Vlan for the servers. This goes along with most design concepts except that at least 2 or more departments often shared a wiring closet. When tech support would plug in PCs, they often would not call and the PC would end up being put in Vlan 1 or a different department's Vlan. Obviously labeling the ports would be helpful but the way things changed it would never be accurate. Then everytime the PCs had to access a server, they had to hit the 5500 RSM.
I have heard so many suggestions such as use a different Vlans for servers, printers, and PCs. I strongly disagree about putting printers in a different Vlan because there is no reason for a traffic to hit a router when the PC and printer are next to each other. What I am thinking about doing is putting groups of closets in Vlans, use Vlan capable NICs in shared servers, and put other servers that are dedicated to departments in their Vlan. For the most part, departments all go into the same closet. I am wondering is what logic are other people using for Vlans. I know traffic flow is a big consideration which I will break up by groups of closets. I average about 20-40 connections per closet. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=23928&t=23928 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
