Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

1465526

June 15th, 2010 06:00

VLAN support: trunk mode vs general mode

Hi,

Can anyone outline the difference between the trunk mode and general mode for VLAN support and the pros/cons of each mode?

We have two PowerConnect 6248 switches interconnected with a LAG (2 x 10GbE) and we need to VLAN support for the LAG between the two switches and also a couple of other LAGs (2 x 1GbE) to older PowerConnect 5324 switches.

We have about 10 different VLANs.

We're not sure if we should use trunk mode or general mode for the LAGs.

Thanks.

909 Posts

June 15th, 2010 09:00

I mis-remembered.  I did some testing with vlan 1 a while back.  The results are below.   The problem is vlan 1 is handled differently between PowerConnect models and also differently from Cisco.  My suggestion is stil to use general mode.

PowerConnect 62xx,8xxx,M6xxx,M8xxx:

  • “switchport trunk native vlan xxx” – command not available
  • Vlan 1
    • “switch trunk allowed vlan add 1” – allowed
    • vlan 1 egress traffic is always tagged
    • tagged vlan 1 ingress traffic is accepted if vlan 1 is in trunk
    • untagged ingress traffic is dropped

 

PowerConnect 33xx, 34xx, 35xx, 53xx, 54xx, 60xx

  • “switchport trunk native vlan xxx” – available
  • Vlan 1
    • “switch trunk allowed vlan add 1” – not allowed
    • vlan 1 egress traffic is always untagged, can not be tagged
    • tagged vlan 1 ingress traffic is always dropped
    • untagged ingress traffic is put in native vlan

 

Cisco

  • “switchport trunk native vlan xxx” – available
  • Vlan 1
    • “switch trunk allowed vlan add 1” – allowed
    • vlan 1 egress traffic is untagged if native, tagged if in trunk
    • untagged ingress traffic is put in native vlan
    • tagged vlan 1 ingress traffic is dropped if native vlan, accepted if in trunk

909 Posts

June 15th, 2010 07:00

62xx,8xxx,M6xxx,M8xxx:

Trunk: all vlans tagged, no native (untagged) vlans, vlan 1 not allowed

General: can choose multiple tagged and untagged vlans, pvid allow classification of untagged vlans, default is untagged

5324, M5316, 54xx, 35xx, 33xx:

Trunk: native vlan allows one untagged vlan, all other vlans tagged

General: can choose multiple tagged and untagged vlans, pvid allow classification of untagged vlans, default is tagged

I always use general mode on PowerConnect because it is the most flexible.  The default difference (tagged/untagged) between the different models can be confusing when comparing configurations produced from a "show running-config" though.

 

 

108 Posts

June 15th, 2010 08:00

62xx,8xxx,M6xxx,M8xxx:

Trunk: all vlans tagged, no native (untagged) vlans, vlan 1 not allowed

General: can choose multiple tagged and untagged vlans, pvid allow classification of untagged vlans, default is untagged

Thanks for the information, but it looks like it needs an update: trunk mode will also allow VLAN 1.

E.g. traffic for VLAN 1 seems to be able to pass just fine through the LAG connecting two PowerConnect 6248 switches with firmware version 3.2.0.7 with the following config:

interface port-channel 1

switchport mode trunk

switchport trunk allowed vlan add 1

Is that a feature of the new firmware version?

Thanks.

22 Posts

June 16th, 2010 13:00

Just one comment - native (untagged) vlans on  trunks are the common source of misconfigurations, loops and also serious security issue (vlan hopping attack).

Thus for switch-to-switch interconnections I'd strongly recommend using 'switchport mode trunk' which on 62xx enforces tagging for all vlans and disallows the user to configure any untagged vlan.

108 Posts

June 17th, 2010 08:00

I think I'll use the trunk mode instead of general mode for the interconnection between the two PC6248 switches.

But since we still have some legacy equipment on VLAN 1 and we need to interconnect the newer PC6248 switch with an older PC5324 switch, it looks like we're forced to use the general mode for that interconnection, since the trunk mode for the PC6248 will tag VLAN 1 packets, while the same mode on the PC5324 won't, correct?

Or is there a way to force the PC5324 to also tag VLAN 1 packets?

Thanks.

22 Posts

June 17th, 2010 10:00

There is a chance that 5324 just blocks vlan 1 because it's the native vlan by default and the same vlan couldn't be both tagged and untagged. Try creating some dummy vlan (e.g. vlan 4000) and then assign it as native to your interconnection:

 

interface xy

switchport mode trunk

switchport trunk native vlan 4000

switchport trunk allowed vlan add 1

 

If this succeeds, you'll have tagged vlan 1 also on 5324.

 

9 Posts

September 21st, 2010 07:00

 

I don't understand at all diffrence between general i trunk mode. I have pc 6248, 1/g10 is in general mode, i set few vlans as untagged. What happend when untagged frame will enter the port ? what vlan will be associate to this frame ? Could You explain ?

thank You

Popo

 

#show interfaces switchport ethernet 1/g10      

Port: 1/g10
VLAN Membership mode:General Mode

Operating parameters:
PVID: 1      
Ingress Filtering: Enabled    
Acceptable Frame Type: Admit All   
Default Priority: 0           
GVRP status:Disabled
Protected:Disabled

Port 1/g10 is member in:

VLAN    Name                              Egress rule   Type
----    --------------------------------- -----------   --------
1       Default                           Untagged      Default 
58                                        Untagged      Static  
59                                        Untagged      Static  
60                                        Untagged      Static  

                    


Static configuration:
PVID: 1      
Ingress Filtering: Enabled    
Acceptable Frame Type: Admit All   

