Student Guide Student Guide Student Guide Student Guide: Educationservicescourseware

e d u c a t io n se rv ic e s c o u rse w a re
Enabling Metro-
Metro-E Services
with Junos Platforms: Part 3
Student Guide
Enabling Metro-E Services with Junos Platforms: Part 3
NOTE: Please note this Student Guide has been developed from an audio narration. Therefore it will have
conversational English. The purpose of this transcript is to help you follow the online presentation and may require
reference to it.
Slide 1
Build the Best
© 2016 Juniper Networks, Inc. All rights reserved. CONFIDENTIAL SOT-SPAD04C-ML5 www.juniper.net | 1
Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 2

Slide 2
Service Provider Access and

Aggregation Design
Best Practices
Enabling Metro-E Services with

Junos Platforms: Part 3
© 2016 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential
Welcome to Juniper Networks “Enabling Metro-E Services with Junos Platforms: Part 3” eLearning module.

Slide 3
Navigation
Throughout this module, you will find slides with valuable detailed information. You can stop any slide with the Pause
button to study the details. You can also read the notes by using the Notes tab. You can click the Feedback link at any
time to submit suggestions or corrections directly to the Juniper Networks eLearning team.

Slide 4
Course Objectives
After successfully completing this course, you will be

able to:
•Describe the Operation, Administration, and Maintenance
toolset and how it is used in the network
•Explore a representative deployment scenario as an
example of what is supported by the Juniper Carrier Ethernet
Services solution
After successfully completing this course, you will be able to:

• Describe the Operation, Administration, and Maintenance toolset and how it is used in the network; and
• Explore a representative deployment scenario as an example of what is supported by the Juniper Carrier Ethernet
Services (CES) solution.

Slide 5
Agenda: Enabling Metro-E Services with

Junos Platforms: Part 3
Operation, Administration, and Maintenance
Deployment Scenarios and Recommendations
This course consists of two sections. The two main sections are as follows:
• Operation, Administration, and Maintenance (OAM); and
• Deployment Scenarios and Recommendations.

Slide 6

Aggregation Design
Best Practices
OAM
OAM

Slide 7
Section Objectives
After successfully completing this section, you will be

able to:
•Discuss the use of available OAM tools
•Describe intrasegment and intersegment OAM
After successfully completing this section, you will be able to:

• Discuss the use of available OAM tools; and
• Describe intrasegment and intersegment OAM.

Slide 8
OAM
A toolset detecting and reporting connection failures, or
measurement of connection performance parameters
• Used within various layers of the protocol stack
• Includes general requirements for network management, including
FCAPS, service provisioning, and monitoring
The purpose of OAM tools is twofold:
• To determine the fault in the network
Customers might benefit from: • To isolate and diagnose faults so that
• A solution for basic FCAPS management corrective action can be taken
• A solution for Zero Touch Deployment
• A broad capability for network automation with scripting
• Configlets provided by Junos Space Network Management platform
• Network optimization with NorthStar software
• Service-level agreement management
• A comprehensive API for OSS/BSS integration provided by the Junos Space platform
OAM
Operation, Administration, and Maintenance (OAM) is a general term that refers to a toolset that can be used for
detecting and reporting connection failures or measurement of connection performance parameters. OAM was
originally used in the world of telephony and has since been adopted in packet-based networks. OAM mechanisms
are used within various layers of the protocol stack and are applied to a variety of different protocols.
In some cases, OAM requirements are formulated much broader than Ethernet OAM (E-OAM). It also includes
general requirements for network management—including fault, configuration, accounting, performance, and security
(FCAPS) network management, service provisioning and monitoring where Juniper does not have a well-established
story. Meanwhile, there are a few things that should be presented to customers in this area. As part of the Juniper
metro Ethernet solution, customers might benefit from:
• A solution for basic FCAPS management; a solution for Zero Touch Deployment;
• A broad capability for network automation with scripting;
• Configlets provided by the Junos Space Network Management platform;
• Network optimization with NorthStar software;
• Service-level agreement (SLA) management; and
• A comprehensive API for operations support systems/business support systems (OSS/BSS) integration provided
by the Junos Space platform.
The transport layer for OAM depends on Ethernet-based and MPLS-based OAM tools. The purpose of OAM tools is
twofold: to determine the fault in the network, and to isolate and diagnose faults so that corrective action can be taken.
For example, redirecting the traffic from a failed path to a backup path, and repairing any faults after they have been
isolated.
OAM tools and management entities can be deployed at various points in the transport network. A failure can be
defined in relation to the requirements, which might be a complete loss of connectivity, or partial loss, such as a one-
way failure. Also, the failure could be that connection quality drops below a certain threshold.
In this section, we discuss OAM for active monitoring of active paths in each segment, and across each segment, in
the network.

