Description

Traffic that isn't vlan tagged is dropped following Junos upgrade to version 21.4R3-S8.5 on EX4300-32F

Symptoms

Prior upgrading EX4300 on version 14.1X53-D40.8, SRX was sending untagged traffic properly from point A to point B



Connections: SRX340 — EX4300 — EX4300 — SRX340


Interface configuration on EX4300:


set interfaces ge-0/0/3 flexible-vlan-tagging

set interfaces ge-0/0/3 native-vlan-id 4094

set interfaces ge-0/0/3 encapsulation extended-vlan-bridge

set interfaces ge-0/0/3 ether-options auto-negotiation

set interfaces ge-0/0/3 unit 1002 vlan-id-list 1-4094

set interfaces ge-0/0/3 unit 1002 input-vlan-map push

set interfaces ge-0/0/3 unit 1002 output-vlan-map pop

set interfaces ge-0/0/3 unit 1002 family ethernet-switching storm-control STORMCTL:10M:SHUT

set interfaces ge-0/0/3 unit 1002 family ethernet-switching recovery-timeout 300

Solution

On EX2300, EX3400, EX4300, EX4300-MP, EX4600, EX4650, and the QFX5000 line of switches except QFX5220, QFX5130, QFX5230, QFX5240, and QFX5700, for a Q-in-Q tunneling configuration, enable or disable whether the switch inserts a native VLAN identifier in untagged frames received on the C-VLAN interface when the configuration statement input-vlan-map with a push operation is configured


If you do not include the input-native-vlan-push statement, the option is enabled.


Note: 

Starting in Junos OS Release 21.4R3-S7, the default on EX4300 switches is enable, In earlier releases, the default is disable.


  • After configuring on EX4300 #set interfaces ge-x/x/x input-native-vlan-push disable, ping started to work between SRX devices. 


Modification History

2024-11-29 : Article Created