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 (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.
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
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.
Perfect, then goto VLAN, VLAN members and select vlan 2. The click so you get vlan 2 on LAG 1.
Now the LAG 1 will pass VLAN 2 as well. -
@Pete-S said in VLAN on Dell N4064 Stacked:
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
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.
Perfect, then goto VLAN, VLAN members and select vlan 2. The click so you get vlan 2 on LAG 1.
Now the LAG 1 will pass VLAN 2 as well.Click Te1/1/1 on vlan2 to say 'U'?
-
@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:
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.
Perfect, then goto VLAN, VLAN members and select vlan 2. The click so you get vlan 2 on LAG 1.
Now the LAG 1 will pass VLAN 2 as well.Click Te1/1/1 on vlan2 to say 'U'?
No, further down, where it says LAG and then shows you the LAG groups.
-
@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:
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
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.
Perfect, then goto VLAN, VLAN members and select vlan 2. The click so you get vlan 2 on LAG 1.
Now the LAG 1 will pass VLAN 2 as well.Click Te1/1/1 on vlan2 to say 'U'?
No, further down, where it says LAG and then shows you the LAG groups.
I think I see this now. I have made the changed remote, will test tomorrow when in the office. Will update how I got on.
I set LAG1 on vLAN2 to 'U', should it be 'T'?
-
Im guessing 'U' is fine. As I want vLAN2 to pass traffic where the device has already set vlan2 in its NIC. If the LAG is set to 'T', all traffic will be set to vlan2, right? Even when from vLan1/default...
-
@Jimmy9008 said in VLAN on Dell N4064 Stacked:
Im guessing 'U' is fine. As I want vLAN2 to pass traffic where the device has already set vlan2 in its NIC. If the LAG is set to 'T', all traffic will be set to vlan2, right? Even when from vLan1/default...
I think it's better to tag every vlan in both ends. Then you can be certain traffic ends up on the same vlan on the other switch stack.
