Alcatel-Lucent NRSII Workshop

Version A 1.0
May 2013

Software Version: 7750 SR OS 10.0

 Table of contents
Lab 1 Basic IP Configuration .....................................................................5
Lab 1.1 Physical connectivity ...................................................................................5
Lab 1.2 IP connectivity .............................................................................................6
Lab 1.3 IPv6 connectivity .........................................................................................8
Lab 2 IGP Configuration ..........................................................................10
Lab 2.1 IS-IS in a single area ..................................................................................10
Lab 2.2 6over4 tunneling ........................................................................................11
Lab 2.3 OSPF in a single area .................................................................................12
Lab 2.4 OSPF in multi-area ....................................................................................13
Lab 2.5 OSPFv3 ......................................................................................................14
Lab 3 MPLS Configuration ......................................................................17
Lab 3.1 LDP ............................................................................................................17
Lab 3.2 Constraint-based RSVP-TE LSPs ..............................................................18
Lab 3.3 RSVP bandwidth reservation .....................................................................19
Lab 3.4 RSVP one-to-one Fast Reroute ..................................................................21
Lab 4 Services Configuration ...................................................................23
Lab 4.1 Epipe ..........................................................................................................23
Lab 4.2 VPLS spoke termination on epipe .............................................................24
Lab 4.3 VPLS spoke termination on IES ................................................................26
Lab 4.4 VPRN with BGP PE-CE ............................................................................27
Lab 4.5 6VPE ..........................................................................................................28
Lab 4.6 VPLS spoke termination on VPRN (OPTIONAL)....................................30
Lab 1 Solutions: Basic IP Configuration .................................................32
Lab 1.1 Physical connectivity .................................................................................32
Lab 1.2 IP connectivity ...........................................................................................33
Lab 1.3 IPv6 connectivity .......................................................................................35
Lab 2 IGP Configuration ..........................................................................36
Lab 2.1 IS-IS in a single area ..................................................................................36
Lab 2.2 6over4 tunneling ........................................................................................38
Lab 2.3 OSPF in a single area .................................................................................40
Lab 2.4 OSPF in multi-area ....................................................................................42
Lab 2.5 OSPFv3 ......................................................................................................45
Lab 3 MPLS Configuration ......................................................................49
Lab 3.1 LDP ............................................................................................................49
Lab 3.2 Constraint-based RSVP-TE LSPs ..............................................................51
Lab 3.3 RSVP bandwidth reservation .....................................................................55
Lab 3.4 RSVP one-to-one Fast Reroute ..................................................................57
Lab 4 Services Configuration ...................................................................62
Lab 4.1 Epipe ..........................................................................................................62
Lab 4.2 VPLS spoke termination on epipe .............................................................65
Lab 4.3 VPLS spoke termination on IES ................................................................69
Lab 4.4 VPRN with BGP PE-CE ............................................................................76
Lab 4.5 6VPE ..........................................................................................................83
Lab 4.6 VPLS spoke termination on VPRN (OPTIONAL)....................................87
List of Commands .................................................................................................90

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 3

 List of Figures
Figure 1: Network connectivity .......................................................................................... 5
Figure 2: IPv4 Network topology ....................................................................................... 6
Figure 3: IPv6 Network topology ....................................................................................... 8
Figure 4: IS-IS Network.................................................................................................... 10
Figure 5: 6over4 Network topology.................................................................................. 11
Figure 6: OSPF Network in a single area ......................................................................... 12
Figure 7: OSPF Network in multi-area ............................................................................. 13
Figure 8: OSPFv3 Network in multi-area ......................................................................... 14
Figure 9: Network Topology for LDP .............................................................................. 17
Figure 10: Network topology for RSVP-TE LSPs ........................................................... 18
Figure 11: Network topology for RSVP bandwidth reservation ...................................... 20
Figure 12: Network topology for RSVP-TE FRR LSP .................................................... 21
Figure 13: Network topology for Epipe ............................................................................ 23
Figure 14: Network topology for VPLS spoke termination on epipe ............................... 25
Figure 15: Network topology for VPLS spoke termination on IES.................................. 26
Figure 16: Network topology for VPRN .......................................................................... 27
Figure 17: Network topology for 6VPE............................................................................ 29
Figure 18: Network topology for VPLS termination on VPRN ....................................... 30

List of Tables
Table 1: Router Interface Addresses ................................................................................... 7
Table 2: IPv6 Router Interface Addresses .......................................................................... 8
Table 3: Command List ................................................................................................... 92

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 4

Lab 1 Basic IP Configuration

Lab 1.1 Physical connectivity

Objective
The objective of this lab is to verify the operation and physical connectivity of routers, which
are connected according to Figure 1. Please confirm specific routers’ IP addresses with your
instructor. Your instructor should also provide you with the network topology for your Metro.

Figure 1: Network connectivity

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 5

Recommended completion time: 10 minutes

Exercise
1. Student #1: Connect to routers R1, R3, and R5 using the management IP addresses
given to you by your instructor. The username and password for all devices is
‘student’. If you are unable to connect to any of the routers, please notify your
instructor.

2. Student #2: Connect to routers R2, R4, and R6 using the management IP addresses
given to you by your instructor. The username and password for all devices is
‘student’. If you are unable to connect to any of the routers, please notify your
instructor.

3. Verify that all the configured ports are operationally up before moving on to the next
section.

Lab 1.2 IP connectivity

Objective
The objective of this lab is to verify the IP connectivity among the following six routers.

Figure 2: IPv4 Network topology

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 6

 Router Interface IP Address
