Native VLAN

[Pulakesh09]

Can a already assigned Access vlan( e.g VLAN 888 assigned for Access Point) be assigned as a Native VLAN at the same time. Screenshot attached.

[M02@rt37 · Accepted solution]

Hello @Pulakesh09,

The access VLAN and the native VLAN are two distinct concepts

Access VLAN
This is the VLAN to which an access port belongs. An access port carries traffic for only one VLAN, and this VLAN is referred to as the access VLAN.

Native VLAN
The native VLAN is used on trunk links to carry untagged traffic. By default, it is VLAN 1. However, you can configure a different VLAN as the native VLAN on a trunk.

So, in the context of an access port (like one connected to an Access Point), the concept of a native VLAN doesn't apply. Access ports are typically associated with a single VLAN, and there is no concept of "native VLAN" for them.

If you're dealing with a trunk port, you can configure the native VLAN separately from access VLANs. Just keep in mind that the native VLAN on a trunk is used to carry untagged traffic, and it should match on both ends of the trunk to avoid potential issues.

[Joseph W. Doherty]

"An access port carries traffic for only one VLAN . . ."

BTW, no longer true for switches that also support a (tagged) voice VLAN.

[M02@rt37]

Hello @Joseph W. Doherty 

That the reason why we call that voice port  :: mini-trunk even if the command is a voice vlan access x. 

[Joseph W. Doherty]

Hmm, first time I've heard "mini-trunk".

Searched the Internet for that term in reference to Cisco.  Only found one usage, in a reply posted here:  https://learningnetwork.cisco.com/s/question/0D53i00000KsuGyCAJ/ip-phone-and-trunk

Actually, not a bad term, although it might confuse until one realizes a switch port is physically capable of many operations, just the configuration determines usage restrictions.  Another example is a L3 port running as a '"routed port".

BTW, way back in ye olden times, before there were access ports with a voice VLAN option, we used actual "trunk" ports.

[Joseph W. Doherty]

What you're seeing (in your posted screen shot) is the config retaining some inactive interface configuration statements.

Switchport mode determines which applicable interface configuration statements apply.

[KJK99]

I can confirm what Joseph said. You have probably used the WebUI to configure the port. When you do that any change to the default configuration is saved even if it doesn’t really apply. That’s how it works on my CBS350 switches at least.

[Pulakesh09]

CLI using Secure CRT

[KJK99]

If I was doing that using CLI, I would remove the command “switchport access vlan 888,” because it does nothing when the switchport mode is trunk and its presence may be confusing to someone.

[MHM Cisco World]

The use of trank with voice must ve done after we check what VoIP phone do to traffic from PC connect to.

If VoIP send it traffic as tag and forward PC traffic  as untag

If VoIP send it traffic as untag and forward PC traffic as tag 

This force us to select which native we will use in SW it can native vlan is voice or data vlan.

But best solution is not using mini trunk' use voice vlan and data vlan in access mode.

MHM

[MHM Cisco World]

Hi friend'

Your config is not mini trunk and it not optimal 

When you config access vlan x 

Then you add mode trunk 

The SW will make this port as trunk not access' and native vlan since you are not config is defualt vlan1.

MHM