Slide 9
Ethernet OAM
Reference Architecture for the Ethernet OAM in Metro Area Networks
Small
Corporate AN1 (ACX) EVC 505 Corporate
Office EVC 505 Office
AN1 (ACX) VPLS
UNI A2 PE VPLS
Ethernet AN2 (ACX)
PE UNI B
with
G.8032v2
UNI A1 ERP
Corporate AN3 (ACX) Ethernet to VPLS H-VPLS
Office stitching point stitching point
E-LMI (evc 505) E-LMI (evc 505)
Y.1731 (loss, delay, jitter)
Service
Y.1731 (loss, delay, jitter)
802.1ag MD5
Connectivity
802.1ag Customer
MD3
802.1ag (PW data plane)
Provider
Transport 802.3ah 802.3ah 802.3ah
Ethernet OAM
As Ethernet emerged from being a LAN technology into a carrier-class technology, Ethernet OAM (E-OAM) has been
developed to ease the operations, administration, and maintenance of complex Ethernet service provider networks
and lower their operational expenditures. We will provide a high-level technical overview of E-OAM and define its main
functions—such as link fault management (LFM), connectivity fault management (CFM), and performance monitoring.
We will provide some examples of how E-OAM mechanisms can be deployed in the metro area network and how they
help to solve some particular problems. The diagram on this slide illustrates a reference architecture of the E-OAM
protocols in metro Ethernet networks.
The MX Series and the ACX Series routers used in the Juniper solution have full support for the Ethernet OAM
protocols and are compliant with the OAM architecture proposed by industry standards. An essential parameter of the
routing platforms used for establishing metro services is logical scale, which becomes crucial for metro provider edge
(PE) nodes located at the aggregation and metro edge segments. To enable scale, many of the OAM functions—such
as Bidirectional Forwarding Detection (BFD) and CFM—have been moved out from the Routing Engine of the system
and are supported by dedicated daemons running in the line cards of the routers. Thus, adding port density won’t
decrease a platform’s OAM capability.

