L2PT Limitations

L2PT and protocol filtering is implemented in software, so the number of frames that can be filtered or tunneled is limited.
Both L2PT and protocol filtering can be configured only through CLI. Configuration through SNMP (Simple Network Management Protocol)/XML is not supported for this release.
If L2PT configurations are made on PWs, these configurations are lost on a restart of the MPLS (Multiprotocol Label Switching) process unless the L2PT process is also restarted.
If L2PT configurations are made on a VPLS or VPWS service, dot1p tag inclusion must be enabled on the VPLS/VPWS. Also, VPLS or VPWS service must have same VLAN (Virtual LAN) IDs at each end of a PW.
When tunneling protocols are point-to-point in nature, it is your responsibility to ensure that there are only two tunnel endpoints for the protocol.
If a protocol that is configured to be tunneled on a service interface cannot be uniquely identified by its destination address and EtherType, then all packets with the same DA and EtherType of the protocol being tunneled (but that are not really PDUs of the protocol) will be slow path forwarded.
Tagged protocol PDUs cannot be tunneled over VLANs. Tagged protocol PDUs can only be tunneled over VMANs (the VMAN can be the service VMAN for a VPLS/VPWS service, or a standalone VMAN). Untagged protocol PDUs can be tunneled over both VLANs and VMANs (the VLAN/VMAN can be standalone, or be the service VMAN for a VPLS/VPWS service).
Untagged protocol PDUs cannot be bypassed if the ingress port is an untagged VMAN port with a default CVID. Untagged protocol PDUs can be bypassed if the ingress port is an untagged VMAN port without a default CVID.
In VPLS, only full-mesh configuration is supported for L2PT.
L2PT is not supported on VLAN ports that have a port specific tag.

Published March 2020prev | next

Email this topic

Print this page Print this page

Leave feedback Feedback