Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

no-native-vlan-insert

 

Syntax

Hierarchy Level

Release Information

Statement introduced in Junos OS Release 17.1R1.

Description

Send traffic without the native VLAN ID (native-vlan-id) to the remote end of the network if untagged traffic is received.

If this statement is not configured, then native-vlan-id is added to untagged traffic. But if this statement is configured, then native-vlan-id is not added to untagged traffic.

Note
  • This feature works only on MX Series routers with MPCs/MICs. Configuring this statement on MX Series routers with DPCs results is no behavioral change. However, if you configure the statement on aggregated Ethernet (ae) interfaces with logical interfaces across MPCs/MICs and DPCs, then the MPCs/MICs and DPCs behave differently.

  • In the egress direction, this feature is disrupted by VLAN normalization. Because of normalization, the egress interface cannot distinguish between untagged traffic and tagged traffic. And untagged traffic is sent out with native-vlan-id. Consider this while configuring both VLAN normalization and new native-vlan-id statement.

    There will be a problem with ingress firewall filter if filter term includes native-vlan-id. With no-native-vlan-insert statement configured, native-vlan-id will not be inserted to untagged traffic. So, firewall filter term will not match with untagged traffic. But if incoming traffic have VLAN ID which is equal to native-vlan-id, then firewall filter term will match and firewall will work.

  • When this feature is used with AE, all sub-interfaces of AE should be in same type of FPC.

Default

By default, native-vlan-id is inserted to untagged traffic. That is, if this statement is not configured, then native-vlan-id is inserted to untagged traffic.

Required Privilege Level

interface—To view this statement in the configuration.

interface-control—To add this statement to the configuration.