Slide 10
Intrasegment OAM
OAM in the UAA Network
Access Pre-aggregation Aggregation Service Edge
UAN UAN AG3.1 PE1.1
1.2 1.1 AG1.1 AG1.3 AG2.1
BBE/ 3G DC
BE RNC
UAN Core Network
1.3 4G
IP/MPLS
EPC
AG1.2 AG1.4 AG2.2 AG3.2 PE1.2
IP/Internet
UAN UAN
1.4 1.5 Core IGP Domain
Connectivity for 802.1ag
L2 Services 802.1ag
802.1ag 802.1ag 802.1ag
Link-Fault 802.1ah 802.1ah
Physical
OSPF and IS-IS OAM BFD BFD BFD BFD Connectivity
The intrasegment
MPLS/RSVP Transport BFD BFD BFD BFD
of the transport
BGP-LU Transport Multi-hop BFD Multi-hop BFD Multi-hop BFD
network uses link
level OAM to detect
BGP-MP Service Level Multi-hop BFD Multi-hop BFD
failure within a
Layer 2 VPN Service Level 802.1ag segment
Intrasegment OAM
The intrasegment of the transport network uses link-level OAM to detect failure within a segment. Because all of the
links in the transport network are Ethernet, IP, or MPLS, you can use either CFM or BFD to monitor and measure the
network performance. Both CFM and BFD provide aggressive timers, which detect failure in less than a second.
BFD or CFM session connectivity verification can trigger RSVP traffic engineering or LDP failover. The CFM suite
provides advanced capabilities, such as packet loss and delay measurement, to determine the health of the link.
The diagram on this slide shows the use of CFM (IEEE standard 802.1ag) to check end-to-end data link layer OAM.
For completeness in this diagram, we have included LFM (standard 802.3ah) to show that you can use LFM when
your network includes copper links instead of optical links or when an ACX Series router is connected to a microwave
transmission system. In this scenario, LFM provides fast link failure detection, which is not provided by other
techniques. (Note that LFM is not verified as part of the solution.)
At the IGP, transport, and service levels, BFD is used for intrasegment OAM because it provides a single mechanism
for detection of forwarding plane-to-forwarding plane connectivity (including links, interfaces, tunnels, and so on). The
single mechanism is independent of media, routing protocol, and data protocol, and it provides fast convergence of
routing protocols—particularly on shared media (Ethernet)—detects one-way link failures, and does not require
changes to existing protocols.

Slide 11
Intersegment OAM
Intersegment OAM detects faults in the remote part of

the network to redirect traffic as soon as possible and
close to the source
• Multi-hop BFD is used to monitor remote BGP peers
• In the event of a BFD session failure, the alternate BGP peer is used
End-to-end OAM is used to detect the operational
capability of remote access devices
• The best way to do so is by using BFD over the LSP
• If the BFD session goes down, either the remote CSR has failed or a
path to the device through the transport network does not exist
• BFD over an LSP provides approximately sub-second failure
detection
Intersegment OAM
Intersegment OAM detects faults in the remote part of the network to redirect traffic as soon as possible and closer to
the source, using multi-hop BFD to monitor remote BGP peers. In the event of a BFD session failure, the alternate
BGP peer is used.
End-to-end OAM is used to detect the operational capability of remote access devices, and the best way to do so is by
using BFD over the label-switched path (LSP). If the BFD session goes down, either the remote cell site router (CSR)
has failed or a path to the device through the transport network does not exist. BFD over an LSP provides
approximately sub-second failure detection.

Slide 12
Section Summary
In this section, we:

•Discussed the use of available OAM tools
•Described intrasegment and intersegment OAM

• Discussed the use of available OAM tools; and
• Described intrasegment and intersegment OAM.

Slide 13
Learning Activity 1: Question 1
OAM tools serve which two purposes in the network?

(Choose two.)
A. Prevent faults in the network

B. Determine a fault has occurred
C. Isolate and diagnose faults
D. Proactively take action on a fault

Slide 14

Aggregation Design
Best Practices
Deployment Scenarios and

Recommendations
Deployment Scenarios and Recommendations

Slide 15
Section Objectives
After successfully completing this section, you will be

able to:
•Describe EP-Line deployment as a sample scenario
supported by Juniper Networks
•Explore four types of EP-Line deployment scenario examples
After successfully completing this section, you will be able to:

• Describe EP-Line deployment as a sample scenario supported by Juniper Networks; and
• Explore four types of EP-Line deployment scenario examples.

Slide 16
EP-Line Deployment Scenarios
EP-Line service can be originated or terminated on

