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.