Dell PowerConnect 2724 and VLAN Trunk

The DELL PowerConnect 2724 is a decent web managed switch. What I was trying to accomplish was setting up VLANs on my main switch and passing the information to the 2724 through a TRUNK.

A trunk is used so that instead of taking a network cable from one switch’s VLAN and running it to another switch (vlan 1 to vlan 1, vlan2 to vlan2, etc making you use up ports to connect different vlans) you can use one port to hold all the VLAN information. If you didn’t use trunking, then each VLAN that you wanted to communicate between the switches would EACH need a cable running to the VLAN.

VLAN1 is the default VLAN. You cannot receive TAGGED packets to VLAN1. Other VLANs you can receive tagged packets. I wanted to setup 3 VLANs.

VLAN 1 – Ports 1-8
VLAN 2 – Ports 9-17
VLAN 3 – Ports 18-24

First you go into your Dell management web gui and click on VLAN membership. Here you create VLAN 2 and VLAN 3. Next you UNTAG packets on the VLANS for the specific ports, so VLAN1 would have  U by ports 1-8. I will be using PORT 1 as the trunk, so for VLAN2 and VLAN3, make sure you specify port 1 as the trunk, and it will show a T which means tagged egress packets.  VLAN1 cannot cannot receive tagged packets, so you cannot make port1 on VLAN1 the T, it will remain U which means untag egress packets.

The switch that will be connected to the Dell Powerconnect 2724 is a HP ProCurve. The trunk port on this end is configured to send UNTAGGED packets to VLAN1, and TAGGED packets to VLAN2 and VLAN3. This is very important, or nothing will work.

Now this line of Dell switches are a little different. You created the VLAN you think and specified which ports are associated with which VLAN under the VLAN membership. For some reason, we are NOT done. Click on the VLAN port settings. Here you will need to AGAIN specify which VLAN each port is associated with, by entering in the VLAN # in the PVID.

