Hello unfraget,
EoMPLS can transport any L2 protocol except MACSec with any configuration option.
To support MACSec transport over EoMPLS the PE nodes must use Port based EoMPLS I have configured it successfully on ME 3600 with IOS XE 15.5.3.
So be prepared for possibled issues with MACSec if the provider using modern syntax EVC based EoMPLS.
For all the other protocols any type of EoMPLS works well.
A port based EoMPLS is configured like the following:
interface GigabitEthernet0/9
description Port Based EoMPLS for trustsec
no switchport
no ip address
! the following command may be not needed it can be used to make the pseudowire up even not connected
!no keepalive
xconnect 192.168.246.19 3002 encapsulation mpls
!
TrustSec is another hame for MACSec. These protocols use destination addresses that are sent to main cpu of every device working at OSI layer2. This is done by design to avoid to have L2 devices in the middle of a MACsec session.
Port based EoMPLS make the PE interface so dumb/stupid that is only OSI layer1 and allow to pass these frames.
When using EoMPLS based on EVC these frames cannot pass they are sent to cpu of the PE node. Because EoMPLS with EVC are OSI layer 2 entities.
So ask the provide to give you port based EoMPLS for the reasons explained above and you wil be able to pass also MACSec frames.
Note: no form of Ethernet OAM is supported on port based EoMPLS. this is the price to pay to support MACSec / TrustSec over EoMPLS.
Hope to help
Giuseppe
