Carrier Ethernet Technology Forum - Ethernet Academy

Generated: 2 July, 2013, 01:47

l2cp handling with EVPL

Posted by eliot - 2010/04/12 15:42 _____________________________________

New to this stuff and having hard time to figure the following - maybe someone can help. When defining an EVPL service, what is the expected l2cp processing expected: I am defining an 2 EVPL services, connected to the same UNI (multiplex) Assuming i have mapped vlan 100 to an EVC1, and vlan 200 to EVC2. The UNI port is configured as "pass to EVC" for STP and PEER for L2CP. EVC1 is configured as STP - drop, l2cp - drop. while EVC2 is configured as STP tunnel, l2cp tunnel. Is all that possible - from what i understood so far it is a valid config, right ? Now lets assume: 1. receive STP frame without any vlan. 2. receive STP frame with vlan 100 3. receive STP frame with vlan 200 4. receive STP frame with vlan 300 5. receive l2cp frame without any vlan 6. receive l2cp frame with vlan 100 7. receive l2cp frame with vlan 200 8. receive l2cp frame with vlan 300 what should be done in each of the cases above ? Are there any more options ? 10x
============================================================================

Re:l2cp handling with EVPL

Hi,

Posted by Shahram Davari - 2010/04/12 17:40 _____________________________________

Please take a look at MEF 6.1. L2CP handling is specified for EVPL and other types of services in that IA. All L2CP configurations are per UNI and not per EVC. Regards, Shahram
============================================================================

Re:l2cp handling with EVPL

Posted by Ayal Lior - 2010/04/13 00:35 _____________________________________

Hi,
1/5

Carrier Ethernet Technology Forum - Ethernet Academy

Generated: 2 July, 2013, 01:47

MEF 6.1 is the place to find answers Please see section 8 for general explanation and then 8.2 for specific guidelines for EVPL You can definitely pass to EVC STP and by VLAN tag decide to which EVC you pass You can also map the untagged frames to one of the EVCs. You cannot however write general rule for all L2CPs, you need to do it per type and follow the 8.2 options (should you want to have a MEF compliant service). Ayal
============================================================================

Re:l2cp handling with EVPL

Posted by eliot - 2010/04/13 05:20 _____________________________________

Ayal 10x read the relevant sections in MEF6.1. However still not sure i get it... lets assume that i define the GARP handling attribute for a given UNI as peer. On the same UNI vlan 100 is mapped to EVC1. Now a GARP packet arrives on this UNI encap in a CE-VLAN 100. Should i peer with it ? should i pass it to the evc as data ? Now a GARP packet arrives without a vlan . Should i peer with it ? should i pass it to the evc as data ? What would happen if the GARP handling would have been tunnel ? lets assume that i define the BPDU handling attribute for this given UNI as discard what will happen for a BPDU that arrives on the port with CE-VLAN 100 should i still pass it as data - as it was encap by a vlan - and can no longer be regarded as a "true" L2CP packet ?
============================================================================

Re:l2cp handling with EVPL

Posted by Ayal Lior - 2010/04/13 05:26 _____________________________________

Hi, The handling of L2CP per EVC and per UNI type 2 (per MEF 20) is done before the mapping to the EVC. So, if you decided to Peer or Discard then the frames will not enter the EVC. Tunnel means that you map to the EVC and it is mapped per the EVC mapping (CE_VLAN IDs). As stated in section 8 of MEF 6.1, L2CP is identified by the MAC DA regardless of the VLAN. VLAN is used for mapping to EVC, assuming you decided to map it to some EVC Hope this helps,
2/5

Carrier Ethernet Technology Forum - Ethernet Academy

Generated: 2 July, 2013, 01:47

Ayal
============================================================================

Re:l2cp handling with EVPL

Posted by Dmitri Kalintsev - 2010/04/13 15:27 _____________________________________

Probably a useful thing to remember is the fact that practically all Layer 2 control protocols use untagged frames. The only ones that come to mind that would ever use VLAN tags are some of S-OAM (802.1ag) frames and Cisco PVST+ PDUs. Regards, - Dmitri
============================================================================

