Hi, this scheme breaks if you use subnets with a netmask longer than 24. This scheme is not applicable to IPv6 either.
Thus I don't really like, but YMMV. 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 02:31 AM, Lou H. Goddard wrote:
I try to use VLAN IDs that match up with the third octet of our IP space. For example: 205.153.180.0 is VLAN 180 10.205.150.0 is VLAN 150 10.99.99.0 is VLAN 99 I use superstitious numbers like 666 for testing or temporary VLANS. From looking at your website I've gathered that you have locations all over the world. My advice from an old office in the armpit of Delaware may not be applicable. Thanks, Lou Goddard Network Engineer 302-552-8053 [email protected] -----Original Message----- From: Nick Allen [mailto:[email protected]] Sent: Friday, August 31, 2012 8:06 PM To: Enterasys Customer Mailing List Subject: [enterasys] VLANs 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]