any type of AN that leads to a number of scenarios
supported by Juniper’s CES solution for EP-Line
service
UNI A MX Series as MX Series as ACX Series as ACX Series as
UNI B VPLS AN Ethernet AN MPLS PW AN Ethernet AN
MX Series as VPLS AN n/a n/a n/a n/a
MX Series as Ethernet AN n/a Yes Yes Yes
ACX Series as MPLS PW AN n/a Yes Yes Yes
ACX Series as Ethernet AN n/a Yes Yes Yes
PW = pseudowire
n/a stands for Not Applicable for this type of service
EP-Line Deployment Scenarios
We will now describe some deployment scenarios. We will not cover every deployment scenario available in Juniper’s
solution. Instead, the scenarios described should provide enough information to construct other types of services. For
information on additional scenarios, refer to the latest Juniper documentation.
EP-Line service can be originated or terminated on any type of access node (AN)—MPLS AN, VPLS AN or Ethernet
AN—that leads to a number of scenarios supported by the Juniper Carrier Ethernet Services (CES) solution for EP-
Line service. The scenarios are summarized in the table shown on this slide.
We will explore the following four deployment scenarios:

• EP-Line between ANs in one Ethernet segment;
• EP-Line between two MPLS ANs;
• EP-Line between Ethernet AN and MPLS AN with stitching at the preaggregation router; and
• EP-Line between two Ethernet ANs located in different Ethernet segment connected over MPLS aggregation
network.

Slide 17
EP-Line with Native Ethernet Segment

Traffic Flow EP-Line Scenario with Ethernet Access Segment
Ethernet II EVC EP-Line Ethernet II

C-VLAN ALL - C-VLAN ALL
CoS 0-7 push S-VLAN 615 S-VLAN 615 pop S-VLAN 615 CoS 0-7
Map Map
Priority Tagged Ethernet II Ethernet II Ethernet II Priority Tagged
Untagged Access Segment Untagged
Tunnel or Do Do Not Tunnel
L2CP L2CP
Not Tunnel or Tunnel
OAM Tunnel S-VLAN OAM Tunnel
615
Carrier Ethernet Ring
or Hub-and-Spoke
AN 1 G.8032 Ring AN 2
UNI A Protection
UNI B
CPE
CPE
-
pop S-VLAN 615 S-VLAN 615 push S-VLAN 615
Ethernet II Ethernet II Ethernet II
Traffic Flow
EP-Line with Native Ethernet Segment
In the scenario illustrated on this slide, EP-Line service is provided between two customers’ locations connected to the
provider Ethernet access nodes—AN 1 and AN 2—in the same access segment. The following actions are taken to
forward traffic from UNI A to UNI B. The customer sends untagged, priority tagged, or C-VLAN tagged (802.1q)
Ethernet traffic from the customer premises equipment (CPE) to the provider access node’s UNI A—represented by
the solid line between the CPE and AN 1 on the left of the diagram. Ingress customer traffic is encapsulated at UNI A
into an 802.1q/802.1ad Ethernet frame with an outer S-VLAN tag (615) and goes into the bridge domain (BD)—
represented in the diagram with short orange pipes on each node in the ring—at the AN 1 node. Finally, traffic is
delivered to the AN 2 node over the Ethernet ring where AN 2 pops the outer tag and sends customer traffic over UNI
B to the CPE on the right. Both UNI A and UNI B have identical configurations.
There are two available traffic paths in the ring to reach UNI B from UNI A—represented by the solid orange line. To
avoid a Layer 2 loop in the Ethernet ring, the G.8032 protocol is used. Each AN in the ring should be configured within
the protection group. Protected links should be assigned in the network—represented by the dotted blue line in the
diagram—which stays blocked all the time until a link or node failure happens in the ring. EVC provides proper
tunneling of the customer OAM and Layer 2 Control Protocol (L2CP) traffic.

Slide 18
EP-Line with End-to-End MPLS PW

Traffic Flow EP-Line Scenario with End-to-End MPLS PW
Ethernet II EVC EP-LINE Ethernet II

