Start a Conversation

Unsolved

J

3 Posts

835

May 9th, 2019 06:00

vLAN - routing between multiple stacks

Hi all,

I am trying to setup vLAN routing but am starting to struggle.

First part of my setup:

3 x N4000 in a stack. IP: 172.16.0.200

3 x N3000 in a stack. IP: 172.16.0.202

These 2 x 3 unit stacks are connected by 1 x LAG. This specifically is, 1 x 10 GbE from each unit on the N4000 connect to 1 x 10 GbE on each N3000 unit. Ports are set to Trunk mode.

On these, I have:

vLAN1/default = 172.16.0.0, 255.255.240.0

vLAN10 = 10.4.0.0, 255.255.0.0

vLAN10 on N4000 = 10.4.0.2, N3000 = 10.4.0.3

I have set these vLAN to route mode. When on the 10.4.x.x network, I can ping any 10.x machine. I can ping the vLAN interfaces (0.2 and 0.3) and I can ping both 172.16.0.200 and 172.16.0.202 (which are vLAN1). I can do so from any of the 6 switch.

If connect a client to vLAN1 though, say 172.16.0.53, I am unable to ping this from the 10.4.x.x vLAN. I can only ping the vLAN interface IPs. The same for anything on 172.x, it can ping 10.4.x.2, and .x.3, but not x.67.

What am I missing here?

I am pretty sure that as I can ping the gateways/vLAN IPs from either vLAN that the routing is setup. But, its almost like any traffic from vLAN1 hits vLAN10 10.4.0.2, but then doesnt know where to go, and vise versa...

 

The second part of my setup:

I also have a stack of 3 x PowerConnect 6248. This stack is connected by 1 GbE to the N4000 stack. The 6248 is 172.16.0.1. and that is default/vLAN1.

I have created a vLAN10 on the 6248 stack and that is 10.4.0.4/255.255.0.0. Int 1,2 of 6248 is connected to Int1,1 on N4000 master. Its currently set to access port.

172.16.x.x from both N3000, N4000 and 6248 stacks can talk/ping successfully. What I want to do next is allow vLAN10 to talk between these stacks too. I guess I need to set int1,2 and int1,1 to trunk mode, and set the interface to U for 172.16, and T for 10.0?

Any ideas would be welcome...

Best,

Jim

3 Posts

May 9th, 2019 06:00

Additionally, I am not sure the second part is needed.

The N4000/3000 can currently talk perfectly to the old Powerconnect LAN via 1,1 and 1,2. If vLAN routing is enabled properly on the N4000/3000, if you try to talk to 172.x from 10.4.x from N4000, the vLAN should pass this to the vLAN1, which would route out to the Powerconnect anyway, right?

Moderator

 • 

8.5K Posts

May 9th, 2019 12:00

3 Posts

May 10th, 2019 01:00

Yep, apologies. I mean vLAN4 on the Powerconnect. So, if I can get vLAN1 and vLAN10 (172.x.x.x and 10.4.x.x) routing on the N3000/N4000, would I need to do anything on the old Powerconnect? vLAN1 172.x.x.x on the N4000 can already talk to 172.x.x.x on the Powerconnect, so I assume if 10.4.x.x and 172.x.x.x can talk then traffic would go 10.4.x.x -> 172.x.x.x -> Powerconnect?

Moderator

 • 

8.5K Posts

May 13th, 2019 09:00

You shouldn’t have to, the routing would happen on the n series switches.

No Events found!

Top