Difference Between L2VPN and EoMPLS

l2vpnmpls

Quick terminology question:

It appears as though L2VPN describes a group of technologies. Ethernet over Multiprotocol Label Switching (EoMPLS) is one of these technologies. VPLS and Pseudowire are others.

If this is correct, it's not possible to configure L2VPNs, per se. Instead, we configure, for instance EoMPLS which achieves a L2VPN.

Is this correct?

Best Answer

You are correct. L2VPN is the technology, and VPLS and VPWS are services configured using that technology. When someone talks about configuring an L2VPN, they could be talking about configuring any of those services.

https://datatracker.ietf.org/wg/l2vpn/about/ https://www.rfc-editor.org/rfc/rfc4664

Related Solutions

Vpn – the difference between VPLS vs Layer 2 VPN

L2VPN is generic term for group of technologies out of which one is VPLS, but could be number of other technologies such as emerging EVPN.

For more information read WG charter/mailing lists as L2VPN has lot of active work going on. Also read RFC6624 and RFC4761

EoMPLS, MSTP, and RPVST

The ME3600s don't support the forwarding of STP or MST frames through EVC. Port based PWE3s will transport STP frames but you will have to chew up a lot of ports. Really you should be engaging your vendor to platform specific questions like this that are "Will the switch support X feature" or "Does your switch forward X traffic".

I suggest also habinga look at a feature backup pseudowires. That removes the loops at layer 2 at least although doesn't address your problem of no support for STP when using EVCs: http://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/fspseudo.html

It maybe also be that VPLS is a better way to go if it is a small number of peers and traffic. The ME3600s do support VPLS (I suggest runnnig 15.3(3)S3 at the time of writting).

Update

Since I wrote this the command is now present to forward L2 PDUs in the EVC however I haven't tested this:

ME3600-1(config-if-srv)#l2protocol tunnel ?
  R4     Reserved Protocol using DA Mac 0180.C200.0004
  R5     Reserved Protocol using DA Mac 0180.C200.0005
  R6     Reserved Protocol using DA Mac 0180.C200.0006
  R8     Reserved Protocol using DA Mac 0180.C200.0008
  R9     Reserved Protocol using DA Mac 0180.C200.0009
  RA     Reserved Protocol using DA Mac 0180.C200.000A
  RB     Reserved Protocol using DA Mac 0180.C200.000B
  RC     Reserved Protocol using DA Mac 0180.C200.000C
  RD     Reserved Protocol using DA Mac 0180.C200.000D
  RF     Reserved Protocol using DA Mac 0180.C200.000F
  cdp    Cisco Discovery Protocol
  dtp    Dynamic Trunking Protocol
  elmi   ELMI Protocol
  esmc   ESMC Protocol
  lacp   LACP Protocol
  lldp   Link Layer Discovery Protocol
  loam   Link OAM Protocol
  pagp   Port Aggregation Protocol
  ptppd  PTP Peer Delay Protocol
  stp    Spanning Tree Protocol
  udld   UDLD Protocol
  vtp    Vlan Trunking Protocol
  <cr>

2nd Update

Tested and works! The ME3600X/ME3800X are MEF 2.0 compliant devices so this is a required feature.

Best Answer

Related Solutions

Vpn – the difference between VPLS vs Layer 2 VPN

EoMPLS, MSTP, and RPVST

Related Topic