PP8610 and mixing IP classes

[gillymonst]

I currently have a core 8600 @ ver3.2.4 w/ about 35 vlans in a class A (subnetted as a class B)...10.250.x.x/22 configuration. My question is can I create a new straight class A set of VLANs in the 10.x.x.x/16 range and run both IP classes together as I cut-over from my current class B range to the class A VLANs over a period of time w/ out the 8610 going braindead...not sure if the box was designed to route multiple IP classes?

Thanks in advance.

 

[mucka]

I wouldnt think this is a problem,we have 13 x 8600,s & have lots of "class c" adresses
and lots of 10.x.x.x/23 subnetted addresses all mixed on all of our passports.

Mucka

 

[gillymonst]

Thanks mucka,
I'll try it out. I get a little punchy around the 8600 as its our only one and I'm still green with IP and the capabilities of the box.

 

[whiskeytrain]

I assume you will be using port based VLANs and tagging if you are trying to cut ip's on the same segment. Unlike BayRS you can not multi-net(secondary IP address in Cisco terms) on the 8600. If you are moving to a new segment it should not be a problem.

 

[gillymonst]

Yes,
I am using port based vlans and tagging currently. If I understand you correctly I can add the class A vlans to the existing class B tagged trunks to extend all B and C class vlans together between switches...which brings up another question.
? Will the class B DefaultVlanId of the trunk have any negative impact on the new class A vlans?...I know that the Id determines what the management vlan for the trunk is but I believe there is more to it than that...just not sure what.

 

[whiskeytrain]

/22 255.255.252.0 is not a "B" mask Using 10.250.x.x you will get 16382 subnets with 1022 addresses each.

/16 255.255.0.0 is a "B" mask Using 10.250.x.x you will get 254 subnets with 65534 addresses each.

/8 255.0.0.0 is an "A" mask It will be 10.x.x.x It is 1 subnet with 16777214 addresses.

With that in mind, as stated above it looks like you are overlapping ranges and I don't think the router will like it.
How many ip addresses do you need for each vlan? What routing protocol are you using? Is there IPX floating around?

If you are using the /22 and /16 as stated above, just missed naming convention, just don't use 10.250.x.x/16 for any of your new vlans.

I think I have this correct. Let me know if it is unclear or I made an error.

 

[gillymonst]

Your right that my class naming conventions are not correct but I do know that the 10.250.x.x/22 that I currently use gives you 64 subnets w/ 1022 addresses each...and the 10.x.x.x/16 that I want to add will give me 256 subnets w/ 65,534 addresses each. "I'm no IP guru, just puncing #'s into this online calculator:

http://www.cotse.com/networkcalculator.html"

My intent is to create all my new vlans in the 10.x.x.x/16 scheme not necessarilly because I need 16 million+ addresses but just to be able to cut over a closet or a building at a time to the new scheme where if I tried to re-distribute a new 10.250.x.x/22 I would have to design it around the existing spare subnets in my current scheme or start from scratch and do the whole project in one weekend...not gonna happen.

The main goal is to end up w/ 10 vlans that span geographic locations instead of 35 vlans that are building specific...I believe the original design was to be able to segregate these different groups in each building for security reasons but we found we really dont have a need to do so...It would also be easier to manage less vlans.