To join this thread.. I have used in a few places the following:
10.x.y.z 10 network while huge, gives you the most flexibility x is the location y is the service z devices So if I have a 10 building spread out geographically.. just vary up "x" Y is the service. So if the students/HR/Admin/etc would get this vlan Z are the amount of devices. /22 /22 /24 which ever works for you. The VLAN ID match the "Y" service My campus runs with "8" as the Admin group. 208 is Carr Admin 308 is Design Center Admin The "32" group is the students 232 332 Building Services is "20" -Heating/AC/Video Cameras 220 320 It stacks nicely and let you know where you are So 208 would tell me it is "carr" -which could be a state/country that is running an "admin" vlan 332 would be Design Center "student" vlan. It has worked in a few business I have set this up for....As I have set it up, it is limited to 0-99..but that is a HUGE chunk. However, if you know how big your environment is or suspect your growth rate, you can easily work around that with plenty of wiggle room. Ian On Sat, Sep 1, 2012 at 1:54 PM, Erik Auerswald <[email protected]>wrote: > Hi, > > that sounds good, but it does not scale well (1 <= VLAN ID <= 4094). > > Many useful VLAN numbering schemes exist. Biggest problem is > future-proofing them. There may be new functional VLANs, more sites, > merging or carving out companies, for example. So I'd advise against using > all the available number space for the initial scheme. > > In my experience, re-using VLAN IDs on different sites works well. It is a > lot easier than creating a simple numbering scheme that scales to hundreds > or thousands of VLANs (as needed for global enterprises). > > Regards, > Erik > -- > Dipl.-Inform. Erik Auerswald http://www.fg-networking.de/ > E:[email protected] P:+49-631-4149988-0 M:+49-176-64228513 > > Gesellschaft für Fundamental Generic Networking mbH > Geschäftsführung: Volker Bauer, Jörg Mayer > Gerichtsstand: Amtsgericht Kaiserslautern - HRB: 3630 > > On 09/01/2012 07:39 PM, Shuttlesworth, James wrote: > >> We use a VLAN numbering scheme that maintains some similarity between >> ranges to make it easier to remember, but still unique - all vlans are 4 >> digits the first digit indicates its general function e.g. 1 for users 2 >> for VOIP 3 for management then the second number indicates it's site (site >> 1 site 2 site 3 etc. - we have 6 sites) the last two digits then are for >> specific locations/buildings etc. >> >> We put use before site so it's more apparent by glancing at it what the >> VLAN is for which is more frequently something you need to know than what >> site you are at. >> >> -----Original Message----- >> From: Erik Auerswald >> [mailto:auerswald@fg-**networking.de<[email protected]> >> ] >> Sent: Saturday, September 01, 2012 1:12 PM >> To: Enterasys Customer Mailing List >> Subject: Re: [enterasys] VLANs >> >> Hi, >> >> this works fine and helps in troubleshooting (is the server's MAC address >> seen in the server VLAN?). >> >> Regards, >> Erik >> > > --- > To unsubscribe from enterasys, send email to [email protected] with the > body: unsubscribe enterasys [email protected] > --- To unsubscribe from enterasys, send email to [email protected] with the body: unsubscribe enterasys [email protected]
