Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Help with VLANS on Dell PowerConnect 6024

Posted on 2013-06-03
Medium Priority
Last Modified: 2016-11-23
Hello all,
I am looking for some help setting up a VLAN on a Dell 6024 switch (does support Layer 3\Routing).

What I want do, if I can, is just plug the switch into the existing network (192.168.2.x IPs), configure about 8 ports as a VLAN 250 (192.168.250.x IPs) and then allow routing from the 250.x VLAN to the rest of the network including internet access.

Is this possible? In theory I believe it is but I seem to having some issue getting it configured correctly. Right now I have 2 VLANs configured. I also want to disallow DHCP from the regular network (VLAN 20) to the other VLAN 250 network.

192.168.2.x       Ports g1-g6
VLAN 250
192.168.250.x       Ports 13-16

I have the ports set as “General” and “Admit All”, and I have the starting ports(Port 1 and Port 13) for each VLAN set as “Access” and “Admit All”

Thank you for any help you can provide. I have looked at this for quite some time and can reset my switch to default again and start over if needed. I just need some help getting it done. Thank you again.
Question by:CCG3
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
LVL 25

Accepted Solution

Cyclops3590 earned 2000 total points
ID: 39218628
sorry, i have never configured a dell switch before but I can help guide you in the right direction as to how this "should" be configured.

This is definitely possible first of all.

First, identify the device that will do your inter-vlan traffic routing.  Is this the dell or do you have another device.  I'm assuming you have another device.  You'll need to setup the address sub-interface on that device so that it can be the gateway for the 250 vlan.

second, connect the new switch to your existing switch infrastructure.  The interface on the switch you plug it into and the interface you use on the new switch both need to be configured like a trunk.  Basically, vlan1 (or whatever you have as your native vlan) is untagged and everything else is tagged.  

Finally, assign all the ports to the desired vlan.  Do this by assigning them to be an untagged vlan for only a single vlan.  all other vlans would just be non-existent on the interface.  I hope I'm not making that sound confusing but I'm mostly a cisco guy and trying to remember how I've seen other companies do their vlan tagging.

By default, DHCP will not be in vlan 250 because of the way DHCP works.  If you should ever want DHCP on that vlan though, you'd need to setup a new scope for the 250 network on your server and then configure your inter-vlan routing device as a dhcp relay for that vlan as well.

Also, just as a side note.  If you want to use the dell switch as the inter-vlan device for the 250 network and the current device you're using for everything else, then do exactly what I mentioned above except when it comes to the .1 address sub-interface creation, that would be on the dell switch.  You would also have to create another sub-interface in the correct vlan on the dell switch with an ip to communicate to the current gateway router and then add a route on the current gateway to the dell switch using the non-vlan 250 address you setup and a default route on the dell to the current gateway router.

hope i didn't confuse you too much as that is a lot, let me know if you have any questions.  Remember though I can't help with configuration specifics as I have never configured a dell.  if you supplied a text config or screenshots I might be able to help a little further though.

Author Comment

ID: 39222945
Thanks so much for your reply Cyclops3590.

It does make me feel better that this can be done. But I hate that I can't get it to work. I think I am really close I am just missing something small.

Ok so I have an existing network now running 2.x,4.x, and 5.x and they can all see each other.

I setup the 20 VLAN on this switch and when I plug into it my devices get a DHCP address from the DHCP server in my network as expected.

I also setup a 250 VLAN that my Ruckus Zone Director connects to (250.2) and the Access Points (250.3-250.6) and the Zone Director handles the DHCP for my laptops. This works as expected and the Laptops are getting the IP address of 250.x.

However, I don’t understand how to make the 2 VLANs talk to each other so that my laptops (250.x) can communicate with my wired network (2.x). I am sure it is something simple that I am missing I just don’t see it yet.
LVL 25

Expert Comment

ID: 39223013
ok, it sounds like you have two layer 3 devices.  We'll call the device handling 2, 4, 5, and 20 networks Router1 and the dell with 250 network Router2.

Here's the problem it sounds like you're having.
vlan 250 hosts can't talk to anything but 250 hosts and can't reach anything outside their subnet.  the rest of the vlans all work just fine.

If that is correct, here is your problem.  Router2, while it may be plugged into Router1, doesn't know how to communicate back and forth; no routing capability.

Here is your solution.

1) Setup another interface on Router1 that is part of vlan 250.
2) Switch all clients to using that new interface as the default gateway


1) setup another interface on Router2 that is part of vlan X where X can be 2, 4, 5 or 20
2) Setup a route on Router2 for 0/0 (default route) and set the next hop as the IP in that vlan you just added to the IP associated with the corresponding vlan interface on Router1
3) setup a route on Router1 for 250.x/24 and point it toward the IP address of the vlan interface setup on Router2 done in step 1

personally I would do the first one as its easier to maintain having a single device be the inter-vlan routing device.  at this point you should be able to communicate back and forth provided there is no network firewall rules preventing such communication

Author Comment

ID: 39238876
I have put this on hold for now. Thanks for your help with this! I think you were taking me down the right path and when I can I will revisit it.

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Problem Description:   Couple of months ago we upgraded the ADSL line at our branch office from Home to Business line. The purpose of transforming the service to have static public IP’s. We were in need for public IP’s to publish our web resour…
I recently attended Cisco Live! in Las Vegas, a conference that boasted over 28,000 techies in attendance, and a week of hands-on learning hosted by a solid partner with which Concerto goes to market.  Every year, Cisco displays cutting-edge technol…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
Suggested Courses

609 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question