VLAN on Dell N4064 Stacked
-
@Pete-S said in VLAN on Dell N4064 Stacked:
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
@Pete-S said in VLAN on Dell N4064 Stacked:
I did some stacking on N-series not too long ago.
Dell have some info on their site:
https://www.dell.com/support/article/se/sv/sedhs1/how10357/how-to-stack-and-unstack-a-member-in-dell-emc-networking-n4000-switch?lang=enThere is also some stacking videos on youtube. It's not too complicated but it requires some power cycling.
PS. Can't help you on DHCP and routing. I haven't done much L3 stuff with these switches but I assume it will work.
Thats pretty much the process that I have in mind. The part im not sure about is between step 1 and 2. To get to the part where you can configure the interfaces as stacking interfaces, you have to go through first boot and setup the switch... (does all of that setup get removed when they become stack members?)
I didn't do any update of the stack firmware I just checked that they had the same version. It's a lot easier to update the firmware after they are stacked because they get upgraded together.
This is also true of Extreme Networks switches.
-
I have have N3000 stack too. If I connect 1 * 10 GbE from the N4000 stack to 1 * 10 GbE on the N3000 stack, and set the interfaces to allow vLAN1 and vLAN20, on both stacks, will anything on each vLAN route though the 10 GbE to the other stacks respective vLAN? I guess like a dumb layer 2 switch being connected to another dumb switch, they just pass traffic irrespective of vLAN?
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
I have have N3000 stack too. If I connect 1 * 10 GbE from the N4000 stack to 1 * 10 GbE on the N3000 stack, and set the interfaces to allow vLAN1 and vLAN20, on both stacks, will anything on each vLAN route though the 10 GbE to the other stacks respective vLAN? I guess like a dumb layer 2 switch being connected to another dumb switch, they just pass traffic irrespective of vLAN?
It should.
-
@Jimmy9008
It does if they are the same type of port (general or trunk).But it would better to use use two 10G links and bond them with LACP active on both switch stacks.
-
@Pete-S but would I still need to adding the two vLAN to that bonding?
-
Or would that act like the stacking module with traffic just passed?
-
@Jimmy9008
Yes, you have to add vlans to it.
First select the interfaces you want to aggregate and make a channel-group (mode active). Then select the channel-group and add vlans to it. Do it on both stacks.If you want redundancy for switch failure you can put each port that is aggregated on different switches in the stack.
Aggregating (bonding,teaming or whatever you want to call it) with LACP is just to make the connection between the switches redundant and load-balanced. It's still works logically like a single port.
-
I'm at a point now where I have the three n4000 switch stacked together is one unit. Default/vLan1 is set.
Also, the three n3000 are stacked together with default/vLan1 set.
I have used link aggregation and hooked 10TbE 1 from N3000 switch 1 to 10TbE 1 in N4000 switch 1, and 10TbE 2 in N3000 switch 2 to 10TbE 1 in N4000 switch 2.
Anything I put in to the N3000's can ping anything on the N4000s. Same the other way around. So the two stacks, and the LAG are working perfectly for the default/vLan1.
Now, I can see where to create vLan2, that's fine. I can do that on both stacks. I just don't see how to get vLan2 to also be allowed over the LAG so clients on the vLan2 on either switch can talk. I'd like say interface 1 on N3000 unit 1 to be default/vLan1 if the device plugged in does not specify a vLan, if the device does specify vLan2, I want it to be able to get to a device on N4000 switch 1 interface 1 which is also set to vLan2...
Any help would be appreciated....
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
I'm at a point now where I have the three n4000 switch stacked together is one unit. Default/vLan1 is set.
Also, the three n3000 are stacked together with default/vLan1 set.
I have used link aggregation and hooked 10TbE 1 from N3000 switch 1 to 10TbE 1 in N4000 switch 1, and 10TbE 2 in N3000 switch 2 to 10TbE 1 in N4000 switch 2.
Anything I put in to the N3000's can ping anything on the N4000s. Same the other way around. So the two stacks, and the LAG are working perfectly for the default/vLan1.
Now, I can see where to create vLan2, that's fine. I can do that on both stacks. I just don't see how to get vLan2 to also be allowed over the LAG so clients on the vLan2 on either switch can talk. I'd like say interface 1 on N3000 unit 1 to be default/vLan1 if the device plugged in does not specify a vLan, if the device does specify vLan2, I want it to be able to get to a device on N4000 switch 1 interface 1 which is also set to vLan2...
Any help would be appreciated....
The LAG has a name like Po1 right?
You need to add the vlans to the port-channel (Po1).Do
show vlanso see what you have configured.Right now you'll only see the default vlan 1 on the LAG.
-
@Pete-S said in VLAN on Dell N4064 Stacked:
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
I'm at a point now where I have the three n4000 switch stacked together is one unit. Default/vLan1 is set.
Also, the three n3000 are stacked together with default/vLan1 set.
I have used link aggregation and hooked 10TbE 1 from N3000 switch 1 to 10TbE 1 in N4000 switch 1, and 10TbE 2 in N3000 switch 2 to 10TbE 1 in N4000 switch 2.
Anything I put in to the N3000's can ping anything on the N4000s. Same the other way around. So the two stacks, and the LAG are working perfectly for the default/vLan1.
Now, I can see where to create vLan2, that's fine. I can do that on both stacks. I just don't see how to get vLan2 to also be allowed over the LAG so clients on the vLan2 on either switch can talk. I'd like say interface 1 on N3000 unit 1 to be default/vLan1 if the device plugged in does not specify a vLan, if the device does specify vLan2, I want it to be able to get to a device on N4000 switch 1 interface 1 which is also set to vLan2...
Any help would be appreciated....
The LAG has a name like Po1 right?
You need to add the vlans to the port-channel.I'll take a look for it and see if I can find that. On a train at the moment.
-
The LAG should be general mode or trunk mode? I guess general, as I've read trunk move only allows tagged traffic to flow. General seems to allow tagged and untagged...
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
The LAG should be general mode or trunk mode? I guess general, as I've read trunk move only allows tagged traffic to flow. General seems to allow tagged and untagged...
Don't think it matters between switches. Traffic always belong to a vlan anyway (even if it is untagged). You can set both to trunk.
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
@Pete-S said in VLAN on Dell N4064 Stacked:
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
I'm at a point now where I have the three n4000 switch stacked together is one unit. Default/vLan1 is set.
Also, the three n3000 are stacked together with default/vLan1 set.
I have used link aggregation and hooked 10TbE 1 from N3000 switch 1 to 10TbE 1 in N4000 switch 1, and 10TbE 2 in N3000 switch 2 to 10TbE 1 in N4000 switch 2.
Anything I put in to the N3000's can ping anything on the N4000s. Same the other way around. So the two stacks, and the LAG are working perfectly for the default/vLan1.
Now, I can see where to create vLan2, that's fine. I can do that on both stacks. I just don't see how to get vLan2 to also be allowed over the LAG so clients on the vLan2 on either switch can talk. I'd like say interface 1 on N3000 unit 1 to be default/vLan1 if the device plugged in does not specify a vLan, if the device does specify vLan2, I want it to be able to get to a device on N4000 switch 1 interface 1 which is also set to vLan2...
Any help would be appreciated....
The LAG has a name like Po1 right?
You need to add the vlans to the port-channel.I'll take a look for it and see if I can find that. On a train at the moment.
it's something like (going by memory)
interface po1 switchport general allowed vlan add 2 tagged -
@Pete-S can you only do this through the console/com?
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
@Pete-S can you only do this through the console/com?
I think you can do it through the gui as well. It's a pretty basic requirement if you think about it - sharing vlans between switches.
-
-
So, thats how the N4000 is setup, see any issues? VLAN2 in top image has int 4 (Te3) set to T, for tagged traffic (anything I plug in will have vlan 2 set in the NIC). [First image].
Second image shows Te/1/1/1, which is LAG port. Its set to general to pass all vlans. (I think). Image 3 shows Po1.
Image 4 shows Interface 3 switch 1, which is also set to General.
Image 5 shows default vLAN. Te3 is 'u'. So anything plugged in to te3, if not set to vLAN 2 should be in U on vlan1?
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
Second image shows Te/1/1/1, which is LAG port. Its set to general to pass all vlans. (I think). Image 3 shows Po1.
LAG is not named Te1/1/1, it's an ordinary port (could be a member of a LAG group).
Look under Link Aggregation.
Or activate the freakin ssh port
-
-
Thats the LAG page. So unit 1, Te1/1 is LAG1. Unit 2, Te1/1 is LAG1 (both N4000). Then on the N3000 it has the same where Unit1 Te/1 and Unit2 Te/1 are LAG1. Traffic passes over these perfectly for vlan1.
