Hi,
to future-proof VLAN IDs keep them below 1000. If you need to merge two
such VLAN schemes, prepend a 1 and 2 to the existing numbers if the VLAN
IDs still need to be unique. Generalize as needed. ;-)
Allocating VLAN IDs by function eases merging of organizations: servers
go to the server VLAN, and so on. Most often you have VLAN ID ranges per
function, which lets you keep end devices from different original
organizations separated, if needed.
The need for L2 tunnels between sites looks like a design mistake to me.
Anyway, L2 tunnels don't necessarily transport VLAN tags, so they may
not interfere with the VLAN numbering.
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:19 PM, Strebler, Reinhard (SCC) wrote:
Hi Nick,
About five years ago I had to merge two organizations - both had lots of
VLANs. Our first step was making VLAN IDs unique. This was a huge job.
May be in future you will have to run L2 tunnels between the locations
of your organization. In this future case the current decision to same
IDs in different locations had been a wrong decision. Therefore my
suggestion is: keep VLAN IDs unique in your organization.
Kind regards
Reinhard
Karlsruher Institut für Technologie (KIT)
Steinbuch Centre for Computing (SCC)
Dipl.-Ing. Reinhard Strebler
Abteilungsleiter Netze und Telekommunikation (NET)
Kaiserstraße 12
76131 Karlsruhe
Telefon: +49 721 608-42068/29046
Fax: +49 721 32550
E-Mail: [email protected]
www.scc.kit.edu
KIT - Universität des Landes Baden-Württemberg und
nationales Forschungszentrum in der Helmholtz-Gemeinschaft
Am 01.09.2012 02:05, schrieb Nick Allen:
Hi,
Before we get too far down the road with our restructuring plans, does
anyone have a strong view on whether VLAN IDs should be unique across
all sites?
We have 5 sites - all layer 3 routed between them so - except for
transit VLANs - we figured we'd reuse the same VLAN IDs for the same
purpose on each site. I don't foresee any issues with doing so.
e.g management VLAN is 1000 on each site. 1002 is servers, 1004 is
voice etc.
Just wondered if maybe someone had done it but then later realised
that actually it would have been better to make them unique across all
sites - for easier documentation, or easier to use management tools
for example.
?
Thanks,
N.
---
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]
