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

[BTI] Example - Tunneling LLDP packets between Juniper BTI8XX devices

0

0

Article ID: KB34140 KB Last Updated: 20 Jun 2019Version: 1.0
Summary:

This article shows the default behavior of BTI8XX for layer 2 protocol and how to pass LLDP packets (establish LLDP neighbor) across BTI8XX devices.

Symptoms:

Topology:

Issue:

By default, Switch A and Switch B will not be able to see each other's LLDP neighbor information.

If Switch A and Switch B want to see each other's LLDP neighbor across the SA-8XX network, the user must create a UNI and Ethernet EVC on the SA-8XX.

Cause:

With the SA-8XXs default L2CP profile, both UNI and EPLINE EVC will not tunnel LLDP packets. The LLDP packets from the Switch are terminated at SA-8XX.

The following commands can be used to check the existing L2CP profiles that bond to UNI and EPLINE EVC:

BTI-SA-821# show ethernet uni

Local UNI
----------------------------------------------------------------
UNI uni1
 Description                  : eth-0-1
 Mapped Interface             : eth-0-1
 TPID Value                   : 0x8100
 MTU
Size                     : 1522
 Default
CVLANID              : 0
 Default SVLAN Priority       : 0
 All to One
Bundling          : Yes
 
Bundling                     : No
 Service
Multiplexing         : No
 Maximum Number of
EVC        : 1
 L2CP Profile                 : uni-
epl-option1
 Number of
EVC                : 1
 Number of OVC                : 0
 
Efpsd                        : disabled(LBM with LIS disabled)
 EVC List ------------------------------------------------------
  L2CP4LLDP,
----------------------------------------------------------------

BTI-SA-821# show ethernet
evc
----------------------------------------------------------------
EVC L2CP4LLDP
 Service
Type                  : epline
 VC Type                       : Point-to-Point
 SVLAN
ID                      : 1000
 CE-VLAN ID
Preservation       : Yes
 CE-VLAN CoS ID
Preservation   : Yes
 Maximum Number of
UNI         : 2
 Number of
UNI                 : 1
 Number of RUNI                : 0
 Number of ENNI                : 0
 L2CP Profile                  :
evc-epl-option1
 EVC MEG
state                 : disable
 Local UNI List ------------------------------------------------
  uni1,
 INNI List ------------------------------------------------------
  nni7,
----------------------------------------------------------------
 

Different EVC types have different EVC L2CP profiles. The user can confirm this by executing "show ethernet l2cp" command; see below.

NOTE:

1) In case of a conflict, lower [index] rules have a higher priority.

2) UNI will peer the LLDP packets, whereas EPLINE EVC will discard it. This means both SA-8XX's UNI interface(s) will try to establish the LLDP relationship with Switch A and Switch B.

BTI-SA-821# show ethernet l2cp

Name: uni-epl-option1
  Index  PDU Address        MASK            Action    
  -----  -----------------  --------------  ----------
  1      0180.c200.0000     ffff.ffff.fff0  discard   
  2      0180.c200.0020     ffff.ffff.fff0  pass-to-evc
  3      0180.c200.0007     ffff.ffff.ffff  discard   
  4      0180.c200.000b     ffff.ffff.ffff  pass-to-evc
  5      0180.c200.000c     ffff.ffff.ffff  pass-to-evc
  6      0180.c200.000d     ffff.ffff.ffff  pass-to-evc
  7      0180.c200.000e     ffff.ffff.ffff  discard   
  8      0180.c200.000f     ffff.ffff.ffff  pass-to-evc
  11     stp                ffff.ffff.ffff  pass-to-evc
  12     slow-proto         ffff.ffff.ffff  peer      
  13     dot1x              ffff.ffff.ffff  discard   
  14     lldp               ffff.ffff.ffff  peer      
 
Name: evc-epl-option1
  Index  PDU Address        MASK            Action    
  -----  -----------------  --------------  ----------
  1      0180.c200.0000     ffff.ffff.fff0  discard   
  2      0180.c200.0020     ffff.ffff.fff0  tunnel    
  3      0180.c200.0007     ffff.ffff.ffff  discard   
  4      0180.c200.000b     ffff.ffff.ffff  tunnel    
  5      0180.c200.000c     ffff.ffff.ffff  tunnel    
  6      0180.c200.000d     ffff.ffff.ffff  tunnel    
  7      0180.c200.000e     ffff.ffff.ffff  discard   
  8      0180.c200.000f     ffff.ffff.ffff  tunnel    
  11     stp                ffff.ffff.ffff  tunnel    
  12     slow-proto         ffff.ffff.ffff  discard   
  13     dot1x              ffff.ffff.ffff  discard   
  14     lldp               ffff.ffff.ffff  discard    

Solution:

The user can create a new L2CP profile and apply it to UNI and EVC. The alternative is to modify an existing profile. In this case, modify Rule 14 only, then apply it.

For LLDP tunneling the L2CP behavior is: UNI: pass-to-evc, EVC: tunnel

Prerequisite: Any modification to an existing L2CP profile requires that the profile is not bonded to any UNI or EVC. The user must unbundle the existing L2CP profiles. Hence, JTAC recommends creating a new L2CP profile and apply it as needed. 


Example:

This example shows how you can create new profiles, delete an existing one and apply the one you just created. After the changes are applied, Switch A and Switch B should able to see each other's LLDP neighbor information.

Summary:

  • Create new UNI and EPLINE EVC L2CP profile that will tunnel LLDP.
  • LLDP behavior is alias to action 14
  • Change the behavior as UNI: pass-to-evc, EVC: tunnel
  • Leave the rest of the actions as default.   

‚Äč1) New UNI L2CP profile:

BTI-SA-821(config)# ethernet l2cp add uni-epl-option1-new
BTI-SA-821(config-l2cp)# action 1 discard
BTI-SA-821(config-l2cp)# action 2 pass-to-evc
BTI-SA-821(config-l2cp)# action 3 discard
BTI-SA-821(config-l2cp)# action 4 pass-to-evc
BTI-SA-821(config-l2cp)# action 5 pass-to-evc
BTI-SA-821(config-l2cp)# action 6 pass-to-evc
BTI-SA-821(config-l2cp)# action 7 discard
BTI-SA-821(config-l2cp)# action 8 pass-to-evc
BTI-SA-821(config-l2cp)# action 11 pass-to-evc
BTI-SA-821(config-l2cp)# action 12 peer
BTI-SA-821(config-l2cp)# action 13 discard
BTI-SA-821(config-l2cp)# action 14 pass-to-evc
BTI-SA-821(config-l2cp)# exit

2) New EPLINE EVC L2CP profile:

BTI-SA-821(config)# ethernet l2cp add evc-epl-option1-new
BTI-SA-821(config-l2cp)# action 1 discard
BTI-SA-821(config-l2cp)# action 2 tunnel
BTI-SA-821(config-l2cp)# action 3 discard
BTI-SA-821(config-l2cp)# action 4 tunnel
BTI-SA-821(config-l2cp)# action 5 tunnel
BTI-SA-821(config-l2cp)# action 6 tunnel
BTI-SA-821(config-l2cp)# action 7 discard
BTI-SA-821(config-l2cp)# action 8 tunnel
BTI-SA-821(config-l2cp)# action 11 tunnel
BTI-SA-821(config-l2cp)# action 12 discard
BTI-SA-821(config-l2cp)# action 13 discard
BTI-SA-821(config-l2cp)# action 14 tunnel
BTI-SA-821(config-l2cp)# exit

3) Remove the existing profile on UNI and EVC, and apply the one you just created:

BTI-SA-821(config)# ethernet uni uni1
BTI-SA-821(config-uni)# no l2cp
BTI-SA-821(config-uni)# l2cp uni-epl-option1-new
BTI-SA-821(config-uni)# exit
BTI-SA-821(config)# ethernet evc L2CP4LLDP
BTI-SA-821(config-evc)# no l2cp
BTI-SA-821(config-evc)# l2cp evc-epl-option1-new
BTI-SA-821(config-evc)# exit

 
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