[c-nsp] Network split in several VLANs
Brian Feeny
signal at shreve.net
Fri Feb 4 11:18:15 EST 2005
I agree with Justin, since your using rfc1918 anyways, pick a new block
and move to
this new space. Its much easier to keep things straight, and then when
its all done
you can prune all your ACL's and configs by looking for any instance of
the legacy subnets
and removing them.
Brian
On Feb 4, 2005, at 8:50 AM, Justin M. Streiner wrote:
> On Fri, 4 Feb 2005, Xavier wrote:
>
>> What the best way to achieve this? The VLANs will be managed by two
>> Catalysts 4506.
>>
>> Keep 10.50.0.0/16 as a "default" VLAN and move hosts into new ones?
>> (So we need to assign IP to servers, ...) and use new 10.60, 10.70,
>> ...
>> Try to not change IP's and split the existing subnet?
>
> It's usually much cleaner to create new networks and VLANs in parallel
> with the old ones and then move the old devices to the new IPs and
> VLANs
> over time.
>
> Splitting existing subnets can cause all kinds of odd communication
> prolems between the machines, resulting from things like inconsistent
> netmasks or possibly double-assigned IP address ranges. It doesn't
> save
> you any work compared to starting fresh, in fact it would likely be
> more
> work because of the additional troubleshooting needed, on top of
> changing
> the network configurations on the machines.
>
> jms
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
------------------------------------------------------------------------
------
Brian Feeny, CCIE #8036, CISSP e: signal at shreve.net
Network Engineer p: 318.213.4709
ShreveNet Inc. f: 318.221.6612
More information about the cisco-nsp
mailing list