C-VLAN ALL push PW Label PW Label PW Label pop PW Label C-VLAN ALL
CoS 0-7 - - - - CoS 0-7
Map Map
Priority Tagged Ethernet II Ethernet II Ethernet II Ethernet II Priority Tagged
Untagged Untagged
Access Pre-aggregation and Aggregation Access
Not Tunnel or Not Tunnel or
L2CP L2CP
Tunnel Tunnel
AG1.1 AG1.4
OAM Tunnel OAM Tunnel
AN 1 AN 2
Virtual-circuit-id 605
UNI A UNI B
CPE
IP/MPLS CPE
AG1.2 AG1.3
LDP Signaled PW
pop PW Label PW Label PW Label push PW Label
- - - -
Ethernet II Ethernet II Ethernet II Ethernet II
Traffic Flow
EP-Line with End-to-End MPLS PW
The diagram on this slide represents the second deployment scenario for EP-Line service provided to the customer
CPEs connected to the two MPLS nodes—AN 1 and AN 2 routers—which can belong to the same or different MPLS
access segments.
The following actions are taken to forward traffic from UNI A to UNI B. Customers send untagged, priority tagged, or
C-VLAN tagged (802.1q) Ethernet traffic from the CPE to the provider AN UNI A—represented by the solid line
between the CPE and AN 1.
Customer Ethernet traffic is encapsulated at ingress UNI A into MPLS pseudowire (PW) Type 5—encapsulation type
Ethernet—and tunneled over a seamless MPLS access and aggregation network to AN 2. The AN 2 node pops the
MPLS service label and sends Ethernet frames over UNI B to the CPE. Either BGP or LDP can be used to signal end-
to-end pseudowires between AN 1 and AN 2 nodes in the MAN. Our Universal Access and Aggregation (UAA)
solution uses LDP as part of the verification process.
In this deployment scenario, EVC provides proper tunneling of the customer OAM and L2CP. However, when using
ACX Series routers as an MPLS node, additional consideration regarding customer L2CP traffic tunneling should be
taken into account. If both nodes belong to the same MPLS access segment, then additional consideration should be
made regarding the path of the pseudowire between two nodes. There are two available options, as follows:
• Pseudowire takes the shortest path between two ANs (fully meshed LSP topology); or
• Pseudowire takes the path through the AG router (hub-and-spoke LSP topology).
The choice between these two options is defined by the intra-LSP topology—a full-mesh or hub-and-spoke LSP
topology, with AG routers as the hub and AN routers as spokes.

Slide 19
EP-Line with Ethernet to MPLS PW Stitching

Traffic Flow EP-Line Scenario with Ethernet To MPLS PW Stitching

C-VLAN ALL - push PW Label pop PW Label C-VLAN ALL
CoS 0-7 pushS-VLAN 615 S-VLAN 615 S-VLAN 615 pop S-VLAN 615 CoS 0-7
Map Map
Priority Tagged Ethernet II Ethernet II Ethernet II Ethernet II Priority Tagged
Untagged Untagged
Do Not Tunnel Do Not Tunnel
L2CP L2CP
or Tunnel or Tunnel
S-VLAN AG1.1
OAM Tunnel 615 OAM Tunnel
CE20-615-VPLS
VPLS Instance
AN 1 AN 2
IP/MPLS
UNI A UNI B
CPE
CPE
or Hub-and-Spoke AG1.2
G.8032 Ring
Protection LDP Signaled PW
- pop PW Label push PW Label
pop S-VLAN 615 S-VLAN 615 S-VLAN 615 push S-VLAN 615
Ethernet II Ethernet II Ethernet II Ethernet II
Traffic Flow
EP-LINE with Ethernet to MPLS PW Stitching
The diagram on this slide represents a third deployment scenario where the AN 1 router belongs to the Layer 2
Ethernet access segment and the AN 2 router belongs to the MPLS Layer 2 access segment.
The following actions are taken to forward traffic from UNI A to UNI B. Ingress customer traffic is encapsulated at UNI
A into an Ethernet 802.1q/802.1ad frame with an outer S-VLAN tag (615) and goes into the BD (represented on the
diagram with short orange pipes on each Ethernet AN in the ring) at the AN 1 node. Then traffic is delivered to the pre-
aggregation router—AG1.1 or AG1.2 router in our example—over the Ethernet ring where it is terminated into VPLS—
virtual-switch routing instance CE20-615-VPLS—which is configured on both AG1.1 and AG1.2. VPLS provides for
stitching the Ethernet access segment and LDP-signaled pseudowires of Type 4 encapsulation from MPLS access
node AN 2. Finally, traffic is delivered to AN 2, which pops the MPLS service label and the outer VLAN tag, and sends
customer traffic over UNI B to the CPE on the right.
There are two available paths for traffic from UNI A to reach the pre-aggregation routers—represented by the orange
line in the diagram. To avoid Layer 2 loops and provide rapid failure detection and forwarding path switchover in the
Ethernet ring, the G.8032 protocol is used. Each AN in the ring, as well as the pre-aggregation routers’ access facing
interfaces, should be configured with protection groups. A protected link should be configured in the network,
represented by the dotted blue line in the diagram, which stays blocked all the time until a link or node failure happens
in the ring.
To provide resiliency in the MPLS segment, an active/backup pair of MPLS pseudowires is established from node AN
2 to AG1.1 and AG1.2, respectively (shown on the slide diagram as virtual circuit ID 11615, the dashed line, for the
backup pseudowire, and as virtual circuit ID 12615, the solid line, for the active pseudowire).
The EVC provides proper tunneling of the customer OAM traffic. However, the UAA solution does not support other
L2CP protocol tunneling for this deployment scenario. Only the No tunnel option is available for L2CP traffic.

Slide 20
EP-Line with Ethernet to VPLS Termination

Traffic Flow EP-Line Deployment Scenario with Ethernet To VPLS Stitching

C-VLAN ALL - push VPLS Label pop VPLS Label pop VPLS Label C-VLAN ALL
CoS 0-7 push S-VLAN 615 S-VLAN 615 S-VLAN 615 S-VLAN 615 pop S-VLAN 615 CoS 0-7
Map Map
Priority Tagged Ethernet II Ethernet II Ethernet II Ethernet II Ethernet II Priority Tagged
Untagged Untagged
Do Not Tunnel Do Not Tunnel
L2CP L2CP
or Tunnel or Tunnel
S-VLAN AG1.1 AG1.3
OAM Tunnel 615 VPLS Instance OAM Tunnel
CE20-615-VPLS
AN 1 AN 2
UNI A UNI B
CPE
IP/MPLS CPE
or Hub-and-Spoke AG1.2 AG1.4
G.8032 Ring BGP or LDP
Protection Signaled VPLS
- pop PW Label PW Label -
pop S-VLAN 615 S-VLAN 615 S-VLAN 615 S-VLAN 615 push S-VLAN 615
Ethernet II Ethernet II Ethernet II Ethernet II Ethernet II
Traffic Flow
EP-Line with Ethernet to VPLS Termination
In this fourth deployment scenario for EP-Line services (illustrated on this slide), AN routers belong to different Layer 2
Ethernet access segments connected through the MPLS-enabled metro aggregation/core segments.
The following actions are taken to forward traffic from UNI A to UNI B. Ingress customer traffic is encapsulated at UNI
A into an Ethernet 802.1q/802.1ad frame with an outer S-VLAN tag (615) and goes into the BD (represented in the
diagram with short orange pipes on each Ethernet AN in the ring) at the AN 1 node. Then traffic is delivered to the pre-
aggregation router—AG1.1 or AG1.2 router—over the Ethernet ring where it is terminated into VPLS (virtual-switch
routing instance CE20-615-VPLS, represented by the solid blue pipes and lines in the middle of the diagram), which is
configured on the pre-aggregation routers at both ends of the MPLS segment—AG1.1, AG1.2, AG1.3, and AG1.4.
VPLS provides the stitching for the Ethernet access segment at both ends of the MPLS segment.
From the AG1.1 or AG1.2 router, the customer Ethernet frames are encapsulated with a VPLS service label and are
delivered to the other end of the MPLS segment—the AG1.3 or AG1.4 router. The exact traffic forwarding path is not
predetermined and defined by the MAC learning mechanism in the VPLS bridge domain. The AG1.3 or AG1.4 router
pops the MPLS service label and sends the traffic into the Ethernet access segment on the right with the same outer
S-VLAN tag (615) as in the original AN 1 node access segment. Finally, traffic is delivered over the Ethernet access
ring to the AN 2 node, which pops the outer S-VLAN tag and sends traffic to the CPE.
There are two available traffic paths in each Ethernet access segment for traffic from an AN to reach the pre-
aggregation routers—these paths are represented by the solid orange line in the diagram. To avoid Layer 2 loops and
provide rapid failure detection and forwarding path switchover in the Ethernet ring, the G.8032 protocol is used. Each
AN in the ring, as well as the pre-aggregation routers’ access facing interfaces, should be configured within a
protection group. A protected link should be assigned in the network, represented by the dotted blue lines in the
diagram, which stays blocked until a link or node failure happens in the ring.
Also, as in the previously discussed scenario, the EVC provides proper tunneling of the customer OAM traffic.
However, the UAA solution does not support other L2CP protocol tunneling for this deployment scenario. Only the No
tunnel option is available for L2CP traffic.

Slide 21
Section Summary

•Described EP-Line deployment as a sample scenario
supported by Juniper Networks
•Explored four types of EP-Line deployment scenario
examples

• Described EP-Line deployment as a sample scenario supported by Juniper Networks; and
• Explored four types of EP-Line deployment scenario examples.

Slide 22
True or false: An EP-Line service can be originated or

terminated on any type of access node.
A. True
B. False

Slide 23
Course Summary
In this course, we:

•Described the Operation, Administration, and Maintenance
toolset and how it is used in the network
•Explored a representative deployment scenario as an
example of what is supported by the Juniper Carrier Ethernet
Services solution
In this course, we:

• Described the Operation, Administration, and Maintenance toolset and how it is used in the network; and
• Explored a representative deployment scenario as an example of what is supported by the Juniper Carrier
Ethernet Services solution.

Slide 24
Additional Resources
Education Services training classes

•http://www.juniper.net/training/technical_education/
Juniper Networks Certification Program Web site
•www.juniper.net/certification
Juniper Networks documentation and white papers
•www.juniper.net/techpubs
To submit errata or for general questions
•elearning@juniper.net
For additional resources or to contact the Juniper Networks eLearning team, click the links on the screen.

Slide 25
Evaluation and Survey
You have reached the end of this Juniper Networks

eLearning module
You should now return to your Juniper Learning
Center to take the assessment and the student
survey
•After successfully completing the assessment, you will earn
credits that will be recognized through certificates and non-
monetary rewards
•The survey will allow you to give feedback on the quality and
usefulness of the course
You have reached the end of this Juniper Networks eLearning module. You should now return to your Juniper
Learning Center to take the assessment and the student survey. After successfully completing the assessment, you
will earn credits that will be recognized through certificates and non-monetary rewards. The survey will allow you to
give feedback on the quality and usefulness of the course.

Slide 26
Copyright © 2016 Juniper Networks, Inc.
All rights reserved. JUNIPER NETWORKS, the Juniper Networks logo,

JUNOS, QFABRIC, NETSCREEN, and SCREENOS are registered
trademarks of Juniper Networks, Inc. in the United States and other
countries. All other trademarks, service marks, registered
trademarks, or registered service marks are the property of their
respective owners.
Copyright © 2016 Juniper Networks, Inc.
All rights reserved. JUNIPER NETWORKS, the Juniper Networks logo, JUNOS, QFABRIC, NETSCREEN, and
SCREENOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective
owners. Juniper Networks reserves the right to change, modify, transfer or otherwise revise this publication without
notice.

Slide 27
CONFIDENTIAL

e d u c a t io n se r v ic e s c o u rse w a re
Co rp o rat e and Sales Head q uart ers APAC Head q uart ers EM EA Head q ua rt ers Copyright 20 10 Junip er Net w orks, Inc.
All right s reserved. Junip er Net w o rks,
Junip er Net w orks, Inc. Junip er Net w orks ( Ho ng Kong) Junip er Net w orks Ireland t he Junip er Net w orks lo go, Juno s,
119 4 Nort h Mat hild a Avenue 26 / F, Cit yp laza One Airsid e Business Park Net Screen, and ScreenOS are regist ered
Sunnyvale, CA 9 4 0 8 9 USA 1111 King’s Ro ad Sw ord s, Co unt y Dub l in, Ireland t rad em arks of Junip er Net w o rks, Inc. in
Phone: 8 8 8 .JUNIPER Taikoo Shing, Ho ng Kong Phone: 35 .31.8 9 0 3.6 0 0 t he Unit ed St at es and ot her count ries.
( 8 8 8 .5 8 6 .4737) Phone: 8 5 2.2332.36 36 EMEA Sales: 0 0 8 0 0 .4 58 6 .4737 All o t her t rad em arks, service m arks,
or 4 0 8 .74 5 .20 0 0 Fax: 8 5 2.2574 .78 0 3 Fax: 35 .31.8 9 0 3.6 0 1 regist ered m arks, or regist ered service
Fax: 4 0 8 .74 5.210 0 m arks are t he p ro p ert y of t heir
w w w.junip er.net resp ect ive ow ners. Junip er Net w orks
assum es no resp o nsib ilit y f or any
inaccuracies in t his d o cum ent . Junip er
Net w orks reserves t he right t o change,
m o d if y, t ransf er, o r ot herw ise revise t his
p ub l icat ion w it hout not ice.

Student Guide Student Guide Student Guide Student Guide: Educationservicescourseware

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Student Guide Student Guide Student Guide Student Guide: Educationservicescourseware

Uploaded by

Copyright:

Available Formats

e d u c a t io n se rv ic e s c o u rse w a re

Build the Best

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 2

Service Provider Access and

Enabling Metro-E Services with

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 3

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 4

After successfully completing this course, you will be

After successfully completing this course, you will be able to:

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 5

Agenda: Enabling Metro-E Services with

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 6

Service Provider Access and

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 7

After successfully completing this section, you will be

After successfully completing this section, you will be able to:

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 8

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 9

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 10

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 11

Intersegment OAM detects faults in the remote part of

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 12

In this section, we:

In this section, we:

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 13

Learning Activity 1: Question 1

OAM tools serve which two purposes in the network?

A. Prevent faults in the network

Learning Activity 1: Question 1

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 14

Service Provider Access and

Deployment Scenarios and

Deployment Scenarios and Recommendations

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 15

After successfully completing this section, you will be

After successfully completing this section, you will be able to:

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 16

EP-Line Deployment Scenarios

EP-Line service can be originated or terminated on

EP-Line Deployment Scenarios

We will explore the following four deployment scenarios:

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 17

EP-Line with Native Ethernet Segment

Ethernet II EVC EP-Line Ethernet II

EP-Line with Native Ethernet Segment

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 18

EP-Line with End-to-End MPLS PW

Ethernet II EVC EP-LINE Ethernet II

EP-Line with End-to-End MPLS PW

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 19

EP-Line with Ethernet to MPLS PW Stitching

Ethernet II EVC EP-LINE Ethernet II

EP-LINE with Ethernet to MPLS PW Stitching

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 20

EP-Line with Ethernet to VPLS Termination

Ethernet II EVC EP-LINE Ethernet II

EP-Line with Ethernet to VPLS Termination

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 21

In this section, we:

In this section, we:

Course SOT-SPAD04C-ML5 © Juniper Networks, Inc. 22

Learning Activity 2: Question 1

True or false: An EP-Line service can be originated or