Epipe
Epipe service is designed to carry Ethernet frame payloads, so it can provide connectivity
between any two SAPs on different nodes that pass Ethernet frames. The following SAP
encapsulations are supported on the 7705 SAR Epipe service:
While different encapsulation types can be used at either end, encapsulation mismatching
can occur if the encapsulation behavior is not understood by connecting devices and if those
devices are unable to send and receive the expected traffic. For example, if the encapsulation
type on one side of the Epipe is dot1q and the other is null, tagged traffic received on the null
SAP will be double-tagged when it is transmitted out of the dot1q SAP.
The supported PW service types are 0x0004 (Ethernet tagged mode), and 0x0005 (Ethernet
raw).
Ipipe
Ipipe service supports Ethernet null, Ethernet dot1q, IPCP, and PPP/MLPPP SAP
encapsulation over IP or MPLS. Ipipes support SAP-to-spoke SDP binding with a default
service MTU of 1500 bytes.
Ipipe service supports 0x000B (IP Layer2 Transport) PW service type.
ATM PWE3 N-to-1 Cell Mode Encapsulation
ATM PWE3 signaling over a PSN uses N-to-1 cell mode encapsulation (as per RFC 4717).
For Release 3.0, N is not user-configurable and N = 1 is the only value supported.
shows the structure of an N-to-1 cell mode frame.
7705 SAR OS Services Guide
•
Ethernet null
•
Ethernet dot1q
VLL Services
Figure 33
Page 183