Jncie-Sp (Service Provider) : Lab Preparation Workbook v2.0
Jncie-Sp (Service Provider) : Lab Preparation Workbook v2.0
iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
JNCIE-SP
(Service Provider)
Lab preparation workbook
v2.0
JNCIE-SP workbook:
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
Maxim lives in Russia and speaks Russian and English. He started his networking career in 1999.
Throughout the years Maxim has designed and implemented several large scale networks for
enterprise and service provider customers. Over the years he has developed several high quality
courseware materials for industry leading networking vendors. Maxim has the following
certifications: JNCIE, JNCIP-ENT, JNCIS-SEC, Nortel NNCSS. For technology Max values efficiency and
pragmatic design. When Max is not at work he likes to spend time with his family. Max enjoys being
outside in the nature and loves to travel and exploring the world.
Ivan Ivanov
Ivan van lives in East Europe country of Bulgaria. He has more than 10 years experience with IP
technologies, working at several Internet Service Providers, big enterprise companies and
International system integrators. Throughout his career, Ivan gained extensive experience designing,
implementing and supporting IP networks based mostly on Juniper Networks and Cisco Systems
solutions and devices. Ivan worked on various international projects, designing, securing and
implementing MPLS/IP backbone for multinational mobile operators. Ivan has the following
certificates: JNCIE, JNCIP-SEC and various Cisco certificates.
JNCIE-SP workbook:
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
Jörg Buesink
Jörg lives in the Netherlands and brings more than 15 years of experience in the IT and networking
industry. He worked for several large ISPs / service providers in the role of technical consultant,
designer and network architect. He has extensive experience in network implementation, design and
architecture. Jörg is quadruple JNCIE certified (JNCIE-DC#007, JNCIE-ENT#21, JNCIE-SP#284 and
JNCIE-SEC#30) as well as triple CCIE#15032 (Routing/ Switching, Service provider and Security), Cisco
CCDE#20110002, Huawei HCIE#2188 Routing and Switching certified.
JNCIE-SP workbook:
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
General information
Rack rental service
Did you know that this workbook can be used in combination with iNETZEROs JNCIE rack rental
service? Take a look on our website for more information www.inetzero.com
Target audience
This workbook is developed for experienced network engineers who are preparing for the Juniper
Networks JNCIE-SP lab exam. Although not required it is highly recommended that you have passed
the JNCIS-SP and JNCIP-SP written exams before you start using this workbook. iNET ZERO’s JNCIE-SP
preparation workbook is developed in such a way that we expect you to have theoretical knowledge
about the JNCIE-SP lab exam blueprint topics (JNCIP-SP certified or working towards this
certification). For example, in this workbook we will not explain what rib-groups, LSP’s or Multicast
VPNs are. What we will do is test if you are able to configure all these technologies based on certain
requirements and understand how they interact in a typical SP environment.
Topology diagrams
In the chapters you will find several topology diagrams in small format. In the appendix of this
workbook you will find larger versions of the topology diagrams for better readability. We
recommend to print the topology diagrams.
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
Table of Contents
General information ................................................................................................................................ 5
Rack rental service .............................................................................................................................. 5
Target audience ................................................................................................................................... 5
How to use this workbook ................................................................................................................... 5
Topology diagrams .............................................................................................................................. 5
iNET ZERO support .............................................................................................................................. 5
Exam strategy ...................................................................................................................................... 6
JNCIE Hall of Fame ............................................................................................................................... 8
Workbook and configuration file updates .......................................................................................... 8
Chapter One: General System Features ................................................................................................ 14
Task 1. Initial System Settings ........................................................................................................... 15
Task 2. SNMP Configuration .............................................................................................................. 18
Task 3. Firewall Filters ....................................................................................................................... 19
Task 4. Interface Configuration ......................................................................................................... 20
Task 5. Scripting ................................................................................................................................. 22
Chapter Two: IGP Configuration and Troubleshooting ......................................................................... 23
Task 1. OSPF Troubleshooting ........................................................................................................... 23
Task 2. ISIS Troubleshooting .............................................................................................................. 25
Task 3. IGP Rollout ............................................................................................................................. 28
Chapter Three: BGP and Routing Policy ................................................................................................ 32
Task 1. IBGP and Confederation ........................................................................................................ 32
Task 2. EBGP Configuration ............................................................................................................... 33
Task 3. Routing Policies ..................................................................................................................... 35
Task 4. IBGP and Route Reflection .................................................................................................... 36
Chapter Four: MPLS Configuration ........................................................................................................ 38
Task 1. LDP Configuration ................................................................................................................. 38
Task 2. RSVP Configuration ............................................................................................................... 39
Task 3. RSVP Protection ..................................................................................................................... 43
Task 4. IPv6 Tunneling with 6PE ........................................................................................................ 44
Chapter Five: L3VPN Configuration ....................................................................................................... 45 JNCIE-SP workbook: General information
Task 1. L3VPN Configuration ............................................................................................................. 45
Task 2. Multicast in L3VPN ................................................................................................................ 48
Task 3. IPv6 Tunneling with 6VPE ...................................................................................................... 49
Chapter Six: L2VPN and VPLS Configuration ......................................................................................... 50
Task 1. L2VPN Configuration ............................................................................................................. 50
Task 2. VPLS Configuration ................................................................................................................ 52
Chapter Seven: Inter-provider VPN Configuration ................................................................................ 54
Task 1. Inter-provider VPN Option B ................................................................................................. 54
Task 2. Inter-provider VPN Option C ................................................................................................. 55
Chapter Eight: Class of Service .............................................................................................................. 56
Task 1. Forwarding Classes, Queues and Schedulers ........................................................................ 56
Task 2. Classification, Policing and Marking ...................................................................................... 58 9
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
45
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
5) Customer C1 has some backdoor OSPF connections but prefers that your MPLS network
would be used for traffic forwarding between the customer sites.
6) Make sure that your MPLS network can be used as a backup path between CE1-2 and CE1-3.
7) Make sure that once customer C1 disables its backdoor connections any of the R3 or R4 PE
failure will not result in any of the customer sites become isolated.
8) Customer C2 requires that the customer site S1 is used as a central transit site for all traffic
exchanges among all the customer sites in a hub-and-spoke fashion.
9) Make sure that if a route is originated in customer C2 site S1 or S2, it is never advertised back
to the same site.
10) Make sure that PE-CE link subnets in customer C2 VPN are advertised to the customer
remote VPN sites.
11) Make sure that all PE routers receive only the routes with those targets that they specifically
request for.
12) Allow local communication between customer C1 site S2 and customer C2 site S2 at R4.
Make sure that the routes exchanged between the local VRFs are not advertised to any of
the remote PE routers.
13) Customer C1 must be provided with Internet access at the customer site S2 using single
customer-facing interface. Make sure that any of the R3 or R4 failure will not have customer
C1 site S2 isolated from the Internet.
NOTE: The customer IP ranges are assumed to be globally routable or NATted outside of your
network.
14) Customer C2 must be provided with Internet access at the customer site S1, using a
dedicated interface i9 at both R1 and R2 routers. All other customer sites should be able to
reach the Internet via the site S1.
47
http://www.inetzero.com - Copyright 2018 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute - SteganoID=ON
1292 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
The external devices (CE and peers) are virtualized on the VR-device. Use only the
interfaces and VLANs on the diagram for connectivity between the routers.
AS 5673.873
BGP
AS 87.109
U1 U2 VPNB-CE1 Src1 VPNA-CE1 AS iBG
64 P
99
9
Rsv1
GE-0/0/5.1101
GE-0/0/5.2002 GE-0/0/5.2003
GE-0/0/5.2001 GE-0/0/5.110
BGP GE-0/0/5.101 VPNA-CE2
AS 789.12
P1 GE-0/0/5.1102
R3 GE-0/0/4.35 R5 GE-0/0/5.102
GE
OSPFv2 -0/
GE-0/0/5.2012 0/5 OSPF
GE-0/0/4.37 OSPFv3 ZE .58
ON GE-0/0/4.59
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
BR
GE-0/0/4.56
GE-0/0/5.111
GE-0/0/2
GE-0/0/1
R7 Area 50 R8 VPNB-CE2
GE-0/0/5.200 GE-0/0/4.45 GOLD
RIP
GE-0/0/4.47 RR 68 Area 8
DC-1
/ 4.
GE-0/0/4.49 /0
-0 GE-0/0/3.3002
GE
GE-0/0/5.200
R4 GE-0/0/4.46 R6
SILVER GE-0/0/3.3002
GE-0/0/5.1103 VPLS-2
GE Area 0 6
-0/ 4.1
0/4 /0/ GE-0/0/5.2004
GE-0/0/4.14
GE-0/0/4.26
Rsv2
GE-0/0/5.2021 .24 E-0
SILVER
G
GOLD
BRO
N ZE NZ
BRO E U3
OSPFv2
C1 OSPFv3 BGP
AS 9687
R1 GE-0/0/4.12 R2
BGP
GOLD
AS 65457
GE-0/0/5.112 GE-0/0/3
GE-0/0/3.3001 GE-0/0/5.2022
GE-0/0/5.103 GE-0/0/5.104
ISP1
BGP
AS 4356 BGP
AS65456
Physical Diagram
The logical diagram shows all information needed for configuring the logical connectivity between
the devices.
1292
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1294 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
1) SSH access is preconfigured as part of the initial configuration on all routers. Limit
the SSH connections to 2 at a time and no more than 2 connection attempts per
minute.
a. All devices.
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
RACK RENTAL NOTE: SSH is already configured as part of the initial configuration with
user root allowed to login. Please, do not change it, as it is required by iNETZERO rack
rental service.
Below two configuration lines are required to successfully complete the first task.
[edit]
lab@R1# set system services ssh connection-limit 2
[edit]
lab@R1# set system services ssh rate-limit 2
2) Enable NETCONF protocol over SSH using the standard port – TCP 830.
a. All devices.
NETCONF provides mechanisms to install, manipulate, and delete the configuration of
network devices. After enabling SSH on JUNOS devices, NETCONF is enabled
automatically accepting connections on the default SSH port 22. The task asks for
enabling NETCONF over the standard port 830 defined by RFC4742. In JUNOS, this is done
when you add ssh option under the netconf service.
[edit]
lab@R1# set system services netconf ssh
1294
Below is excerpt from the system connection table on router R1 after committing the
change.
[edit]
lab@R1# run show system connections
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1295 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
a. All devices.
[edit]
lab@R1# set snmp interface fxp0.0
[edit]
lab@R1# set snmp community superlab clients 10.10.10.1/32
[edit]
lab@R1# set routing-options static route 10.10.10.1/32 next-hop
10.10.1.200
[edit]
lab@R1# set system backup-router 10.10.1.200
[edit]
lab@R1# set system backup-router destination 10.10.10.1/32
Solution - Task 1.2: Centralized authentication management
JUNOS provides three different methods for user account authentication, authorization
and accounting. Those are the local database, using a RADIUS server and using a TACACS+
server. This Task requires configuring the devices to communicate successfully with a
TACACS+ server.
HelloInterval 9(second)
Address 10.50.0.9
ActiveResv 2, PreemptionCnt 0, Update threshold 10%
Subscription 100%,
bc0 = ct0, StaticBW 300Mbps
ct0: StaticBW 300Mbps, AvailableBW 300Mbps
MaxAvailableBW 300Mbps = (bc0*subscription)
ReservedBW [0] 0bps[1] 0bps[2] 0bps[3] 0bps[4] 0bps[5] 0bps[6] 0bps[7] 0bps
Protection: On, Bypass: 1, LSP: 1, Protected LSP: 1, Unprotected LSP: 0
1 Dec 3 11:56:46 New bypass to-r6
Bypass: to-r6, State: Up, Type: LP, LSP: 1, Backup: 0
4 Dec 3 11:56:46 Record Route: 10.50.0.2 10.50.0.18
3 Dec 3 11:56:46 Up
2 Dec 3 11:56:46 CSPF: computation result accepted
1 Dec 3 11:56:46 Originate Call
Solution - Task 4.2: MPLS and LDP configuration
5) Assume that R8 supports only LDP protocol. Configure R5 and R6 to provide MPLS
transport gateway functionality to the rest of network for R8. CEs attached to R8
should be able to exchange labeled packets with the CEs behind R1 and R2.
The task mentions that router R8 does not support RSVP. In order to enable services to be
deployed between router R8 and routers R1 and R2, you have to configure R5 and R6 to
transport LDP traffic in RSVP signaled LSP. You have to configure LDP targeted sessions
between routers R1, R2, R5 and R6.
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
a. R1
In JUNOS configuring LDP over RSVP can be done by enabling ldp-tunneling for the
RSVP LSPs connecting the two routers configured for LDP. Targeted LDP sessions are
established between the Loopback IP addresses.
[edit]
lab@R1# set protocols ldp interface lo0.0
[edit]
lab@R1# set protocols mpls label-switched-path r1-to-r5 ldp-tunneling
[edit]
lab@R1# set protocols mpls label-switched-path r1-to-r6 ldp-tunneling
b. R2
[edit]
lab@R2# set protocols ldp interface lo0.0
[edit]
lab@R2# set protocols mpls label-switched-path r2-to-r5 ldp-tunneling
[edit]
lab@R2# set protocols mpls label-switched-path r2-to-r6 ldp-tunneling
c. R5
Routers R5, R6 with R8 establish direct LDP sessions over the logical interface between 1413
them.
[edit]
lab@R5# set protocols ldp interface ge-0/0/4.58
[edit]
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1414 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R5# set protocols mpls label-switched-path r5-to-r1 ldp-tunneling
[edit]
lab@R5# set protocols mpls label-switched-path r5-to-r2 ldp-tunneling
d. R6
[edit]
lab@R6# set protocols ldp interface ge-0/0/4.68
[edit]
lab@R6# set protocols ldp interface lo0.0
[edit]
lab@R6# set protocols mpls label-switched-path r6-to-r1 ldp-tunneling
[edit]
lab@R6# set protocols mpls label-switched-path r6-to-r2 ldp-tunneling
e. R8
[edit]
lab@R8# set protocols ldp interface ge-0/0/4.58
[edit]
lab@R8# set protocols ldp interface ge-0/0/4.68
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
Enabling LDP on the Loopback interface on R8 is needed to establish targeted sessions to
routers R1 and R2.
[edit]
lab@R8# set protocols ldp interface lo0.0
[edit]
lab@R8# run show ldp neighbor
Address Interface Label space ID Hold time
10.50.250.1 lo0.0 10.50.250.1:0 38
10.50.250.2 lo0.0 10.50.250.2:0 43
10.50.250.6 lo0.0 10.50.250.6:0 42
10.50.0.49 ge-0/0/4.58 10.50.250.5:0 12
10.50.0.53 ge-0/0/4.68 10.50.250.6:0 14
[edit]
lab@R8# run show ldp database
Input label database, 10.50.250.8:0--10.50.250.1:0 1414
Labels received: 5
Label
3
Prefix
10.50.250.1/32
299778
299776
10.50.250.5/32
10.50.250.6/32
299783 10.50.250.8/32
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1415 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
[edit]
lab@R8# run show route table inet.3
[edit]
lab@R1# run show ldp interface
Interface Label space ID Nbr count Next hello
lo0.0 10.50.250.1:0 2 0
[edit]
lab@R1# run show ldp neighbor
Address Interface Label space ID Hold time
10.50.250.5 lo0.0 10.50.250.5:0 31
10.50.250.6 lo0.0 10.50.250.6:0 42
10.50.250.8 lo0.0 10.50.250.8:0 44
[edit]
lab@R1# run show ldp database
Input label database, 10.50.250.1:0--10.50.250.5:0
Labels received: 4 1415
Label Prefix
299777
299776
10.50.250.1/32
10.50.250.2/32
299781
3 10.50.250.5/32
10.50.250.8/32
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1435 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
Router R5 is advertising the routes from the other three sites to the VPNA-CE1. Two
prefixes advertised by CE2 received from the MPLS core, are advertised as internal
because of the independent-domain configuration.
[edit]
lab@R5# run show route advertising-protocol bgp 192.168.15.5
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
Similarly, router R8 receives two routes from VPNA-CE2 and advertises the routes for the
other VPNA sites.
[edit]
lab@R8# run show bgp summary
Groups: 3 Peers: 3 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0
511 511 0 0 0 0
inet6.0
16 0 0 0 0 0
bgp.l3vpn.0
30 30 0 0 0 0
bgp.l2vpn.0
2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
192.168.15.9 64999 24 35 0 0 9:40
Establ
VPNA.inet.0: 2/2/2/0
[edit]
lab@R8# run show route table VPNA.inet.0
[edit]
lab@R8# run show bgp summary
Groups: 3 Peers: 3 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0
511 511 0 0 0 0
inet6.0
16 0 0 0 0 0
bgp.l3vpn.0
30 30 0 0 0 0
bgp.l2vpn.0
2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn
State|#Active/Received/Accepted/Damped...
172.17.0.6 65100 448 480 0 1 3:26:03
Establ
VPNB.inet.0: 5/5/5/0
[edit]
lab@R8# run show route receive-protocol bgp 172.17.0.6
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
* 172.17.21.0/24 172.17.0.6 65100 I
* 172.17.22.0/24 172.17.0.6 65100 I
* 172.17.23.0/24 172.17.0.6 65100 I
* 172.17.24.0/24 172.17.0.6 65100 I
* 172.17.25.0/24 172.17.0.6
5) You have to provide connectivity to and from AS 87.109 for site CE.. Make sure
you do not advertise additional routes to the other VPN sites.
a. R5
[edit]
lab@R5# set policy-options policy-statement VPNB-export.target term
filter.AS87.109 from protocol bgp
[edit]
lab@R5# set policy-options policy-statement VPNB-export.target term
filter.AS87.109 from as-path 87.109.origin
[edit]
lab@R5# set policy-options policy-statement VPNB-export.target term
filter.AS87.109 then reject
The configuration lines below are explicitly advertising the routes received from AS
87.109 to CE1.
[edit] 1445
lab@R5# set policy-options policy-statement to.VPNB-CE1 term accept.AS87.109 from
protocol bgp
[edit]
lab@R5# set policy-options policy-statement to.VPNB-CE1 term accept.AS87.109 from
as-path 87.109.origin
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1447 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R5# set routing-options interface-routes rib-group inet local-interfaces
The rib-group bgp.to.VPNB is associated to the internal BGP group. You might make the
mistake here and apply the rib-group to the external BGP group to peer U2. Although that
will accomplish what is asked, you have to take into account that the connection to U2
could fail.
[edit]
lab@R5# set protocols bgp group internal family inet unicast rib-group
bgp.to.VPNB
[edit]
lab@R5# set routing-instances VPNB routing-options interface-routes rib-group
inet local-interfaces
[edit]
lab@R5# set routing-instances VPNB protocols bgp group VPNB-CE1 family inet
unicast rib-group VPNB.to.bgp
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
VPNB.inet.0: 492 destinations, 745 routes (491 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
Conversely, the routes received from VPNB-CE1 are copied to master routing table.
[edit]
lab@R5# run show route receive-protocol bgp 172.17.0.2
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1448 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
The AS 87.109 routes are not sent to router R8, hence they are not advertised to VPNB-
CE2.
[edit]
lab@R8# run show route advertising-protocol bgp 172.17.0.6
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
VPNB.inet.0: 28 destinations, 28 routes (28 active, 0 holddown, 0 hidden)
Prefix Nexthop MED Lclpref AS path
* 10.50.0.32/30 Self I
* 10.50.0.44/30 Self I
* 10.50.0.48/30 Self I
* 10.50.0.84/30 Self I
* 10.50.0.100/30 Self I
* 10.50.250.5/32 Self I
* 15.16.18.84/30 Self I
* 172.16.5.4/30 Self 4356 I
* 172.17.0.0/30 Self I
* 172.17.1.0/24 Self 5673.873 I
* 172.17.2.0/24 Self 5673.873 I
* 172.17.3.0/24 Self 5673.873 I
* 172.17.4.0/24 Self 5673.873 I
* 172.17.5.0/24 Self 5673.873 I
* 172.17.6.0/24 Self 5673.873 I
6) Since site CE3 is connected to 3rd party provider ISP1, you must extend the VPNB
using an inter-provider method that will provide you with a way to filter routes
received from ISP-1 based on target-communities. Do not use routing policy on R1
for providing connectivity to CE3. The remote PE is using route-target community
target:4356:500.
Three options can be used to extend a L3VPN via other provider network.
• Option A – within each AS, the routes are announced by the MP-BGP 1448
protocol used for all L3VPNs. On the AS border routers a VRF for each
Inter-AS L3VPN is configured and a pure IP connection is established
between the ASBRs. This is the least scalable solution and does not fit in
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1449 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
the requirements of the Task. Because, the routes exchanged between the
ASBRs are not vpnv4 routes, they do not carry route-target communities.
• Option B – All routes exchanged should be stored locally on ASBR. Since,
the exchanged routes are vpnv4 carying VPN labels with route-target
communities, there is a way to further filter or manipulate the VPN routes.
• Option C – provides the most scalable method, using Labeled BGP sessions
to create an MPLS path end-to-end. On top of that, a multihop external
MP-BGP session exchanges the vpnv4 routes between the ASs. Since, the
ASBRs do not have visibility of the overlay MP-BGP routes, there is not way
to control the exchange of the routes.
From the three methods the Option B is one that should be used to accomplish the Task.
a. R1
First, the interface between the two networks must be configured. Inter-AS option B
exchanges labeled routes between the ASBRs, this means the interconnect interfaces
must be also configured with family mpls.
[edit]
lab@R1# set interfaces ge-0/0/5 unit 112 description "=== connection to ISP1 ==="
[edit]
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
lab@R1# set interfaces ge-0/0/5 unit 112 vlan-id 112
[edit]
lab@R1# set interfaces ge-0/0/5 unit 112 family inet address 172.17.0.9/30
[edit]
lab@R1# set interfaces ge-0/0/5 unit 112 family mpls
Next the external MP-BGP session is configured between router R1 and the ISP1 peer.
[edit]
lab@R1# set protocols bgp group ISP1 log-updown
[edit]
lab@R1# set protocols bgp group ISP1 family inet-vpn unicast
[edit]
lab@R1# set protocols bgp group ISP1 peer-as 4356
[edit]
lab@R1# set protocols bgp group ISP1 neighbor 172.17.0.10
b. R5
Because using a routing policy on router R1 to manipulate the routes exchanged between
the ASBRs is not allowed, you can accept the remote route-target community on router
R5 and R8. This will provide successful communication between the local and remote
sites of VPNB.
[edit] 1449
lab@R5# set policy-options policy-statement VPNB-export.target term accept.rest
then community add VPNB-CE3
[edit]
lab@R5# set policy-options policy-statement VPNB-import.target term 1 from
community VPNB-CE3
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1450 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R5# set policy-options community VPNB-CE3 members target:4356:500
c. R8
[edit]
lab@R8# set policy-options policy-statement VPNB-export.target term accept.rest
then community add VPNB-CE3
[edit]
lab@R8# set policy-options policy-statement VPNB-import.target term 1 from
community VPNB-CE3
[edit]
lab@R8# set policy-options community VPNB-CE3 members target:4356:500
4356:500:172.16.5.4/30
*[BGP/170] 04:41:35, localpref 100
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
AS path: 4356 I, validation-state: unverified
> to 172.17.0.10 via ge-0/0/5.112, Push 299786
4356:500:172.17.31.0/24
*[BGP/170] 04:41:35, localpref 100
AS path: 4356 65100 I, validation-state: unverified
> to 172.17.0.10 via ge-0/0/5.112, Push 299786
4356:500:172.17.32.0/24
*[BGP/170] 04:41:35, localpref 100
AS path: 4356 65100 I, validation-state: unverified
> to 172.17.0.10 via ge-0/0/5.112, Push 299786
4356:500:172.17.33.0/24
*[BGP/170] 04:41:35, localpref 100
AS path: 4356 65100 I, validation-state: unverified
> to 172.17.0.10 via ge-0/0/5.112, Push 299786
4356:500:172.17.34.0/24
*[BGP/170] 04:41:35, localpref 100
AS path: 4356 65100 I, validation-state: unverified
> to 172.17.0.10 via ge-0/0/5.112, Push 299786
4356:500:172.17.35.0/24
*[BGP/170] 04:41:35, localpref 100
AS path: 4356 65100 I, validation-state: unverified
> to 172.17.0.10 via ge-0/0/5.112, Push 299786
Using the remote route-target community in the import vrf policy, router R5 imports the
remote routes into the vrf routing table.
[edit]
lab@R5# run show route 172.17.31.0/24
4356:500:172.17.31.0/24
*[BGP/170] 02:48:55, localpref 100, from 10.50.250.10
AS path: 4356 65100 I, validation-state: unverified
> to 10.50.0.46 via ge-0/0/4.56, label-switched-path r5-to-r1
Similarly, router R8 successfully imports the routes into the VPNB routing table.
[edit]
lab@R8# run show route advertising-protocol bgp 172.17.0.6
7) Ensure that all BGP sessions in VPNB can send and receive packets larger than the
default 512-byte maximum segment size.
a. R5 and R8
By default, BGP uses packets with a maximum size of 512-bytes. This way it is ensured
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
that even if the MTU is lower on some links, BGP packets will not be fragmented.
To force BGP to use bigger packets, you have to enable the MTU discovery functionality.
This will automatically detect the maximum MTU between the peers and will use it for
the size of the BGP packets.
[edit]
lab@R5# set routing-instances VPNB protocols bgp mtu-discovery
[edit]
lab@R8# set routing-instances VPNB protocols bgp mtu-discovery
8) Make sure that traffic coming from VPNB with precedence bits 010, 011, 100 and
100 is classified as assured-forwarding. Ensure 20% high priority bandwidth
reservation for that traffic in your network, while keep the default reservation for
rest of the traffic.
The last task requires providing QoS should is for VPNB only.
a. R1, R2, R4, R5, R6 and R8
First, behavior aggregate classifiers are configured that will be later used for classifying
the traffic.
The EXP classifier is needed to map the traffic coming from the MPLS core interfaces and
associate it to forwarding-classes. To inherit the default mapping use the import function
to use the default EXP classifier as a template. Next, change the mapping for the assured-
1451
forwarding classes as required by the task.
[edit]
lab@R1# set class-of-service classifiers exp custom-exp import default
[edit]
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1452 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R1# set class-of-service classifiers exp custom-exp forwarding-class assured-
forwarding loss-priority low code-points 011
[edit]
lab@R1# set class-of-service classifiers exp custom-exp forwarding-class assured-
forwarding loss-priority low code-points 100
[edit]
lab@R1# set class-of-service classifiers exp custom-exp forwarding-class assured-
forwarding loss-priority low code-points 101
An IP precedence classifier is intended to map the IP traffic coming from the CE sites to
forwarding-classes. Again, the default classifier mappings are used as a template.
[edit]
lab@R1# set class-of-service classifiers inet-precedence VPNB-precedence import
default
[edit]
lab@R1# set class-of-service classifiers inet-precedence VPNB-precedence
forwarding-class assured-forwarding loss-priority low code-points 010
[edit]
lab@R1# set class-of-service classifiers inet-precedence VPNB-precedence
forwarding-class assured-forwarding loss-priority low code-points 011
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
[edit]
lab@R1# set class-of-service classifiers inet-precedence VPNB-precedence
forwarding-class assured-forwarding loss-priority low code-points 100
[edit]
lab@R1# set class-of-service classifiers inet-precedence VPNB-precedence
forwarding-class assured-forwarding loss-priority low code-points 101
A custom scheduler-map and classifier are assigned to the MPLS core interfaces.
[edit]
lab@R1# set class-of-service interfaces ge-0/0/4 scheduler-map custom-map
[edit]
lab@R1# set class-of-service interfaces ge-0/0/4 unit * classifiers exp custom-
exp
[edit]
lab@R1# set class-of-service scheduler-maps custom-map forwarding-class best-
effort scheduler be
[edit]
lab@R1# set class-of-service scheduler-maps custom-map forwarding-class network-
control scheduler nc
1452
Custom schedulers are used to define the properties of output queues. The task requires
modifying the assured-forwarding only, but it is a good practice to ensure the rest of the
traffic is properly handled.
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1453 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R1# set class-of-service schedulers af transmit-rate percent 20
[edit]
lab@R1# set class-of-service schedulers af priority high
[edit]
lab@R1# set class-of-service schedulers nc transmit-rate percent 5
[edit]
lab@R1# set class-of-service schedulers nc priority low
[edit]
lab@R1# set class-of-service schedulers be transmit-rate remainder
[edit]
lab@R1# set class-of-service schedulers be priority low
b. R5
By default, associating scheduler-map can be done under the physical interfaces under
the class-of-service stanza. However, since you are not allowed to apply custom CoS
policies to traffic other then VPNB, you have to enable per-unit-scheduler for the
interface to the CE sites. This allows you to apply the custom scheduler only for a specific
unit.
[edit]
lab@R5# set interfaces ge-0/0/5 per-unit-scheduler
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
[edit]
lab@R5# set class-of-service interfaces ge-0/0/5 unit 110 scheduler-map custom-
map
[edit]
lab@R5# set class-of-service interfaces ge-0/0/5 unit 110 classifiers inet-
precedence VPNB-precedence
When vrf-table-label is used for the routing instances, a default classifier is applied to the
routing-instance logical interface. You have to replace the default EXP classifier with the
custom one, to map the traffic coming from the MPLS core. The purpose of this classifier
is to match on the vpn label after the transport label is stripped off.
[edit]
lab@R5# set class-of-service routing-instances VPNB classifiers exp custom-exp
c. R8
[edit]
lab@R8# set class-of-service interfaces ge-0/0/5 unit 111 scheduler-map custom-
map
[edit]
lab@R8# set class-of-service interfaces ge-0/0/5 unit 111 classifiers inet- 1453
precedence VPNB-precedence
[edit]
lab@R8# set class-of-service routing-instances VPNB classifiers exp custom-exp
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1454 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R5# run show class-of-service routing-instance VPNB
Routing instance: VPNB
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
Solution - Task 6.3: VPLS configuration
9) Configure VPLS L2 VPN between sites VPLS-1 and VPLS-2, using the interfaces as
shown in the physical diagram. Since site VPLS-2 has connectivity to both R6 and
R8, dedicate R8 as primary PE and R6 as backup PE. You have to use LDP signaled
VPLS with automatic site discovery, hence you are not allowed to configure the
sites explicitly.
The task description suggests that LDP signaled VPLS should connect the two sites.
However, automatic site discovery must be used. Enable MP-BGP protocol for that
purpose. This is known as FEC 129 LDP signaled VPLS.
a. All devices including the route-reflector
A new MP-BGP family is added to BGP running in the network.
[edit]
lab@R1# set protocols bgp group internal family l2vpn auto-discovery-only
b. R1
Configuring a new physical interface to connecting site VPLS-1. You have to exclude the
apply-group to enable family mpls on logical interfaces. Otherwise, the commit will fail
due to an error.
[edit]
lab@R1# set interfaces ge-0/0/3 apply-groups-except enable_mpls
1454
[edit]
lab@R1# set interfaces ge-0/0/3 vlan-tagging
[edit]
lab@R1# set interfaces ge-0/0/3 encapsulation vlan-vpls
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1455 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R1# set interfaces ge-0/0/3 unit 3001 description "=== connection to VPLS-1
==="
[edit]
lab@R1# set interfaces ge-0/0/3 unit 3001 encapsulation vlan-vpls
[edit]
lab@R1# set interfaces ge-0/0/3 unit 3001 vlan-id 3001
[edit]
lab@R1# set interfaces ge-0/0/3 unit 3001 family vpls
Make sure the routing instance type is set to vpls. Because BGP is used for auto-
discovery, you have to assign route-distinguisher and route-target to the routing instance
configuration.
[edit]
lab@R1# set routing-instances VPLS instance-type vpls
[edit]
lab@R1# set routing-instances VPLS interface ge-0/0/3.3001
[edit]
lab@R1# set routing-instances VPLS route-distinguisher 10.50.250.1:300
The auto-discovery process require a unique extended L2 VPN community identifying the
particular instance.
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
[edit]
lab@R1# set routing-instances VPLS l2vpn-id l2vpn-id:300:300
[edit]
lab@R1# set routing-instances VPLS vrf-target target:371786601L:300
[edit]
lab@R1# set routing-instances VPLS protocols vpls no-tunnel-services
c. R8
Configuring a new physical interface to connect site VPLS-2. You have to exclude the
apply-group again.
[edit]
lab@R8# set interfaces ge-0/0/3 apply-groups-except enable_mpls
[edit]
lab@R8# set interfaces ge-0/0/3 description "=== connection to VPLS-2 ==="
[edit]
lab@R8# set interfaces ge-0/0/3 vlan-tagging
[edit] 1455
lab@R8# set interfaces ge-0/0/3 encapsulation vlan-vpls
[edit]
lab@R8# set interfaces ge-0/0/3 unit 3002 encapsulation vlan-vpls
[edit]
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1457 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
[edit]
lab@R6# set interfaces ge-0/0/3 description "=== connection to VPLS-2 ==="
[edit]
lab@R6# set interfaces ge-0/0/3 vlan-tagging
[edit]
lab@R6# set interfaces ge-0/0/3 encapsulation vlan-vpls
[edit]
lab@R6# set interfaces ge-0/0/3 unit 3002 encapsulation vlan-vpls
[edit]
lab@R6# set interfaces ge-0/0/3 unit 3002 vlan-id 3002
[edit]
lab@R6# set interfaces ge-0/0/3 unit 3002 family vpls
[edit]
lab@R6# set routing-instances VPLS instance-type vpls
[edit]
lab@R6# set routing-instances VPLS interface ge-0/0/3.3002
[edit]
lab@R6# set routing-instances VPLS route-distinguisher 10.50.250.6:300
[edit]
lab@R6# set routing-instances VPLS l2vpn-id l2vpn-id:300:300
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
[edit]
lab@R6# set routing-instances VPLS vrf-target target:371786601L:300
[edit]
lab@R6# set routing-instances VPLS protocols vpls no-tunnel-services
[edit]
lab@R6# set routing-instances VPLS protocols vpls multi-homing site VPLS-2
identifier 2
Router R6 is configured with preference backup, which means that it is less likely to
become a DF.
[edit]
lab@R6# set routing-instances VPLS protocols vpls multi-homing site VPLS-2
preference backup
[edit]
lab@R6# set routing-instances VPLS protocols vpls multi-homing site VPLS-2
interface ge-0/0/3.3002
Instance: VPLS
L2vpn-id: 300:300
Local-id: 10.50.250.1
Remote-id Type St Time last up # Up trans
10.50.250.6 rmt Up Dec 3 17:16:19 2016 1
Remote PE: 10.50.250.6, Negotiated control-word: No
Incoming label: 262156, Outgoing label: 262154
Negotiated PW status TLV: No
Local interface: lsi.1048587, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls VPLS local-id 10.50.250.1 remote-id 10.50.250.6
neighbor 10.50.250.6
Flow Label Transmit: No, Flow Label Receive: No
10.50.250.8 rmt Up Dec 3 17:16:44 2016 1
Remote PE: 10.50.250.8, Negotiated control-word: No
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
Incoming label: 262157, Outgoing label: 262154
Negotiated PW status TLV: No
Local interface: lsi.1048588, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls VPLS local-id 10.50.250.1 remote-id 10.50.250.8
neighbor 10.50.250.8
Flow Label Transmit: No, Flow Label Receive: No
L2vpn-id: 300:300
Local-id: 10.50.250.8
Remote-id Type St Time last up # Up trans
10.50.250.1 rmt Up Dec 5 12:23:28 2016 1
Remote PE: 10.50.250.1, Negotiated control-word: No
Incoming label: 262402, Outgoing label: 262146
Negotiated PW status TLV: No
Local interface: lsi.1048579, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls VPLS local-id 10.50.250.8 remote-id 10.50.250.1
neighbor 10.50.250.1
Flow Label Transmit: No, Flow Label Receive: No
10.50.250.6 rmt Up Dec 5 12:25:17 2016 1
Remote PE: 10.50.250.6, Negotiated control-word: No
Incoming label: 262401, Outgoing label: 262145
Negotiated PW status TLV: No
Local interface: lsi.1048580, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls VPLS local-id 10.50.250.8 remote-id 10.50.250.6
neighbor 10.50.250.6
Flow Label Transmit: No, Flow Label Receive: No
Multi-home:
Local-site Id Pref State
VPLS-2 2 200 Up
[edit]
lab@R6# run show vpls connections
Layer-2 VPN connections:
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not available
BK -- Backup connection ST -- Standby connection
PF -- Profile parse failure PB -- Profile busy
RS -- remote site standby SN -- Static Neighbor
LB -- Local site not best-site RB -- Remote site not best-site
VM -- VLAN ID mismatch
Instance: VPLS
L2vpn-id: 300:300
Local-id: 10.50.250.6
Remote-id Type St Time last up # Up trans
10.50.250.1 rmt Up Dec 3 14:58:50 2016 1
Remote PE: 10.50.250.1, Negotiated control-word: No
Incoming label: 262154, Outgoing label: 262156
Negotiated PW status TLV: No
Local interface: lsi.1048586, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls VPLS local-id 10.50.250.6 remote-id 10.50.250.1
neighbor 10.50.250.1 1459
Flow Label Transmit: No, Flow Label Receive: No
10.50.250.8 rmt Up Dec 3 14:59:09 2016
Remote PE: 10.50.250.8, Negotiated control-word: No
1
Incoming label: 262155, Outgoing label: 262155
Negotiated PW status TLV: No
Local interface: lsi.1048587, Status: Up, Encapsulation: ETHERNET
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute
1460 iNET ZERO JNCIE-SP lab workbook with detailed solutions version 2.0
10.50.250.1:300:10.50.250.1/96 AD
*[BGP/170] 02:45:57, localpref 100, from 10.50.250.1
AS path: I, validation-state: unverified
> to 10.50.0.97 via ge-0/0/1.49
10.50.250.6:300:10.50.250.6/96 AD
*[BGP/170] 02:45:59, localpref 100, from 10.50.250.6
AS path: I, validation-state: unverified
> to 10.50.0.97 via ge-0/0/1.49
to 10.50.0.101 via ge-0/0/1.59
10.50.250.8:300:10.50.250.8/96 AD
*[BGP/170] 02:45:43, localpref 100, from 10.50.250.8
AS path: I, validation-state: unverified
> to 10.50.0.101 via ge-0/0/1.59
JNCIE-SP workbook: Chapter eleven solutions: Full Day Lab Challenge III
10) One more site attached to R2 should be connected to the VPLS VPN. Assume that
R2 supports only L2 circuit VPNs. Interconnect the L2VPN-3 site with the VPLS VPN
at R8 as primary and R6 asa a back-up connection.
L2 circuit VPN uses LDP for signaling; therefor a targeted LDP session is required between
the PEs connecting the two sites. However, LDP targeted sessions already exist due to the
LDP tunneling configuration.
a. R2
Configure the interface to connect site L2VPN-3 to the network. Again, the apply group
must be excluded.
[edit]
lab@R2# set interfaces apply-groups enable_mpls
[edit]
lab@R2# set interfaces ge-0/0/3 apply-groups-except enable_mpls
[edit]
lab@R2# set interfaces ge-0/0/3 description "=== connection to L2VPN-3 ==="
The encapsulation used on the interface must be ccc, as well as the family on logical
interface.
[edit]
lab@R2# set interfaces ge-0/0/3 encapsulation ethernet-ccc
1460
[edit]
lab@R2# set interfaces ge-0/0/3 unit 0 family ccc
The interface is added to the l2circuit neighbor configuration, together with the backup
neighbor. The virtual circuit id must match on both ends of the connection.
http://www.inetzero.com - Copyright 2017 iNET ZERO. All rights reserved
For personal non commercial use only – do not distribute