Re:l2cp handling with EVPL

Posted by Peng He - 2010/04/13 20:30 _____________________________________

I also saw vendors (other than not Cisco) adopted vlan-tagged STP BPDUs. Of course, this is not per std; it belongs to protocol-extension by vendors.
============================================================================

Re:l2cp handling with EVPL

Posted by zhu yao - 2012/09/12 00:21 _____________________________________

In MEF 9 ATS, it said that only frames untagged or the vlan which untagged frames mapped to are recognized as L2CP,other are recognized as user traffic I think pratically all L2CP is untagged
============================================================================

Re:l2cp handling with EVPL

Posted by zhu yao - 2012/09/12 00:45 _____________________________________

MEF9 Case 13 Verify an EVC configured with the EVC Layer 2 Control Processing Attribute associates two or more UNIs and when specific Layer 2 Control Protocols are configured for tunneling, the MEN tunnels the specific Layer 2 Control Protocols on theEVC that is mapped to the untagged CE-VLAN ID in the CE-VLAN ID/EVC Mapand deliver the Service Frames carrying the specific Layer 2 protocols at all egress UNIs in the EVC identical to the corresponding ingress Service Frames.
3/5

Carrier Ethernet Technology Forum - Ethernet Academy

Generated: 2 July, 2013, 01:47
============================================================================

Re:l2cp handling with EVPL

Posted by Ayal Lior - 2012/09/12 00:57 _____________________________________

Hi, Not quite so. Indeed, some L2CP are link layer and have no tag (e.g. PAUSE, LLDP, Link OAM). However other L2CPs may very well be tagged. For example: 1. MSTP is clearly VLAN tagged. 2. PTP (1588 ) can be tagged My 2 cents, Ayal
============================================================================

Re:l2cp handling with EVPL

Posted by zhu yao - 2012/09/12 03:00 _____________________________________

So why MEF 9 case 13 said that? MSTP and PTP have tag, I know any other protocols?
============================================================================

Re:l2cp handling with EVPL

Posted by Ayal Lior - 2012/09/12 03:08 _____________________________________

Hi, Let's step back and think of L2CP handling. You first need to pass the decision at the UNI, now say you decided to tunnel a certain L2cP you now map it to EVC. If it is tagged, then it goes according to the CE-VLAN ID / EVC map. Case 13 tests that untagged case and now the requirement is to map these L2CP along side untagged service frames to the EVC that untagged frames map to (per UNI's attribute "CE-VLAN ID for untagged and priority tagged Service Frames"). I hope this clarifies your concern. Ayal
============================================================================

4/5

Carrier Ethernet Technology Forum - Ethernet Academy

Generated: 2 July, 2013, 01:47

Re:l2cp handling with EVPL

Posted by zhu yao - 2012/09/12 03:15 _____________________________________

OK, sounds reasonable Thanks for your help

============================================================================

Re:l2cp handling with EVPL

zhu yao wrote: So why MEF 9 case 13 said that? MSTP and PTP have tag, I know any other protocols? This is not correct.

Posted by Alexander Kugel - 2012/09/13 07:02 _____________________________________

There are no tags in MSTP BPDU encapsulation. MSTP uses a single untagged frame that encapsulates all the information about VLANs and STP instances inside. As for proprietary Tagged STP implementations (PVST), they use proprietary MAC aadresses and as such are not part of L2CP protocols defined by MEF/IEEE. I also assume that L2CP part of the PTP (Peer-Delay messages) uses untagged frames as well. To summarize, there are no tagged L2CP frames within the DA range of 01-80-C2-00-00-00 to 01-80-C2-00-00-0F. L2CP protocols that use VLANs use the DA range of 01-80-C2-00-00-10 to 01-80-C2-00-00-2F. MVRP is one of such protocols, for example. It looks like MEF-9 performs tests for the more common L2CPs in the 00 to 0F MAC addresses block, and therefore it correctly requires to use the proper EVC to handle untagged traffic. I hope this helps. Alex
============================================================================

5/5