cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
927
Views
5
Helpful
16
Replies

C1300 and Dell switch problem with untagged traffic and general mode

I am having trouble configuring the C1300 and Dell 6224 switch.

On the Dell side, I received the following configuration:
krzysztofmaciejewskiit_0-1751470855583.png

The assumption is that traffic in VLAN150 is tagged, and I have no problem with that. The problem is with VLAN1, which is supposed to leave C1300 untagged and be tagged on Dell in VLAN51 (PVID51). I cannot find the correct configuration to make traffic from both VLANs work properly. On the Cisco C1300 side, I discovered that I can also set the general mode, but that didn't help either. Below is the port configuration I ended up trying:
interface TenGigabitEthernet1/0/21
 speed 1000
 description UPLINK
 switchport mode general
 switchport general allowed vlan add 150 tagged
 switchport general allowed vlan add 1 untagged
 switchport general pvid 51

Does anyone have experience with connecting Cisco <-> Dell?

EDIT: C1300 sees Dell's MAC in VLAN1 and Dell sees C1300's MAC in VLAN1.

1 Accepted Solution

Accepted Solutions

hello man. u're right that most solutions avoid vlan1, but since ur guidelines require it, u can still make it work without moving vlan1/ out. I've had only two cases where this scenario worked properly. The key looks to be ,on the dell side cause it tends to treat Vlan1 specially, even if you set a pvid. If vlan1 is still in the allowed vlan list, dell might ignore the pvid setting and treat untagged traffic as vlan1 anyway.

Try this config on the Dell:

int eth 1/g21
switchp mo general
switchp gen allow vla add 150 tagged
switchp gen allow vla add 51 untagged
switchpt gene pvid 51

Make sure vlan1 isn’t allowed on the dell port, cause this lets dell map untagged vlan1 traffic from Cisco to vlan51. I’ve seen this work in two similar cases, and i hope it will help u G. Worked for me, so try it......

 

-Enes

more Cisco?!
more Gym?!



If this post solved your problem, kindly mark it as Accepted Solution. Much appreciated!

View solution in original post

16 Replies 16

Mark Elsen
Hall of Fame
Hall of Fame

 

  - @krzysztofmaciejewskiit    Perhaps these info's can help you : https://www.dell.com/community/en/conversations/networking-general/need-help-with-vlan-configuration-dell-6224-and-cisco-2970/647f2068f4ccf8a8de4051c0
                                                          

                                                                                   https://learningnetwork.cisco.com/s/question/0D53i00000Kt2tdCAB/trunking-a-dell-6224-switch-to-a-cisco-3750g

  M.        



-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
    When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Unfortunately, this does not help, because here the solution to the problem was to move out of VLAN1 from what I understand, and in my case this is not an option, because these are the guidelines.

EDIT: I did not notice the second link, I will refer to it later.

This second link is also unlikely to bring anything new for me, I have general mode set.
Maybe only this VLAN1 on the Dell side is causing the problem?

Does anyone have experience with combining Cisco and Dell?

hello man. u're right that most solutions avoid vlan1, but since ur guidelines require it, u can still make it work without moving vlan1/ out. I've had only two cases where this scenario worked properly. The key looks to be ,on the dell side cause it tends to treat Vlan1 specially, even if you set a pvid. If vlan1 is still in the allowed vlan list, dell might ignore the pvid setting and treat untagged traffic as vlan1 anyway.

Try this config on the Dell:

int eth 1/g21
switchp mo general
switchp gen allow vla add 150 tagged
switchp gen allow vla add 51 untagged
switchpt gene pvid 51

Make sure vlan1 isn’t allowed on the dell port, cause this lets dell map untagged vlan1 traffic from Cisco to vlan51. I’ve seen this work in two similar cases, and i hope it will help u G. Worked for me, so try it......

 

-Enes

more Cisco?!
more Gym?!



If this post solved your problem, kindly mark it as Accepted Solution. Much appreciated!