Port 1/g10 is statically configured to:

VLAN    Name                              Egress rule
----    --------------------------------- -----------
58                                        Untagged 
59                                        Untagged 
60                                        Untagged

 

909 Posts

September 21st, 2010 14:00

on 6200:

Trunk mode- all traffic is transmitted with a vlan tag in the selected vlans.  All incoming traffic must be tagged in the selected vlans or it is dropped.

General mode is much more flexible:  At its simplest, general mode ports can transmit tagged or untagged packets in the selected vlans.  Incoming traffic can be tagged or untagged. The PVID sets the vlan of incoming untagged packets.  You may also classify incoming traffic wiith MAC/IP association.

In your example, the PVID is 1, so untagged traffic will be switched in vlan 1.

2 Posts

April 12th, 2011 12:00

Although late reaction, someone else might be helped with the answer/extra information:

For the above described situation you could use both trunk as general mode: in both cases you can define which traffic (VLAN's) are allowed on the link and in both cases you can include VLAN1 as allowed traffix.

When you connect to a Cisco switch that has a trunk configured to your Dell 62xx, M6xxx or M8xxx you will need the general mode as on a Cisco trunk the native VLAN (often Vlan1 but can be another one) is UNtagged.

Because the Dell switches in trunk mode expect all traffic (ingress) to be tagged and sends all outgoing (egress) tagged the traffic to/from native VLAN configured on the Cisco switch won't be recognized by the Dell switch and this can result in STP topology changes and thus flapping interfaces.

So when you connect your Dell switch to a Cisco switch with more then one VLAN of traffic on it use the general mode on the Dell switch as explained above.

23 Posts

August 7th, 2021 13:00

Can you help me to understand this configuration?

   console#show running-config interface gigabitethernet 1/0/2
   
   switchport mode general
   switchport general pvid 99
   switchport general allowed vlan add 50,60
   switchport general allowed vlan add 99 tagged
   
   
   console#show interfaces switchport gigabitethernet 1/0/2
   
   Port: Gi1/0/2
   VLAN Membership Mode: General Mode
   Access Mode VLAN: 1 (default)
   General Mode PVID: 99
   General Mode Ingress Filtering: Enabled
   General Mode Acceptable Frame Type: Admit All
   General Mode Dynamically Added VLANs:
   General Mode Untagged VLANs: 1,50,60
   General Mode Tagged VLANs: 99
   General Mode Forbidden VLANs:
   Trunking Mode Native VLAN: 1 (default)
   Trunking Mode Native VLAN Tagging: Disabled
   Trunking Mode VLANs Enabled: All
   Private VLAN Host Association: none
   Private VLAN Mapping:
   Private VLAN Operational Bindings:
   Default Priority: 0
   Protected: Disabled
   
   
    console#show interfaces status
   
   Port Description Duplex Speed Neg Link Flow M VLAN
   State Ctrl
   --------- --------------- ------ ------- ---- ------ ----- -- -------------------
   Gi1/0/1 N/A Unknown Auto Down Off T (99),50,60
   Gi1/0/2 N/A Unknown Auto Down Off G (99),1,50,60
   Gi1/0/3 N/A Unknown Auto Down Off A 50
   Gi1/0/4 N/A Unknown Auto Down Off A 60
   Gi1/0/5 N/A Unknown Auto Down Off A 99

The traffic from access vlan 50,60 will be redirected to the vlan 99?

How is handled the Response traffic?

 

Thanks

 

Moderator

 • 

3.6K Posts

August 8th, 2021 23:00

Hi, please see the attached screenshot for the configuration issue.

 

Also

there is difference some difference between trunk port and general port mode on switches 6248 & 5324.
Please refer to both.

1 Attachment

23 Posts

August 9th, 2021 03:00

Thanks for your reply.

This is a dummy configuration , I only want to clear myself how the switchport in general mode manage untagged traffic.

In this configuration, vlan 50 and vlan 60 are set as untagged...how can the switch manage 2 ( or more) untagged vlans in a single general port.

 

I can provide the same configuration in a trunk mode using native vlan...(so why and when general mode is needed and also general mode exist in dell devices only? ) 

Moderator

 • 

2.1K Posts

August 9th, 2021 04:00

Hello,

Hope this will help, 

  • General switchport mode consists of a combination of VLAN Trunk and Access Links.
  • General Links can have both tagged and untagged frames.
  • All frames sent to a specific VLAN must be tagged.  All untagged frames are sent to the native VLAN.
  • The native VLAN still applies to the General switchport mode. While it is possible to have multiple untagged VLANs on a General link, you can only have one (1) Port VLAN ID (PVID).  The PVID represents the native VLAN.
  • While untagged traffic may be sent via several untagged VLANs, returning untagged traffic will only be received by the PVID and therefore will NOT be forwarded to a specific VLAN.

     
HOW10261_en_US__1icon Note: The PowerConnect 62xx series switches must use General mode if you want to allow management traffic onto the switch over the PVID. If you use Trunk mode, you will not have the default VLAN on those ports. The ports will only allow tagged traffic.
And if you click on the link, you can see the available commands, examples and configuration from the GUI interface in the rest of the article. https://dell.to/3lPYB0v

23 Posts

August 9th, 2021 11:00

Ok, I think I got it.

Can you confirm that this scheme is correct?

Reikidude89_0-1628534890041.png

 

Reikidude89_2-1628535416307.png

 

  • General mode is a Dell proprietary protocol?

Thanks

23 Posts

August 9th, 2021 12:00

Great, so is this  a Dell proprietary protocol?

Also I suppose that the native comand is dedicated for links to NotDellSwitches.

 

Am I right?

No Events found!

Top