FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Leased Line Services
Issue: 13 3HH-11985-AAAA-TQZZA 107
4 Virtual Leased Line Services
4.1 In This Chapter
4.2 Ethernet Pipe (Epipe) Services
4.3 VLL Service Considerations
4.4 Configuring a VLL Service with CLI
4.5 VLL Services CLI Command Reference
4.6 VLL Service CLI Configuration Commands
4.1 In This Chapter
This chapter provides information about Virtual Leased Line (VLL) services and
implementation notes.
4.2 Ethernet Pipe (Epipe) Services
4.2.1 Epipe Service Overview
An Epipe service is Nokia’s implementations of an Ethernet VLL based on the IETF
“Martini Drafts” (draft-martini-l2circuit-trans-mpls-08.txt and
draft-martini-l2circuit-encapmpls-04.txt) and the IETF Ethernet Pseudo-wire Draft
(draft-so-pwe3-ethernet-00.txt).
An Epipe service is a layer 2 point-to-point service where the customer data is
encapsulated and transported across a service provider’s IP or MPLS network. An
Epipe service is completely transparent to the subscriber’s data and protocols. The
Epipe service does not perform any MAC learning. A local Epipe service consists of
two SAPs on the same node, whereas a distributed Epipe service consists of two
SAPs on different nodes. Service Distribution Points (SDPs) are not used in local
Epipe services.
This product only supports distributed Epipe service.
Each SAP configuration includes a specific port on which service traffic enters the
ISAM from the customer side (also called the access side). Each port is configured
with an encapsulation type. If a port is configured with an IEEE 802.1Q (referred to
as dot1q) encapsulation, then a unique encapsulation value (ID) must be specified.
To Next Page
Loading...
