Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

49475

October 2nd, 2015 13:00

Troubles passing multiple vlans from layer 3 to layer 2

Hello,

We have a PowerConnect 6248 layer 3 switch with multiple vlans and routing enabled and also a PowerConnect 5324 layer 2 switch with a couple vlans configured.  My goal is to have multiple vlans passed through the layer 3 switch to the layer 2 switch and all vlans communicate with each other. 

I followed the steps under the Layer 3 + Layer 2 section under this post:

en.community.dell.com/.../19506015

Unfortunately, it's not working. 

Here is my current set up and what I've tried. All my configuration is being done through the web interface.

The 6248 has vlans 1, 64, 110, 150 and a few others configured on the switch. The IP address of the 6248 is 192.168.64.1.  I'm trying to get vlan 150 and 110 to the layer 2 switch so that I can have some ports serving up vlan 150 and some serving vlan 110.

I have the IP routing (Routing>IP>Interface Configuration) for vlan 150 as 192.168.150.1/24 and vlan 110 as 192.168.110.1/24. 

The 5324 is connected to the 6248 through one port (plugged into port 1 on the 5324 and port 18 on the 6248).  Port 18 on the 6248 is currently configured as General/Admit All/PVID 150.  Port 1 on the 5324 is currently configured to the same, but with a PVID of 1.  Vlan 150 is being sent untagged from the 6248 switch and vlan 110 is being sent tagged. 

The 5324 switch is configured with an IP address of 192.168.150.2 and a gateway of 192.168.150.1.  I'm able to access the switch's web interface and plug machines into any port and get on the 192.168.150.0 subnet.  I created a vlan 110 on the 5324 and tagged it on port 1 and port 4, but port 4 will not receive any traffic from vlan 110. I have tried many different port/vlan membership settings that have all resulted in failure. 

I would greatly appreciate some help on this.  It seems like such an easy feat, but I just can't figure it out.  I have attached some pictures for people to review. 

10 Posts

October 28th, 2015 12:00

I got it figured out.  I enabled Double VLAN on the trunk port of the 6248 switch and it works now.  

Moderator

 • 

8.5K Posts

October 2nd, 2015 18:00

Hi,

Is there a default gateway set on the 5324? Is VLAN 34 configured on the trunk port? If the device on port 4 is on PVID 34 and is sending untagged frames on 34 it needs to know how to get to the 6248 over the trunk port.

10 Posts

October 12th, 2015 14:00

Hi Josh,

Sorry about that, I had the wrong screen shots in there.  I have corrected it to vlan 110, which is the one I'm trying to configure with vlan 150 to carry across to the 5324 switch.  

Yes, the default gateway is set to 192.168.150.1 on the 5324.  

Vlan 110 is configured on the 6248 to be tagged on port 18.  On the 5324, I created a 110 vlan that is tagged on the trunk port as well as the port that I am trying to connect a device to 110.

Also, I have both ports that are connecting the 6248 and 5324 set to General.  I have tried setting both to trunk, but I am unable to receive traffic on the 5324 after that.  Is it correct that a trunk port can only allow tagged traffic?  That is how it acts on the 6248 when I set it to trunk.

Moderator

 • 

8.5K Posts

October 12th, 2015 15:00

Yes, a trunk port can only pass tagged traffic.

10 Posts

October 12th, 2015 16:00

So I should have the ports connecting the switches both set to trunk and have vlan 110 and 150 tagged?

How should the remaining ports be configured?  

Moderator

 • 

8.5K Posts

October 12th, 2015 16:00

Both being trunk with both VLANs should be what you want. Typically the ports that connect directly to devices are untagged because clients are not VLAN aware.

10 Posts

October 13th, 2015 15:00

When I set both ports to trunk and vlan 150 and 110 to tagged on the 6248 trunk port, I lose communication to the switch.  I can reach the switch if I set the port on the 6248 to General with a PVID of 150 and set vlan 150 to untagged on the trunk port, but I still can't get vlan 110 across.  I have created a 110 vlan on the 5324 that I have tagged on the trunk port and set a few other ports to untagged, but nothing is coming through.  I've tried configuring an IP interface for the vlan of 192.168.110.3/24, but still nothing.  

Moderator

 • 

8.5K Posts

October 13th, 2015 16:00

If it works as a general port the traffic you are sending it is untagged. Do ports on 110 on one switch talk to ports on 110 on the other?

10 Posts

October 13th, 2015 21:00

I'm not able to get anything with vlan 110 on the 5324 switch.  110 is working correctly through a different port (general pvid 110 untagged) hooked into a powerconnect 5548.  

Moderator

 • 

8.5K Posts

October 14th, 2015 09:00

It sounds like untagged is the only thing that is working. What types of devices are attached to the switches?

10 Posts

October 14th, 2015 16:00

Yeah, that seems to be the case currently.  That's why I'm pulling out my hair :)

It's just a Latitude E5500 that's connected to the port with vlan 110 on the 5324 switch.  

Moderator

 • 

8.5K Posts

October 14th, 2015 16:00

Where is it pointing to for its default gateway? Typically it would point to the IP address for VLAN 110 and you have the switch pointing to the other switch for its default route.

10 Posts

October 28th, 2015 09:00

The default gateway of the switch is set to 192.168.150.1 on the 5324.  The default gateway for the E5500 is 192.168.110.1 for one NIC (no traffic) and the other NIC has a default GW of 192.168.150.1 (working with traffic).  I should have the 5324 pointing to the 6248 for the default route?

Moderator

 • 

8.5K Posts

October 28th, 2015 10:00

If the traffic from the 5234 has to go through the 6248 it should point there or at least have a route there so it knows where to send data.

No Events found!

Top