Epipe Emulation using Dot1q VLAN range SAP in VPLS with G8032
Page 288 7210 SAS-X, R6 OS Services Guide
scale the number of VLANs that can be handled by the node. This took care of the need to support
hundreds of VLANs using a single SAP or a small number of SAPs. When MPLS the mode is
deployed in ring topology, operators have the option of using different redundancy mechanisms
such as FRR, primary/secondary LSPs, Active/Standby PWs, to improve Epipe service
availability. No such option is available to protect Epipe service in L2 mode when deployed in a
ring topology. Additionally many operators prefer G.8032 based ring protection mechanism, since
a single control instance on the ring can potentially protect all the VPLS services on the ring.
This feature allows operators to deploy Epipe services in a ring topology when using L2 mode, by
emulating an Epipe service using a VPLS service with G8032 protection and at the same time
provides the benefits of using dot1q range SAPs. The user should ensure that the VPLS service is
a point-to-point service. This is achieved by configuring a VPLS service with an access dot1q
range SAP used at the customer handoff on one node in the ring and an access dot1q range SAP in
a customer handoff of a VPLS service on another node (that is, at the other end of the Epipe), such
that there are only two endpoints for the service in the network.
On the node where the service originates, in addition to the access dot1q range SAP, the service
needs to be configured with access-uplink SAPs on the two G.8032 ring ports. G.8032 mechanism
is used to for breaking the loop in the ring and VPLS service protection. The intermediate nodes
on the ring needs to use VPLS service with access-uplink SAPs on the ring ports and use the same
G.8032 instance for protection, as one is used for service protection on the originating node.
Configuration guidelines and restrictions
The VPLS service with dot1-range SAPs use svc-sap-type of dot1q-range and supports limited
functionality in comparison to a normal VPLS service, The following paragraph provide more
details of the feature functionality, configuration guidelines and restrictions:
• The user can define access dot1q range SAPs, which specifies a group of VLANs which
receive similar service treatment, that is, forwarding behavior, SAP ingress QoS treatment
and SAP (behavior similar to that available in Epipe service) and allows it to be
configured in a VPLS service.
→ On the node, where the service originates, in addition to the access dot1q range SAP,
the service should be configured with Q1.* SAPs on the two G.8032 ring ports. The
access or access-uplink Q1.*SAPs can be used, but the access-uplink SAPs are
recommended for use.The user cannot configure any other SAPs in the same VPLS
service.
→ There is no special configuration required on intermediate nodes, that is, the ring
nodes which do not terminate or originate the service. The nodes should be configured
for providing transit VPLS service and the VPLS service must use the same G8032
instance for protection as is used by the service on originating and terminating node.
To Next Page
Loading...