name
R1 system 10.10.10.1
toR2 10.1.2.1/27
toR3 10.1.3.1/27
toR5 10.1.5.1/27
R2 system 10.10.10.2
toR1 10.1.2.2/27
toR4 10.2.4.2/27
toR6 10.2.6.2/27
R3 system 10.10.10.3
toR1 10.1.3.3/27
toR4 10.3.4.3/27
R4 system 10.10.10.4
toR2 10.2.4.4./27
toR3 10.3.4.4/27
R5 system 10.10.10.5
toR1 10.1.5.5/27
loopback1-1 192.168.1.1/32
loopback1-2 192.168.1.2/32
` loopback1-3 192.168.1.3/32
R6 system 10.10.10.6
toR2 10.2.6.6/27
loopback2-1 192.168.2.1/32
loopback2-2 192.168.2.2/32
loopback2-3 192.168.2.3/32

Table 1: Router Interface Addresses

Recommended completion time: 10 minutes

Exercise

1. Verify that all of the configured router interfaces are operationally up.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 7

Lab 1.3 IPv6 connectivity
Objective
The objective of this lab is to configure IPv6 router interfaces.

Figure 3: IPv6 Network topology

Router Interface IP Address

name
R1 system 2001:db8:a:100::1/128
toR5 --
R2 system 2001:db8:a:200::2/128
toR6 --
R5 system 2001:db8:a:500::5/128
toR1 --
loopback1-1 2001:db8:a:501::1/128
loopback1-2 2001:db8:a:501::2/128
loopback1-3 2001:db8:a:501::3/128
R6 system 2001:db8:a:600::6/128
toR2 --
loopback2-1 2001:db8:a:601::1/128
loopback2-2 2001:db8:a:601::2/128
loopback2-3 2001:db8:a:601::3/128

Table 2: IPv6 Router Interface Addresses

Recommended completion time: 10 minutes

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 8

Exercise
1. Student #1: Configure IPv6 router interfaces on routers R1 and R5 according to Table
2. Enable IPv6 on interfaces between routers R1 and R5 but do not configure IPv6
addresses.

2. Student #2: Configure IPv6 router interfaces on routers R2 and R6 according to Table
2. Enable IPv6 on interfaces between routers R1 and R5 but do not configure IPv6
addresses.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 9

Lab 2 IGP Configuration

Lab 2.1 IS-IS in a single area

Figure 4: IS-IS Network

Recommended completion time: 30 minutes

Exercise
1. Student #1: Configure an IS-IS network as per Figure 4 with the following
requirements:
a. Configure a point-to-point connection between routers R1 and R2.
b. Configure a broadcast connection between routers R1 and R3.
c. Ensure that routers R1 and R3 system interface addresses are advertised into
IS-IS.
d. Configure routers R1 and R3 as level 1 and level 2 routers, respectively.

2. Student #2: Configure an IS-IS network as per Figure 4 with the following
requirements:
a. Configure a point-to-point connection between routers R2 and R4.
b. Configure a broadcast connection between routers R3 and R4.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 10

 c. Ensure that routers R2 and R4 system interface addresses are advertised into
IS-IS.
d. Configure routersR2 and R4 as level 1 and level 2 routers.

3. Verify that level 1 and level 2 IS-IS adjacencies are up among all routers. Ensure that
each router can ping all other routers’ system IP addresses.

4. Configure IS-IS to use the interface bandwidth as a reference for determining cost
similar to how OSPF determines its interface cost. Student #1 will configure routers R1
and R3, while Student #2 will configure routers R2 and R4.

5. Student #1: Configure a simple password authentication between routers R1 and R2.
Use authentication key “secret”. Verify that IS-IS adjacency is operationally up
between routers R1 and R2.

6. Student #2: Configure MD5 authentication between routers R3 and R4. Use
authentication key “md5-password”. Verify that the IS-IS adjacency is operationally up
between routers R3 and R4.

Lab 2.2 6over4 tunneling

Objective
The objective of this lab is to investigate the configuration and behavior of tunneling of IPv6
traffic over an IPv4 network. IS-IS is running in this IPv4 network. In the Figure 5, the two CEs
can communicate through an IPv4 network. Assume the CE routers, R5 and R6, are running
IPv6 only. Assume the PE routers, R1 and R2, are running dual-stack IPv4/IPv6. The P
routers, R3 and R4, are running IPv4 only.

Figure 5: 6over4 Network topology

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 11

Recommended completion time: 30 minutes

Exercise

1. Student #1: Configure two IPv6 static routes on router R1 and one IPv6 static route on
router R5 using IPv6 over IPv4 tunneling. The goal is to make router R5 reach router
R6 system address (2001:db8:a:600::6) and for router R6 to reach router R5 system
address (2001:db8:a:500::5).

2. Student #2: Configure two IPv6 static routes on router R2 and one IPv6 static route on
router R6 using IPv6 over IPv4 tunneling. The goal is to make router R5 reach router R6
system address (2001:db8:a:600::6) and for router R6 to reach router R5 system
address (2001:db8:a:500::5).

3. Student #1: On router R5, verify that a ping to the IPv6 system interface address on
router R6 works (2001:db8:a:600::6).

4. Student #2: On router R6, verify that a ping to the IPv6 system interface address on
router R5 works (2001:db8:a:500::5).

Lab 2.3 OSPF in a single area

Objective
The objective of this lab is to configure OSPF interfaces in a single area. Each pair of
interfaces will form an OSPF adjacency.

Figure 6: OSPF Network in a single area

Recommended completion time: 30 minutes

Exercise

1. Student #1: Configure an OSPF network as per Figure 6 with the following
requirements:

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 12

 a. Configure a point-to-point connection between routers R1 and R2.
b. Configure a broadcast connection between routers R1 and R3.
c. Ensure that routers R1 and R3 system addresses are advertised into OSPF.

2. Student #2: Configure an OSPF network as per Figure 6 with the following
requirements:
a. Configure a point-to-point connection between routers R3 and R4.
b. Configure a broadcast connection between routers R2 and R4.
c. Ensure that routers R2 and R4 system addresses are advertised into OSPF.

3. Ensure that that OSPF adjacencies are formed among all four routers.
Student #1: Verify OSPF adjacencies on routers R1 and R2.
Student #2: Verify OSPF adjacencies on routers R3 and R4.

Lab 2.4 OSPF in multi-area

Objective
The objective of this lab is to configure OSPF in multiple areas.

Figure 7: OSPF Network in multi-area

Recommended completion time: 30 minutes

Exercise

1. Student #1: Configure a point-to-point connection between routers R1 and R5 in OSPF

area 1. Ensure that router R5’s system address is reachable to all routers.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 13

 2. Student #2: Configure a point-to-point connection between routers R2 and R6 in OSPF
area 2. Ensure that router R6’s system address is reachable to all routers.

3. Student #1: Verify that OSPF adjacencies are established in area 1.

Student #2: Verify that OSPF adjacencies are established in area 2.

4. Student #1: Advertise three loopback interfaces configured on router R5 into OSPF as
internal routes. Configure route summarization in area 1 so that routers in other areas
see only one address that represents the three loopback interface addresses on router
R5. Use the most specific prefix possible.

5. Student #2: Advertise three loopback interfaces configured on router R6 into OSPF as
internal routes. Configure route summarization in area 2 so that routers in other areas
see only one address that represents the three loopback interface addresses on router
R6. Use the most specifc prefix possible.

6. Student #1: Configure a loopback interface called “dummy-loopback” on router R5

with address 192.168.11.1/32. Use a routing policy to redistribute this interface
address into OSPF.

7. Student #2: Configure a loopback interface called “dummy-loopback” on router R6

with address 192.168.22.1/32. Use a routing policy to redistribute this interface
address into OSPF.

Lab 2.5 OSPFv3

Objective
The objective of this lab is to configure OSPFv3 in multiple areas.

Figure 8: OSPFv3 Network in multi-area

Recommended completion time: 30 minutes

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 14

Exercise

1. Student #1: Configure an OSPFv3 network with the following requirements:

a. Configure a point-to-point interface on router R1 toward router R2 in area 0.
b. Configure authentication for the point-to-point interface on router R1 toward
router R2.
i. Configure a static IPSec security association (static-sa) using sha1
authentication.
ii. Specify an ascii key “ospfv3-password-nrs2”.
iii. Specify AH protocol and SPI value 300.
iv. Associate a bi-directional authentication for the point-to-point
interface on router R1 toward router R2.
c. Configure an OSPFv3 point-to-point connection between routers R1 and R5 in
area 1 according to Figure 8.
d. Ensure that router R1 IPv6 system address is advertised into area 0 and router
R5 IPv6 system address is advertised into area 1.

2. Student #2: Configure an OSPFv3 network with the following requirements:

a. Configure a point-to-point interface on router R2 toward router R1 in area 0.
b. Configure authentication for the point-to-point interface on router R2 toward
router R1.
i. Configure a static IPSec security association (static-sa) using sha1
authentication.
ii. Specify an ascii key, “ospfv3-password-nrs2”.
iii. Specify AH protocol and SPI value 300.
iv. Associate a bi-directional authentication for the point-to-point
interface on router R2 toward router R1.
c. Configure an OSPFv3 point-to-point connection between routers R2 and R6 in
area 2 according to Figure 8.
d. Ensure that router R2 IPv6 system address is advertised into area 0 and router
R6 IPv6 system address is advertised into area 2.

3. Verify OSPFv3 adjacencies in all areas are operationally up.

4. Student #1: Advertise the three loopback interfaces (loopback1-1, loopback1-2, and
loopback1-3) from router R5 to OSPFv3. Configure route summarization with the most
specific prefix possible in area 1 so that only one address is advertised to other areas
instead of three loopback interface addresses.
a. Verify that router R6 can reach router R5 loopback interface addresses.

5. Student #2: Advertise the three loopback interfaces (loopback2-1, loopback2-2, and
loopback2-3) from router R6 to OSPFv3. Configure route summarization with the most

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 15

 specific prefix possible in area 2 so that only one address is advertised to other areas
instead of three loopback interface addresses.
a. Verify that router R5 can reach router R6 loopback interface addresses.

6. Student #1: Configure a loopback interface named “dummy-loopback” on router R5

with address 2001:db8:dd:501::1/128. Configure a route policy to ensure all routers
can reach this loopback interface address.

7. Student #2: Configure a loopback interface named “dummy-loopback” on router R6

with address 2001:db8:dd:601::1/128. Configure a route policy to ensure all routers
can reach this loopback interface address.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 16

Lab 3 MPLS Configuration

Lab 3.1 LDP

Objective
The objective of this lab is to observe the LDP sessions established among routers in multiple
OSPF areas.

Figure 9: Network Topology for LDP

Recommended completion time: 30 minutes

Exercise

1. Student #1: Configure Link LDP on all interfaces on routers R1, R3 and R5.

2. Student #2: Configure Link LDP on all interfaces on routers R2, R4, and R6.

3. Verify that all LDP interfaces are up and that each router has label bindings for all
other routers.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 17

 4. Student #1: Configure router R5 to generate label bindings for its three loopback
interface addresses (loopback1-1, loopback1-2, and loopback1-3). Ensure that all
routers have three label bindings for router R5’s three loopback interface addresses.

5. Student #2: Configure router R6 to generate label bindings for its three loopback
interface addresses (loopback2-1, loopback2-2, and loopback2-3). Ensure that all
routers have three label bindings for router R6’s three loopback interface addresses.

Lab 3.2 Constraint-based RSVP-TE LSPs

Objective
The objective of this lab is to observe the behavior of CSPF-enabled RSVP-TE LSPs. Various
LSP constraints including admin group, TE metric, and hop limit will be configured. OSPF is
used as an IGP since by default it has a higher preference than IS-IS.

Figure 10: Network topology for RSVP-TE LSPs

Recommended completion time: 30 minutes

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 18

Exercise

1. Student #1: Configure an LSP named “toR2-1” from router R1 to router R2 using a
fully loose path.

2. Student #2: Configure an LSP named “toR1-1” from router R2 to router R1 using a
fully loose path.

3. Student #1: Configure an LSP named “toR2-2” from router R1 to router R2. Use the
TE metric to make this LSP follow the path R1-R3-R4-R2.

4. Student #2: Configure an LSP named “toR1-2” from router R2 to router R1. Use a hop
limit to make this LSP follow a direct path from router R2 to router R1.

5. Student #1: Configure an LSP named “toR2-3” from router R1 to router R2. Use an
administrative group to make this LSP follow the path R1-R3-R4-R2.

6. Student #2: Configure an LSP named “toR1-3” from router R2 to router R1. Use a
strict path to make this LSP follow the path R2-R4-R3-R1.

7. Verify that all LSPs are operationally up.

Lab 3.3 RSVP bandwidth reservation

Objective
The objective of this lab is to observe the behavior of RSVP-TE bandwidth.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 19

 Figure 11: Network topology for RSVP bandwidth reservation

Recommended completion time: 30 minutes

Exercise

1. Student #1: Configure an LSP named “toR4-1” on router R1 to router R4 with the
following requirements:
a. Change the bandwidth subscription rate to 50 for router R1 interface toward
router R2.
b. Configure the primary path with bandwidth requirement of 300 Mbps, and
setup and hold priority of 2.
c. Ensure that the primary path uses the path R1-R2-R4 by configuring one strict
hop.
d. Configure a standby secondary path with bandwidth requirement of 600 Mbps.
e. Ensure that the secondary path uses the path R1-R3-R4 by configuring an admin
group.
f. Verify the total bandwidth and reservable bandwidth on router R1 interface
toward router R2, and on router R1 interface toward router R3.

2. Student #2: Configure an LSP named “toR3-1” on router R2 to R3 with the following
requirements:
a. Change the bandwidth subscription rate to 50 for router R2 interface toward
router R1.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 20

 b. Configure the primary path with bandwidth requirement of 300 Mbps, and
setup and hold priority of 3.
c. Ensure that the primary path uses a strict path R2-R1-R3.
d. Configure a standby secondary path with a bandwidth requirement of 600
Mbps.
e. Ensure that it uses a strict path R2-R4-R3.
f. Verify the total bandwidth and reservable bandwidth on router R2 interface
toward router R1 and on router R2 interface toward router R4.

Lab 3.4 RSVP one-to-one Fast Reroute

Objective
The objective of this lab is to configure an RSVP-TE LSP with one-to-one fast reroute enabled.

Figure 12: Network topology for RSVP-TE FRR LSP

Recommended completion time: 20 minutes

Exercise

1. Student #1: Configure one-to-one fast reroute on the LSP named “toR4-1”.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 21

2. Student #2: Configure one-to-one fast reroute on the LSP named “toR3-1”.

3. Verify that LSPs are operationally up.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 22

Lab 4 Services Configuration

Lab 4.1 Epipe

Objective
The objective of this lab is to configure and verify a distributed epipe service. Routers R5 and
R6 will act as CE routers and they will not have any routing protocol or MPLS running on them.
Routers R1 and R2 will act as PE routers. Routers R3 and R4 will act as P routers.

Figure 13: Network topology for Epipe

Recommended completion time: 30 minutes

Exercise

1. Student #1: Shut down OSPF/OSPFv3 configuration, LDP sessions, and RSVP-TE LSPs on
router R5.

2. Student #2: Shut down OSPF/OSPFv3 configuration, LDP sessions, and RSVP-TE LSPs on
router R6.

3. Student #1: Configure an epipe service with service ID 10 on router R1 as per Figure
13.
a. Configure a SAP toward router R5 with a vlan ID 10 for the epipe service.
(Hint: You will need to remove a port association from an existing router
interface and change this port to access port).

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 23

 b. On router R5, configure a router interface toward the epipe service with IP
address 192.168.100.5/24 with a vlan ID 10. Do not delete any existing
interfaces.
c. The epipe service should support a maximum IP payload of 1490 bytes only.
d. Connect the epipe service on router R1 to the epipe service on router R2 that
Student #2 creates in the next step.
e. All SDPs must be configured to use LDPs.

4. Student #2: Configure an epipe service with service ID 10 on router R2 as per Figure
13.
a. Configure a SAP toward router R6 with a vlan ID 10 for the epipe service.
(Hint: You will need to remove a port association from an existing router
interface and change this port to access port).
b. On router R6, configure a router interface toward the epipe service with IP
address 192.168.100.6/24 using vlan ID 10. Do not delete any existing
interfaces.
c. The epipe service should support a maximum IP payload of 1490 bytes only.
d. Connect this epipe service on router R2 to the epipe service on router R1 that
Student #1 created in the previous step.
e. All SDPs must be configured to use LDPs.

5. Verify that the epipe service is operationally up.

a. Student #1: Verify that router R5 can ping router R6 interface address
(192.168.100.6).
b. Student #2: Verify that router R6 can ping router R5 interface address
(192.168.100.5).

Lab 4.2 VPLS spoke termination on epipe

Objective
The objective of this lab is to connect a VPLS and an epipe service using spoke SDPs.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 24

 Figure 14: Network topology for VPLS spoke termination on epipe

Recommended completion time: 30 minutes

Exercise

1. Student #1: Shut down the epipe service 10 on router R1. On router R1, configure an
epipe service with service ID 200 as per Figure 14.
a. Connect this epipe service to the VPLS 100 that Student #2 will create in the
next step.
b. Configure a SAP toward router R5 with vlan ID 20 for this epipe service.
c. On router R5, configure a router interface toward router R1 with address
192.168.20.5/24 using vlan ID 20.
d. All SDPs must be configured to use LDPs.

2. Student #2: Shut down epipe service 10 on router R2. On routers R2 and R4, configure
a VPLS with service ID 100 as per Figure 14.
a. Connect this VPLS to the epipe service 200 that Student #1 created in the
previous step.
b. On router R2, configure a SAP toward router R6 with vlan ID 20 for this VPLS.
c. Connect VPLS between routers R2 and R4 using full mesh SDPs.
d. All SDPs must be configured to use LDPs.
e. On router R6, configure a router interface toward R2 with the address
192.168.20.6/24 and vlan ID 20.

3. Verify that the epipe service 200 and VPLS 100 are both operationally up. Verify MAC
addresses in the VPLS ID 100.

4. A ping from router R5 to router R6 (192.168.20.6) and from router R6 to router R5

(192.168.20.5) should work. Verify MAC addresses in the VPLS ID 100.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 25

Lab 4.3 VPLS spoke termination on IES
Objective
The objective of this lab is to connect Layer 2 service with Layer 3 service. In this lab
exercise, a VPLS and an IES are connected using spoke SDPs.

Figure 15: Network topology for VPLS spoke termination on IES

Recommended completion time: 30 minutes

Exercise

1. Student #1: Shut down the epipe service 200 on router R1. On router R1, configure
an IES with service ID 300 as per Figure 15.
a. Configure an IES interface with IP address 192.168.30.1/24.
b. Connect this IES to the VPLS ID 400 that Student #2 will create in the next step.
c. All SDPs must be configured to use LDPs.

2. Student #2: Shut down the VPLS 100 on routers R2 and R4. Create a VPLS with
service ID 400 on routers R2 and R4 as per Figure 15.
a. On router R2, configure a SAP toward router R6 with vlan ID 30.
b. Connect this VPLS to the IES 300 that Student #1 created in the previous step.
c. On router R6, configure a router interface connecting to this VPLS with IP
address 192.168.30.2/24 using vlan ID 30
d. Connect VPLS between routers R2 and R4 using full mesh SDPs.
e. All SDPs must be configured to use LDPs.

3. Student #1: Verify that both IES and VPLS are operationally up.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 26

 4. Student #2: Perform a ping from router R6 to the IES interface (192.168.30.1). Verify
MAC entries in the VPLS FDB.

Lab 4.4 VPRN with BGP PE-CE

Objective
The objective of this lab is to configure two VPRN services with BGP running between PE and
CE. Routers R1 and R2 will act as PEs for the VPRN services. Routers R5 and R6 will act as
CE and they belong to the same VPRN.

Figure 16: Network topology for VPRN

Recommended completion time: 60 minutes

Exercise

1. Student #1: Shut down IES 300. Shut down all IGPs (IS-IS, OSPF, and OSPFv3) on router
R5.

2. Student #2: Shut down VPLS 400. Shut down all IGPs (IS-IS, OSPF, and OSPFv3) on
router R6.

3. Student #1: Configure an Autonomous System number for routers R1 and R5 according
to Figure 16.

4. Student #2: Configure an Autonomous System number for routers R2 and R6 according
to Figure 16.

5. Student #1: Configure a VPRN service with service ID 500 on router R1 with the
following requirements:
a. Use 65000:10 as route distinguisher and route target values.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 27

 b. Configure the VPRN to use LDP.
c. Configure a VRF interface on router R1 for this VPRN service toward router R5
with IP address 192.168.50.1/27 using vlan ID 50.
d. Use BGP as PE-CE protocol between routers R1 and R5.
e. Configure MP-BGP on router R1 to exchange IPv4 VPN routes between routers
R1 and R2. Ensure that all IPv4 VPN routes are advertised into router R5.
f. Configure a router interface on router R5 toward router R1 with IP address
192.168.50.2/27 using vlan ID 50.
g. Ensure that all local routes in router R5 are advertised into this VPRN service.

6. Student #2: Configure a VPRN service with service ID 500 on router R2 with the
following requirements:
a. Use 65000:10 as route distinguisher and route target values.
b. Configure the VPRN to use LDP.
c. Configure a VRF interface on router R2 for this VPRN service toward router R6
with IP address 192.168.60.1/27 using vlan ID 50.
d. Use BGP as PE-CE protocol between routers R2 and R6.
e. Configure MP-BGP on router R2 to exchange IPv4 VPN routes between routers
R1 and R2. Ensure that all IPv4 VPN routes are advertised into router R6.
f. Configure a router interface on router R6 toward router R2 with IP address
192.168.60.2/27 using vlan ID 50.
g. Ensure that all local routes in router R6 are advertised into this VPRN service.

7. Ensure that the VPRN service is operationally up and BGP sessions are established
between PEs and CEs.

8. Student #1: Perform a ping from router R5 to router R6 (192.168.60.2).

9. Student #2: Perform a ping from router R6 to router R5 (192.168.101.1). You will need
to specify a source address.

Lab 4.5 6VPE

Objective
The objective of this lab is to configure a VPRN service for IPv6 with BGP running between PE
and CE. Routers R5 and R6 will act as PEs for the VPRN services as they are dual stack routers
running both IPv4 and IPv6. Routers R9 and R10 will act as CEs and they are IPv6 routers.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 28

 Figure 17: Network topology for 6VPE

Recommended completion time: 30 minutes

Exercise

1. Student #1: Shut down OSPFv3 on router R1. Configure a VPRN service with service ID
700 with the following requirements:
a. Use 65000:70 as route distinguisher and route target values.
b. Configure the VPRN service to use LDP.
c. Use BGP as PE-CE protocol between routers R1 and R5.
d. On router R1, configure a VRF interface toward router R5 with address
2001:db8:1:5::1/64 using vlan ID 70.
e. Configure MP-BGP on router R1 to exchange both IPv4 and IPv6 VPN routes
between routers R1 and R2. Ensure that all VPN routes are advertised into
router R5.
f. On router R5, configure a router interface toward router R1 with address
2001:db8:1:5::5/64 using vlan ID 70.
g. Redistribute the address of a loopback interface named “dummy-loopback” on
router R5 across this VPRN service.

2. Student #2: Shut down OSPFv3 on router R2. Configure a VPRN service with service ID
700 with the following requirements:
a. Use 65000:70 as route distinguisher and route target values.
b. Configure the VPRN service to use LDP.
c. Use BGP as PE-CE protocol between routers R2 and R6.
d. On router R2, configure a VRF interface toward router R6 with address
2001:db8:2:6::2/64 using vlan ID 70.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 29

 e. Configure MP-BGP on router R2 to exchange both IPv4 and IPv6 VPN routes
between routers R1 and R2. Ensure that all VPN routes are advertised into
router R6.
f. On router R6, configure a router interface toward router R2 with address
2001:db8:2:6::6/64 using vlan ID 70.
g. Redistribute the address of a loopback interface named “dummy-loopback” on
router R6 across this VPRN service.

3. Verify that the VPRN service is operationally up.

4. Student #1: Perform a ping from router R5 to router R6 (2001:DB8:2:6::6).

5. Student #2: Perform a ping from router R6 to router R5 (2001:DB8:DD:501::1).

Lab 4.6 VPLS spoke termination on VPRN (OPTIONAL)

Objective
The objective of this lab is to configure a spoke SDP termination on VPLS and VPRN. This will
allow traffic exchanges between Layer 2 service (VPLS) and Layer 3 service (VPRN).

Figure 18: Network topology for VPLS termination on VPRN

Recommended completion time: 20 minutes

Exercise

1. Student #1: On router R1, configure a VPLS with service ID 800 with the following
requirements:

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 30

 a. Configure a SAP toward router R5 using vlan ID 80.
b. On router R5, configure an interface toward router R1 with IP address
192.168.80.1/24 using vlan ID 80.

2. Student #2: On router R2, configure a VPRN service with service ID 800 with the
following requirements:
a. Use 65000:80 as route distinguisher and route target values.
b. Configure the VPRN service to use LDP.
c. Create a VRF interface with IP address 192.168.80.2/24.

3. Student #1: On router R1, connect the VPLS to the VPRN service with service ID 800
that Student #2 configured.

4. Student #2: On router R2, connect the VPRN service to the VPLS with service ID 800
that Student #1 configured.

5. Verify that both the VPLS and the VPRN service are operationally up.

6. Student #1: Perform a ping from router R5 to VRF interface address (192.168.80.2).

7. Student #2: Perform a ping from router R2 to router R5 interface address

(192.168.80.1).

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 31

Lab Solution Set
Lab 1 Solutions: Basic IP Configuration

Lab 1.1 Physical connectivity

1. Verify that all the configured ports are operationally up before moving on to the next
section.

A:Metro1_R1# show port

===============================================================================
Ports on Slot 1
===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
1/1/1 Up Yes Up 1578 1578 - netw null gige
1/1/2 Up Yes Up 1578 1578 - netw null gige
1/1/3 Up Yes Up 1578 1578 - netw null gige
1/1/4 Up Yes Up 1578 1578 - netw null gige
1/1/5 Down No Down 1578 1578 - netw null gige
1/1/6 Down No Down 1578 1578 - netw null gige
1/1/7 Down No Down 1578 1578 - netw null gige
1/1/8 Down No Down 1578 1578 - netw null gige
1/1/9 Down No Down 1578 1578 - netw null gige
1/1/10 Down No Down 1578 1578 - netw null gige
1/2/1 Down No Down 1578 1578 - netw null gige
1/2/2 Down No Down 1578 1578 - netw null gige
1/2/3 Down No Down 1578 1578 - netw null gige
1/2/4 Down No Down 1578 1578 - netw null gige
1/2/5 Down No Down 1578 1578 - netw null gige
1/2/6 Down No Down 1578 1578 - netw null gige
1/2/7 Down No Down 1578 1578 - netw null gige
1/2/8 Down No Down 1578 1578 - netw null gige
1/2/9 Down No Down 1578 1578 - netw null gige
1/2/10 Down No Down 1578 1578 - netw null gige

===============================================================================
Ports on Slot A
===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
A/1 Up Yes Up 1514 1514 - netw null faste MDI

===============================================================================
Ports on Slot B
===============================================================================
Port Admin Link Port Cfg Oper LAG/ Port Port Port C/QS/S/XFP/
Id State State MTU MTU Bndl Mode Encp Type MDIMDX
-------------------------------------------------------------------------------
B/1 Up No Ghost 1514 1514 - netw null faste
===============================================================================
A:Metro1_R1#

Similar outputs should be seen on other routers.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 32

Lab 1.2 IP connectivity
1. All of the configured router interfaces should be operationally up.

R1:
A:Metro1_R1# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up/Down Network system
10.10.10.1/32 n/a
toR2 Up Up/Down Network 1/1/3
10.1.2.1/27 n/a
toR3 Up Up/Down Network 1/1/1
10.1.3.1/27 n/a
toR5 Up Up/Down Network 1/1/2
10.1.5.1/27 n/a
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
A:Metro1_R1#

R2:
A:Metro1_R2# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up/Down Network system
10.10.10.2/32 n/a
toR1 Up Up/Down Network 1/1/3
10.1.2.2/27 n/a
toR4 Up Up/Down Network 1/1/1
10.2.4.2/27 n/a
toR6 Up Up/Down Network 1/1/2
10.2.6.2/27 n/a
-------------------------------------------------------------------------------
Interfaces : 4
===============================================================================
A:Metro1_R2#

R3:
A:Metro1_R3# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up/Down Network system
10.10.10.3/32 n/a
toR1 Up Up/Down Network 1/1/1
10.1.3.3/27 n/a
toR4 Up Up/Down Network 1/1/2
10.3.4.3/27 n/a
-------------------------------------------------------------------------------
Interfaces : 3
===============================================================================

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 33

 A:Metro1_R3#

R4:
A:Metro1_R4# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up/Down Network system
10.10.10.4/32 n/a
toR2 Up Up/Down Network 1/1/1
10.2.4.4/27 n/a
toR3 Up Up/Down Network 1/1/2
10.3.4.4/27 n/a
-------------------------------------------------------------------------------
Interfaces : 3
===============================================================================
A:Metro1_R4#

R5:
A:Metro1_R5# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
loopback1-1 Up Up/Down Network loopback
192.168.1.1/32 n/a
loopback1-2 Up Up/Down Network loopback
192.168.1.2/32 n/a
loopback1-3 Up Up/Down Network loopback
192.168.1.3/32 n/a
system Up Up/Down Network system
10.10.10.5/32 n/a
toR1 Up Up/Down Network 1/1/2
10.1.5.5/27 n/a
-------------------------------------------------------------------------------
Interfaces : 5
===============================================================================
A:Metro1_R5#

R6:
A:Metro1_R6# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
loopback2-1 Up Up/Down Network loopback
192.168.2.1/32 n/a
loopback2-2 Up Up/Down Network loopback
192.168.2.2/32 n/a
loopback2-3 Up Up/Down Network loopback
192.168.2.3/32 n/a
system Up Up/Down Network system
10.10.10.6/32 n/a
toR2 Up Up/Down Network 1/1/2
10.2.6.6/27 n/a
-------------------------------------------------------------------------------
Interfaces : 5

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 34

 ===============================================================================
A:Metro1_R6#

Lab 1.3 IPv6 connectivity

1. Student #1: Configure IPv6 router interfaces on routers R1 and R5 according to Table
2. Enable IPv6 on interfaces between routers R1 and R5 but do not configure IPv6
addresses.

R1:
A:Metro1_R1# configure router interface "system"
A:Metro1_R1>config>router>if# ipv6 address 2001:db8:a:100::1/128
*A:Metro1_R1>config>router>if# back
*A:Metro1_R1>config>router# interface "toR5"
*A:Metro1_R1>config>router>if# ipv6

R5:
A:Metro1_R5# configure router interface "system"
A:Metro1_R5>config>router>if# ipv6 address 2001:db8:a:500::5/128
*A:Metro1_R5>config>router>if# back
*A:Metro1_R5>config>router# interface "toR1"
*A:Metro1_R5>config>router>if# ipv6
*A:Metro1_R5>config>router>if>ipv6# back
*A:Metro1_R5>config>router>if# back
*A:Metro1_R5>config>router# interface "loopback1-1"
*A:Metro1_R5>config>router>if# ipv6 address 2001:db8:a:501::1/128
*A:Metro1_R5>config>router>if# back
*A:Metro1_R5>config>router# interface "loopback1-2"
*A:Metro1_R5>config>router>if# ipv6 address 2001:db8:a:501::2/128
*A:Metro1_R5>config>router>if# back
*A:Metro1_R5>config>router# interface "loopback1-3"
*A:Metro1_R5>config>router>if# ipv6 address 2001:db8:a:501::3/128

2. Student #2: Configure IPv6 router interfaces on routers R2 and R6 according to Table
2. Enable IPv6 on interfaces between routers R1 and R5 but do not configure IPv6
addresses.

R2:
A:Metro1_R2# configure router interface "system"
A:Metro1_R2>config>router>if# ipv6 address 2001:db8:a:200::2/128
*A:Metro1_R2>config>router>if# back
*A:Metro1_R2>config>router# interface "toR6" ipv6

R6:
A:Metro1_R6# configure router interface "system"
A:Metro1_R6>config>router>if# ipv6 address 2001:db8:a:600::6/128
*A:Metro1_R6>config>router>if# back
*A:Metro1_R6>config>router# interface "toR2" ipv6
*A:Metro1_R6>config>router>if>ipv6# back
*A:Metro1_R6>config>router>if# back
*A:Metro1_R6>config>router# interface "loopback2-1"
*A:Metro1_R6>config>router>if# ipv6 address 2001:db8:a:601::1/128
*A:Metro1_R6>config>router>if# back
*A:Metro1_R6>config>router# interface "loopback2-2"
*A:Metro1_R6>config>router>if# ipv6 address 2001:db8:a:601::2/128
*A:Metro1_R6>config>router>if# back
*A:Metro1_R6>config>router# interface "loopback2-3"
*A:Metro1_R6>config>router>if# ipv6 address 2001:db8:a:601::3/128

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 35

Lab 2 IGP Configuration

Lab 2.1 IS-IS in a single area

1. Student #1: Configure an IS-IS network as per the Figure 4 with the following
requirements:
a. Configure a point-to-point connection between routers R1 and R2.
b. Configure a broadcast connection between routers R1 and R3.
c. Ensure that routers R1 and R3 system interface addresses are advertised into
IS-IS.
d. Configure routers R1 and R3 as level 1 and level 2 routers, respectively.

R1:
A:Metro1_R1# configure router isis
A:Metro1_R1>config>router>isis$ area-id 49.01
*A:Metro1_R1>config>router>isis$ interface "system"
*A:Metro1_R1>config>router>isis>if$ back
*A:Metro1_R1>config>router>isis$ interface "toR2" interface-type point-to-point
*A:Metro1_R1>config>router>isis$ interface "toR3" interface-type broadcast

R2:
A:Metro1_R2# configure router isis
A:Metro1_R2>config>router>isis$ area-id 49.01
*A:Metro1_R2>config>router>isis$ interface "toR1" interface-type point-to-point

R3:
A:Metro1_R3# configure router isis
A:Metro1_R3>config>router>isis$ area-id 49.01
*A:Metro1_R3>config>router>isis$ interface "system"
*A:Metro1_R3>config>router>isis>if$ back
*A:Metro1_R3>config>router>isis$ interface "toR1" interface-type broadcast

2. Student #2: Configure an IS-IS network as per the figure above with the following
requirements:
a. Configure a point-to-point connection between routers R2 and R4.
b. Configure a broadcast connection between routers R3 and R4.
c. Ensure that routers R2 and R4 system interface addresses are advertised into
IS-IS.
d. Configure routers R2 and R4 as level 1 and level 2 routers, respectively.
R2:
*A:Metro1_R2# configure router isis
*A:Metro1_R2>config>router>isis# interface "system"
*A:Metro1_R2>config>router>isis>if# back
*A:Metro1_R2>config>router>isis# interface "toR4" interface-type point-to-point

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 36

 R3:
*A:Metro1_R3# configure router isis
*A:Metro1_R3>config>router>isis# interface "toR4" interface-type broadcast

R4:
A:Metro1_R4# configure router isis
*A:Metro1_R4>config>router>isis# area-id 49.01
*A:Metro1_R4>config>router>isis# interface "toR2" interface-type point-to-point
*A:Metro1_R4>config>router>isis$ interface "toR3" interface-type broadcast
*A:Metro1_R4>config>router>isis$ interface "system"

3. Verify that level 1 and level 2 IS-IS adjacencies are up among all routers. Ensure that
each router can ping to all other routers’ system IP addresses.

Output from router R1 only:

*A:Metro1_R1# ping 10.10.10.2 count 1
PING 10.10.10.2 56 data bytes
64 bytes from 10.10.10.2: icmp_seq=1 ttl=64 time=1.30ms.

---- 10.10.10.2 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.30ms, avg = 1.30ms, max = 1.30ms, stddev = 0.000ms
*A:Metro1_R1#
*A:Metro1_R1# ping 10.10.10.3 count 1
PING 10.10.10.3 56 data bytes
64 bytes from 10.10.10.3: icmp_seq=1 ttl=64 time=1.41ms.

---- 10.10.10.3 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.41ms, avg = 1.41ms, max = 1.41ms, stddev = 0.000ms
*A:Metro1_R1#
*A:Metro1_R1# ping 10.10.10.4 count 1
PING 10.10.10.4 56 data bytes
64 bytes from 10.10.10.4: icmp_seq=1 ttl=63 time=1.95ms.

---- 10.10.10.4 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 1.95ms, avg = 1.95ms, max = 1.95ms, stddev = 0.000ms
*A:Metro1_R1#

4. Configure IS-IS to use the interface bandwidth as a reference for determining cost
similar to how OSPF determines its interface cost. Student #1 will configure routers R1
and R3, while Student #2 will configure routers R2 and R4.

R1:
*A:Metro1_R1# configure router isis
*A:Metro1_R1>config>router>isis# level 1 wide-metrics-only
*A:Metro1_R1>config>router>isis# level 2 wide-metrics-only
*A:Metro1_R1>config>router>isis# reference-bandwidth 100000000

R2:
*A:Metro1_R2# configure router isis
*A:Metro1_R2>config>router>isis# level 1 wide-metrics-only
*A:Metro1_R2>config>router>isis# level 2 wide-metrics-only
*A:Metro1_R2>config>router>isis# reference-bandwidth 100000000

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 37

 R3:
*A:Metro1_R3# configure router isis
*A:Metro1_R3>config>router>isis# level 1 wide-metrics-only
*A:Metro1_R3>config>router>isis# level 2 wide-metrics-only
*A:Metro1_R3>config>router>isis# reference-bandwidth 100000000

R4:
*A:Metro1_R4# configure router isis
*A:Metro1_R4>config>router>isis# level 1 wide-metrics-only
*A:Metro1_R4>config>router>isis# level 2 wide-metrics-only
*A:Metro1_R4>config>router>isis# reference-bandwidth 100000000

5. Student #1: Configure a simple password hello authentication between routers R1 and
R2. Use authentication key “secret”. Verify that the IS-IS adjacency is operationally
up between routers R1 and R2.

R1:
*A:Metro1_R1# configure router isis
*A:Metro1_R1>config>router>isis# interface "toR2"
*A:Metro1_R1>config>router>isis>if# hello-authentication
*A:Metro1_R1>config>router>isis>if# hello-authentication-type password
*A:Metro1_R1>config>router>isis>if# hello-authentication-key secret

R2:
*A:Metro1_R2# configure router isis
*A:Metro1_R2>config>router>isis# interface "toR1"
*A:Metro1_R2>config>router>isis>if# hello-authentication
*A:Metro1_R2>config>router>isis>if# hello-authentication-type password
*A:Metro1_R2>config>router>isis>if# hello-authentication-key secret

6. Student #2: Configure MD5 ‘hello authentication' between routers R3 and R4. Use
authentication key “md5-password”. Verify that the IS-IS adjacency is operationally up
between routers R3 and R4.

*A:Metro1_R3# configure router isis

*A:Metro1_R3>config>router>isis# interface "toR4"
*A:Metro1_R3>config>router>isis>if# hello-authentication
*A:Metro1_R3>config>router>isis>if# hello-authentication-type message-digest
*A:Metro1_R3>config>router>isis>if# hello-authentication-key md5-password

*A:Metro1_R4# configure router isis

*A:Metro1_R4>config>router>isis# interface "toR3"
*A:Metro1_R4>config>router>isis>if# hello-authentication
*A:Metro1_R4>config>router>isis>if# hello-authentication-type message-digest
*A:Metro1_R4>config>router>isis>if# hello-authentication-key md5-password

Lab 2.2 6over4 tunneling

Exercise

1. Student #1: Configure two IPv6 static routes on router R1 and one IPv6 static route on
router R5 using IPv6 over IPv4 tunneling. The goal is to make router R5 reach router

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 38

 R6 system address (2001:db8:a:600::6) and for router R6 to reach router R5 system
address (2001:db8:a:500::5).

R1:
*A:Metro1_R1# configure router static-route 2001:db8:a:600::6/128 indirect
10.10.10.2
*A:Metro1_R1# configure router static-route 2001:db8:a:500::5/128 next-hop
FE80::203:FAFF:FEAC:9757-toR5
*A:Metro1_R1#

R5:
A:Metro1_R5# configure router static-route 2001:db8:a:600::6/128 next-hop
FE80::216:4DFF:FE27:7291-toR1

2. Student #2: Configure two IPv6 static routes on router R2 and one IPv6 static route on
router R6 using IPv6 over IPv4 tunneling. The goal is to make router R5 to reach router
R6 system address (2001:db8:a:600::6) and for router R6 to reach router R5 system
address (2001:db8:a:500::5).

R2:
*A:Metro1_R2# configure router static-route 2001:db8:a:500::5/128 indirect
10.10.10.1
*A:Metro1_R2# configure router static-route 2001:db8:a:600::6/128 next-hop
FE80::216:4DFF:FE27:3439-toR6

R6:
A:Metro1_R6# configure router static-route 2001:db8:a:500::5/128 next-hop
FE80::216:4DFF:FE27:6F0D-toR2

3. Student #1: On router R5, verify that a ping to the IPv6 system interface address on
router R6 works.

*A:Metro1_R5# ping 2001:DB8:A:600::6 count 1

PING 2001:DB8:A:600::6 56 data bytes
64 bytes from 2001:DB8:A:600::6 icmp_seq=1 hlim=62 time=7.86ms.

---- 2001:DB8:A:600::6 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 7.86ms, avg = 7.86ms, max = 7.86ms, stddev = 0.000ms
*A:Metro1_R5#

4. Student #2: On router R6, verify that a ping to the IPv6 system interface address on
router R5 works.

*A:Metro1_R6# ping 2001:DB8:A:500::5 count 1

PING 2001:DB8:A:500::5 56 data bytes
64 bytes from 2001:DB8:A:500::5 icmp_seq=1 hlim=62 time=6.38ms.

---- 2001:DB8:A:500::5 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 6.38ms, avg = 6.38ms, max = 6.38ms, stddev = 0.000ms
*A:Metro1_R6# #

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 39

Lab 2.3 OSPF in a single area

1. Student #1: Configure an OSPF network with the following requirements:

a. Configure a point-to-point connection between routers R1 and R2.
b. Configure a broadcast connection between routers R1 and R3.
c. Ensure that routers R1 and R3 system addresses are advertised into OSPF.

R1:
*A:Metro1_R1# configure router ospf
*A:Metro1_R1>config>router>ospf$ area 0 interface "toR2" interface-type point-to-
point
*A:Metro1_R1>config>router>ospf$ area 0 interface "toR3" interface-type broadcast
*A:Metro1_R1>config>router>ospf$ area 0 interface "system"

R2:
*A:Metro1_R2# configure router ospf
*A:Metro1_R2>config>router>ospf$ area 0 interface "toR1" interface-type point-to-
point

R3:
*A:Metro1_R3# configure router ospf
*A:Metro1_R3>config>router>ospf$ area 0 interface "toR1" interface-type broadcast
*A:Metro1_R3>config>router>ospf$ area 0 interface "system"

2. Student #2: Configure an OSPF network with the following requirements:

a. Configure a point-to-point connection between routers R3 and R4.
b. Configure a broadcast connection between routers R2 and R4.
c. Ensure that routers R2 and R4 system addresses are advertised into OSPF.

R2:
*A:Metro1_R2# configure router ospf
*A:Metro1_R2>config>router>ospf# area 0 interface "toR4" interface-type broadcast
*A:Metro1_R2>config>router>ospf$ area 0 interface "system"

R3:
*A:Metro1_R3# configure router ospf
*A:Metro1_R3>config>router>ospf# area 0 interface "toR4" interface-type point-to-
point

R4:
*A:Metro1_R4# configure router ospf
*A:Metro1_R4>config>router>ospf# area 0 interface "toR2" interface-type broadcast
*A:Metro1_R4>config>router>ospf# area 0 interface "toR3" interface-type point-to-
point
*A:Metro1_R4>config>router>ospf# area 0 interface "system"

3. Ensurethat OSPF adjacencies are formed among all four routers.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 40

 Student #1: Verify the OSPF adjacencies on routers R1 and R2.
Student #2: Verify the OSPF adjacencies on routers R3 and R4.

R1:
*A:Metro1_R1# show router ospf neighbor

===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
toR2 10.10.10.2 Full 1 0 31
0.0.0.0
toR3 10.10.10.3 Full 1 0 32
0.0.0.0
-------------------------------------------------------------------------------
No. of Neighbors: 2
===============================================================================
*A:Metro1_R1#

R2:
*A:Metro1_R2# show router ospf neighbor

===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
toR1 10.10.10.1 Full 1 0 38
0.0.0.0
toR4 10.10.10.4 Full 1 0 37
0.0.0.0
-------------------------------------------------------------------------------
No. of Neighbors: 2
===============================================================================
*A:Metro1_R2#

R3:
*A:Metro1_R3# show router ospf neighbor

===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
toR1 10.10.10.1 Full 1 0 39
0.0.0.0
toR4 10.10.10.4 Full 1 0 36
0.0.0.0
-------------------------------------------------------------------------------
No. of Neighbors: 2
===============================================================================
*A:Metro1_R3#

R4:
*A:Metro1_R4# show router ospf neighbor

===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 41

 toR2 10.10.10.2 Full 1 0 34
0.0.0.0
toR3 10.10.10.3 Full 1 0 36
0.0.0.0
-------------------------------------------------------------------------------
No. of Neighbors: 2
===============================================================================
*A:Metro1_R4#

Lab 2.4 OSPF in multi-area

1. Student #1: Configure a point-to-point connection between routers R1 and R5 in OSPF
area 1. Ensure that router R5 system address is reachable to all routers.

R1:
*A:Metro1_R1# configure router ospf
*A:Metro1_R1>config>router>ospf# area 1 interface "toR5" interface-type point-to-
point

R5:
*A:Metro1_R5# configure router ospf
*A:Metro1_R5>config>router>ospf$ area 1 interface "toR1" interface-type point-to-
point
*A:Metro1_R5>config>router>ospf$ area 1 interface "system"

2. Student #2: Configure a point-to-point connection between routers R2 and R6 in OSPF

area 2. Ensure that router R6 system address is reachable to all routers.

R2:
*A:Metro1_R2# configure router ospf
*A:Metro1_R2>config>router>ospf# area 2 interface "toR6" interface-type point-to-
point

R6:
*A:Metro1_R6# configure router ospf
*A:Metro1_R6>config>router>ospf$ area 2 interface "toR2" interface-type point-to-
point
*A:Metro1_R6>config>router>ospf$ area 2 interface "system"

3. Student #1: Verify OSPF adjacencies are established in area 1.

Student #2: Verify OSPF adjacencies are established in area 2.

*A:Metro1_R1# show router ospf neighbor

===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 42

 -------------------------------------------------------------------------------
toR2 10.10.10.2 Full 1 0 35
0.0.0.0
toR3 10.10.10.3 Full 1 0 37
0.0.0.0
toR5 10.10.10.5 Full 1 0 35
0.0.0.1
-------------------------------------------------------------------------------
No. of Neighbors: 3
===============================================================================
*A:Metro1_R1#

*A:Metro1_R2# show router ospf neighbor

===============================================================================
OSPF Neighbors
===============================================================================
Interface-Name Rtr Id State Pri RetxQ TTL
Area-Id
-------------------------------------------------------------------------------
toR1 10.10.10.1 Full 1 0 35
0.0.0.0
toR4 10.10.10.4 Full 1 0 30
0.0.0.0
toR6 10.10.10.6 Full 1 0 36
0.0.0.2
-------------------------------------------------------------------------------
No. of Neighbors: 3
===============================================================================
*A:Metro1_R2#

4. Student #1: Advertise three loopback interfaces configured on router R5 into OSPF as
internal routes. Configure route summarization in area 1 so that routers in other areas
see only one address that represents the three loopback interface addresses on router
R5. Use the most specific prefix possible.

R5:
A:Metro1_R5# configure router ospf
A:Metro1_R5>config>router>ospf# area 1
A:Metro1_R5>config>router>ospf>area# interface "loopback1-1"
*A:Metro1_R5>config>router>ospf>area>if$ back
*A:Metro1_R5>config>router>ospf>area# interface "loopback1-2"
*A:Metro1_R5>config>router>ospf>area>if$ back
*A:Metro1_R5>config>router>ospf>area# interface "loopback1-3"

R1:
A:Metro1_R1# configure router ospf
A:Metro1_R1>config>router>ospf# area 1 area-range 192.168.1.0/30 advertise

5. Student #2: Advertise three loopback interfaces configured on router R6 into OSPF as
internal routes. Configure route summarization in area 2 so that routers in other areas
see only one address that represents the three loopback interface addresses on router
R6. Use the most specific prefix possible.
R6:
A:Metro1_R6# configure router ospf
A:Metro1_R6>config>router>ospf# area 2 interface "loopback2-1"
*A:Metro1_R6>config>router>ospf>area>if$ back
*A:Metro1_R6>config>router>ospf>area# interface "loopback2-2"
*A:Metro1_R6>config>router>ospf>area>if$ back

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 43

 *A:Metro1_R6>config>router>ospf>area# interface "loopback2-3"

R2:
A:Metro1_R2# configure router ospf
A:Metro1_R2>config>router>ospf# area 2 area-range 192.168.2.0/30 advertise

6. Student #1: Configure a loopback interface called dummy-loopback on router R5 with

address 192.168.11.1/32. Use a routing policy to redistribute this interface address
into OSPF.
*A:Metro1_R5# configure router interface dummy-loopback
*A:Metro1_R5>config>router>if$ address 192.168.11.1/32
*A:Metro1_R5>config>router>if$ loopback
*A:Metro1_R5>config>router>if$ exit all
*A:Metro1_R5# configure router policy-options
*A:Metro1_R5>config>router>policy-options# begin
*A:Metro1_R5>config>router>policy-options# prefix-list dummy-loopback
*A:Metro1_R5>config>router>policy-options>prefix-list$ prefix 192.168.11.1/32
*A:Metro1_R5>config>router>policy-options>prefix-list$ back
*A:Metro1_R5>config>router>policy-options# policy-statement dummy-loopback
*A:Metro1_R5>config>router>policy-options>policy-statement$ entry 10
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ from prefix-list
"dummy-loopback"
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ from protocol
direct
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R5>config>router>policy-options>policy-statement>entry>action$ back
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ back
*A:Metro1_R5>config>router>policy-options>policy-statement$ back
*A:Metro1_R5>config>router>policy-options# commit
*A:Metro1_R5>config>router>policy-options# exit all
*A:Metro1_R5# configure router ospf
*A:Metro1_R5>config>router>ospf# asbr
*A:Metro1_R5>config>router>ospf# export "dummy-loopback"

7. Student #2: Configure a loopback interface called “dummy-loopback” on router R6

with address 192.168.22.1/32. Use a routing policy to redistribute this interface
address into OSPF.

*A:Metro1_R6# configure router interface dummy-loopback

*A:Metro1_R6>config>router>if$ address 192.168.22.1/32
*A:Metro1_R6>config>router>if$ loopback
*A:Metro1_R6>config>router>if$ exit all
*A:Metro1_R6# configure router policy-options
*A:Metro1_R6>config>router>policy-options# begin
*A:Metro1_R6>config>router>policy-options# prefix-list dummy-loopback
*A:Metro1_R6>config>router>policy-options>prefix-list$ prefix 192.168.22.1/32
*A:Metro1_R6>config>router>policy-options>prefix-list$ back
*A:Metro1_R6>config>router>policy-options# policy-statement dummy-loopback-to-ospf
*A:Metro1_R6>config>router>policy-options>policy-statement$ entry 10
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ from prefix-list
"dummy-loopback"
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ from protocol
direct
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R6>config>router>policy-options>policy-statement>entry>action$ back
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ back
*A:Metro1_R6>config>router>policy-options>policy-statement$ back
*A:Metro1_R6>config>router>policy-options# commit
*A:Metro1_R6>config>router>policy-options# exit all
*A:Metro1_R6# configure router ospf
*A:Metro1_R6>config>router>ospf# asbr

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 44

 *A:Metro1_R6>config>router>ospf# export "dummy-loopback"

Lab 2.5 OSPFv3

1. Student #1: Configure an OSPFv3 network with the following requirements:

a. Configure a point-to-point interface on router R1 toward router R2 in area 0.
b. Configure authentication for the point-to-point interface on router R1 toward
router R2.
i. Configure a static IPSec security association (static-sa) using sha1
authentication.
ii. Specify an ascii key “ospfv3-password-nrs2”.
iii. Specify AH protocol and SPI value 300.
iv. Associate a bi-directional authentication for the point-to-point
interface on router R1 toward router R2.
c. Configure an OSPFv3 point-to-point connection between routers R1 and R5 in
area 1 according to Figure 8.
d. Ensure that router R1 IPv6 system address is advertised into area 0 and router
R5 IPv6 system address is advertised into area 1.

R1:
*A:Metro1_R1# configure router interface "toR2"
*A:Metro1_R1>config>router>if# ipv6
*A:Metro1_R1>config>router>if>ipv6# exit all
*A:Metro1_R1# configure router ospf3
*A:Metro1_R1>config>router>ospf3$ area 0 interface "toR2" interface-type point-to-
point
*A:Metro1_R1>config>router>ospf3$ area 0 interface "system"
*A:Metro1_R1>config>router>ospf3>area>if$ exit all
*A:Metro1_R1# configure ipsec static-sa ospfv3 create
*A:Metro1_R1>config>ipsec>static-sa# authentication sha1 ascii-key ospfv3-
password-nrs2
*A:Metro1_R1>config>ipsec>static-sa# protocol ah
*A:Metro1_R1>config>ipsec>static-sa# spi 300
*A:Metro1_R1>config>ipsec>static-sa# exit all
*A:Metro1_R1# configure router ospf3
*A:Metro1_R1>config>router>ospf3# area 0 interface "toR2" authentication
bidirectional "ospfv3"
*A:Metro1_R1>config>router>ospf3# area 1 interface "toR5" interface-type point-to-
point

R5:
*A:Metro1_R5# configure router ospf3
*A:Metro1_R5>config>router>ospf3$ area 1 interface "toR1" interface-type point-to-
point
*A:Metro1_R5>config>router>ospf3$ area 1 interface "system"

2. Student #2: Configure an OSPFv3 network with the following requirements:

a. Configure a point-to-point interface on router R2 toward router R1 in area 0.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 45

 b. Configure authentication for the point-to-point interface on router R2 toward
router R1.
i. Configure a static IPSec security association (static-sa) using sha1
authentication.
ii. Specify an ascii key “ospfv3-password-nrs2”.
iii. Specify AH protocol and SPI value 300.
iv. Associate a bi-directional authentication for the point-to-point
interface on router R2 toward router R1.
c. Configure an OSPFv3 point-to-point connection between routers R2 and R6 in
area 2 according to Figure 8.
d. Ensure that router R2 IPv6 system address is advertised into area 0 and router
R6 IPv6 system address is advertised into area 2.

R2:
*A:Metro1_R2# configure router interface "toR1" ipv6
*A:Metro1_R2>config>router>if>ipv6# exit all
*A:Metro1_R2# configure router ospf3
*A:Metro1_R2>config>router>ospf3$ area 0 interface "toR1" interface-type point-to-
point
*A:Metro1_R2>config>router>ospf3$ area 0 interface "system"
*A:Metro1_R2>config>router>ospf3>area>if$ exit all
*A:Metro1_R2# configure ipsec static-sa ospfv3 create
*A:Metro1_R2>config>ipsec>static-sa# authentication sha1 ascii-key ospfv3-
password-nrs2
*A:Metro1_R2>config>ipsec>static-sa# protocol ah
*A:Metro1_R2>config>ipsec>static-sa# spi 300
*A:Metro1_R2>config>ipsec>static-sa# exit all
*A:Metro1_R2# configure router ospf3
*A:Metro1_R2>config>router>ospf3# area 0 interface "toR1" authentication
bidirectional "ospfv3"
*A:Metro1_R2>config>router>ospf3# area 2 interface "toR6" interface-type point-to-
point

R6:
*A:Metro1_R6# configure router ospf3
*A:Metro1_R6>config>router>ospf3$ area 2 interface "toR2" interface-type point-to-
point
*A:Metro1_R6>config>router>ospf3$ area 2 interface "system"

3. Verify that OSPFv3 adjacencies in all areas are operationally up.

4. Student #1: Advertise the three loopback interfaces (loopback1-1, loopback1-2, and
loopback1-3) from router R5 to OSPFv3. Configure route summarization with the most
specific prefix possible in area 1 so that only one address is advertised to other areas
instead of three loopback interface addresses.

R5:
*A:Metro1_R5# configure router ospf3
*A:Metro1_R5>config>router>ospf3# area 1 interface "loopback1-1"
*A:Metro1_R5>config>router>ospf3>area>if$ back
*A:Metro1_R5>config>router>ospf3>area# interface "loopback1-2"
*A:Metro1_R5>config>router>ospf3>area>if$ back
*A:Metro1_R5>config>router>ospf3>area# interface "loopback1-3"

R1:

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 46

 *A:Metro1_R1# configure router ospf3
*A:Metro1_R1>config>router>ospf3# area 1 area-range 2001:db8:a:501::/126 advertise

a. Verify that router R6 can reach router R5 loopback interface addresses.

*A:Metro1_R6# ping 2001:DB8:A:501::1 count 1

PING 2001:DB8:A:501::1 56 data bytes
64 bytes from 2001:DB8:A:501::1 icmp_seq=1 hlim=62 time=4.60ms.

---- 2001:DB8:A:501::1 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 4.60ms, avg = 4.60ms, max = 4.60ms, stddev = 0.000ms
*A:Metro1_R6#

5. Student #2: Advertise the three loopback interfaces (loopback2-1, loopback2-2, and
loopback2-3) from router R6 to OSPFv3. Configure route summarization with the most
specific prefix possible in area 2 so that only one address is advertised to other areas
instead of three loopback interface addresses.

R6:
*A:Metro1_R6# configure router ospf3
*A:Metro1_R6>config>router>ospf3# area 2 interface "loopback2-1"
*A:Metro1_R6>config>router>ospf3>area>if$ back
*A:Metro1_R6>config>router>ospf3>area# interface "loopback2-2"
*A:Metro1_R6>config>router>ospf3>area>if$ back
*A:Metro1_R6>config>router>ospf3>area# interface "loopback2-3"

R2:
*A:Metro1_R2# configure router ospf3
*A:Metro1_R2>config>router>ospf3# area 2 area-range 2001:db8:a:601::/126 advertise

a. Verify that router R5 can reach router R6 loopback interface addresses.

*A:Metro1_R5# ping 2001:DB8:A:601::1 count 1
PING 2001:DB8:A:601::1 56 data bytes
64 bytes from 2001:DB8:A:601::1 icmp_seq=1 hlim=62 time=3.87ms.

---- 2001:DB8:A:601::1 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 3.87ms, avg = 3.87ms, max = 3.87ms, stddev = 0.000ms
*A:Metro1_R5#

6. Student #1: Configure a loopback interface named “dummy-loopback” on router R5

with address 2001:db8:dd:501::1/128. Configure a route policy to ensure all routers
can reach this loopback interface address.

*A:Metro1_R5# configure router interface "dummy-loopback"

*A:Metro1_R5>config>router>if# ipv6 address 2001:db8:dd:501::1/128
*A:Metro1_R5>config>router>if# loopback
*A:Metro1_R5>config>router>if# exit all
*A:Metro1_R5# configure router policy-options
*A:Metro1_R5>config>router>policy-options# begin
*A:Metro1_R5>config>router>policy-options# prefix-list "dummy-loopback"
*A:Metro1_R5>config>router>policy-options>prefix-list# prefix
2001:db8:dd:501::1/128
*A:Metro1_R5>config>router>policy-options>prefix-list# exit
*A:Metro1_R5>config>router>policy-options# commit
*A:Metro1_R5>config>router>policy-options# info

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 47

 ----------------------------------------------
prefix-list "dummy-loopback"
prefix 192.168.11.1/32 exact
prefix 2001:DB8:DD:501::1/128 exact
exit
policy-statement "dummy-loopback"
entry 10
from
protocol direct
prefix-list "dummy-loopback"
exit
action accept
exit
exit
exit
----------------------------------------------
*A:Metro1_R5>config>router>policy-options#
*A:Metro1_R5>config>router>policy-options# exit all
*A:Metro1_R5# configure router ospf3
*A:Metro1_R5>config>router>ospf3# asbr
*A:Metro1_R5>config>router>ospf3# export "dummy-loopback "

7. Student #2: Configure a loopback interface named “dummy-loopback” on router R6

with address 2001:db8:dd:601::1/128. Configure a route policy to ensure all routers
can reach this loopback interface address.

*A:Metro1_R6# configure router interface dummy-loopback

*A:Metro1_R6>config>router>if$ ipv6 address 2001:db8:dd:601::1/128
*A:Metro1_R6>config>router>if$ loopback
*A:Metro1_R6>config>router>if$ exit all
*A:Metro1_R6# configure router policy-options
*A:Metro1_R6>config>router>policy-options# begin
*A:Metro1_R6>config>router>policy-options# prefix-list "dummy-loopback"
*A:Metro1_R6>config>router>policy-options>prefix-list# prefix
2001:db8:dd:601::1/128
*A:Metro1_R6>config>router>policy-options>prefix-list# exit
*A:Metro1_R6>config>router>policy-options# commit
*A:Metro1_R6>config>router>policy-options# info
----------------------------------------------
prefix-list "dummy-loopback"
prefix 192.168.22.1/32 exact
prefix 2001:DB8:DD:601::1/128 exact
exit
policy-statement "dummy-loopback"
entry 10
from
protocol direct
prefix-list "dummy-loopback"
exit
action accept
exit
exit
exit
----------------------------------------------
*A:Metro1_R6>config>router>policy-options# exit all
*A:Metro1_R6# configure router ospf3
*A:Metro1_R6>config>router>ospf3# asbr
*A:Metro1_R6>config>router>ospf3# export "dummy-loopback"
*A:Metro1_R6>config>router>ospf3#

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 48

Lab 3 MPLS Configuration

Lab 3.1 LDP

1. Student #1: Configure Link LDP on all interfaces on routers R1, R3 and R5.
R1:
A:Metro1_R1# configure router ldp
*A:Metro1_R1>config>router>ldp$ interface-parameters interface "toR2"
*A:Metro1_R1>config>router>ldp>if-params>if$ back
*A:Metro1_R1>config>router>ldp>if-params$ interface "toR3"
*A:Metro1_R1>config>router>ldp>if-params>if$ back
*A:Metro1_R1>config>router>ldp>if-params$ interface "toR5"

R3:
A:Metro1_R3# configure router ldp
*A:Metro1_R3>config>router>ldp$ interface-parameters interface "toR1"
*A:Metro1_R3>config>router>ldp>if-params>if$ back
*A:Metro1_R3>config>router>ldp>if-params$ interface "toR4"

R5:
A:Metro1_R5# configure router ldp
*A:Metro1_R5>config>router>ldp$ interface-parameters interface "toR1"

2. Student #2: Configure Link LDP on all interfaces on routers R2, R4, and R6.

R2:
A:Metro1_R2# configure router ldp
*A:Metro1_R2>config>router>ldp$ interface-parameters interface "toR1"
*A:Metro1_R2>config>router>ldp>if-params>if$ back
*A:Metro1_R2>config>router>ldp>if-params$ interface "toR4"
*A:Metro1_R2>config>router>ldp>if-params>if$ back
*A:Metro1_R2>config>router>ldp>if-params$ interface "toR6"

R4:
A:Metro1_R4# configure router ldp
*A:Metro1_R4>config>router>ldp$ interface-parameters interface "toR2"
*A:Metro1_R4>config>router>ldp>if-params>if$ back
*A:Metro1_R4>config>router>ldp>if-params$ interface "toR3"

R6:
A:Metro1_R6# configure router ldp
*A:Metro1_R6>config>router>ldp$ interface-parameters interface "toR2"

3. Verify all LDP interfaces are up and that each router has label bindings for all other
routers.

R1:
*A:Metro1_R1# show router ldp bindings

===============================================================================
LDP LSR ID: 10.10.10.1
===============================================================================
Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn
S - Status Signaled Up, D - Status Signaled Down

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 49

 E - EPipe Service, V - VPLS Service, M - Mirror Service
A - Apipe Service, F - Fpipe Service, I – IES Service, R – VPRN Service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service
BU - Alternate Next-hop for Fast Re-Route, TLV - (Type, Length: Value)
===============================================================================
LDP Prefix Bindings
===============================================================================
Prefix IngLbl EgrLbl EgrIntf/ EgrNextHop
Peer LspId
-------------------------------------------------------------------------------
10.10.10.1/32 131071U -- -- --
10.10.10.2
10.10.10.1/32 131071U -- -- --
10.10.10.3
10.10.10.1/32 131071U -- -- --
10.10.10.5
10.10.10.2/32 -- 131071 1/1/3 10.1.2.2
10.10.10.2
10.10.10.2/32 131068U 131068 -- --
10.10.10.3
10.10.10.2/32 131068U 131068 -- --
10.10.10.5
10.10.10.3/32 131070U 131069 -- --
10.10.10.2
10.10.10.3/32 -- 131071 1/1/1 10.1.3.3
10.10.10.3
10.10.10.3/32 131070U 131069 -- --
10.10.10.5
10.10.10.4/32 131067N 131067 1/1/3 10.1.2.2
10.10.10.2
10.10.10.4/32 131067U 131067 -- --
10.10.10.3
10.10.10.4/32 131067U 131067 -- --
10.10.10.5
10.10.10.5/32 131069U 131068 -- --
10.10.10.2
10.10.10.5/32 131069U 131069 -- --
10.10.10.3
10.10.10.5/32 -- 131071 1/1/2 10.1.5.5
10.10.10.5
10.10.10.6/32 131066N 131066 1/1/3 10.1.2.2
10.10.10.2
10.10.10.6/32 131066U 131066 -- --
10.10.10.3
10.10.10.6/32 131066U 131066 -- --
10.10.10.5
-------------------------------------------------------------------------------
No. of Prefix Bindings: 18
=============================================================================== :
:
:
*A:Metro1_R1#

4. Student #1: Configure router R5 to generate label bindings for its three loopback
interface addresses (loopback1-1, loopback1-2, and loopback1-3). Ensure that all
routers have three label bindings for router R5’s three loopback interface addresses.
R5:
*A:Metro1_R5# configure router policy-options
*A:Metro1_R5>config>router>policy-options# begin
*A:Metro1_R5>config>router>policy-options# prefix-list loopback
*A:Metro1_R5>config>router>policy-options>prefix-list$ prefix 192.168.1.1/32
*A:Metro1_R5>config>router>policy-options>prefix-list$ prefix 192.168.1.2/32
*A:Metro1_R5>config>router>policy-options>prefix-list$ prefix 192.168.1.3/32
*A:Metro1_R5>config>router>policy-options>prefix-list$ exit
*A:Metro1_R5>config>router>policy-options# policy-statement loopback
*A:Metro1_R5>config>router>policy-options>policy-statement$ entry 10

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 50

 *A:Metro1_R5>config>router>policy-options>policy-statement>entry$ from prefix-list
"loopback"
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R5>config>router>policy-options>policy-statement>entry>action$ exit
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ exit
*A:Metro1_R5>config>router>policy-options>policy-statement$ exit
*A:Metro1_R5>config>router>policy-options# commit
*A:Metro1_R5>config>router>policy-options# exit all
*A:Metro1_R5# configure router ldp export "loopback"
*A:Metro1_R5# configure router ldp aggregate-prefix-match

R2:
*A:Metro1_R2# configure router ldp aggregate-prefix-match

R6:
*A:Metro1_R6# configure router ldp aggregate-prefix-match

5. Student #2: Configure router R6 to generate label bindings for its three loopback
interface addresses (loopback2-1, loopback2-2, and loopback2-3). Ensure that all
routers have three label bindings for router R6’s three loopback interface addresses.
R6:
A:Metro1_R6# configure router policy-options
A:Metro1_R6>config>router>policy-options# begin
A:Metro1_R6>config>router>policy-options# prefix-list loopback
A:Metro1_R6>config>router>policy-options>prefix-list$ prefix 192.168.2.1/32 exact
A:Metro1_R6>config>router>policy-options>prefix-list$ prefix 192.168.2.2/32 exact
A:Metro1_R6>config>router>policy-options>prefix-list$ prefix 192.168.2.3/32 exact
A:Metro1_R6>config>router>policy-options>prefix-list$ exit
A:Metro1_R6>config>router>policy-options# policy-statement loopback
A:Metro1_R6>config>router>policy-options>policy-statement$ entry 10
A:Metro1_R6>config>router>policy-options>policy-statement>entry$ from prefix-list
"loopback"
A:Metro1_R6>config>router>policy-options>policy-statement>entry$ action accept
A:Metro1_R6>config>router>policy-options>policy-statement>entry>action$ exit
A:Metro1_R6>config>router>policy-options>policy-statement>entry$ exit
A:Metro1_R6>config>router>policy-options>policy-statement$ exit
A:Metro1_R6>config>router>policy-options# commit
*A:Metro1_R6>config>router>policy-options# exit all
*A:Metro1_R6# configure router ldp export "loopback"

R1:
A:Metro1_R1# configure router ldp aggregate-prefix-match

R3:
A:Metro1_R3# configure router ldp aggregate-prefix-match

R4:
A:Metro1_R4# configure router ldp aggregate-prefix-match

Lab 3.2 Constraint-based RSVP-TE LSPs

Exercise

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 51

1. Student #1: Configure an LSP named “toR2-1” from router R1 to router R2 using a
fully loose path.

R1:
A:Metro1_R1# configure router mpls
*A:Metro1_R1>config>router>mpls$ interface "toR2"
*A:Metro1_R1>config>router>mpls>if$ exit
*A:Metro1_R1>config>router>mpls$ interface "toR3"
*A:Metro1_R1>config>router>mpls>if$ exit
*A:Metro1_R1>config>router>mpls$ no shutdown
*A:Metro1_R1>config>router>mpls$ path loose
*A:Metro1_R1>config>router>mpls>path$ no shutdown
*A:Metro1_R1>config>router>mpls>path$ back
*A:Metro1_R1>config>router>mpls$ lsp toR2-1
*A:Metro1_R1>config>router>mpls>lsp$ to 10.10.10.2
*A:Metro1_R1>config>router>mpls>lsp$ primary "loose"
*A:Metro1_R1>config>router>mpls>lsp>primary$ back
*A:Metro1_R1>config>router>mpls>lsp# cspf
*A:Metro1_R1>config>router>mpls>lsp$ no shutdown
*A:Metro1_R1>config>router>mpls>lsp$ exit
*A:Metro1_R1>config>router>mpls$ exit all
*A:Metro1_R1# configure router rsvp no shutdown
*A:Metro1_R1# configure router ospf traffic-engineering

R3:
*A:Metro1_R3# configure router mpls interface "toR4"
*A:Metro1_R3>config>router>mpls>if$ back
*A:Metro1_R3>config>router>mpls# no shutdown
*A:Metro1_R3>config>router>mpls# back
*A:Metro1_R3>config>router# rsvp no shutdown
*A:Metro1_R3>config>router# ospf traffic-engineering

R4:
A:Metro1_R4# configure router mpls interface "toR2"
*A:Metro1_R4>config>router>mpls>if$ back
*A:Metro1_R4>config>router>mpls$ interface "toR3"
*A:Metro1_R4>config>router>mpls>if$ back
*A:Metro1_R4>config>router>mpls$ no shutdown
*A:Metro1_R4>config>router>mpls$ back
*A:Metro1_R4>config>router# rsvp no shutdown
*A:Metro1_R4>config>router# ospf traffic-engineering

2. Student #2: Configure an LSP named “toR1-1” from router R2 to router R1 using a
fully loose path.

R2:
A:Metro1_R2# configure router mpls
*A:Metro1_R2>config>router>mpls$ interface "toR1"
*A:Metro1_R2>config>router>mpls>if$ back
*A:Metro1_R2>config>router>mpls$ interface "toR4"
*A:Metro1_R2>config>router>mpls>if$ back
*A:Metro1_R2>config>router>mpls$ path loose
*A:Metro1_R2>config>router>mpls>path$ no shutdown
*A:Metro1_R2>config>router>mpls>path$ back
*A:Metro1_R2>config>router>mpls$ lsp toR1-1
*A:Metro1_R2>config>router>mpls>lsp$ to 10.10.10.1
*A:Metro1_R2>config>router>mpls>lsp$ primary "loose"
*A:Metro1_R2>config>router>mpls>lsp>primary$ back
*A:Metro1_R2>config>router>mpls>lsp$ cspf
*A:Metro1_R2>config>router>mpls>lsp$ no shutdown
*A:Metro1_R2>config>router>mpls>lsp$ exit all
*A:Metro1_R2# configure router rsvp no shutdown
*A:Metro1_R2# configure router mpls no shutdown

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 52

 *A:Metro1_R2# configure router ospf traffic-engineering

R3:
*A:Metro1_R3# configure router mpls interface "toR1"
*A:Metro1_R3>config>router>mpls>if$ back
*A:Metro1_R3>config>router>mpls# no shutdown
*A:Metro1_R3>config>router>mpls# back
*A:Metro1_R3>config>router# rsvp no shutdown
*A:Metro1_R3>config>router# ospf traffic-engineering

R4:
*A:Metro1_R4# configure router mpls interface "toR3"
*A:Metro1_R4>config>router>mpls>if# back
*A:Metro1_R4>config>router>mpls# no shutdown
*A:Metro1_R4>config>router>mpls# back
*A:Metro1_R4>config>router# rsvp no shutdown
*A:Metro1_R4>config>router# ospf traffic-engineering

3. Student #1: Configure an LSP named “toR2-2” from router R1 to router R2. Use the
TE metric to make this LSP follow the path R1-R3-R4-R2.

*A:Metro1_R1# configure router mpls interface "toR2" te-metric 8000

*A:Metro1_R1# configure router mpls lsp "toR2-2"
*A:Metro1_R1>config>router>mpls>lsp# to 10.10.10.2
*A:Metro1_R1>config>router>mpls>lsp# cspf use-te-metric
*A:Metro1_R1>config>router>mpls>lsp# primary "loose"
*A:Metro1_R1>config>router>mpls>lsp>primary$ back
*A:Metro1_R1>config>router>mpls>lsp# no shutdown

4. Student #2: Configure an LSP named “toR1-2” from router R2 to router R1. Use a hop
limit to make this LSP follow a direct path from router R2 to router R1.

*A:Metro1_R2# configure router mpls lsp toR1-2

*A:Metro1_R2>config>router>mpls>lsp$ to 10.10.10.1
*A:Metro1_R2>config>router>mpls>lsp$ cspf
*A:Metro1_R2>config>router>mpls>lsp$ hop-limit 2
*A:Metro1_R2>config>router>mpls>lsp$ primary "loose"
*A:Metro1_R2>config>router>mpls>lsp>primary$ back
*A:Metro1_R2>config>router>mpls>lsp$ no shutdown
*A:Metro1_R2>config>router>mpls>lsp$ exit all

5. Student #1: Configure an LSP named “toR2-3” from router R1 to router R2. Use an
administrative group to make this LSP follow the path R1-R3-R4-R2.

*A:Metro1_R1# configure router mpls

*A:Metro1_R1>config>router>mpls# admin-group red 1
*A:Metro1_R1>config>router>mpls# interface "toR2" admin-group "red"
*A:Metro1_R1>config>router>mpls# lsp toR2-3
*A:Metro1_R1>config>router>mpls>lsp$ to 10.10.10.2
*A:Metro1_R1>config>router>mpls>lsp$ cspf
*A:Metro1_R1>config>router>mpls>lsp$ exclude "red"
*A:Metro1_R1>config>router>mpls>lsp$ primary "loose"
*A:Metro1_R1>config>router>mpls>lsp>primary$ back
*A:Metro1_R1>config>router>mpls>lsp$ no shutdown

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 53

6. Student #2: Configure an LSP named “toR1-3” from router R2 to router R1. Use a
strict path to make this LSP follow the path R2-R4-R3-R1.

*A:Metro1_R2# configure router mpls

*A:Metro1_R2>config>router>mpls# path toR1-strict
*A:Metro1_R2>config>router>mpls>path$ hop 10 10.10.10.4 strict
*A:Metro1_R2>config>router>mpls>path$ hop 20 10.10.10.3 strict
*A:Metro1_R2>config>router>mpls>path$ hop 30 10.10.10.1 strict
*A:Metro1_R2>config>router>mpls>path$ no shutdown
*A:Metro1_R2>config>router>mpls>path$ exit all
*A:Metro1_R2# configure router mpls lsp toR1-3
*A:Metro1_R2>config>router>mpls>lsp$ to 10.10.10.1
*A:Metro1_R2>config>router>mpls>lsp$ primary "toR1-strict"
*A:Metro1_R2>config>router>mpls>lsp>primary$ back
*A:Metro1_R2>config>router>mpls>lsp$ no shutdown

7. Verify that all LSPs are operationally up.

R1:
*A:Metro1_R1# show router mpls lsp

===============================================================================
MPLS LSPs (Originating)
===============================================================================
LSP Name To Tun Fastfail Adm Opr
Id Config
-------------------------------------------------------------------------------
toR2-1 10.10.10.2 1 No Up Up
toR2-2 10.10.10.2 2 No Up Up
toR2-3 10.10.10.2 3 No Up Up
-------------------------------------------------------------------------------
LSPs : 3
===============================================================================
*A:Metro1_R1#

R2:
*A:Metro1_R2# show router mpls lsp

===============================================================================
MPLS LSPs (Originating)
===============================================================================
LSP Name To Tun Fastfail Adm Opr
Id Config
-------------------------------------------------------------------------------
toR1-1 10.10.10.1 1 No Up Up
toR1-2 10.10.10.1 2 No Up Up
toR1-3 10.10.10.1 3 No Up Up
-------------------------------------------------------------------------------
LSPs : 3
===============================================================================
*A:Metro1_R2#

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 54

Lab 3.3 RSVP bandwidth reservation
Exercise

1. Student #1: Configure an LSP named “toR4-1” on router R1 to router R4 with the
following requirements:
a. Change the bandwidth subscription rate to 50 for router R1 interface toward
router R2.
b. Configure the primary path with a bandwidth requirement of 300 Mbps, and a
setup and hold priority of 2.
c. Ensure that the primary path uses the path R1-R2-R4 by configuring one strict
hop.
d. Configure a standby secondary path with bandwidth requirement of 600 Mbps.
e. Ensure that the secondary path uses the path R1-R3-R4 by configuring an admin
group.

:Metro1_R1# configure router rsvp interface "toR2" subscription 50

*A:Metro1_R1# configure router mpls path toR4-strict
*A:Metro1_R1>config>router>mpls>path$ hop 10 10.10.10.2 strict
*A:Metro1_R1>config>router>mpls>path$ no shutdown
*A:Metro1_R1>config>router>mpls>path$ back
*A:Metro1_R1>config>router>mpls# lsp toR4-1
*A:Metro1_R1>config>router>mpls>lsp$ to 10.10.10.4
*A:Metro1_R1>config>router>mpls>lsp$ cspf
*A:Metro1_R1>config>router>mpls>lsp$ primary "toR4-strict"
*A:Metro1_R1>config>router>mpls>lsp>primary$ bandwidth 300
*A:Metro1_R1>config>router>mpls>lsp>primary$ priority 2 2
*A:Metro1_R1>config>router>mpls>lsp>primary$ back
*A:Metro1_R1>config>router>mpls>lsp$ secondary "loose"
*A:Metro1_R1>config>router>mpls>lsp>secondary$ bandwidth 600
*A:Metro1_R1>config>router>mpls>lsp>secondary$ standby
*A:Metro1_R1>config>router>mpls>lsp>secondary$ exclude "red"
*A:Metro1_R1>config>router>mpls>lsp>secondary$ back
*A:Metro1_R1>config>router>mpls>lsp$ no shutdown

f. Verify the total bandwidth and the reservable bandwidth on router R1 interface
toward router R2, and on router R1 interface toward router R3.

*A:Metro1_R1# show router rsvp interface "toR2"

===============================================================================
RSVP Interface : toR2
===============================================================================
Interface Total Active Total BW Resv BW Adm Opr
Sessions Sessions (Mbps) (Mbps)
-------------------------------------------------------------------------------
toR2 2 2 500 300 Up Up
===============================================================================
*A:Metro1_R1#

*A:Metro1_R1# show router rsvp interface "toR3"

===============================================================================
RSVP Interface : toR3
===============================================================================
Interface Total Active Total BW Resv BW Adm Opr

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 55

 Sessions Sessions (Mbps) (Mbps)
-------------------------------------------------------------------------------
toR3 3 3 1000 600 Up Up
===============================================================================
*A:Metro1_R1#

The total bandwidth on router R1 interface toward router R2 is 500 Mbps because
50% subscription is configured on the interface with 1Gbps bandwidth capability.
300Mbps have been used by the primary path of this LSP.

The total bandwidth on router R1 interface toward router R3 is 1Gbps because no

subscription is configured on the interface and this interface has 1Gbps bandwidth
capability. 600Mbps have been used by the secondary path of this LSP.

2. Student #2: Configure an LSP named “toR3-1” on router R2 to R3 with the following
requirements:
a. Change the bandwidth subscription rate to 50 for router R2 interface toward
router R1.
b. Configure the primary path with a bandwidth requirement of 300 Mbps and a
setup and hold priority of 3.
c. Ensure that the primary path uses a strict path R2-R1-R3.
d. Configure a standby secondary path with bandwidth requirement of 600 Mbps.
e. Ensure that it uses a strict path R2-R4-R3.

A:Metro1_R2# configure router rsvp interface "toR1" subscription 50

*A:Metro1_R2# configure router mpls path toR3-strict
*A:Metro1_R2>config>router>mpls>path$ hop 10 10.10.10.1 strict
*A:Metro1_R2>config>router>mpls>path$ hop 20 10.10.10.3 strict
*A:Metro1_R2>config>router>mpls>path$ no shutdown
*A:Metro1_R2>config>router>mpls>path$ back
*A:Metro1_R2>config>router>mpls# path toR3-strict2
*A:Metro1_R2>config>router>mpls>path$ hop 10 10.10.10.4 strict
*A:Metro1_R2>config>router>mpls>path$ hop 20 10.10.10.3 strict
*A:Metro1_R2>config>router>mpls>path$ no shutdown
*A:Metro1_R2>config>router>mpls>path$ back
*A:Metro1_R2>config>router>mpls# lsp toR3-1
*A:Metro1_R2>config>router>mpls>lsp$ to 10.10.10.3
*A:Metro1_R2>config>router>mpls>lsp$ cspf
*A:Metro1_R2>config>router>mpls>lsp$ primary "toR3-strict"
*A:Metro1_R2>config>router>mpls>lsp>primary$ bandwidth 300
*A:Metro1_R2>config>router>mpls>lsp>primary$ priority 3 3
*A:Metro1_R2>config>router>mpls>lsp>primary$ back
*A:Metro1_R2>config>router>mpls>lsp$ secondary "toR3-strict2"
*A:Metro1_R2>config>router>mpls>lsp>secondary$ standby
*A:Metro1_R2>config>router>mpls>lsp>secondary$ bandwidth 600
*A:Metro1_R2>config>router>mpls>lsp>secondary$ back
*A:Metro1_R2>config>router>mpls>lsp$ no shutdown

f. Verify the total bandwidth and reservable bandwidth on router R2 interface

toward router R1, and on router R2 interface toward router R4.

*A:Metro1_R2# show router rsvp interface "toR1"

===============================================================================
RSVP Interface : toR1
===============================================================================
Interface Total Active Total BW Resv BW Adm Opr

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 56

 Sessions Sessions (Mbps) (Mbps)
-------------------------------------------------------------------------------
toR1 3 3 500 300 Up Up
===============================================================================
*A:Metro1_R2#

Lab 3.4 RSVP one-to-one Fast Reroute

1. Student #1: Configure one-to-one fast reroute on the LSP named “toR4-1”.

A:Metro1_R1# configure router mpls lsp "toR4-1" fast-reroute one-to-one

2. Student #2: Configure one-to-one fast reroute on the LSP named “toR3-1”.

A:Metro1_R2# configure router mpls lsp "toR3-1" fast-reroute one-to-one

3. Verify that LSPs are operationally up.

R1:
*A:Metro1_R1# show router mpls lsp "toR4-1" path detail

===============================================================================
MPLS LSP toR4-1 Path (Detail)
===============================================================================
Legend :
@ - Detour Available # - Detour In Use
b - Bandwidth Protected n - Node Protected
s - Soft Preemption
S - Strict L - Loose
===============================================================================
-------------------------------------------------------------------------------
LSP toR4-1 Path loose
-------------------------------------------------------------------------------
LSP Name : toR4-1 Path LSP ID : 35330
From : 10.10.10.1 To : 10.10.10.4
Adm State : Up Oper State : Up
Path Name : loose Path Type : Standby
Path Admin : Up Path Oper : Up
OutInterface: 1/1/1 Out Label : 131056
Path Up Time: 0d 00:12:24 Path Dn Time: 0d 00:00:00
Retry Limit : 0 Retry Timer : 30 sec
RetryAttempt: 0 NextRetryIn : 0 sec

Adspec : Disabled Oper Adspec : Disabled

CSPF : Enabled Oper CSPF : Enabled
CSPF-FL : Disabled Oper CSPF-FL: Disabled
Least Fill : Disabled Oper LeastF*: Disabled
Prop Adm Grp: Disabled Oper PropAG : Disabled

Neg MTU : 1564 Oper MTU : 1564

Bandwidth : 600 Mbps Oper Bw : 600 Mbps
Hop Limit : 255 Oper HopLim*: 255
Record Route: Record Oper RecRou*: Record
Record Label: Record Oper RecLab*: Record
SetupPriori*: 7 Oper SetupP*: 7
Hold Priori*: 0 Oper HoldPr*: 0

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 57

 Class Type : 0 Oper CT : 0
Include Grps: Oper InclGr*:
None None
Exclude Grps: Oper ExclGr*:
red red

Adaptive : Enabled Oper Metric : 200

Preference : 255
Path Trans : 1 CSPF Queries: 1
Failure Code: noError Failure Node: n/a
ExplicitHops:
No Hops Specified
Actual Hops :
10.1.3.1(10.10.10.1) Record Label : N/A
-> 10.1.3.3(10.10.10.3) Record Label : 131056
-> 10.3.4.4(10.10.10.4) Record Label : 131056
ComputedHops:
10.1.3.1(S) -> 10.1.3.3(S) -> 10.3.4.4(S)
Srlg : Disabled
SrlgDisjoint: False
ResigEligib*: False
LastResignal: n/a CSPF Metric : 200
-------------------------------------------------------------------------------
LSP toR4-1 Path toR4-strict
-------------------------------------------------------------------------------
LSP Name : toR4-1 Path LSP ID : 35332
From : 10.10.10.1 To : 10.10.10.4
Adm State : Up Oper State : Up
Path Name : toR4-strict Path Type : Primary
Path Admin : Up Path Oper : Up
OutInterface: 1/1/3 Out Label : 131053
Path Up Time: 0d 00:12:24 Path Dn Time: 0d 00:00:00
Retry Limit : 0 Retry Timer : 30 sec
RetryAttempt: 0 NextRetryIn : 0 sec

Adspec : Disabled Oper Adspec : Disabled

CSPF : Enabled Oper CSPF : Enabled
CSPF-FL : Disabled Oper CSPF-FL: Disabled
Least Fill : Disabled Oper LeastF*: Disabled
FRR : Enabled Oper FRR : Enabled
FRR NodePro*: Enabled Oper FRR NP : Enabled
FR Hop Limit: 16 Oper FRHopL*: 16
Prop Adm Grp: Disabled Oper PropAG : Disabled

Neg MTU : 1564 Oper MTU : 1564

Bandwidth : 300 Mbps Oper Bw : 300 Mbps
Hop Limit : 255 Oper HopLim*: 255
Record Route: Record Oper RecRou*: Record
Record Label: Record Oper RecLab*: Record
SetupPriori*: 2 Oper SetupP*: 2
Hold Priori*: 2 Oper HoldPr*: 2
Class Type : 0 Oper CT : 0
Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
Include Grps: Oper InclGr*:
None None
Exclude Grps: Oper ExclGr*:
None None

Adaptive : Enabled Oper Metric : 200

Preference : n/a
Path Trans : 2 CSPF Queries: 2
Failure Code: noError Failure Node: n/a
ExplicitHops:
10.1.2.2(S)
Actual Hops :
10.1.2.1(10.10.10.1) @ n Record Label : N/A
-> 10.1.2.2(10.10.10.2) @ Record Label : 131053

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 58

 -> 10.2.4.4(10.10.10.4) Record Label : 131052
ComputedHops:
10.1.2.1(S) -> 10.1.2.2(S) -> 10.2.4.4(S)
ResigEligib*: False
LastResignal: n/a CSPF Metric : 200
Last MBB :
MBB Type : ConfigChange MBB State : Success
Ended At : 02/12/2013 07:32:20 Old Metric : 200
Signaled BW: 300 Mbps

DetourStatus: Standby DetourType : Originate

DetourAvoid*: 10.10.10.2 DetourOrigin: 10.10.10.1
SetupPriori*: 2 Hold Priori*: 2
Class Type : 0
DetourActiv*: n/a DetourUpTime: 0d 00:00:55
InInterface : n/a InLabel : n/a
OutInterface: 1/1/1 OutLabel : 131054
NextHop : 10.1.3.3
ExplicitHops:
10.1.3.1(S) -> 10.1.3.3(S) -> 10.3.4.4(S)

DetourStatus: Up DetourType : Terminate

DetourAvoid*: 10.2.4.4 DetourOrigin: 10.10.10.2
SetupPriori*: 2 Hold Priori*: 2
Class Type : 0
InInterface : 1/1/3 InLabel : 131055
PreviousHop : 10.1.2.2
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Metro1_R1#

Router R1 provides both node protection and link protection for router R2 as
indicated by symbols “@” and “n”. Router R2 provides link protection for router
R4.

R2:
*A:Metro1_R2# show router mpls lsp "toR3-1" path detail

===============================================================================
MPLS LSP toR3-1 Path (Detail)
===============================================================================
Legend :
@ - Detour Available # - Detour In Use
b - Bandwidth Protected n - Node Protected
s - Soft Preemption
S - Strict L - Loose
===============================================================================
-------------------------------------------------------------------------------
LSP toR3-1 Path toR3-strict
-------------------------------------------------------------------------------
LSP Name : toR3-1 Path LSP ID : 60932
From : 10.10.10.2 To : 10.10.10.3
Adm State : Up Oper State : Up
Path Name : toR3-strict Path Type : Primary
Path Admin : Up Path Oper : Up
OutInterface: 1/1/3 Out Label : 131054
Path Up Time: 0d 00:09:47 Path Dn Time: 0d 00:00:00
Retry Limit : 0 Retry Timer : 30 sec
RetryAttempt: 0 NextRetryIn : 0 sec

Adspec : Disabled Oper Adspec : Disabled

CSPF : Enabled Oper CSPF : Enabled
CSPF-FL : Disabled Oper CSPF-FL: Disabled
Least Fill : Disabled Oper LeastF*: Disabled
FRR : Enabled Oper FRR : Enabled
FRR NodePro*: Enabled Oper FRR NP : Enabled
FR Hop Limit: 16 Oper FRHopL*: 16

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 59

 Prop Adm Grp: Disabled Oper PropAG : Disabled

Neg MTU : 1564 Oper MTU : 1564

Bandwidth : 300 Mbps Oper Bw : 300 Mbps
Hop Limit : 255 Oper HopLim*: 255
Record Route: Record Oper RecRou*: Record
Record Label: Record Oper RecLab*: Record
SetupPriori*: 3 Oper SetupP*: 3
Hold Priori*: 3 Oper HoldPr*: 3
Class Type : 0 Oper CT : 0
Backup CT : None
MainCT Retry: n/a
Rem :
MainCT Retry: 0
Limit :
Include Grps: Oper InclGr*:
None None
Exclude Grps: Oper ExclGr*:
None None

Adaptive : Enabled Oper Metric : 200

Preference : n/a
Path Trans : 2 CSPF Queries: 2
Failure Code: noError Failure Node: n/a
ExplicitHops:
10.1.2.1(S) -> 10.1.3.3(S)
Actual Hops :
10.1.2.2(10.10.10.2) @ n Record Label : N/A
-> 10.1.2.1(10.10.10.1) @ Record Label : 131054
-> 10.1.3.3(10.10.10.3) Record Label : 131053
ComputedHops:
10.1.2.2(S) -> 10.1.2.1(S) -> 10.1.3.3(S)
ResigEligib*: False
LastResignal: n/a CSPF Metric : 200
Last MBB :
MBB Type : ConfigChange MBB State : Success
Ended At : 02/12/2013 07:16:43 Old Metric : 200
Signaled BW: 300 Mbps

DetourStatus: Standby DetourType : Originate

DetourAvoid*: 10.10.10.1 DetourOrigin: 10.10.10.2
SetupPriori*: 3 Hold Priori*: 3
Class Type : 0
DetourActiv*: n/a DetourUpTime: 0d 00:04:54
InInterface : n/a InLabel : n/a
OutInterface: 1/1/1 OutLabel : 131053
NextHop : 10.2.4.4
ExplicitHops:
10.2.4.2(S) -> 10.2.4.4(S) -> 10.3.4.3(S)

DetourStatus: Up DetourType : Terminate

DetourAvoid*: 10.1.3.3 DetourOrigin: 10.10.10.1
SetupPriori*: 3 Hold Priori*: 3
Class Type : 0
InInterface : 1/1/3 InLabel : 131054
PreviousHop : 10.1.2.1
-------------------------------------------------------------------------------
LSP toR3-1 Path toR3-strict2
-------------------------------------------------------------------------------
LSP Name : toR3-1 Path LSP ID : 60930
From : 10.10.10.2 To : 10.10.10.3
Adm State : Up Oper State : Up
Path Name : toR3-strict2 Path Type : Standby
Path Admin : Up Path Oper : Up
OutInterface: 1/1/1 Out Label : 131054
Path Up Time: 0d 00:09:48 Path Dn Time: 0d 00:00:00
Retry Limit : 0 Retry Timer : 30 sec
RetryAttempt: 0 NextRetryIn : 0 sec

Adspec : Disabled Oper Adspec : Disabled

CSPF : Enabled Oper CSPF : Enabled

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 60

 CSPF-FL : Disabled Oper CSPF-FL: Disabled
Least Fill : Disabled Oper LeastF*: Disabled
Prop Adm Grp: Disabled Oper PropAG : Disabled

Neg MTU : 1564 Oper MTU : 1564

Bandwidth : 600 Mbps Oper Bw : 600 Mbps
Hop Limit : 255 Oper HopLim*: 255
Record Route: Record Oper RecRou*: Record
Record Label: Record Oper RecLab*: Record
SetupPriori*: 7 Oper SetupP*: 7
Hold Priori*: 0 Oper HoldPr*: 0
Class Type : 0 Oper CT : 0
Include Grps: Oper InclGr*:
None None
Exclude Grps: Oper ExclGr*:
None None

Adaptive : Enabled Oper Metric : 200

Preference : 255
Path Trans : 1 CSPF Queries: 1
Failure Code: noError Failure Node: n/a
ExplicitHops:
10.2.4.4(S) -> 10.3.4.3(S)
Actual Hops :
10.2.4.2(10.10.10.2) Record Label : N/A
-> 10.2.4.4(10.10.10.4) Record Label : 131054
-> 10.3.4.3(10.10.10.3) Record Label : 131055
ComputedHops:
10.2.4.2(S) -> 10.2.4.4(S) -> 10.3.4.3(S)
Srlg : Disabled
SrlgDisjoint: False
ResigEligib*: False
LastResignal: n/a CSPF Metric : 200
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Metro1_R2#

Router R2 provides both node protection and link protection for router R1 as
indicated by symbols “@” and “n”. Router R1 provides link protection for router
R3.

*A:Metro1_R1# show router rsvp session from 10.10.10.1 to 10.10.10.4

===============================================================================
RSVP Sessions
===============================================================================
From To Tunnel LSP Name State
ID ID
-------------------------------------------------------------------------------
10.10.10.1 10.10.10.4 5 35330 toR4-1::loose Up
10.10.10.1 10.10.10.4 5 35332 toR4-1::toR4-strict Up
10.10.10.1 10.10.10.4 5 35332 toR4-1::toR4-strict_detour Up
10.10.10.1 10.10.10.4 5 35332 toR4-1::toR4-strict_detour Up
-------------------------------------------------------------------------------
Sessions : 4
===============================================================================
*A:Metro1_R1#

The same tunnel ID and LSP ID are assigned for both the protected LSP and the
detour tunnel . The detour tunnels are associated with the original tunnel that
they protect.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 61

Lab 4 Services Configuration

Lab 4.1 Epipe

Exercise

1. Student #1: Shut down OSPF/OSPFv3 configuration, LDP sessions, and RSVP-TE LSPs on
router R5.

A:Metro1_R5# configure router ospf shutdown

*A:Metro1_R5# configure router ospf3 shutdown
*A:Metro1_R5# configure router ldp shutdown
*A:Metro1_R5# configure router mpls shutdown
*A:Metro1_R5# configure router rsvp shutdown

2. Student #2: Shut down OSPF/OSPFv3 configuration, LDP sessions, and RSVP-TE LSPs on
router R6.

A:Metro1_R6# configure router ospf shutdown

*A:Metro1_R6# configure router ospf3 shutdown
*A:Metro1_R6# configure router ldp shutdown
*A:Metro1_R6# configure router mpls shutdown
*A:Metro1_R6# configure router rsvp shutdown

3. Student #1: Configure an epipe service with service ID 10 on router R1 as per Figure
13.

a. Configure a SAP toward router R5 with a vlan ID 10 for the epipe service.
(Hint: You will need to remove a port association from an existing router
interface and change this port to an access port).
b. On router R5, configure a router interface toward the epipe service with IP
address 192.168.100.5/24 with a vlan ID 10. Do not delete any existing
interfaces.
c. The epipe service should only support a maximum IP payload of 1490 bytes.
d. Connect this epipe service on router R1 to the epipe service on router R2 that
Student #2 will create in the next step.
e. All SDPs must be configured to use LDPs.

R1:
A:Metro1_R1# configure service sdp 2 mpls create
*A:Metro1_R1>config>service>sdp$ ldp
*A:Metro1_R1>config>service>sdp$ far-end 10.10.10.2
*A:Metro1_R1>config>service>sdp$ no shutdown
*A:Metro1_R1>config>service>sdp$ exit all
*A:Metro1_R1# configure router interface "toR5" shutdown
*A:Metro1_R1# configure router interface "toR5" no port
*A:Metro1_R1# configure port 1/1/2
*A:Metro1_R1>config>port# shutdown
*A:Metro1_R1>config>port# ethernet mode access
*A:Metro1_R1>config>port# ethernet encap-type dot1q

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 62

 *A:Metro1_R1>config>port# no shutdown
*A:Metro1_R1>config>port# exit all
*A:Metro1_R1# configure service epipe 10 customer 1 create
*A:Metro1_R1>config>service>epipe$ service-mtu 1504
*A:Metro1_R1>config>service>epipe$ sap 1/1/2:10 create
*A:Metro1_R1>config>service>epipe>sap$ back
*A:Metro1_R1>config>service>epipe$ spoke-sdp 2:10 create
*A:Metro1_R1>config>service>epipe>spoke-sdp$ back
*A:Metro1_R1>config>service>epipe$ no shutdown

R5:
*A:Metro1_R5# configure router interface "toR1"
*A:Metro1_R5>config>router>if# shutdown
*A:Metro1_R5>config>router>if# no port
*A:Metro1_R5>config>router>if# exit all
*A:Metro1_R5# configure port 1/1/2
*A:Metro1_R5>config>port# shutdown
*A:Metro1_R5>config>port# ethernet encap-type dot1q
*A:Metro1_R5>config>port# no shutdown
*A:Metro1_R5>config>port# exit all
*A:Metro1_R5# configure router interface toR1-epipe10
*A:Metro1_R5>config>router>if$ address 192.168.100.5/24
*A:Metro1_R5>config>router>if$ port 1/1/2:10

4. Student #2: Configure an epipe service with service ID 10 on router R2 as per Figure
13.
a. Configure a SAP toward router R6 with a vlan ID 10 for the epipe service. (Hint:
You will need to remove a port association from an existing router interface
and change this port to an access port).
b. On router R6, configure a router interface toward the epipe service with IP
address 192.168.100.6/24 using vlan ID 10. Do not delete any existing
interfaces.
c. The epipe service should only support a maximum IP payload of 1490 bytes.
d. Connect this epipe service on router R2 to the epipe service on router R1 that
Student #1 created in the previous step.
e. All SDPs must be configured to use LDPs.

R2:
A:Metro1_R2# configure service sdp 1 mpls create
*A:Metro1_R2>config>service>sdp$ ldp
*A:Metro1_R2>config>service>sdp$ far-end 10.10.10.1
*A:Metro1_R2>config>service>sdp$ no shutdown
*A:Metro1_R2>config>service>sdp$ exit all
*A:Metro1_R2# configure router interface "toR6"
*A:Metro1_R2>config>router>if# shutdown
*A:Metro1_R2>config>router>if# no port
*A:Metro1_R2>config>router>if# exit all
*A:Metro1_R2# configure port 1/1/2
*A:Metro1_R2>config>port# shutdown
*A:Metro1_R2>config>port# ethernet mode access
*A:Metro1_R2>config>port# ethernet encap-type dot1q
*A:Metro1_R2>config>port# no shutdown
*A:Metro1_R2>config>port# exit all
*A:Metro1_R2# configure service epipe 10 customer 1 create
*A:Metro1_R2>config>service>epipe$ service-mtu 1504
*A:Metro1_R2>config>service>epipe$ sap 1/1/2:10 create
*A:Metro1_R2>config>service>epipe>sap$ back
*A:Metro1_R2>config>service>epipe$ spoke-sdp 1:10 create
*A:Metro1_R2>config>service>epipe>spoke-sdp$ back

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 63

 *A:Metro1_R2>config>service>epipe$ no shutdown

R6:
*A:Metro1_R6# configure router interface "toR2"
*A:Metro1_R6>config>router>if# shutdown
*A:Metro1_R6>config>router>if# no port
*A:Metro1_R6>config>router>if# exit all
*A:Metro1_R6# configure port 1/1/2
*A:Metro1_R6>config>port# shutdown
*A:Metro1_R6>config>port# ethernet encap-type dot1q
*A:Metro1_R6>config>port# no shutdown
*A:Metro1_R6>config>port# exit all
*A:Metro1_R6# configure router interface toR2-epipe10
*A:Metro1_R6>config>router>if$ address 192.168.100.6/24
*A:Metro1_R6>config>router>if$ port 1/1/2:10

5. Verify that the epipe service is operationally up.

R1:
*A:Metro1_R1# show service id 10 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 10 Vpn Id : 0
Service Type : EPipe
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 07:54:39
Last Mgmt Change : 02/12/2013 07:51:54
Admin State : Up Oper State : Up
MTU : 1504
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:10 q-tag 1518 1518 Up Up
sdp:2:10 S(10.10.10.2) Spok 0 1556 Up Up
===============================================================================
*A:Metro1_R1#

R2:
*A:Metro1_R2# show service id 10 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 10 Vpn Id : 0
Service Type : EPipe
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 07:41:11
Last Mgmt Change : 02/12/2013 07:41:11
Admin State : Up Oper State : Up
MTU : 1504
Vc Switching : False

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 64

 SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:10 q-tag 1518 1518 Up Up
sdp:1:10 S(10.10.10.1) Spok 0 1556 Up Up
===============================================================================
*A:Metro1_R2#

a. Student #1: Verify that router R5 can ping router R6 interface address
(192.168.100.6).
b. Student #2: Verify that router R6 can ping router R5 interface address
(192.168.100.5).

R5:
*A:Metro1_R5# ping 192.168.100.6 count 1
PING 192.168.100.6 56 data bytes
64 bytes from 192.168.100.6: icmp_seq=1 ttl=64 time=8.35ms.

---- 192.168.100.6 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 8.35ms, avg = 8.35ms, max = 8.35ms, stddev = 0.000ms
*A:Metro1_R5#

R6:
*A:Metro1_R6# ping 192.168.100.5 count 1
PING 192.168.100.5 56 data bytes
64 bytes from 192.168.100.5: icmp_seq=1 ttl=64 time=5.33ms.

---- 192.168.100.5 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 5.33ms, avg = 5.33ms, max = 5.33ms, stddev = 0.000ms
*A:Metro1_R6#

Lab 4.2 VPLS spoke termination on epipe

1. Student #1: Shut down the epipe service 10 on router R1. On router R1, configure an
epipe service with service ID 200 as per Figure 14.
a. Connect this epipe service to the VPLS 100 that Student #2 will create in the
next step.
b. Configure a SAP toward router R5 with vlan ID 20 for this epipe service.
c. On router R5, configure a router interface toward router R1 with address
192.168.20.5/24 using vlan ID 20.
d. All SDPs must be configured to use LDPs.

R1:
A:Metro1_R1# configure service epipe 10 shutdown

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 65

 *A:Metro1_R1# configure service epipe 200 customer 1 create
*A:Metro1_R1>config>service>epipe$ spoke-sdp 2:200 create
*A:Metro1_R1>config>service>epipe>spoke-sdp$ back
*A:Metro1_R1>config>service>epipe$ sap 1/1/2:20 create
*A:Metro1_R1>config>service>epipe>sap$ back
*A:Metro1_R1>config>service>epipe$ no shutdown

R5:
A:Metro1_R5# configure router interface toR1-epipe200
*A:Metro1_R5>config>router>if$ address 192.168.20.5/24
*A:Metro1_R5>config>router>if$ port 1/1/2:20

2. Student #2: Shut down the epipe service 10 on router R2. On routers R2 and R4,
configure a VPLS with service ID 100 as per Figure 14.
a. Connect this VPLS to the epipe service 200 that Student #1 created in the
previous step.
b. On router R2, configure a SAP toward router R6 with vlan ID 20 for this VPLS.
c. Connect VPLS between routers R2 and R4 using full mesh SDPs.
d. All SDPs must be configured to use LDPs.
e. On router R6, configure a router interface toward R2 with address
192.168.20.6/24 and vlan ID 20.

R2:
A:Metro1_R2# configure service epipe 10 shutdown
*A:Metro1_R2# configure service vpls 100 customer 1 create
*A:Metro1_R2>config>service>vpls$ spoke-sdp 1:200 create
*A:Metro1_R2>config>service>vpls>spoke-sdp$ back
*A:Metro1_R2>config>service>vpls$ sap 1/1/2:20 create
*A:Metro1_R2>config>service>vpls>sap$ back
*A:Metro1_R2>config>service>vpls$ no shutdown
*A:Metro1_R2>config>service>vpls$ back
*A:Metro1_R2>config>service# exit all
*A:Metro1_R2# configure service sdp 4 mpls create
*A:Metro1_R2>config>service>sdp$ ldp
*A:Metro1_R2>config>service>sdp$ far-end 10.10.10.4
*A:Metro1_R2>config>service>sdp$ no shutdown
*A:Metro1_R2>config>service>sdp$ exit all
*A:Metro1_R2# configure service vpls 100
*A:Metro1_R2>config>service>vpls# mesh-sdp 4 create

R4:
A:Metro1_R4# configure service sdp 2 mpls create
*A:Metro1_R4>config>service>sdp$ ldp
*A:Metro1_R4>config>service>sdp$ far-end 10.10.10.2
*A:Metro1_R4>config>service>sdp$ no shutdown
*A:Metro1_R4>config>service>sdp$ exit all
*A:Metro1_R4# configure service vpls 100 customer 1 create
*A:Metro1_R4>config>service>vpls$ mesh-sdp 2 create
*A:Metro1_R4>config>service>vpls>mesh-sdp$ back
*A:Metro1_R4>config>service>vpls$ no shutdown

R6:
A:Metro1_R6# configure router interface toR2-vpls100
*A:Metro1_R6>config>router>if$ address 192.168.20.6/24

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 66

 *A:Metro1_R6>config>router>if$ port 1/1/2:20

3. Verify that the epipe service 200 and the VPLS 100 are both operationally up. Verify
MAC addresses in the VPLS ID 100.

R1:
*A:Metro1_R1# show service id 200 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 200 Vpn Id : 0
Service Type : Epipe
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 10:05:30
Last Mgmt Change : 02/12/2013 09:52:04
Admin State : Up Oper State : Up
MTU : 1514
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:20 q-tag 1518 1518 Up Up
sdp:22:200 S(10.10.10.2) Spok 0 1556 Up Up
===============================================================================
*A:Metro1_R1#

R2:
A:Metro1_R2# show service id 100 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 100 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 09:52:30
Last Mgmt Change : 02/12/2013 09:53:06
Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 100
SAP Count : 1 SDP Bind Count : 2
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
Def. Gateway IP : None
Def. Gateway MAC : None
Temp Flood Time : Disabled Temp Flood : Inactive
Temp Flood Chg Cnt: 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 67

 sap:1/1/2:20 q-tag 1518 1518 Up Up
sdp:4:100 M(10.10.10.4) Mesh 0 1556 Up Up
sdp:11:200 S(10.10.10.1) Spok 0 1556 Up Up
===============================================================================
A:Metro1_R2#

*A:Metro1_R2# show service id 100 fdb detail

===============================================================================
Forwarding Database, Service 100
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
No Matching Entries
===============================================================================
*A:Metro1_R2#

A MAC FDB does not exist for the epipe service even though it terminates on a VPLS.
Since no traffic has been sent through the VPLS, no MAC entries exist in the VPLS
because no MAC addresses are learned yet.

4. A ping from router R5 to router R6 (192.168.20.6) and a ping from router R6 to router
R5 (192.168.20.5) should work. Verify MAC addresses in the VPLS ID 100.

R5:
*A:Metro1_R5# ping 192.168.20.6 count 1
PING 192.168.20.6 56 data bytes
64 bytes from 192.168.20.6: icmp_seq=1 ttl=64 time=12.3ms.

---- 192.168.20.6 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 12.3ms, avg = 12.3ms, max = 12.3ms, stddev = 0.000ms
*A:Metro1_R5#

R6:
*A:Metro1_R6# ping 192.168.20.5 count 1
PING 192.168.20.5 56 data bytes
64 bytes from 192.168.20.5: icmp_seq=1 ttl=64 time=5.09ms.

---- 192.168.20.5 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 5.09ms, avg = 5.09ms, max = 5.09ms, stddev = 0.000ms
*A:Metro1_R6#

R2:
A:Metro1_R2# show service id 100 fdb detail

===============================================================================
Forwarding Database, Service 100
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
100 00:03:fa:ac:97:57 sdp:11:200 L/15 02/12/13 11:50:32
100 00:16:4d:27:34:39 sap:1/1/2:20 L/15 02/12/13 11:50:32
-------------------------------------------------------------------------------
No. of MAC Entries: 2
-------------------------------------------------------------------------------

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 68

 Legend: L=Learned O=Oam P=Protected-MAC
===============================================================================
A:Metro1_R2#

As mentioned earlier, a MAC FDB does not exist for the epipe service on router R1
even though it terminates on a VPLS. Traffic received from router R5 through the
SAP is simply forwarded to the spoke SDP and on to far-end PE, router R2. Traffic
received from the far-end PE, router R2 through the spoke SDP, is forwarded to
the SAP and on to router R5.

There are two MAC entries on router R2 MAC FDB. When router R2, with the VPLS
configured, receives traffic through a SAP, it learns router R6’s MAC address.
When router R2 receives traffic through a spoke SDP, it learns router R5’s MAC
address.

Lab 4.3 VPLS spoke termination on IES

1. Student #1: Shut down the epipe service 200 on router R1. On router R1, configure an
IES with service ID 300 as per Figure 15.
a. Configure an IES interface with IP address 192.168.30.1/24.
b. Connect this IES to the VPLS ID 400 that Student #2 will create in the next step.
c. All SDPs must be configured to use LDPs.

A:Metro1_R1# configure service epipe 200 shutdown

*A:Metro1_R1# configure service ies 300 customer 1 create
*A:Metro1_R1>config>service>ies$ interface toR2-vpls400 create
*A:Metro1_R1>config>service>ies>if$ address 192.168.30.1/24
*A:Metro1_R1>config>service>ies>if$ spoke-sdp 2:300 create
*A:Metro1_R1>config>service>ies>if>spoke-sdp$ back
*A:Metro1_R1>config>service>ies>if$ no shutdown
*A:Metro1_R1>config>service>ies>if$ back
*A:Metro1_R1>config>service>ies$ no shutdown

2. Student #2: Shut down the VPLS 100 on routers R2 and R4. Create a VPLS with
service ID 400 on routers R2 and R4 as per Figure 15.
a. On router R2, configure a SAP toward router R6 with vlan ID 30.
b. Connect this VPLS to the IES 300 that was created by Student #1 in the previous
step.
c. Connect VPLS between routers R2 and R4 using full mesh SDPs.
d. All SDPs must be configured to use LDPs.
e. On router R6, configure a router interface on router R6 connecting to this VPLS
with IP address 192.168.30.2/24 using vlan ID 30.

R2:
A:Metro1_R2# configure service vpls 100 shutdown
*A:Metro1_R2# configure service vpls 400 customer 1 create
*A:Metro1_R2>config>service>vpls$ sap 1/1/2:30 create
*A:Metro1_R2>config>service>vpls>sap$ back
*A:Metro1_R2>config>service>vpls$ spoke-sdp 1:300 create

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 69

 *A:Metro1_R2>config>service>vpls>spoke-sdp$ back
*A:Metro1_R2>config>service>vpls$ mesh-sdp 4 create
*A:Metro1_R2>config>service>vpls>mesh-sdp$ back
*A:Metro1_R2>config>service>vpls$ no shutdown

R4:
A:Metro1_R4# configure service vpls 100 shutdown
*A:Metro1_R4# configure service vpls 400 customer 1 create
*A:Metro1_R4>config>service>vpls$ mesh-sdp 2 create
*A:Metro1_R4>config>service>vpls>mesh-sdp$ back
*A:Metro1_R4>config>service>vpls$ no shutdown

R6:
A:Metro1_R6# configure router interface toR2-vpls400
*A:Metro1_R6>config>router>if$ address 192.168.30.2/24
*A:Metro1_R6>config>router>if$ port 1/1/2:30

3. Student #1: Verify that both IES and VPLS are operationally up.

R1:
*A:Metro1_R1# show service id 300 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 300 Vpn Id : 0
Service Type : IES
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/11/2013 09:06:13
Last Mgmt Change : 02/12/2013 12:07:54
Admin State : Up Oper State : Down
SAP Count : 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:2:300 S(10.10.10.2) Spok 0 1556 Up Down
===============================================================================
*A:Metro1_R1#
*A:Metro1_R1# show service id 300 sdp 2 detail

===============================================================================
Service Destination Point (Sdp Id : 2) Details
===============================================================================
-------------------------------------------------------------------------------
Sdp Id 22:300 -(10.10.10.2)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 2:300 Type : Spoke
Spoke Descr : (Not Specified)
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 1556
Far End : 10.10.10.2 Delivery : MPLS
Tunnel Far End : n/a LSP Types : LDP
Hash Label : Disabled Hash Lbl Sig Cap : Disabled
Oper Hash Label : Disabled

Admin State : Up Oper State : Down

Acct. Pol : None Collect Stats : Disabled

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 70

 Ingress Label : 131064 Egress Label : 131064
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr IPv6 Fltr-Id : n/a Egr IPv6 Fltr-Id : n/a
BGP FlowSpec : Disabled
Admin ControlWord : Not Preferred Oper ControlWord : False
Last Status Change : 02/11/2013 09:06:13 Signaling : TLDP
Last Mgmt Change : 02/12/2013 12:07:47
Class Fwding State : Down
Flags : PWPeerFaultStatusBits ServiceMTUMismatch
Local Pw Bits : pwNotForwarding
Peer Pw Bits : pwNotForwarding
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : None
Application Profile: None

Ingress Qos Policy : (none) Egress Qos Policy : (none)

Ingress FP QGrp : (none) Egress Port QGrp : (none)
Ing FP QGrp Inst : (none) Egr Port QGrp Inst: (none)

KeepAlive Information :
Admin State : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10

Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0

:
:
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Metro1_R1#

R2:
*A:Metro1_R2# show service id 400 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 400 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 12:00:45
Last Mgmt Change : 02/12/2013 12:00:45
Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 400
SAP Count : 1 SDP Bind Count : 2
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
Def. Gateway IP : None
Def. Gateway MAC : None
Temp Flood Time : Disabled Temp Flood : Inactive
Temp Flood Chg Cnt: 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:30 q-tag 1518 1518 Up Up
sdp:1:300 S(10.10.10.1) Spok 0 1556 Up Down
sdp:4:400 M(10.10.10.4) Mesh 0 1556 Up Up

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 71

 ===============================================================================
*A:Metro1_R2#
*A:Metro1_R2# show service id 400 sdp 1 detail

===============================================================================
Service Destination Point (Sdp Id : 1) Details
===============================================================================
-------------------------------------------------------------------------------
Sdp Id 11:300 -(10.10.10.1)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 1:300 Type : Spoke
Spoke Descr : (Not Specified)
Split Horiz Grp : (Not Specified)
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 1520
Far End : 10.10.10.1 Delivery : MPLS
Tunnel Far End : n/a LSP Types : LDP
Hash Label : Disabled Hash Lbl Sig Cap : Disabled
Oper Hash Label : Disabled

Admin State : Up Oper State : Down

Acct. Pol : None Collect Stats : Disabled
Ingress Label : 131064 Egress Label : 131064
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr IPv6 Fltr-Id : n/a Egr IPv6 Fltr-Id : n/a
Admin ControlWord : Not Preferred Oper ControlWord : False
Last Status Change : 02/11/2013 08:53:01 Signaling : TLDP
Last Mgmt Change : 02/12/2013 11:57:31 Force Vlan-Vc : Disabled
Endpoint : N/A Precedence : 4
PW Status Sig : Enabled
Class Fwding State : Down
Flags : PWPeerFaultStatusBits ServiceMTUMismatch
Time to RetryReset : never Retries Left : 3
Mac Move : Blockable Blockable Level : Tertiary
Local Pw Bits : pwNotForwarding
Peer Pw Bits : pwNotForwarding
Peer Fault Ip : None
Application Profile: None
Max Nbr of MAC Addr: No Limit Total MAC Addr : 0
Learned MAC Addr : 0 Static MAC Addr : 0

MAC Learning : Enabled Discard Unkwn Srce: Disabled

MAC Aging : Enabled
BPDU Translation : Disabled
L2PT Termination : Disabled
MAC Pinning : Disabled
Ignore Standby Sig : False Block On Mesh Fail: False
Oper Group : (none) Monitor Oper Grp : (none)
Rest Prot Src Mac : Disabled
Auto Learn Mac Prot: Disabled RestProtSrcMacAct : Disable

Ingress Qos Policy : (none) Egress Qos Policy : (none)

Ingress FP QGrp : (none) Egress Port QGrp : (none)
Ing FP QGrp Inst : (none) Egr Port QGrp Inst: (none)

:
:
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Metro1_R2#

Both of the SDP bindings for the IES and the VPLS are operationally down. Both
SDP bindings have a failure code of “ServiceMTUMismatch”. This indicates that
the VC MTUs do not match between the IES and the VPLS.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 72

 The VC MTU of the IES is based on the network port MTU. The current network
port MTU is 1578 bytes. The VC MTU would be 1542 bytes (1578 – 14 bytes port
encapsulation - 14 bytes Ethernet header, – 4 bytes transport label – 4 byte
service label).

The VC MTU of the VPLS is based on the service MTU. The service MTU is 1514
bytes by default and the VC MTU is therefore 1500 bytes (1514 bytes – 14 bytes
Ethernet header).

*A:Metro1_R1# show router ldp bindings fec-type services

===============================================================================
LDP LSR ID: 10.10.10.1
===============================================================================
Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn
S - Status Signaled Up, D - Status Signaled Down
E - Epipe Service, V - VPLS Service, M - Mirror Service
A - Apipe Service, F - Fpipe Service, I - IES, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service
BU - Alternate Next-hop for Fast Re-Route, TLV - (Type, Length: Value)
===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 2 10.10.10.2 131069U 131068D 1490 1490
E-Eth 200 200 2 10.10.10.2 131066U 131066D 1500 1500
I-Eth 300 300 2 10.10.10.2 131065U 131065D 1542 1500
-------------------------------------------------------------------------------
No. of VC Labels: 3
===============================================================================

===============================================================================
LDP Service FEC 129 Bindings
===============================================================================
AGI SAII
TAII
Type SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
No Matching Entries Found
===============================================================================
*A:Metro1_R1#
*A:Metro1_R1# show port 1/1/3

===============================================================================
Ethernet Interface
===============================================================================
Description : 1-Gig Ethernet SFP
Interface : 1/1/3 Oper Speed : 1 Gbps
Link-level : Ethernet Config Speed : N/A
Admin State : up Oper Duplex : full
Oper State : up Config Duplex : N/A
Physical Link : Yes MTU : 1578
Single Fiber Mode : No Min Frame Length : 64 Bytes
IfIndex : 35749888 Hold time up : 0 seconds
Last State Change : 03/28/2013 12:17:30 Hold time down : 0 seconds
Last Cleared Time : N/A DDM Events : Enabled
Phys State Chng Cnt: 1

Configured Mode : network Encap Type : null

Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
PBB Ethertype : 0x88e7
Ing. Pool % Rate : 100 Egr. Pool % Rate : 100
Ing. Pool Policy : n/a
Egr. Pool Policy : n/a
Net. Egr. Queue Pol: default
Egr. Sched. Pol : n/a

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 73

 Auto-negotiate : true MDI/MDX : N/A
Accounting Policy : None Collect-stats : Disabled
:
:
*A:Metro1_R1#

*A:Metro1_R2# show router ldp bindings fec-type services

===============================================================================
LDP LSR ID: 10.10.10.2
===============================================================================
Legend: U - Label In Use, N - Label Not In Use, W - Label Withdrawn
S - Status Signaled Up, D - Status Signaled Down
E - Epipe Service, V - VPLS Service, M - Mirror Service
A - Apipe Service, F - Fpipe Service, I - IES, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service
BU - Alternate Next-hop for Fast Re-Route, TLV - (Type, Length: Value)
===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 1 10.10.10.1 131068U 131069D 1490 1490
V-Eth 200 100 1 10.10.10.1 131066U 131066D 1500 1500
V-Eth 300 400 1 10.10.10.1 131065U 131065D 1500 1542
V-Eth 400 400 4 10.10.10.4 131064U 131066 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 4
===============================================================================

===============================================================================
LDP Service FEC 129 Bindings
===============================================================================
AGI SAII
TAII
Type SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
No Matching Entries Found
===============================================================================
*A:Metro1_R2#

*A:Metro1_R1# configure service ies 300

*A:Metro1_R1>config>service>ies# interface "toR2-vpls400"
*A:Metro1_R1>config>service>ies>if# ip-mtu 1500
*A:Metro1_R1>config>service>ies>if# exit all
*A:Metro1_R1#
*A:Metro1_R1#
*A:Metro1_R1# show service id 300 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 300 Vpn Id : 0
Service Type : IES
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 12:19:22
Last Mgmt Change : 02/12/2013 12:07:54
Admin State : Up Oper State : Up
SAP Count : 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 74

 Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:2:300 S(10.10.10.2) Spok 0 1556 Up Up
===============================================================================
*A:Metro1_R1#

*A:Metro1_R2# show service id 400 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 400 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 04/02/2013 06:51:43
Last Mgmt Change : 04/02/2013 06:51:43
Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 400
SAP Count : 1 SDP Bind Count : 2
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
Def. Gateway IP : None
Def. Gateway MAC : None
Temp Flood Time : Disabled Temp Flood : Inactive
Temp Flood Chg Cnt: 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:30 q-tag 1518 1518 Up Up
sdp:1:300 S(10.10.10.1) Spok 0 1556 Up Up
sdp:4:400 M(10.10.10.4) Mesh 0 1556 Up Up
===============================================================================
*A:Metro1_R2#

After adjusting the VC MTU on the IES, both the VPLS and the IES and their SDP
bindings are operationally up.

4. Student #2: Perform a ping from router R6 to the IES interface (192.168.30.1). Verify
MAC entries in the VPLS FDB.

*A:Metro1_R6# ping 192.168.30.1 count 1

PING 192.168.30.1 56 data bytes
64 bytes from 192.168.30.1: icmp_seq=1 ttl=64 time=7.98ms.

---- 192.168.30.1 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 7.98ms, avg = 7.98ms, max = 7.98ms, stddev = 0.000ms
*A:Metro1_R6#

R2:
*A:Metro1_R2# show service id 400 fdb detail

===============================================================================
Forwarding Database, Service 400

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 75

 ===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
400 00:16:4d:27:34:39 sap:1/1/2:30 L/15 02/12/13 12:07:25
400 7c:68:ff:00:00:00 sdp:11:300 L/15 02/12/13 12:05:51
-------------------------------------------------------------------------------
No. of MAC Entries: 2
-------------------------------------------------------------------------------
Legend: L=Learned O=Oam P=Protected-MAC
===============================================================================
*A:Metro1_R2#

There are no MAC entries in the IES because it is a Layer 3 service. There are two
MAC entries in the VPLS. One MAC entry belongs to router R6’s MAC address.
which is learned through a SAP. Another MAC entry belongs to router R1’s MAC
address where IES interface resides.

Lab 4.4 VPRN with BGP PE-CE

1. Student #1: Shut down IES 300. Shut down all IGPs (IS-IS, OSPF, and OSPFv3) on
router R5.

R1:
*A:Metro1_R1# configure service ies 300 shutdown

R5:
A:Metro1_R5# configure router isis shutdown
*A:Metro1_R5# configure router ospf shutdown
*A:Metro1_R5# configure router ospf3 shutdown

2. Student #2: Shut down VPLS 400. Shut down all IGPs (IS-IS, OSPF, and OSPFv3) on
router R6.

R2:
*A:Metro1_R2# configure service vpls 400 shutdown

R6:
A:Metro1_R6# configure router isis shutdown
*A:Metro1_R6# configure router ospf shutdown
*A:Metro1_R6# configure router ospf3 shutdown

3. Student #1: Configure an Autonomous System number for routers R1 and R5 according
to Figure 16.

R1:
*A:Metro1_R1# configure router autonomous-system 65000

R5:
*A:Metro1_R5# configure router autonomous-system 65005

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 76

 4. Student #2: Configure an Autonomous System number for routers R2 and R6 according
to Figure 16.

R2:
*A:Metro1_R2# configure router autonomous-system 65000

R6:
*A:Metro1_R6# configure router autonomous-system 65006

5. Student #1: Configure a VPRN service with service ID 500 on router R1 with the
following requirements:
a. Use 65000:10 as route distinguisher and route target values.
b. Configure the VPRN to use LDP.
c. Configure a VRF interface on router R1 for this VPRN service toward router R5
with IP address 192.168.50.1/27 using vlan ID 50.
d. Use BGP as PE-CE protocol between routers R1 and R5.
e. Configure MP-BGP on router R1 to exchange IPv4 VPN routes between routers
R1 and R2. Ensure that all IPv4 VPN routes are advertised into router R5.
f. Configure a router interface on router R5 toward R1 with IP address
192.168.50.2/27 using vlan ID 50.
g. Ensure that all local routes in router R5 are advertised into this VPRN service.

R1:
*A:Metro1_R1# configure service vprn 500 customer 1 create
*A:Metro1_R1>config>service>vprn$ route-distinguisher 65000:10
*A:Metro1_R1>config>service>vprn$ vrf-target target:65000:10
*A:Metro1_R1>config>service>vprn$ auto-bind ldp
*A:Metro1_R1>config>service>vprn$ autonomous-system 65000
*A:Metro1_R1>config>service>vprn$ no shutdown
*A:Metro1_R1>config>service>vprn$ interface toR5-vprn500 create
*A:Metro1_R1>config>service>vprn>if$ address 192.168.50.1/27
*A:Metro1_R1>config>service>vprn>if$ sap 1/1/2:50 create
*A:Metro1_R1>config>service>vprn>if>sap$ exit
*A:Metro1_R1>config>service>vprn>if$ exit
*A:Metro1_R1>config>service>vprn$ bgp
*A:Metro1_R1>config>service>vprn>bgp$ group toR5-vprn500
*A:Metro1_R1>config>service>vprn>bgp>group$ neighbor 192.168.50.2
*A:Metro1_R1>config>service>vprn>bgp>group>neighbor$ peer-as 65005
*A:Metro1_R1>config>service>vprn>bgp>group>neighbor$ exit all
*A:Metro1_R1# configure router bgp
*A:Metro1_R1>config>router>bgp$ group mbgp
*A:Metro1_R1>config>router>bgp>group$ family vpn-ipv4
*A:Metro1_R1>config>router>bgp>group$ peer-as 65000
*A:Metro1_R1>config>router>bgp>group$ neighbor 10.10.10.2
*A:Metro1_R1>config>router>bgp>group>neighbor$ exit all
*A:Metro1_R1# configure router policy-options
*A:Metro1_R1>config>router>policy-options# begin
*A:Metro1_R1>config>router>policy-options# policy-statement toCE-vprn
*A:Metro1_R1>config>router>policy-options>policy-statement$ entry 10
*A:Metro1_R1>config>router>policy-options>policy-statement>entry$ from protocol
bgp-vpn
*A:Metro1_R1>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R1>config>router>policy-options>policy-statement>entry>action$ back
*A:Metro1_R1>config>router>policy-options>policy-statement>entry$ back

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 77

 *A:Metro1_R1>config>router>policy-options>policy-statement$ back
*A:Metro1_R1>config>router>policy-options# commit
*A:Metro1_R1>config>router>policy-options# exit all
*A:Metro1_R1# configure service vprn 500
*A:Metro1_R1>config>service>vprn# bgp group "toR5-vprn500"
*A:Metro1_R1>config>service>vprn>bgp>group# export "toCE-vprn"

R5:
*A:Metro1_R5# configure router interface toR1-vprn500
*A:Metro1_R5>config>router>if$ address 192.168.50.2/27
*A:Metro1_R5>config>router>if$ port 1/1/2:50
*A:Metro1_R5>config>router>if$ exit all
*A:Metro1_R5# configure router bgp
*A:Metro1_R5>config>router>bgp# group vprn500
*A:Metro1_R5>config>router>bgp>group# neighbor 192.168.50.1
*A:Metro1_R5>config>router>bgp>group>neighbor$ peer-as 65000
*A:Metro1_R5>config>router>bgp>group>neighbor$ exit all
*A:Metro1_R5# configure router interface loop1-vprn500
*A:Metro1_R5>config>router>if$ loopback
*A:Metro1_R5>config>router>if$ address 192.168.101.1/24
*A:Metro1_R5>config>router>if$ exit all
*A:Metro1_R5# configure router policy-options
*A:Metro1_R5>config>router>policy-options# begin
*A:Metro1_R5>config>router>policy-options# policy-statement direct
*A:Metro1_R5>config>router>policy-options>policy-statement$ entry 10
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ from protocol
direct
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R5>config>router>policy-options>policy-statement>entry>action$ exit
*A:Metro1_R5>config>router>policy-options>policy-statement>entry$ exit
*A:Metro1_R5>config>router>policy-options>policy-statement$ exit
*A:Metro1_R5>config>router>policy-options# commit
*A:Metro1_R5>config>router>policy-options# exit all
*A:Metro1_R5# configure router bgp
*A:Metro1_R5>config>router>bgp# group "vprn500"
*A:Metro1_R5>config>router>bgp>group# export "direct"

6. Student #2: Configure a VPRN service with service ID 500 on router R2 with the
following requirements:
a. Use 65000:10 as route distinguisher and route target values.
b. Configure the VPRN to use LDP.
c. Configure a VRF interface on router R2 for this VPRN service toward router R6
with IP address 192.168.60.1/27 using vlan ID 50.
d. Use BGP as PE-CE protocol between routers R2 and R6.
e. Configure MP-BGP on router R2 to exchange IPv4 VPN routes between routers
R1 and R2. Ensure that all IPv4 VPN routes are advertised into router R5.
f. Configure a router interface on router R6 toward router R2 with IP address
192.168.60.2/27 using vlan ID 50.
g. Ensure that all local routes in router R6 are advertised into this VPRN service.

R2:
*A:Metro1_R2# configure service vprn 500 customer 1 create
*A:Metro1_R2>config>service>vprn$ route-distinguisher 65000:10
*A:Metro1_R2>config>service>vprn$ vrf-target target:65000:10
*A:Metro1_R2>config>service>vprn$ autonomous-system 65000
*A:Metro1_R2>config>service>vprn$ auto-bind ldp
*A:Metro1_R2>config>service>vprn$ no shutdown

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 78

 *A:Metro1_R2>config>service>vprn$ interface tor6-vprn500 create
*A:Metro1_R2>config>service>vprn>if$ address 192.168.60.1/27
*A:Metro1_R2>config>service>vprn>if$ sap 1/1/2:50 create
*A:Metro1_R2>config>service>vprn>if>sap$ exit
*A:Metro1_R2>config>service>vprn>if$ exit
*A:Metro1_R2>config>service>vprn$ bgp group toR6-vprn500
*A:Metro1_R2>config>service>vprn>bgp>group$ neighbor 192.168.60.2
*A:Metro1_R2>config>service>vprn>bgp>group>neighbor$ peer-as 65006
*A:Metro1_R2>config>service>vprn>bgp>group>neighbor$ exit all
*A:Metro1_R2# configure router bgp
*A:Metro1_R2>config>router>bgp$ group mbgp
*A:Metro1_R2>config>router>bgp>group$ family vpn-ipv4
*A:Metro1_R2>config>router>bgp>group$ peer-as 65000
*A:Metro1_R2>config>router>bgp>group$ neighbor 10.10.10.1
*A:Metro1_R2>config>router>bgp>group>neighbor$ exit all
*A:Metro1_R2# configure router policy-options
*A:Metro1_R2>config>router>policy-options# begin
*A:Metro1_R2>config>router>policy-options# policy-statement toCE-vprn
*A:Metro1_R2>config>router>policy-options>policy-statement$ entry 10
*A:Metro1_R2>config>router>policy-options>policy-statement>entry$ from protocol
bgp-vpn
*A:Metro1_R2>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R2>config>router>policy-options>policy-statement>entry>action$ back
*A:Metro1_R2>config>router>policy-options>policy-statement>entry$ back
*A:Metro1_R2>config>router>policy-options>policy-statement$ back
*A:Metro1_R2>config>router>policy-options# commit
*A:Metro1_R2>config>router>policy-options# exit all
*A:Metro1_R2# configure service vprn 500
*A:Metro1_R2>config>service>vprn# bgp group "toR6-vprn500"
*A:Metro1_R2>config>service>vprn>bgp>group# export "toCE-vprn"

R6:
*A:Metro1_R6# configure router bgp
*A:Metro1_R6>config>router>bgp$ group vprn500
*A:Metro1_R6>config>router>bgp>group$ neighbor 192.168.60.1
*A:Metro1_R6>config>router>bgp>group>neighbor$ peer-as 65000
*A:Metro1_R6>config>router>bgp>group>neighbor$ exit all
*A:Metro1_R6# configure router interface toR2-vprn500
*A:Metro1_R6>config>router>if$ address 192.168.60.2/27
*A:Metro1_R6>config>router>if$ port 1/1/2:50
*A:Metro1_R6>config>router>if$ exit all
*A:Metro1_R6# configure router interface loop1-vprn500
*A:Metro1_R6>config>router>if$ loopback
*A:Metro1_R6>config>router>if$ address 192.168.102.1/24
*A:Metro1_R6>config>router>if$ exit all
*A:Metro1_R6# configure router policy-options
*A:Metro1_R6>config>router>policy-options# begin
*A:Metro1_R6>config>router>policy-options# policy-statement direct
*A:Metro1_R6>config>router>policy-options>policy-statement$ entry 10
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ from protocol
direct
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ action accept
*A:Metro1_R6>config>router>policy-options>policy-statement>entry>action$ exit
*A:Metro1_R6>config>router>policy-options>policy-statement>entry$ exit
*A:Metro1_R6>config>router>policy-options>policy-statement$ exit
*A:Metro1_R6>config>router>policy-options# commit
*A:Metro1_R6>config>router>policy-options# exit all
*A:Metro1_R6# configure router bgp
*A:Metro1_R6>config>router>bgp# group "vprn500"
*A:Metro1_R6>config>router>bgp>group# export "direct"

7. Ensure that the VPRN services are operationally up and BGP sessions are established
between PEs and CEs.
R1:
*A:Metro1_R1# show service id 500 base

===============================================================================

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 79

 Service Basic Information
===============================================================================
Service Id : 500 Vpn Id : 0
Service Type : VPRN
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 12:36:01
Last Mgmt Change : 02/12/2013 12:36:01
Admin State : Up Oper State : Up

Route Dist. : 65000:10 VPRN Type : regular

AS Number : 65000 Router Id : 10.10.10.1
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit Auto Bind : LDP
Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Vrf Target : target:65000:10
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled

SAP Count : 1 SDP Bind Count : 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:50 q-tag 1518 1518 Up Up
===============================================================================
*A:Metro1_R1#
*A:Metro1_R1# show router 500 bgp neighbor

===============================================================================
BGP Neighbor
===============================================================================
-------------------------------------------------------------------------------
Peer : 192.168.50.2
Group : toR5-vprn500
-------------------------------------------------------------------------------
Peer AS : 65005 Peer Port : 50284
Peer Address : 192.168.50.2
Local AS : 65000 Local Port : 179
Local Address : 192.168.50.1
Peer Type : External
State : Established Last State : Established
Last Event : recvKeepAlive
Last Error : Cease (Connection Collision Resolution)
Local Family : IPv4
Remote Family : IPv4
Hold Time : 90 Keep Alive : 30
Min Hold Time : 0
Active Hold Time : 90 Active Keep Alive : 30
Cluster Id : None
Preference : 170 Num of Update Flaps : 2
Recd. Paths : 3
IPv4 Recd. Prefixes : 3 IPv4 Active Prefixes : 1
IPv4 Suppressed Pfxs : 0 VPN-IPv4 Suppr. Pfxs : 0
VPN-IPv4 Recd. Pfxs : 0 VPN-IPv4 Active Pfxs : 0
Mc IPv4 Recd. Pfxs. : 0 Mc IPv4 Active Pfxs. : 0
Mc IPv4 Suppr. Pfxs : 0 IPv6 Suppressed Pfxs : 0
IPv6 Recd. Prefixes : 0 IPv6 Active Prefixes : 0
VPN-IPv6 Recd. Pfxs : 0 VPN-IPv6 Active Pfxs : 0
VPN-IPv6 Suppr. Pfxs : 0 L2-VPN Suppr. Pfxs : 0

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 80

 L2-VPN Recd. Pfxs : 0 L2-VPN Active Pfxs : 0
MVPN-IPv4 Suppr. Pfxs: 0 MVPN-IPv4 Recd. Pfxs : 0
MVPN-IPv4 Active Pfxs: 0 MDT-SAFI Suppr. Pfxs : 0
MDT-SAFI Recd. Pfxs : 0 MDT-SAFI Active Pfxs : 0
FLOW-IPV4-SAFI Suppr*: 0 FLOW-IPV4-SAFI Recd.*: 0
FLOW-IPV4-SAFI Activ*: 0 Rte-Tgt Suppr. Pfxs : 0
Rte-Tgt Recd. Pfxs : 0 Rte-Tgt Active Pfxs : 0
Backup IPv4 Pfxs : 0 Backup IPv6 Pfxs : 0
Mc Vpn Ipv4 Recd. Pf*: 0 Mc Vpn Ipv4 Active P*: 0
Backup Vpn IPv4 Pfxs : 0 Backup Vpn IPv6 Pfxs : 0
Input Queue : 0 Output Queue : 0
i/p Messages : 51 o/p Messages : 51
i/p Octets : 1301 o/p Octets : 1186
i/p Updates : 9 o/p Updates : 7
TTL Security : Disabled Min TTL Value : n/a
Graceful Restart : Disabled Stale Routes Time : n/a
Advertise Inactive : Disabled Peer Tracking : Disabled
Advertise Label : None
Auth key chain : n/a
Disable Cap Nego : Disabled Bfd Enabled : Disabled
Flowspec Validate : Disabled Default Route Tgt : Disabled
Local Capability : RtRefresh MPBGP 4byte ASN
Remote Capability : RtRefresh MPBGP 4byte ASN
Local AddPath Capabi*: Disabled
Remote AddPath Capab*: Send - None
: Receive - None
Import Policy : None Specified / Inherited
Export Policy : toCE-vprn

-------------------------------------------------------------------------------
Neighbors : 1
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Metro1_R1#

R2:
*A:Metro1_R2# show service id 500 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 500 Vpn Id : 0
Service Type : VPRN
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 12:27:52
Last Mgmt Change : 02/12/2013 12:27:52
Admin State : Up Oper State : Up

Route Dist. : 65000:10 VPRN Type : regular

AS Number : 65000 Router Id : 10.10.10.2
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit Auto Bind : LDP
Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Vrf Target : target:65000:10
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled

SAP Count : 1 SDP Bind Count : 0

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 81

 -------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:50 q-tag 1518 1518 Up Up
===============================================================================
*A:Metro1_R2#
*A:Metro1_R2# show router 500 bgp neighbor

===============================================================================
BGP Neighbor
===============================================================================
-------------------------------------------------------------------------------
Peer : 192.168.60.2
Group : toR6-vprn500
-------------------------------------------------------------------------------
Peer AS : 65006 Peer Port : 51247
Peer Address : 192.168.60.2
Local AS : 65000 Local Port : 179
Local Address : 192.168.60.1
Peer Type : External
State : Established Last State : Established
Last Event : recvKeepAlive
Last Error : Cease (Connection Collision Resolution)
Local Family : IPv4
Remote Family : IPv4
Hold Time : 90 Keep Alive : 30
Min Hold Time : 0
Active Hold Time : 90 Active Keep Alive : 30
Cluster Id : None
Preference : 170 Num of Update Flaps : 2
Recd. Paths : 3
IPv4 Recd. Prefixes : 3 IPv4 Active Prefixes : 1
IPv4 Suppressed Pfxs : 0 VPN-IPv4 Suppr. Pfxs : 0
VPN-IPv4 Recd. Pfxs : 0 VPN-IPv4 Active Pfxs : 0
Mc IPv4 Recd. Pfxs. : 0 Mc IPv4 Active Pfxs. : 0
Mc IPv4 Suppr. Pfxs : 0 IPv6 Suppressed Pfxs : 0
IPv6 Recd. Prefixes : 0 IPv6 Active Prefixes : 0
VPN-IPv6 Recd. Pfxs : 0 VPN-IPv6 Active Pfxs : 0
VPN-IPv6 Suppr. Pfxs : 0 L2-VPN Suppr. Pfxs : 0
L2-VPN Recd. Pfxs : 0 L2-VPN Active Pfxs : 0
MVPN-IPv4 Suppr. Pfxs: 0 MVPN-IPv4 Recd. Pfxs : 0
MVPN-IPv4 Active Pfxs: 0 MDT-SAFI Suppr. Pfxs : 0
MDT-SAFI Recd. Pfxs : 0 MDT-SAFI Active Pfxs : 0
FLOW-IPV4-SAFI Suppr*: 0 FLOW-IPV4-SAFI Recd.*: 0
FLOW-IPV4-SAFI Activ*: 0 Rte-Tgt Suppr. Pfxs : 0
Rte-Tgt Recd. Pfxs : 0 Rte-Tgt Active Pfxs : 0
Backup IPv4 Pfxs : 0 Backup IPv6 Pfxs : 0
Mc Vpn Ipv4 Recd. Pf*: 0 Mc Vpn Ipv4 Active P*: 0
Backup Vpn IPv4 Pfxs : 0 Backup Vpn IPv6 Pfxs : 0
Input Queue : 0 Output Queue : 0
i/p Messages : 28 o/p Messages : 24
i/p Octets : 904 o/p Octets : 669
i/p Updates : 9 o/p Updates : 6
TTL Security : Disabled Min TTL Value : n/a
Graceful Restart : Disabled Stale Routes Time : n/a
Advertise Inactive : Disabled Peer Tracking : Disabled
Advertise Label : None
Auth key chain : n/a
Disable Cap Nego : Disabled Bfd Enabled : Disabled
Flowspec Validate : Disabled Default Route Tgt : Disabled
Local Capability : RtRefresh MPBGP 4byte ASN
Remote Capability : RtRefresh MPBGP 4byte ASN
Local AddPath Capabi*: Disabled
Remote AddPath Capab*: Send - None
: Receive - None
Import Policy : None Specified / Inherited
Export Policy : toCE-vprn

-------------------------------------------------------------------------------

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 82

 Neighbors : 1
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Metro1_R2#

8. Student #1: Perform a ping from router R5 to router R6 (192.168.60.2).

R5:
*A:Metro1_R5# ping 192.168.60.2 count 1
PING 192.168.60.2 56 data bytes
64 bytes from 192.168.60.2: icmp_seq=1 ttl=62 time=4.43ms.

---- 192.168.60.2 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 4.43ms, avg = 4.43ms, max = 4.43ms, stddev = 0.000ms
*A:Metro1_R5#

9. Student #2: Perform a ping from router R6 to router R5 (192.168.50.2).

R6:
*A:Metro1_R6# ping 192.168.50.2 count 1
PING 192.168.50.2 56 data bytes
64 bytes from 192.168.50.2: icmp_seq=1 ttl=62 time=3.03ms.

---- 192.168.50.2 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 3.03ms, avg = 3.03ms, max = 3.03ms, stddev = 0.000ms
*A:Metro1_R6#

Lab 4.5 6VPE

1. Student #1: Shut down OSPFv3 on router R1. Configure a VPRN service with service ID
700 with the following requirements:
a. Use 65000:70 as route distinguisher and route target values.
b. Configure the VPRN service to use LDP.
c. Use BGP as PE-CE protocol between routers R1 and R5.
d. On router R1, configure a VRF interface toward router R5 with address
2001:db8:1:5::1/64 using vlan ID 70.
e. Configure MP-BGP on router R1 to exchange both IPv4 and IPv6 VPN routes
between routers R1 and R2. Ensure that all VPN routes are advertised into
router R5.
f. On router R5, configure a router interface toward router R1 with address
2001:db8:1:5::5/64 using vlan ID 70.
g. Ensure that all local routes in router R5 are advertised into this VPRN service.

R1:
A:Metro1_R1# configure router ospf3 shutdown
*A:Metro1_R1# configure service vprn 700 customer 1 create
*A:Metro1_R1>config>service>vprn$ route-distinguisher 65000:70
*A:Metro1_R1>config>service>vprn$ vrf-target target:65000:70
*A:Metro1_R1>config>service>vprn$ auto-bind ldp

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 83

 *A:Metro1_R1>config>service>vprn$ autonomous-system 65000
*A:Metro1_R1>config>service>vprn$ no shutdown
*A:Metro1_R1>config>service>vprn$ bgp group toR5-vprn700
*A:Metro1_R1>config>service>vprn>bgp>group$ neighbor 2001:db8:1:5::5
*A:Metro1_R1>config>service>vprn>bgp>group>neighbor$ peer-as 65005
*A:Metro1_R1>config>service>vprn>bgp>group>neighbor$ family ipv6
*A:Metro1_R1>config>service>vprn>bgp>group>neighbor$ export "toCE-vprn"
*A:Metro1_R1>config>service>vprn>bgp>group>neighbor$ exit
*A:Metro1_R1>config>service>vprn>bgp>group$ exit
*A:Metro1_R1>config>service>vprn$ interface toR5-vprn700 create
*A:Metro1_R1>config>service>vprn>if$ ipv6 address 2001:db8:1:5::1/64
*A:Metro1_R1>config>service>vprn>if$ sap 1/1/2:70 create
*A:Metro1_R1>config>service>vprn>if>sap$ exit all
*A:Metro1_R1# configure router bgp
*A:Metro1_R1>config>router>bgp# group "mbgp"
*A:Metro1_R1>config>router>bgp>group# family vpn-ipv4 vpn-ipv6
*A:Metro1_R1>config>router>bgp>group# exit all

R5:
A:Metro1_R5# configure router interface toR1-vprn700
*A:Metro1_R5>config>router>if$ ipv6
*A:Metro1_R5>config>router>if>ipv6$ address 2001:db8:1:5::5/64
*A:Metro1_R5>config>router>if>ipv6$ back
*A:Metro1_R5>config>router>if$ port 1/1/2:70
*A:Metro1_R5>config>router>if$ exit all
*A:Metro1_R5# configure router bgp
*A:Metro1_R5>config>router>bgp# group toR1-vprn700
*A:Metro1_R5>config>router>bgp>group$ neighbor 2001:db8:1:5::1
*A:Metro1_R5>config>router>bgp>group>neighbor$ peer-as 65000
*A:Metro1_R5>config>router>bgp>group>neighbor$ family ipv6
*A:Metro1_R5>config>router>bgp>group>neighbor$ export "direct"

2. Student #2: Shut down OSPFv3 on router R2. Configure a VPRN service with service ID
700 with the following requirements:
a. Use 65000:70 as route distinguisher and route target values.
b. Configure the VPRN service to use LDP.
c. Use BGP as PE-CE protocol between routers R2 and R6.
d. On router R2, configure a VRF interface toward router R6 with address
2001:db8:2:6::2/64 using vlan ID 70.
e. Configure MP-BGP on router R2 to exchange both IPv4 and IPv6 VPN routes
between routers R1 and R2. Ensure that all IPv4 VPN routes are advertised
into router R6.
f. On router R6, configure a router interface toward router R2 with address
2001:db8:2:6::6/64 using vlan ID 70.
g. Ensure that all local routes in router R6 are advertised into this VPRN service.

R2:
A:Metro1_R2# configure router ospf3 shutdown
*A:Metro1_R2# configure service vprn 700 customer 1 create
*A:Metro1_R2>config>service>vprn$ route-distinguisher 65000:70
*A:Metro1_R2>config>service>vprn$ vrf-target target:65000:70
*A:Metro1_R2>config>service>vprn$ auto-bind ldp
*A:Metro1_R2>config>service>vprn$ autonomous-system 65000
*A:Metro1_R2>config>service>vprn$ no shutdown
*A:Metro1_R2>config>service>vprn$ bgp group toR6-vprn700
*A:Metro1_R2>config>service>vprn>bgp>group$ neighbor 2001:db8:2:6::6
*A:Metro1_R2>config>service>vprn>bgp>group>neighbor$ peer-as 65006
*A:Metro1_R2>config>service>vprn>bgp>group>neighbor$ family ipv6

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 84

 *A:Metro1_R2>config>service>vprn>bgp>group>neighbor$ export "toCE-vprn"
*A:Metro1_R2>config>service>vprn>bgp>group>neighbor$ exit
*A:Metro1_R2>config>service>vprn>bgp>group$ exit
*A:Metro1_R2>config>service>vprn$ interface toR6-vprn700 create
*A:Metro1_R2>config>service>vprn>if$ ipv6 address 2001:db8:2:6::2/64
*A:Metro1_R2>config>service>vprn>if$ sap 1/1/2:70 create
*A:Metro1_R2>config>service>vprn>if>sap$ exit all
*A:Metro1_R2# configure router bgp
*A:Metro1_R2>config>router>bgp# group "mbgp"
*A:Metro1_R2>config>router>bgp>group# family vpn-ipv4 vpn-ipv6
*A:Metro1_R2>config>router>bgp>group# exit all

R6:
A:Metro1_R6# configure router interface toR2-vprn700
*A:Metro1_R6>config>router>if$ ipv6 address 2001:db8:2:6::6/64
*A:Metro1_R6>config>router>if$ port 1/1/2:70
*A:Metro1_R6>config>router>if$ exit all
*A:Metro1_R6# configure router bgp
*A:Metro1_R6>config>router>bgp# group toR2-vprn700
*A:Metro1_R6>config>router>bgp>group$ neighbor 2001:db8:2:6::2
*A:Metro1_R6>config>router>bgp>group>neighbor$ peer-as 65000
*A:Metro1_R6>config>router>bgp>group>neighbor$ family ipv6
*A:Metro1_R6>config>router>bgp>group>neighbor# export "direct"

3. Verify that the VPRN service is operationally up.

R1:
*A:Metro1_R1# show service id 700 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 700 Vpn Id : 0
Service Type : VPRN
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 14:41:57
Last Mgmt Change : 02/12/2013 14:41:57
Admin State : Up Oper State : Up

Route Dist. : 65000:70 VPRN Type : regular

AS Number : 65000 Router Id : 10.10.10.1
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit Auto Bind : LDP
Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Vrf Target : target:65000:70
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled

SAP Count : 1 SDP Bind Count : 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:70 q-tag 1518 1518 Up Up
===============================================================================

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 85

 *A:Metro1_R1#

R2:
*A:Metro1_R2# show service id 700 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 700 Vpn Id : 0
Service Type : VPRN
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/12/2013 14:33:20
Last Mgmt Change : 02/12/2013 14:33:20
Admin State : Up Oper State : Up

Route Dist. : 65000:70 VPRN Type : regular

AS Number : 65000 Router Id : 10.10.10.2
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit Auto Bind : LDP
Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Vrf Target : target:65000:70
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled

SAP Count : 1 SDP Bind Count : 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:70 q-tag 1518 1518 Up Up
===============================================================================
*A:Metro1_R2#

4. Student #1: Perform a ping from router R5 to router R6 (2001:DB8:2:6::6).

R5:
*A:Metro1_R5# ping 2001:DB8:2:6::6 count 1
PING 2001:DB8:2:6::6 56 data bytes
64 bytes from 2001:DB8:2:6::6 icmp_seq=1 hlim=62 time=3.59ms.

---- 2001:DB8:2:6::6 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 3.59ms, avg = 3.59ms, max = 3.59ms, stddev = 0.000ms
*A:Metro1_R5#

5. Student #2: Perform a ping from router R6 to router R5 (2001:DB8:DD:501::1).

R6:
*A:Metro1_R6# ping 2001:DB8:1:5::5 count 1
PING 2001:DB8:1:5::5 56 data bytes
64 bytes from 2001:DB8:1:5::5 icmp_seq=1 hlim=62 time=3.55ms.

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 86

 ---- 2001:DB8:1:5::5 PING Statistics ----
1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 3.55ms, avg = 3.55ms, max = 3.55ms, stddev = 0.000ms
*A:Metro1_R6#

Lab 4.6 VPLS spoke termination on VPRN (OPTIONAL)

1. Student #1: On router R1, configure a VPLS with service ID 800 with the following
requirements:
a. Configure a SAP toward router R5 using vlan ID 80.
b. On router R5, configure an interface toward router R1 with IP address
192.168.80.1/24 using vlan ID 80.

R1:
A:Metro1_R1# configure service vpls 800 customer 1 create
*A:Metro1_R1>config>service>vpls$ sap 1/1/2:80 create
*A:Metro1_R1>config>service>vpls>sap$ back
*A:Metro1_R1>config>service>vpls$ no shutdown

R5:
A:Metro1_R5# configure router interface toR1-vpls800
*A:Metro1_R5>config>router>if$ address 192.168.80.1/24
*A:Metro1_R5>config>router>if$ port 1/1/2:80

2. Student #2: On router R2, configure a VPRN service with service ID 800 with the
following requirements:
a. Use 65000:80 as route distinguisher and route target values.
b. Configure the VPRN service to use LDP.
c. Create a VRF interface with IP address 192.168.80.2/24.

R2:
A:Metro1_R2# configure service vprn 800 customer 1 create
*A:Metro1_R2>config>service>vprn$ route-distinguisher 65000:800
*A:Metro1_R2>config>service>vprn$ vrf-target target:65000:80
*A:Metro1_R2>config>service>vprn$ interface toR1 create
*A:Metro1_R2>config>service>vprn>if$ address 192.168.80.2/24
*A:Metro1_R2>config>service>vprn>if$ back
*A:Metro1_R2>config>service>vprn$ autonomous-system 65000
*A:Metro1_R2>config>service>vprn$ no shutdown

3. Student #1: On router R1, connect the VPLS to the VPRN service with service ID 800
that Student #2 configured.
R1:
*A:Metro1_R1# configure service vpls 800
*A:Metro1_R1>config>service>vpls# spoke-sdp 2:800 create

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 87

4. Student #2: On router R2, connect the VPRN service to the VPLS with service ID 800
that Student #1 configured.
R2:
*A:Metro1_R2# configure service vprn 800
*A:Metro1_R2>config>service>vprn# interface "toR1"
*A:Metro1_R2>config>service>vprn>if# spoke-sdp 1:800 create
*A:Metro1_R2>config>service>vprn>if>spoke-sdp$ back
*A:Metro1_R2>config>service>vprn>if# ip-mtu 1500

5. Verify that both the VPLS and the VPRN service are operationally up.

R1:
*A:Metro1_R1# show service id 800 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 800 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/13/2013 10:05:12
Last Mgmt Change : 02/13/2013 10:09:34
Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 800
SAP Count : 1 SDP Bind Count : 1
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
Def. Gateway IP : None
Def. Gateway MAC : None
Temp Flood Time : Disabled Temp Flood : Inactive
Temp Flood Chg Cnt: 0

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:80 q-tag 1518 1518 Up Up
sdp:2:800 S(10.10.10.2) Spok 0 1556 Up Up
===============================================================================
*A:Metro1_R1#

R2:
*A:Metro1_R2# show service id 800 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 800 Vpn Id : 0
Service Type : VPRN
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 02/13/2013 09:54:37
Last Mgmt Change : 02/13/2013 09:57:07
Admin State : Up Oper State : Up

Route Dist. : 65000:80 VPRN Type : regular

AS Number : 65000 Router Id : 10.10.10.2
ECMP : Enabled ECMP Max Routes : 1
Max IPv4 Routes : No Limit Auto Bind : None

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 88

 Max IPv6 Routes : No Limit
Ignore NH Metric : Disabled
Hash Label : Disabled
Vrf Target : target:65000:80
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None
Car. Sup C-VPN : Disabled
Label mode : vrf
BGP VPN Backup : Disabled

SAP Count : 0 SDP Bind Count : 1

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:1:800 S(10.10.10.1) TLDP 0 1556 Up Up
===============================================================================
*A:Metro1_R2#

6. Student #1: Perform a ping from router R5 to the VRF interface address
(192.168.80.2).

*A:Metro1_R5# ping 192.168.80.2 count 1

PING 192.168.80.2 56 data bytes
64 bytes from 192.168.80.2: icmp_seq=1 ttl=64 time=4.93ms.

---- 192.168.80.2 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 4.93ms, avg = 4.93ms, max = 4.93ms, stddev = 0.000ms
*A:Metro1_R5#

7. Student #2: Perform a ping from router R2 to router R5 interface address

(192.168.80.1).

*A:Metro1_R2# ping 192.168.80.1 router 800 count 1

PING 192.168.80.1 56 data bytes
64 bytes from 192.168.80.1: icmp_seq=1 ttl=64 time=2.77ms.

---- 192.168.80.1 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 2.77ms, avg = 2.77ms, max = 2.77ms, stddev = 0.000ms
*A:Metro1_R2#

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 89

List of Commands
Commands required for this workshop are found in the Table 3. Use the ‘?’ character for help and to
explore all command line options.

Configuration Commands
configure router interface <name> address <address>
configure router interface <name> ipv6
configure router interface <name> ipv6 [address <ipv6 address>]
configure router interface port <x/x/x>
configure router ospf area <area-id>
configure router ospf area <area-id> interface <interface-name>
configure router ospf area <area-id> interface <interface-name> interface-type point-
to-point
configure router ospf area <area-id> area-range <ip-prefix/mask> [advertise|not-
advertise]
configure router ospf area <area-id> nssa
configure router ospf area <area-id> nssa originate-default-route
configure router ospf area <area-id> nssa summaries
configure router ospf area <area-id> stub
configure router ospf area <area-id> stub summaries
configure router ospf traffic-engineering
configure router isis area-id <area-address>
configure router isis interface <interface-name>
configure router isis interface <interface-name> hello-authentication
configure router isis interface <interface-name> hello-authentication-type {password
| message-digest}
configure router isis interface <interface-name> hello-authentication-key
<authentication-key | hash-key>
configure router isis level <1|2> wide-metric-only
configure router isis reference-bandwidth <reference-bandwidth>
configure router bgp group <group-name>
configure router bgp group <group-name> family {ipv6} {vpn-ipv4} {vpn-ipv6}
configure router bgp group <group-name> local-as <as number>
configure router bgp group <group-name> remote-as <as number>
configure router mpls interface <ip-int-name>
configure router mpls path <path-name>
configure router mpls path <path-name> hop <index> [strict | loose]
configure router mpls lsp <lsp-name>

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 90

 Configuration Commands
configure router mpls lsp <lsp-name> adspec
configure router mpls lsp <lsp-name> cspf
configure router mpls lsp <lsp-name> fast-reroute [one-to-one|facility]
configure router mpls lsp <lsp-name> hop-limit <number>
configure router mpls lsp <lsp-name> primary <path-name>
configure router mpls lsp <lsp-name> secondary <path-name>
configure router mpls lsp <lsp-name> rsvp-resv-style [se | ff]
configure service epipe <service-id> [customer <customer-id>] create
configure service epipe <service-id> spoke-sdp <sdp-id:vc-id> create
configure service epipe <service-id> sap <sap-id> create
configure service vpls <service-id> [customer <customer-id>] create
configure service vpls <service-id> spoke-sdp <sdp-id:vc-id> create
configure service vpls <service-id> sap <sap-id> create
configure service ies <service-id> [customer <customer-id>] create
configure service ies <service-id> interface <interface-name> create
configure service ies <service-id> interface <interface-name> ip-mtu <mtu>
configure service ies <service-id> interface <interface-name> address
<prefix/mask>
configure service ies <service-id> interface <interface-name> spoke-sdp
<sdp-id:vc-id>
configure service vprn <service-id> [customer <customer-id>] create
configure service vprn <service-id> route-distinguisher <route distingisher>
configure service vprn <service-id> vrf-target <route target>
configure service vprn <service-id> auto-bind rsvp-te
configure service vprn <service-id> interface <interface-name> create
configure service vprn <service-id> interface <interface-name> address
<prefix/mask>
show port
show mda
show chassis
show card <card-number>
show router interface
show router static-route [ipv6]
show router [ospf|ospf3] interface
show router [ospf|ospf3] neighbor
show router [ospf|ospf3] area
show router [ospf|ospf3] database
show router ospf opaque-database

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 91

 Configuration Commands
show router isis interface
show router isis adjacency
show router isis database
show router bgp neighbor
show router bgp routes vpn-ipv4
show router bgp routes vpn-ipv6
show router mpls interface
show router mpls path
show router mpls lsp [detail]
show router mpls lsp <lsp-name> path detail
show router rsvp session
show router rsvp interface detail
show service id <id> base
show service id <id> fdb detail
show router route-table [ipv6]
show router <vrf instance> route-table [ipv6]
admin save

Table 3: Command List

Alcatel-Lucent NRSII Workshop A v1.0 | All Rights reserved © 2013 Alcatel-Lucent 92