ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    VLAN on Dell N4064 Stacked

    IT Discussion
    dell dell n4064 switch vlan networking
    3
    44
    1.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • wrx7mW
      wrx7m @1337
      last edited by wrx7m

      @Pete-S If the N are like the powerconnect line, you might even be able to do this in the web UI. If you are more into that. Obviously, it is much faster to change lots of ports at once in the CLI.

      1 1 Reply Last reply Reply Quote 1
      • J
        Jimmy9008 @1337
        last edited by

        @Pete-S said in VLAN on Dell N4064 Stacked:

        Something like this:

        interface Gi1/0/1
switchport mode general
switchport general pvid 1
switchport general allowed vlan add 20 tagged

        Also don't forget to save the config when you're done or it is gone if you reboot the switch.

        Yep, makes sense. In theory I could set every interface on the whole stack to mode general, pvid1 (so vlan 1 is default if no vlan is set on the device) and all interfaces also vlan 20 allowed. Now, I can have a DHCP on vlan20 to hand out addresses on the switch to the 10.10.x.x network, and DHCP on vLAN1 (or no vLAN set) to provide DHCP to 192.168.x.x network?

        Am I able to allow interface 1-10 pass traffic from vlan 1 to vlan 20, whilst telling 11 - 20 to not pass traffic between vlan?

        1 Reply Last reply Reply Quote 0
        • 1
          1337 @wrx7m
          last edited by

          @wrx7m said in VLAN on Dell N4064 Stacked:

          @Pete-S If the N are like the powerconnect line, you might even be able to do this in the web UI. If you are more into that. Obviously, it is much faster to change lots of ports at once in the CLI.

          Good point. Yes, I think all the N-series switches have the web GUI too.

          1 Reply Last reply Reply Quote 0
          • J
            Jimmy9008
            last edited by Jimmy9008

            When it comes to configuring the stack, I assume I connect by COM/Putty to the unit I want as master, boot it with the CLI, update firmware and restart. Then, go through the setup wizard, set my vLAN1/management/etc, then set the 40GbE interfaces (2 of them) to be 'stack' mode. Save then turn off.

            Once that is done, connect to switch 2 and 3 in turn, update the firmware, run through the setup wizard but set no vLAN/etc as its not needed (as they will get that from the master when connected?), but do set the 2 x 40 GbE on each to 'stack'. Then turn them off.

            Stick the stacking cables in. Finally, turn on the first one and let it boot, it would be master. Once that is up turn on the second switch, as it boots the master will push the config (setup at the start of this post), and finally the third once switch 2 is up...

            I have not done that yet, will on Monday - but am I missing anything?

            wrx7mW 1 Reply Last reply Reply Quote 0
            • wrx7mW
              wrx7m @Jimmy9008
              last edited by

              @Jimmy9008 Is that what the docs say the procedure is? I would imagine you would want to have all the switches at the same firmware level prior to adding them to the stack.

              J 1 Reply Last reply Reply Quote 0
              • J
                Jimmy9008 @wrx7m
                last edited by

                @wrx7m said in VLAN on Dell N4064 Stacked:

                @Jimmy9008 Is that what the docs say the procedure is? I would imagine you would want to have all the switches at the same firmware level prior to adding them to the stack.

                Yeah, they need to be the same firmware. The documentation is very light on setting up a stack.

                I am pretty sure that is the process though.

                1 Reply Last reply Reply Quote 0
                • J
                  Jimmy9008
                  last edited by

                  Can I use the CLI to create a DHCP server running within the stack on vLAN20?

                  1 Reply Last reply Reply Quote 0
                  • 1
                    1337
                    last edited by 1337

                    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=en

                    There 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.

                    J 1 Reply Last reply Reply Quote 0
                    • J
                      Jimmy9008 @1337
                      last edited by

                      @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=en

                      There 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?)

                      1 1 Reply Last reply Reply Quote 0
                      • 1
                        1337 @Jimmy9008
                        last edited by

                        @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=en

                        There 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.

                        wrx7mW 1 Reply Last reply Reply Quote 1
                        • wrx7mW
                          wrx7m @1337
                          last edited by

                          @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=en

                          There 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.

                          1 Reply Last reply Reply Quote 0
                          • J
                            Jimmy9008
                            last edited by Jimmy9008

                            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?

                            wrx7mW 1 2 Replies Last reply Reply Quote 0
                            • wrx7mW
                              wrx7m @Jimmy9008
                              last edited by

                              @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.

                              1 Reply Last reply Reply Quote 1
                              • 1
                                1337 @Jimmy9008
                                last edited by

                                @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.

                                J 1 Reply Last reply Reply Quote 0
                                • J
                                  Jimmy9008 @1337
                                  last edited by

                                  @Pete-S but would I still need to adding the two vLAN to that bonding?

                                  1 Reply Last reply Reply Quote 0
                                  • J
                                    Jimmy9008
                                    last edited by

                                    Or would that act like the stacking module with traffic just passed?

                                    1 Reply Last reply Reply Quote 0
                                    • 1
                                      1337
                                      last edited by 1337

                                      @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.

                                      1 Reply Last reply Reply Quote 0
                                      • J
                                        Jimmy9008
                                        last edited by

                                        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....

                                        1 1 Reply Last reply Reply Quote 0
                                        • 1
                                          1337 @Jimmy9008
                                          last edited by 1337

                                          @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 vlan so see what you have configured.

                                          Right now you'll only see the default vlan 1 on the LAG.

                                          J 1 Reply Last reply Reply Quote 0
                                          • J
                                            Jimmy9008 @1337
                                            last edited by

                                            @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.

                                            1 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 1 / 3
                                            • First post
                                              Last post