Support Support Downloads Knowledge Base Case Manager My Juniper 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

[Junos] Config difference of VLAN under forwarding-options analyzer

0

0

Article ID: KB35750 KB Last Updated: 30 Apr 2020Version: 1.0
Summary:

In release 18.1R3-S3.8, when configuring VLAN under forwarding-options analyzer, depending on the style of interface, only the VLAN name or VLAN-ID/VLAN name might be used. In SP style, when using VLAN ID, although the commit goes through, it is not programmed and VLAN is not in "show forwarding-options analyzer" output. But if vlan name is used, it is seen. However, in config hint, it shows both VLAN name or VLAN ID should work:

user@labtest# set forwarding-options analyzer VXLAN input ingress vlan ?
Possible completions:
  <vlan-name>          VLAN name, VLAN id or VLAN range string
Solution:

In SP style, multiple logical interfaces are configured on the physical interface, and associated each unit with a different VLAN. In Enterprise style, VLAN ID is explicitly mapped with VLAN name, and then bind it to the interfaces. However, in the analyzer implementation, it is programmed per physical interface level. So in-case of SP style configs, we need to specify the vlan-name in analyzer create command, and vlan-id config would not work.

Interface type difference:

For details, refer to the technical documentation on Flexible Ethernet Services Encapsulation 

ENTERPRISE STYLE CONFIGS

------------------------
set interfaces xe-0/0/0:1 unit 0 family ethernet-switching interface-mode trunk
set interfaces xe-0/0/0:1 unit 0 family ethernet-switching vlan members VLAN200
set vlans VLAN200 vlan-id 200
set vlans VLAN100 vlan-id 100 <-- mapping vlan name with identifer

set forwarding-options analyzer TEST input ingress vlan 100 <-- (either VLAN100/100 would work here)
set forwarding-options analyzer TEST output interface xe-0/0/0:1.0

root@labtest> show forwarding-options analyzer TEST                  
  Analyzer name                    : TEST  
  Mirror rate                      : 1     
  Maximum packet length            : 0     
  State                            : up    
  Ingress monitored VLANs          : default-switch/VLAN100
  Output interface                 : xe-0/0/0:1.0

SP STYLE CONFIGS

----------------
set interfaces et-0/0/1 ether-options 802.3ad ae301
set interfaces ae301 flexible-vlan-tagging
set interfaces ae301 encapsulation flexible-ethernet-services
set interfaces ae301 unit 30 encapsulation vlan-bridge
set interfaces ae301 unit 30 vlan-id 30
set vlans vlan30 interface ae301.30

set forwarding-options analyzer TEST2 input ingress vlan vlan30
set forwarding-options analyzer TEST2 output interface xe-0/0/0:1.0

root@labtest> show forwarding-options analyzer TEST2
  Analyzer name                    : TEST2
  Mirror rate                      : 1     
  Maximum packet length            : 0     
  State                            : up    
  Ingress monitored VLANs          : default-switch/vlan30
  Output interface                 : xe-0/0/0:1.0

Please note both SP and enterprise style configurations can co-exist in the system. Hence, commit validation in the analyzers are hard to be handled. In case of wrong usage, the state of the analyzer will remain down and monitored VLAN would not be added.

set forwarding-options analyzer TEST3 input ingress vlan 30
set forwarding-options analyzer TEST3 output interface xe-0/0/0:1.0

root@labtest> show forwarding-options analyzer TEST3
  Analyzer name                    : TEST3
  Mirror rate                      : 1     
  Maximum packet length            : 0     
  State                            : down 
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