Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[ EX/QFX ] Native VLAN behavior on ELS JUNOS OS versions

0

0

Article ID: KB32289 KB Last Updated: 23 Mar 2018Version: 1.0
Summary:

This KB explains how native VLAN behaves on switches with Enhanced Layer 2 Software (ELS) Junos version enabled.

 

Consult the following for a list of switches that support ELS Junos OS: Software Feature: Uniform Enhanced Layer 2 Software (ELS) CLI configuration statements and operational commands

Symptoms:

On switches with non-ELS Junos OS, the native VLAN will NOT tag traffic if native VLAN ID is not mapped in "VLAN Member" configuration.

Example output: (Non-ELS Junos OS)

ge-0/0/23 {
    unit 0 {
        family ethernet-switching {
            port-mode trunk;
            vlan {
                members [ Cust_150 Cust_151 ];
            }
            native-vlan-id 1; <--- Native VLAN traffic will be sent as untagged.
        }
    }
}

However, output of "show vlans" indicates that the physical port is already active and mapped into native VLAN.

{master:0}[edit]
root@EX3300-1# run show vlans

Name           Tag     Interfaces
NATIVE         1       ge-0/0/23.0*

<Output Truncated>

{master:0}[edit]
root@EX3300-1# show vlans

NATIVE {
    vlan-id 1;
}
Solution:

On the other hand, Junos ELS version will NOT recognize the same physical port active into native VLAN even when "native VLAN" is enabled on the specific interface. Communication will fail though using Native VLAN if it isn't mapped into "vlan members" on the specific interface.

 

Example output: (ELS Junos OS)

{master:0}[edit]
root@EX2300-1# run show vlans

Routing instance        VLAN name             Tag          Interfaces
default-switch          NATIVE                100          ge-0/0/0.0     <--- There are no active interfaces mapped into native VLAN.
default-switch          v1                    1            ge-0/0/2.0*

 

{master:0}[edit]
root@EX2300-1# show interfaces ge-0/0/2

native-vlan-id 100;                          <--- Native VLAN has already been enabled under interface ge-0/0/2.
unit 0 {
    family ethernet-switching {
        interface-mode trunk;
        vlan {
            members v1;                      <--- Native VLAN is not mapping in "vlan members" for interface ge-0/0/2, which will make communication via native VLAN fail.
        }
        storm-control default;
    }
}

{master:0}[edit]
root@EX2300-1# show vlans

NATIVE {
    vlan-id 100;
}
 

 

Communication via Native VLAN will not work well until the Native VLAN is mapped into "vlan members".

{master:0}[edit]

root@EX2300-1# show interfaces ge-0/0/2

native-vlan-id 100;              
unit 0 {
    family ethernet-switching {
        interface-mode trunk;
        vlan {
            members [ v1 NATIVE ] ;  <--- Native VLAN mapped under "vlan members"

        }
        storm-control default;
    }
}


 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search