03-09-2011 01:36 PM - edited 03-06-2019 04:00 PM
I have 400 Pcs (Servers, desktops and Laptops), one core switch, multiple access switches and a few wireless access points. Can i have some recommendations or configuration examples for configuring vlans for my network and how many vlans should i have?
Thanks!
03-09-2011 01:41 PM
I have 400 Pcs (Servers, desktops and Laptops), one core switch, multiple access switches and a few wireless access points. Can i have some recommendations or configuration examples for configuring vlans for my network and how many vlans should i have?
1. What switches do you have?
2. If you have 2940/2950/2955 then what IOS are you running?
3. Do you have a Layer 3 device to do inter-VLAN routing?
Here are some references for you to read:
03-12-2011 12:09 PM
The links are not working. Forbidden.
03-14-2011 12:09 AM
Hi,
just get rid of the customer string in the url and it will work.
Regards.
Alain.
03-20-2011 08:18 PM
createshare77 wrote:
I have 400 Pcs (Servers, desktops and Laptops), one core switch, multiple access switches and a few wireless access points. Can i have some recommendations or configuration examples for configuring vlans for my network and how many vlans should i have?
Thanks!
How long is a piece of string?
As a general rule, I apply a distinct VLAN for each purpose - one for servers (no DHCP), one for workstationed 9DHCP enabled), one for printers etc. But this doesn't always work - for example, my current $POE has multiple building levels and more workstations than I am comfortable having in a single broadcast domain - so I have a couple of workstation VLAN's per floor, absed on georgaphic location (which half of the floor) as well as function for workstations, which limits the size of the broadcast domain to something more reasonable.
You don't mention switch types or machine, so this is very generic, however I'd do the following.
1) Configure your core switch with as many VLAN's as you want/need based on your location, and configure all SVI's on this core switch to allow for intra-VLAN routing.
2) Enable 802.1Q trunking between your core switches and access switches, but don't put any SVI's on these (except maybe for management of the switch itself). If your access switches are purpose-specific (I.E. they only have workstations plugged into them), then just trunk the workstation and switch management VLAN's to this switch. If you have multiple device types plugged into a given switch, then trunkt he appropriate VLAN's to that switch - try to avoid trunking VLAN's which aren't used by a particular access switch.
NB: VLAN NUMBERS must match between switches - and, unless you have VTP turned off (transparent), the names must match as well, or things will get flakey. VTP use is up to you - if you don't understand it, then don't use it - set it to mode transparent on all switches and forget about it.
Without some hard numbers, there's not much more that can be said, really.
Good luck!
03-23-2011 01:43 AM
Hi
First of all you must ask yourself what are you trying to achieve ?
we do not know the answer to that question so in turn it makes it difficult for us to guess why you want vlans and how many and so on.
You normally do not need vlan separation for that small type of broadcast domain (400 units).
so
What are you trying to achieve ?
What hardware do you have
and last
How much money are you allowed to spend on it.
(Nothing - some - bucketloads - no limits).
Good luck
HTH
05-06-2011 10:37 PM
Hi,
hope all are good..
kindly note that if you have multiple department defenatly you must have it so creat vlans on core switch according to your departments and two saperate vlans for Wifi users in which one vlan is for internal wireless users and one for wifi guest access and creat your own AAA authentication server for login cridentials that sounds more sceure and smarter way..
thanks & Regards,
Muhammad Umair Afghani
+92333-3189585
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide