Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring BA Classifiers for Bridged Ethernet

date_range 19-Feb-21

On M120 and M320 routers equipped with IQ2 PICs, you can configure BA classification based on the IEEE 802.1 bits for bridged Ethernet over Asynchronous Transfer Mode (ATM), Point-to-Point Protocol (PPP), and frame relay for VPLS applications. The BA classification is applied to the first (outer) tag when tagged frames are received. Untagged frames are bypassed and a value of 000 for the classification IEEE 802.1p bits is assumed. There is no support for circuit cross-connect (CCC), and only port-mode VPLS is supported (in port-mode VPLS, only VLANs on a single physical port are included in the VPLS instance). There is no support for multilink PPP bonding with VPLS. For bridging over frame relay, only frames that do not preserve the frame check sequence (FCS) field are supported. Frames that preserve the FCS field are silently discarded.

The bridging over PPP function is restricted:

  • There is no support for “tinygram” compression and expansion.

  • Frames received with preserved FCS bits are silently discarded.

  • Bridge control frames are also classified based on header bit values.

  • Both tagged and untagged frames are classified and forwarded. The peer must discard frame types that are not supported.

The following example applies an IEEE 802.1p classifier named ppp-ether-vpls-classifier to interface (so-1/2/3) with Ethernet VPLS over PPP encapsulation.

Note:

The interface and CoS configuration must be consistent to support the feature. You must also configure the classifier and other CoS parameters such as forwarding classes.

  1. Apply the CoS behavior aggregate classifier to a logical interface.
    content_copy zoom_out_map
    [edit]
    user@host# set class-of-service interfaces so-1/2/3 unit 0 classifiers ieee-802.1 ppp-ether-vpls-classifier
    
  2. Configure the encapsulation and protocol family for the interface.
    content_copy zoom_out_map
    [edit]
    user@host# set interfaces so-1/2/3 encapsulation ethernet-vpls-ppp unit 0 family vpls
    
  3. Verify the configuration.
    content_copy zoom_out_map
    [edit class-of-service]
    user@host# show
    interfaces {
      so-1/2/3 {
       unit 0 {
        classifiers {
         ieee-802.1 ppp-ether-vpls-classifier;
        }
       }
      }
    }
    content_copy zoom_out_map
    [edit interfaces]
    user@host# show
    s0-1/2/3 {
      encapsulation ether-vpls-over-ppp;
      unit 0 {
       family vpls;
      }
    }
  4. Save the configuration.
    content_copy zoom_out_map
    [edit]
    user@host# commit
    

On routers with IQ2 or IQ2E PICs, you can perform BA classification based on the value of the inner VLAN tag in an Ethernet frame.

  1. To configure BA classification based on the inner VLAN tag value, speciy the inner option at the [edit class-of-service interfaces interface-name unit logical-unit-number classifiers ieee-802.1 classifier-name vlan-tag] hierarchy level. You must also configure the inner VLAN tag for the logical interface with the inner option at the [edit interfaces interface-name unit logical-interface-name vlan-tag] hierarchy level.

    content_copy zoom_out_map
    [edit]
    user@host# set class-of-service interfaces ge-2/2/2 unit 0 classifiers ieee-802.1 inner-vlan-tag-ba-classifier 
    user@host# set class-of-service interfaces ge-2/2/2 unit 0 classifiers ieee-802.1 vlan-tag inner
    
  2. Verify the configuration.

    content_copy zoom_out_map
    [edit]
    user@host# show
    class-of-service {
     interfaces {
       ge-2/2/2 unit 0
        classifiers ieee-802.1 inner-vlan-tag-ba-classifier {
         vlan-tag inner;
        }
      }
    }
    
  3. Save the configuration.

    content_copy zoom_out_map
    [edit]
    user@host# commit
    
footer-navigation