First of all, I am very happy that someone finally wrote back!
Thanks for this advice, tomorrow at work I will try to test this with a client. I know he has it set to 150 on Tagged and 51 on Untagged.
Is the removal of VLAN1 from the interface achieved by checking the “Remove VLAN” checkbox? I have absolutely no experience with the Dell, nor do I have access to this GUI.
krzysztofmaciejewskiit_0-1751811116871.png

Still not working.

Cisco configuration:
interface TenGigabitEthernet1/0/21
speed 1000
description UPLINK
switchport mode general
switchport general allowed vlan add 150 tagged
switchport general allowed vlan add 1 untagged

Also tried with this configuration on cisco site:
interface TenGigabitEthernet1/0/21
speed 1000
description UPLINK
switchport mode trunk
switchport trunk allowed vlan 1,150   /   switchport trunk allowed vlan 150
switchport trunk native vlan 1

Dell configuration 9 (VLAN1 was indeed allowed as untagged, but as you advised, I removed it):
int eth 1/g21
switchport mode general
switchport gen allow vlan add 150 tagged
switchport gen allow vlan add 51 untagged
switchport general pvid 51

In summary, only traffic in VLAN150 is still working, while traffic in VLAN1 is not.

Rest related configuration:
vlan 150
!
interface vlan 1
ip address 192.168.51.233 255.255.255.0
no ip address dhcp
!
interface vlan 150
name MGMT
ip address 192.168.150.60 255.255.255.0
!
ip default-gateway 192.168.51.5
ip default-gateway 192.168.150.5

Thanks for the update. From what u shared, the port configs now look solid, and u're correctly mapping untagged VLAN1 traffic from Cisco into VLAN51 on the Dell side.

However, the issue seems to be that Dell still has its IP address on int vlan 1 , and not vlan 51. Since untagged traffic is now going into vlan51 (as per your pvid51 setting), Dell needs its SVI (Layer 3 interface) on vlan51 to actually handle that traffic.

Try this on the Dell:

no int vlan 1
vlan 51
int vlan 51
ip add 192.168.51.233 255.255.255.0

This should match the traffic flow and allow communication on 192.168.51.x again. vlan150 works because its SVI is set up correctly, and this should fix vlan1s routing too.

Let me know if this works....

 

-Enes

more Cisco?!
more Gym?!



If this post solved your problem, kindly mark it as Accepted Solution. Much appreciated!

I haven't had a chance to test it yet, but I wonder if we shouldn't also add VLAN 51 to those tagged on Dell, because VLAN 51 traffic is supposed to go to the FW subinterface, so in my opinion, tagged traffic should go there...

A funny solution to the problem – the customer didn't connect the VLAN, but insisted that he had :D.

LOOOOL what an epic situation! Just goes to show we should always double check everything. Glad it got sorted out G. Have a good one!

more Cisco?!
more Gym?!



If this post solved your problem, kindly mark it as Accepted Solution. Much appreciated!

I looked through the document, I don't see anything that is similar to my case unless I am looking wrong.
Is this link supposed to imply that these switches are incompatible with each other - “This article does not apply to PowerConnect 6224”?
Sometimes as an engineer you have no impact on what equipment is bought :P.

KJK99
Level 3
Level 3

I have dealt with several brands of network switches and I have never run into any compatibility issues as far as the basic VLAN configuration is concerned. I'm pretty sure you can make it work.

I haven't analyzed the whole message thread, but I see that the configuration shown in your first message is not correct. You have VLAN 1 as untagged, but the PVID is 51. This will not work. When using the general port type, the port PVID must match the untagged VLAN ID. That's how you tell the switch which VLAN untagged frames should be placed.

Kris K

Perhaps I should write this. Later I realized that the PVID is incorrect and changed it to 1 because I read what the PVID is and what it is responsible for and realized that I made a mistake on the Cisco side. Thanks for the advice and will follow @Enes Simnica advice later.