Thanks for those who submitted and clarified some errors. I would like to give credit.

  • Thanks for this.

    Was looking for a straightforward answer to trunking on the 27xx series and was going to give up when I found your page.

    Thanks again, Marc

  • Ah, glad I could be of help. They were well priced switches when I bought them, but the VLANing was definitely a questionable feature. Once you get it to work though, you’re pretty good to go. Thanks for checking out the site.

  • Just a question about the Dell powerconnect 27xx series.. the documentation is not clear to me. Can you use this device and create a trunk port? or does it just read vlan tags?

    I am looking for a GB capable switch for ‘home’ use to test different QoS/altq with FreeBSD.

    From what I can see they do not allow a trunk port; is this true?

  • Brian,

    You can definitely create a VLAN trunk. I’ve created one as you can see by this port.

  • Hey Shank,

    Great and helpfull guide, unfortunatly the Dell documentation IMO is not very explanatory but i found here a good detailed explanation and only 1 doubt left.

    When u write: “I will be using PORT 1 as the trunk, so for VLAN2 and VLAN3, make sure you specify port 1 as the trunk, and it will show a T” you mean specify port 1 as the trunk but this has to be done in the LAG section? i ask, bc i cannot find another option to explicitly say “port X is a trunk” in the web browser… could u tell me where is this set?

    Thank you very much and keep up the good work.


  • Hi Teixeria.

    Thanks for the response and glad this site has helped you. I agree, the Dell manual is useless for these PowerConnect switches.

    To clarify, under the VLAN membership, you would select your VLAN ID on the drop down box, then assuming we are using port 1 as the trunk, you would TAG port 1. So I did this for both VLAN 2 and VLAN 3. So by showing a T there for port 1 on 2 VLANS (not VLAN1 since you can only show a U untag packets because that is the default VLAN).

    Sorry for the misunderstanding, let me know if you have any other questions.

  • Hi Shank,

    i can’t get it work, but thanks to you i understood better the “tagging” process.

    What i have is:
    ##### VLAN Membership #####
    VLAN 1 (default) port 1-14 and 17-24 porta are untagged, they display an U in the

    VLAN 13 port 15,16 without T or U just “Not Member” on these ports but have a T in port 24 which is my trunk port to the other switch.

    ##### VLAN Port Settings #####
    Interface: 15 and 16
    PVID: 13
    Frame Type: Admit All
    Ingress Filtering: Enable

    the remaining port are all by default in vlan1

    my question? should i put port 24 ( trunk port) belonging also to vlan 13? if so, the web interface only let attrib 1 vlan id per port…

    Any suggestions?

    Thank you very much, once, for helping out.


  • Teixeria,

    Yes, it’s kind of confusing with VLAN1 because it is the default VLAN.

    And also if port 24 is the trunk port, you already made it part of VLAN13 by having the T present on it. But for VLAN1, you did not specify port 24 as T.

    Let me know, i’m eager to help you get this working. I’ll be in front of my unit soon so can try to troubleshoot with it also.

  • Hey Shank,

    Thanks once more for your availability to help :)

    As 1 image means more than 1000 words :)
    I took the liberty to post the config images here:
    Vlan Port Settings:
    Vlan Membership:

    I hope it helps you know how do i have the configuration.
    Many thanks.


  • Teixeria,
    I noticed that VLAN1 does not have port24 tagged. Please tag and let me know output


  • Shank,
    I cannot tag the vlan1, bc as is the default vlan, its automatically stays “untagged”.
    Another this i noticed is that, in the trunk port ( 24 ) i’m not able to set the PVID like “10,12,13” its says “PVID must be an Integer between 1 to 4095″ therefore i cannot explicitly say that port 24 ( my trunk ) belongs to vlan 10,12,and 13.



  • I think I contradicted myself, my apologies haha.

    okay so yes you cannot set a TAG port on VLAN1 because that is default.

    How about your switch you are trunking to. What is that configured as? This is also KEY. In your case, the other switch should have it’s trunk port sending VLAN1 untagged, but vlan13 should be tagged. Because VLAN1 on these dells are default and cannot receive receive tagged packets. Try this and let me know..


    A) Make Port 1 your trunk port (as I know I had this working)

    B) Don’t use VLAN1, use a different VLAN instead of VLAN1 to get out of that problem with the default VLAN.

  • i’ve a Dell PC 6024 L3 switch in the other side, and as i can configure it via console its way more direct and easy. In the 6024 switch i’ve the same number and id vlans, and i’ve the “switch mode trunk” activated to the port that connects this 2724 switch, and i’ve the vlan access configured to use the trunk link port.
    I’m gonna try with your tips, put this working… just for curiosity, i searched the Dell community foruns and i found and answer that says: ” set the trunk port PVID = 4095″ weird but…. just for curiosity, if u wanna see it

    Tricky damn switch huh? 😉

    Thanks once, more!


  • Hey, and luck on this?

  • here is my config:

    – VLAN 10: Ports 1-5
    – VLAN 50: Ports 6-10

    Each Port is setup as “T” for the appropriate VLAN, and the PVID is set as “10” or “50” for each port.

    On Port 11 & 12 I have a server running ESX with VMs configured for VLANs 10 & 50. In the cisco world i would “trunk” ports 11 & 12 so all VLANs come communicate across those ports.

    With a Dell 2716, do I simply tag ports 11 & 12 with each VLAN? So port 11 would have a “T” for VLAN 10 & 50 (same for port 12)?? If so, what PVID should be set for ports 11 & 12?

    Thanks…this was a great article!!!!

  • Shank,

    I have problem configuring a Dell 5448 switch for vlans with traffic going in/out from a Netscreen SSG140 FW.

    I created 3 vlans on the switch
    1. vlan2 (internet connection)
    2. vlan3 (web app)
    3. vlan4 (database)

    vlan1 is the Dell default.

    In vlan2, I have the Internet cable and & the public interface of the FW.
    I picked port 11 to be the trunk where the internal fw interface is plugged in.
    I could ping servers on vlan1 from vlan3 but not vice versa.

    The fw guy told to create another vlan100 and match that up with the vlan100 tagged on the FW.
    So I created the vlan100 selecting a port leaving it untagged (U) and picked the trunk port 11 for the vlan100. After I did that, I lost connection to the Internet.
    I am not sure why that would make a difference to solve the problem of pinging vlan3 from vlan1.

    Please advise.

  • I have a question regarding vlans and management interfaces for Powerconnect 2848. If I have vlan 1 and vlan 2 and I trunk to another powerconnect 2848 will I be able to see the vlan 1 across the trunk link meaning will they be in the same broadcast domain because I plan to run DHCP in vlan 1 across multiple 2848 switches. Reason I am asking is because of the management interface defaulting to vlan1 so I want to put a network on vlan 1 and a second network on vlan2 but want the capability to manage the switches from vlan1.

  • More information to my post above


    ports 1-24 untagged
    port 48 tagged

    ports 25-48 untagged
    port48 tagged

    same configuration on both switches. Just need confirmation from you techies to make sure vlan 1 is the same broadcast domain on both switches over the trunk.

  • my mistake you cannot tag vlan 1 so disregard port 48 tagged for vlan1 =0]

  • Yes. You should be able to see DHCP requests being sent over the trunk. I have a very similar setup as you can see.

  • The only difference was I used 4 Dell powerconnect 2724 switches.

    I created a Link Aggregated Group (LAG) on each one consisting of 3 ports on ports 2-4. This LAG membership was trunked. A lag allows the following:

    • Fault tolerance protection from physical link disruption
    • Higher bandwidth connections
    • Improved bandwidth granularity
    • High bandwidth server connectivity

  • Hi, I’m trying to segment off a section of my 274 (ports 17-24) for use as a mini-iSCSI network between a VMware host and a Drobo storage device. No uplink to other switches are required as this is purely a network for the storage array and this new network receives a new IP subnet.

    As I understand the documentation, under VLAN Membership, I create a new vlan (vlan 2), then assign ports 17-24 (set to ‘U’). Then, under VLAN Settings, I assign PVID ‘2’ to ports 17-24, right? At this point, do I need to set anything on the end points (the VMware server allows me to configure a vlan ID for the virtual NIC that is connecting to the newly create vlan but the Drobo does not.

    When I do this though, traffic between the VMware host and the Drobo fails; if I do not set the VLAN Settings PVID (leave as default ‘1’), then I am able to ping devices on ports 17-24 from ports 1-16 on a device that has the same subnet info.

    Any help is appreciated.

  • Hello: I have a powerconnect 2748, and was able to create a trunk on my Cisco 3750 to port 48 on my 2748 (tag T) assign PVID 9 for (VLAN9). I also untagged port 25 with VLAN 9. Then, I created VLAN 5 and Untagged port 1,2,3 assign PVID 5. Everyting work wonderfully. expect, I lost the ablility to Manange the switch, once I applied the changes…. Yea, I can do a direct connect from my laptop into the switch (, If i assign a static ip address on the laptop (, but only if I unplug it from the cisco switch. Any ideas how to fix this issue ?

  • THANKS for posting the instructions.
    I too was about to give up on my Dell switch.

    Thanks to THIS SITE (and NOT Dell) I was able to configure a VLAN trunk port.


  • Hello Shankaran,

    I’m interested in the LAG function could you please give me more information on how to set it up? There are so many places in my switch(PowerConnect 5424) that have LAG settings.

  • Sorry for the LATE responses guys, been so busy. I’m back now though. I don’t have these devices anymore to assist but I will try my best from memory.

    Brian you are probably on the wrong VLAN.

    Greg glad I could be of help.

    Steffo I am unaware of the similarities between that device and the 2700 series. Are any of the changes mentioned above visible in your device?

  • We have three PowerConnect 2748 and would like to setup VLans (two internal & one DMZ) on all three connected by fibre cables interlinking all three. This way all the traffic will be passed at the switch level. Can this be done on this model?

  • Hi Shankaran,

    Thanks for a great article.
    I’m about to implement it in my environment but I would like to confirm a few things with you if that’s ok?

    This is what I have in my environment:
    Cisco ASA 5510
    Port 1.1 – VLAN 10 (Local LAN)
    Port 1.2 – VLAN 20 (DMZ)
    Both are using PORT 1 on the Cisco.

    Port 24 – connected to Cisco ASA PORT 1 – VLAN Membership ID 10 & 20 is set to T.

    Port 23 – connected to 3Com 4200G – VLAN Membership ID 10 is set to T.

    Port 1-4 – connected to VMware Server – VLAN Membership ID 10 & 20 is set to T because few VM servers would be on the DMZ and some on local LAN.

    Port 5-22 connected to LAN PCs on VLAN 10 so I left the VLAN Membership to U.

    Now, this is the tricky part.
    I don’t know what to set on VLAN Port Setting.
    Right now, everthing is defaulted to PVID 1.

    How do I make Port 24 and 1-4, PVID 10 & 20? Or I should just leave it at PVID 1?
    Do I need to make Port 23, PVID 10?

    Any help or suggestion would be appreciated. :)


  • HI,

    I am trying to setup a test network and want to connect 2 subnets together using my 2716. My thoughts are to have a single port on say VLAN1? which uplinksto my firewall for internet access.

    Then have VLAN2 to 1 subnet and VLAN3 to another subnet.

    Can I use port1 for the uplink to internet of this and if I tag all the ports will this allow routing of all the traffic?

    I also want to allow all traffic to all subnet etc…

    Any tips am I on the right lines?

You can follow any responses to this entry through the RSS 2.0 feed.

Trackbacks / Pingbacks