setting up multiple vlans on a subneted address range

Ok so i feel like im looking at this in the wrong way. we have a 6509 which operates at layer two and three. i have an address lets say X.X.38.0 255.255.255.240 and i call this vlan "vlan 38 lets say i have used the first 14 addresses on the first network and i want to use the second network from .17-.30 how would implement a vlan for my second network if i have already used vlan 38.  Im assuming that the ip is associated with the vlan number because that how i have always created them, but we are growing fast and i want to be more practical on how i use our IPs. I have a feeling vlan and IP are not related but i just want to check...

the more detail the better thanks guys :-)
mattlastAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ken BooneNetwork ConsultantCommented:
So from a switch configuration perspective the vlan and ip address have no correlation what so ever. There is a valid range of numbers to use for a vlan ID and a valid range of IP addressess you use.

The vlan is strictly layer 2.  So if you have vlan 38 which is a layer 2 vlan, you probably have a layer 3 interface (SVI) set up on that switch for that vlan  i.e. Interface vlan 38

So vlan 38 is layer 2
interface vlan 38 is layer 3

You put your layer 3 address on the layer 3 interface which ties a specific IP network to that vlan.

So it makes it nice when your numbering schemes sync up if you will from a management persepctive.  So if you mask was a /24 i.e. 255.255.255.0 then it makes sense to maybe match the 3rd octet of the IP numbering scheme to the vlan ID.  This makes it easy for us to recognize what is what.  It is recommended to have some type of plan like this but it is not a necessity.

So in your case you took a /28 block of IP addresses and put it on vlan 38.
The next /28 block of IP addresses will be a different layer 3 network as well as it should be tied to a different layer 2 vlan.  So to make it work you simply need to create another vlan that is unique on your network and assign x.x.38.16/28 to it.  It doesn't matter what the vlan number is for this ip network as long as it is unique.

Is there a reason you are using small subnets?
0
mattlastAuthor Commented:
We have a small section or third party vendors that need devices in our DMz which all require different routes and restrictions. But thank you for you explanation I feel like I knew this but didn't want to assume because I don't have to do it often.
0
Ken BooneNetwork ConsultantCommented:
Yea that makes sense.  I usually number my vlans to match the 3rd octet.  But I usually use a completely different block of addresses on the DMZ, and assign them to high number vlans that won't match anything else.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mattlastAuthor Commented:
thanks for clearing that up
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Network Operations

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.