• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 286
  • Last Modified:

One Vlan with two /24 subnets

Hi,
I'm working on this project where I'm moving L3 off some Foundry equipment and I noticed that someone configured a few of them to use the same VLAN33 but they both have different subnets.  So, 192.168.11.0 /24 and 192.168.22.0/24.  

When I move L3, I configure the subnet on two 6509-E's because that's how they do it around here.  So.. with two different subnets using the same VLAN33, I'm sort of wishing I'd found out about this a while ago as I need to figure this out in my lab before I write up a plan.  Was wondering if any experts had some suggestions.  

Thanks,
R
0
rotarypwr
Asked:
rotarypwr
  • 5
1 Solution
 
rotarypwrAuthor Commented:
Was thinking I would just split up the VLAN, one for each subnet, so it would look like this:
Get rid of Vlan 33
Create Vlan 11 and
Vlan 22

Assign the ports to their new VLANs and make sure that those ports remain in the same subnet.  This way I can just add a respective VRRP config for the respective and now separate VLANs and I'll be able to adhere to the standards where I am doing this job. ??
0
 
ffleismaSenior Network EngineerCommented:
previously on the foundry, same VLAN was using same subnet? Did you check if one of those VLAN/sub-interface/interface was shutdown? Most probably one of those was.

Regarding your plan, that would be the design to pursue. Each subnet is assigned their own VLAN. You won't be able to use the same VLAN for two different subnet, the device wont allow it stating subnet overlaps.

on the 6509, each VLAN is configured with an SVI interface, it is on the SVI where you'll configure the VRRP.

let me know if you have any questions, glad to help out.
0
 
unfragmentedCommented:
@rotarypwr: i think you're on the right track.  If you're in a corporate environment, make sure you communicate your change and do some detailed testing after.  There are some protocols that rely on layer 2 (often broadcasts) that won't work the same with layer 3 separation.  Thinking of things like windows name resolution, multicast heartbeats etc.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
rotarypwrAuthor Commented:
OK,

So here's what I ended up doing as I was not permitted to break up the vlans.  I did a little research on VRRP and between the two 6500-E's here's what I did:



int vlan 33
ip address 192.168.11.2 255.255.255.0
ip address 192.168.22.2 255.255.255.0 secondary
desc Switch 1
ip helper-address 192.168.27.5
vrrp 33 ip 169.230.11.1
vrrp 33 ip 169.230.22.1 secondary
vrrp 33 timers advertise 3
vrrp 33 timers learn
no vrrp 33 preempt
vrrp 33 priority 120
no shut

int vlan 33
ip address 192.168.11.3 255.255.255.0
ip address 192.168.22.3 255.255.255.0 secondary
desc Switch 2
ip helper-address 192.168.27.5
vrrp 33 ip 169.230.11.1
vrrp 33 ip 169.230.22.1 secondary
vrrp 33 timers advertise 3
vrrp 33 timers learn
no vrrp 33 preempt
vrrp 33 priority 100
no shut

No problems and it works nicely.

Thanks,
R
0
 
rotarypwrAuthor Commented:
just added an edit for security reasons.
0
 
rotarypwrAuthor Commented:
none
0
 
rotarypwrAuthor Commented:
The solution was not provided but I was able to finally find it on my own entirely.
0
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.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now