0% found this document useful (0 votes)

231 views122 pages

Services Architecture v3.2 Lab Guide

Uploaded by

Nathaly

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

231 views122 pages

Services Architecture v3.2 Lab Guide

Uploaded by

Nathaly

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 122

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Alcatel-Lucent Services Architecture

Lab Guide
Revision 3.2
April 2012

Software Version: 7750 SR OS 8.0

TABLE OF CONTENTS

LAB 1 IP/MPLS INFRASTRUCTURE....................................................................................................................5

LAB 2 DISTRIBUTED EPIPE SERVICE..............................................................................................................11

LAB 3 VPLS SERVICE..........................................................................................................................................17

LAB 4 SPOKE TERMINATION TO A VPLS .......................................................................................................29

LAB 5 OAM TOOLS..............................................................................................................................................39

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

LAB 6 MIRROR SERVICE....................................................................................................................................46

LAB 7 INTERNET ENHANCED SERVICE (IES)................................................................................................55

LAB 8 VPLS SPOKE TERMINATION ON IES ...................................................................................................59

LAB 9 IPV4 VPRNS...............................................................................................................................................62

LAB 10 IPV6 VPRNS (6VPE) ..................................................................................................................................74

ANSWERS TO REVIEW QUESTIONS ....................................................................................................................84

LAB SOLUTIONS......................................................................................................................................................91

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 2/122
LIST OF FIGURES

Figure 1-1 Physical Connectivity ......................................................................................................................5

Figure 2-1 Distributed Epipe Setup .................................................................................................................11
Figure 3-1 Single VPLS Service .....................................................................................................................17
Figure 4-1 Spoke Termination to a VPLS .......................................................................................................29
Figure 5-1 Epipe 10 .........................................................................................................................................39
Figure 6-1 Local Mirror Service......................................................................................................................46
Figure 7-1 IES Service ....................................................................................................................................55

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 8-1 VPLS 1000 Terminating on IES ....................................................................................................59
Figure 9-1 IPv4 VPRNs...................................................................................................................................62
Figure 10-1 IPv6 VPRNs.................................................................................................................................74

3/122
LIST OF TABLES
Table 1-1 Lab 1 Command List.........................................................................................................................6
Table 1-2 IP Interface Addresses.......................................................................................................................7
Table 2-1 Lab 2 Command List.......................................................................................................................12
Table 3-1 VPLS Service Commands...............................................................................................................18
Table 6-1 Mirror Service Command List ........................................................................................................47
Table 8-1 VPLS with Spoke SDP Commands ................................................................................................59
Table 9-1 IPv4 Addresses................................................................................................................................63
Table 9-2 Customer Provisioning Parameters .................................................................................................66

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Table 9-3 Configuration Parameters................................................................................................................68
Table 10-1 IPv6 Addresses..............................................................................................................................75

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 4/122
LAB 1 IP/MPLS Infrastructure
Objectives:
 Verify the preconfigured IP addressing and physical operation
 Configure IGP routing and MPLS for the service provider network, connected according to the
following diagram:

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 1-1 Physical Connectivity

Labs 1-10:
 Routers R1 through R4 are used as P routers
 Routers R5 through R8 are used as PE routers
 Routers R9 through R12 are used as CE routers

5/122
Syntax:
Commands required for this exercise are found in Table 1-1. Use the ‘?’ character for help and to
explore all command line options. Other commands may also be used, including those from previous
courses.

Lab 1 Configuration Command List

configure router interface <name> address <address>

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure router interface port <x/x/x>
configure router isis
configure router isis interface <interface-name>
configure router ldp
configure router ldp interface-parameters
show router interface
show router isis interface
show router route-table protocol isis
show router route-table
show router ldp bindings active
admin save
Table 1-1 Lab 1 Command List
Exercise:
1. Connect to the routers in your pod using the management IP addresses from the lab diagram given
to you by your instructor. The username and password for all devices is ‘admin’. If you are unable
to connect to any of the routers, notify your instructor.

2. Check the port MTU for all the network ports. If any are set to 1514, make sure they are set to at
least 1536 to support the Layer 2 services we will configure later.

3. Verify the preconfigured interfaces. The IP addresses should be similar to those shown in Table 1-2,
unless you are given a different address plan by your instructor.

4. Configure the service provider network with IS-IS as the routing protocol. Configure all routers as
Level 1/2 capable with point-to-point interfaces. Put each router in area x, where x is your pod
number.

5. Configure LDP as your MPLS label distribution protocol.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 6/122
Pod Number Router Port Interface IP Address
name
Pod 1 R5 --- System 10.10.10.5/32
toR1 10.1.5.5/24
R1 --- System 10.10.10.1/32
toR3 10.1.3.1/24
toR2 10.1.2.1/24

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

toR5 10.1.5.1/24
toR4 10.1.4.1/24
Pod 2 R6 --- System 10.10.10.6/32
toR2 10.2.6.6/24
R2 --- System 10.10.10.2/32
toR6 10.2.6.2/24
toR4 10.2.4.2/24
toR1 10.1.2.2/24
toR3 10.2.3.2/24
Pod 3 R7 --- System 10.10.10.7/32
toR3 10.3.7.7/24
R3 --- System 10.10.10.3/32
toR1 10.1.3.3/24
toR4 10.3.4.3/24
toR2 10.2.3.3/24
toR7 10.3.7.3/24
Pod 4 R8 --- System 10.10.10.8/32
toR4 10.4.8.8/24
R4 --- System 10.10.10.4/32
toR8 10.4.8.4/24
toR3 10.3.4.4/24
toR1 10.1.4.4/24
toR2 10.2.4.4/24
Table 1-2 IP Interface Addresses

7/122
Verification:
1. Verify that all required interfaces are active and operational.

*A:R1# show router interface

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

IP-Address PfxState
-------------------------------------------------------------------------------
system Up Up/Down Network system
10.10.10.1/32 n/a
toR2 Up Up/Down Network 1/1/2
10.1.2.1/24 n/a
toR3 Up Up/Down Network 1/1/3
10.1.3.1/24 n/a
toR4 Up Up/Down Network 1/1/4
10.1.4.1/24 n/a
toR5 Up Up/Down Network 1/1/1
10.1.5.1/24 n/a
-------------------------------------------------------------------------------
Interfaces : 5

2. Verify that the routing tables on the routers of your pod have all internal networks listed.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 8/122
*A:R1# show router route-table

===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.2.0/24 Local Local 00h44m53s 0
toR2 0
10.1.3.0/24 Local Local 00h44m31s 0
toR3 0

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

10.1.4.0/24 Local Local 00h44m20s 0
toR4 0
10.1.5.0/24 Local Local 00h44m00s 0
toR5 0
10.2.3.0/24 Remote ISIS 00h06m18s 15
10.1.2.2 20
10.2.4.0/24 Remote ISIS 00h06m12s 15
10.1.2.2 20
10.2.6.0/24 Remote ISIS 00h06m00s 15
10.1.2.2 20
10.3.4.0/24 Remote ISIS 00h04m37s 15
10.1.3.3 20
10.3.7.0/24 Remote ISIS 00h04m19s 15
10.1.3.3 20
10.4.8.0/24 Remote ISIS 00h03m21s 15
10.1.4.4 20
10.10.10.1/32 Local Local 06d22h31m 0
system 0
10.10.10.2/32 Remote ISIS 00h06m24s 15
10.1.2.2 10
10.10.10.3/32 Remote ISIS 00h04m50s 15
10.1.3.3 10
10.10.10.4/32 Remote ISIS 00h03m46s 15
10.1.4.4 10
10.10.10.5/32 Remote ISIS 00h03m01s 15
10.1.5.5 10
10.10.10.6/32 Remote ISIS 00h02m16s 15
10.1.2.2 20
10.10.10.7/32 Remote ISIS 00h01m50s 15
10.1.3.3 20
10.10.10.8/32 Remote ISIS 00h00m31s 15
10.1.4.4 20
-------------------------------------------------------------------------------
No. of Routes: 18

3. Verify in LDP that you have active label bindings for all eight system interface addresses.

9/122
*A:R1# show router ldp bindings active

===============================================================================
Legend: (S) - Static
===============================================================================
LDP Prefix Bindings (Active)
===============================================================================
Prefix Op IngLbl EgrLbl EgrIntf/LspId EgrNextHop
-------------------------------------------------------------------------------
10.10.10.1/32 Pop 131071 -- -- --
10.10.10.2/32 Push -- 131071 1/1/2 10.1.2.2
10.10.10.2/32 Swap 131070 131071 1/1/2 10.1.2.2

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

10.10.10.3/32 Push -- 131071 1/1/3 10.1.3.3
10.10.10.3/32 Swap 131069 131071 1/1/3 10.1.3.3
10.10.10.4/32 Push -- 131071 1/1/4 10.1.4.4
10.10.10.4/32 Swap 131068 131071 1/1/4 10.1.4.4
10.10.10.5/32 Push -- 131071 1/1/1 10.1.5.5
10.10.10.5/32 Swap 131067 131071 1/1/1 10.1.5.5
10.10.10.6/32 Push -- 131066 1/1/2 10.1.2.2
10.10.10.6/32 Swap 131066 131066 1/1/2 10.1.2.2
10.10.10.7/32 Push -- 131065 1/1/3 10.1.3.3
10.10.10.7/32 Swap 131065 131065 1/1/3 10.1.3.3
10.10.10.8/32 Push -- 131064 1/1/4 10.1.4.4
10.10.10.8/32 Swap 131064 131064 1/1/4 10.1.4.4
-------------------------------------------------------------------------------

Notes

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 10/122
LAB 2 Distributed Epipe Service
Objective:
 Configure two epipe services.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 2-1 Distributed Epipe Setup

11/122
Lab 2 command list
configure service customer <customer-id> create
configure service epipe <service-id> customer <customer-id> create
configure service epipe <service-id> sap <sap-id> [create]
configure service sdp <sdp-id> mpls create
configure service sdp far-end <ip address>
configure service sdp lsp <lsp-name>

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure service sdp signaling tldp
configure router ldp no shutdown
configure service epipe spoke-sdp <sdp-id:vc-id> create
configure port <port-id> ethernet encap-type dot1q
configure port <port-id> ethernet mode [access | network]
configure port <port-id> ethernet mtu <mtu-bytes>
Table 2-1 Lab 2 Command List
Exercise
Configure epipe services across the core by following the steps outlined below:

Phase I
1. On the CE routers, configure the network port towards the PE router for dot1q encapsulation. In
the lab exercise to follow, multiple IP interfaces will be configured using a different VLAN ID for
each one.

2. On the CE router, configure a first interface towards your PE router with an IP address of
192.168.10.x/24 (where x is your pod number) using a VLAN ID of 10.

3. On your PE router, create an SDP using LDP to your diagonal pod (pods 1 and 4 are diagonal and
pods 2 and 3 are diagonal).

4. Create an epipe service on your PE router with a SAP for the epipe on the port facing your CE
router. You will have to change this port to access mode. Be sure to use dot1q encapsulation on
your SAP and the same VLAN ID of 10.

5. Bind the service to your SDP using a spoke SDP.

6. Stop here and wait until the instructor has introduced Phase II before proceeding.

Phase II
1. Switch routers with your pod partner so that the person who configured the CE router in Phase I
will configure the PE router in Phase II, and vice versa.

2. Configure a second interface on the CE router similar to the first, with the address
192.168.20.x/24, except this time the VLAN ID will be 20.

3. Create a second epipe service to your diagonal pod using VLAN 20.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 12/122
Verification:
The epipe service should be operational at this time. Use the following verification steps to ensure the
epipe is operational and to discover useful information about the service and the associated LSPs.

Note: the sample verification screen shots shown below are only for one epipe service on pod 1. Actual
screen shots will vary for each pod.

1. Use the show service SDP command to ensure the SDP is operational

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5# show service sdp 8

==============================================================================
Service Destination Point (Sdp Id : 8)
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
8 0 1556 10.10.10.8 Up Up LDP TLDP
==============================================================================

2. Use the show service sap-using command to verify the correct Service ID is being used and to
ensure that the SAP is both administratively and operationally UP.

*A:R5# show service sap-using

===============================================================================
Service Access Points
===============================================================================
PortId SvcId Ing. Ing. Egr. Egr. Adm Opr
QoS Fltr QoS Fltr
-------------------------------------------------------------------------------
1/1/2:10 10 1 none 1 none Up Up
1/1/2:20 20 1 none 1 none Up Up
-------------------------------------------------------------------------------
Number of SAPs : 2
-------------------------------------------------------------------------------

3. Use the show service id svc-id base command to verify that the epipe is UP and to confirm the
Customer ID, SAP ID and Spoke ID.

13/122
*A:R5# show service id 10 base

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

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:10 q-tag 1518 1518 Up Up
sdp:8:10 S(10.10.10.8) Spok 0 1556 Up Up
===============================================================================

4. Use the show service id svc-id all command to display more detailed information about your
service. This information can be used for troubleshooting as well as statistics-gathering. This
command will provide you with the following information:
 Service type
 Service Destination Point (SDP)
 LSP associated with the SDP
 Number of SDPs
 SAPs are associated with this service
 Encapsulation type used
 SAP statistics
 Queuing statistics

5. Use the show service id svc-id labels command to see the inner Martini service labels and to
ensure that the Service ID is being mapped to the correct SDP binding.

*A:R5# show service id 10 labels

===============================================================================
Martini Service Labels
===============================================================================
Svc Id Sdp Binding Type I.Lbl E.Lbl
-------------------------------------------------------------------------------
10 8:10 Spok 131063 131063
-------------------------------------------------------------------------------
Number of Bound SDPs : 1
-------------------------------------------------------------------------------

6. Use the show router ldp bindings command to ensure that LDP is operational, and to ensure
that you are seeing the LDP binding for the service peer.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 14/122
*A:R5# show router ldp bindings

===============================================================================
LDP LSR ID: 10.10.10.5
===============================================================================
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 Service, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service
TLV - (Type, Length: Value)
===============================================================================

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

LDP Prefix Bindings
===============================================================================
Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
10.10.10.1/32 10.10.10.1 -- 131071 1/1/1 10.1.5.1
10.10.10.2/32 10.10.10.1 131069N 131070 1/1/1 10.1.5.1
10.10.10.3/32 10.10.10.1 131068N 131069 1/1/1 10.1.5.1
10.10.10.4/32 10.10.10.1 131067N 131068 1/1/1 10.1.5.1
10.10.10.5/32 10.10.10.1 131071U -- -- --
10.10.10.6/32 10.10.10.1 131066N 131066 1/1/1 10.1.5.1
10.10.10.7/32 10.10.10.1 131065N 131065 1/1/1 10.1.5.1
10.10.10.8/32 10.10.10.1 131064N 131064 1/1/1 10.1.5.1
-------------------------------------------------------------------------------
No. of Prefix Bindings: 8

===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 8 10.10.10.8 131063U 131063S 1500 1500
E-Eth 20 20 8 10.10.10.8 131062U 131062S 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 2

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

7. Ping from your CE router to the CE router of your diagonally connected pod.

Note: In order to ping successfully, both CE routers have to be members of the same subnet.

15/122
*A:R9# ping 192.168.10.4
PING 192.168.10.4 56 data bytes
64 bytes from 192.168.10.4: icmp_seq=1 ttl=64 time=7.33ms.
64 bytes from 192.168.10.4: icmp_seq=2 ttl=64 time=4.42ms.
64 bytes from 192.168.10.4: icmp_seq=3 ttl=64 time=4.37ms.
64 bytes from 192.168.10.4: icmp_seq=4 ttl=64 time=4.37ms.
64 bytes from 192.168.10.4: icmp_seq=5 ttl=64 time=4.22ms.

---- 192.168.10.4 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.22ms, avg = 4.94ms, max = 7.33ms, stddev = 1.19ms

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Questions:

1. You can see labels for the system address of P routers as well as PE routers by using the show router
ldp bindings command. A label is required for the PE router because it is the end of the transport
tunnel. Why do P routers need labels as well?
_______________________________________________________________________________

2. The show router ldp bindings command shows the LMTU and RMTU for the service. What is the
meaning of these values? Why is the value 1500?
_______________________________________________________________________________

3. CE1, CE2, CE3 and CE4 are all in the same subnet. Why is it possible to ping CE4 from CE1, but not
from CE2 or CE3?
_______________________________________________________________________________

Notes

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 16/122
LAB 3 VPLS Service
Objective:
 Configure a Virtual Private LAN Service (VPLS).

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 3-1 Single VPLS Service

17/122
Lab 3-1 Command List
configure service customer <customer-id> create
configure service vpls <service-id> customer <customer-id> create
configure service vpls description
configure port <port-id> ethernet mode access
configure service vpls <service-id>
configure service vpls sap <sap-id> create

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure service sdp <sdp-id> mpls create
configure service sdp far-end <ip address>
configure service sdp lsp <name>
configure router ldp no shotdown
configure service vpls mesh-sdp <sdp-id> create
configure service vpls <service-id> no shutdown
Table 3-1 VPLS Service Commands
Exercise I:

1. Ensure that you have active LDP label bindings for all four PE routers within the domain.

2. Create a full mesh of Service Distribution Paths (SDP) between all PE routers. You must create an
SDP from your router to every other router that is part of the VPLS; in other words, create an SDP to
each other PE router within the domain. In this lab, each of the other PE routers is part of the VPLS.

3. Create a Customer ID of 200. Use Customer 200 to create a VPLS that has a Service ID of 200.

4. Verify that the PE port connecting to the CE is configured as an access port with dot1q
encapsulation.

5. Add a SAP to the VPLS service. Use dot1q encapsulation with VLAN ID of 30 for the SAP.

6. Bind each of the SDPs to the VPLS as a mesh SDP.

7. Administratively enable the VPLS service.

8. Create a common subnet for all CE routers. Use subnet 192.168.30.0/24 as the common subnet and
configure the CE network interface for VLAN ID 30 with address 192.168.30.x/24, where x is your
pod number. You should be able to ping all other CE routers on this common subnet once all the
other students have completed their configurations.

Verification

1. Use the show service id 200 base command to verify that the service and all components are
operational.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 18/122
*A:R5# show service id 200 base

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 200
SAP Count : 1 SDP Bind Count : 3
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Def. Gateway IP : None
Def. Gateway MAC : None

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:30 q-tag 1518 1518 Up Up
sdp:6:200 M(10.10.10.6) Mesh 0 1556 Up Up
sdp:7:200 M(10.10.10.7) Mesh 0 1556 Up Up
sdp:8:200 M(10.10.10.8) Mesh 0 1556 Up Up
===============================================================================

2. Use the show service id 200 all command and compare the results to show service id 200 base.

3. Use the show service fdb-mac command. How many MAC addresses are in the table? Explain.

*A:R5# show service fdb-mac

===============================================================================
Service Forwarding Database
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
No. of Entries: 0
-------------------------------------------------------------------------------
Legend: L=Learned; P=MAC is protected

4. Use the ping command to ensure that your CE router can ping the other CE routers.

19/122
*A:R9# ping 192.168.30.4
PING 192.168.30.4 56 data bytes
64 bytes from 192.168.30.4: icmp_seq=1 ttl=64 time=10.0ms.
64 bytes from 192.168.30.4: icmp_seq=2 ttl=64 time=3.92ms.
64 bytes from 192.168.30.4: icmp_seq=3 ttl=64 time=4.49ms.
64 bytes from 192.168.30.4: icmp_seq=4 ttl=64 time=4.56ms.
64 bytes from 192.168.30.4: icmp_seq=5 ttl=64 time=4.73ms.

---- 192.168.30.4 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 3.92ms, avg = 5.54ms, max = 10.0ms, stddev = 2.26ms

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

5. Use the show service fdb-mac command to confirm that the MAC forwarding database now
contains entries.

*A:R5# show service fdb-mac

===============================================================================
Service Forwarding Database
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
200 7a:4c:01:01:00:02 sap:1/1/2:30 L/60 01/10/2012 23:30:03
200 7a:4f:01:01:00:02 sdp:8:200 L/60 01/10/2012 23:30:03
-------------------------------------------------------------------------------
No. of Entries: 2
-------------------------------------------------------------------------------
Legend: L=Learned; P=MAC is protected
===============================================================================

6. Confirm the source of the MAC addresses found above.

a) Use the show port <port-id> command on your CE router to find the MAC address of your CE
router interface and compare that MAC address to the MAC address found in step 5.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 20/122
*A:R9# show port 1/1/2

===============================================================================
Ethernet Interface
===============================================================================
Description : 1-Gig Ethernet SFP
Interface : 1/1/2 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

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

IfIndex : 35717120 Hold time up : 0 seconds
Last State Change : 01/10/2012 20:48:45 Hold time down : 0 seconds
Last Cleared Time : N/A DDM Events : Enabled

Configured Mode : network Encap Type : 802.1q

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
Auto-negotiate : true MDI/MDX : N/A
Accounting Policy : None Collect-stats : Disabled
Egress Rate : Default Ingress Rate : Default
Load-balance-algo : default LACP Tunnel : Disabled

Down-when-looped : Disabled Keep-alive : 10

Loop Detected : False Retry : 120
Use Broadcast Addr : False

Sync. Status Msg. : Disabled Rx Quality Level : N/A

Configured Address : 7a:4c:01:01:00:02

Hardware Address : 7a:4c:01:01:00:02
Cfg Alarm :
Alarm Status :

===============================================================================
Traffic Statistics
===============================================================================
Input Output
-------------------------------------------------------------------------------
Octets 1196 1516
Packets 12 17
Errors 0 0
===============================================================================

b) Ask the person in the corresponding pod to confirm their CE router MAC address and
compare it to the MAC address discovered in step 6 above.

21/122
*A:R8# show service fdb-mac

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

-------------------------------------------------------------------------------
Legend: L=Learned; P=MAC is protected
===============================================================================

7. At this point you should be able to ping all CE devices in the network. If not, troubleshoot the
problem until this is complete.

*A:R9# ping 192.168.30.2

PING 192.168.30.2 56 data bytes
64 bytes from 192.168.30.2: icmp_seq=1 ttl=64 time=10.5ms.
64 bytes from 192.168.30.2: icmp_seq=2 ttl=64 time=4.64ms.
64 bytes from 192.168.30.2: icmp_seq=3 ttl=64 time=4.57ms.
64 bytes from 192.168.30.2: icmp_seq=4 ttl=64 time=5.68ms.
64 bytes from 192.168.30.2: icmp_seq=5 ttl=64 time=5.57ms.

---- 192.168.30.2 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.57ms, avg = 6.20ms, max = 10.5ms, stddev = 2.22ms

*A:R9# ping 192.168.30.3

PING 192.168.30.3 56 data bytes
64 bytes from 192.168.30.3: icmp_seq=1 ttl=64 time=10.2ms.
64 bytes from 192.168.30.3: icmp_seq=2 ttl=64 time=4.84ms.
64 bytes from 192.168.30.3: icmp_seq=3 ttl=64 time=4.80ms.
64 bytes from 192.168.30.3: icmp_seq=4 ttl=64 time=4.22ms.
64 bytes from 192.168.30.3: icmp_seq=5 ttl=64 time=4.65ms.

---- 192.168.30.3 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.22ms, avg = 5.74ms, max = 10.2ms, stddev = 2.23ms
round-trip min = 3.74ms, avg = 3.97ms, max = 4.34ms, stddev = 0.234ms

8. Use the show service fdb-mac command to confirm that the MAC forwarding database now
contains all expected entries.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 22/122
*A:R5# show service fdb-mac
===============================================================================
Service Forwarding Database
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
200 7a:4c:01:01:00:02 sap:1/1/2:30 L/60 01/10/2012 23:41:20
200 7a:4d:01:01:00:02 sdp:6:200 L/75 01/10/2012 23:41:20
200 7a:4e:01:01:00:02 sdp:7:200 L/75 01/10/2012 23:41:28
200 7a:4f:01:01:00:02 sdp:8:200 L/60 01/10/2012 23:30:03
-------------------------------------------------------------------------------

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

No. of Entries: 4
-------------------------------------------------------------------------------
Legend: L=Learned; P=MAC is protected
===============================================================================

9. Confirm the CE routers MAC addresses and compare them to the MAC addresses discovered in step 8
above.

*A:R9# show port 1/1/2

===============================================================================
Ethernet Interface
===============================================================================
…output omitted

Configured Address : 7a:4c:01:01:00:02

Hardware Address : 7a:4c:01:01:00:02

*A:R10# show port 1/1/2

===============================================================================
Ethernet Interface
===============================================================================
…output omitted

Configured Address : 7a:4d:01:01:00:02

Hardware Address : 7a:4d:01:01:00:02

*A:R11# show port 1/1/2

===============================================================================
Ethernet Interface
===============================================================================
…output omitted

Configured Address : 7a:4e:01:01:00:02

Hardware Address : 7a:4e:01:01:00:02

*A:R12# show port 1/1/2

===============================================================================
Ethernet Interface
===============================================================================
…output omitted

Configured Address : 7a:4f:01:01:00:02

Hardware Address : 7a:4f:01:01:00:02

23/122
Questions

1. What command can you use to find the service type of a service?
______________________________________________________

2. What is the MTU for this service?

______________________________________________________

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. What will happen if you try to send a frame larger than this MTU to the service?
______________________________________________________

Notes

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 24/122
Exercise II

This exercise will explore some of the possibilities for SAP encapsulation.

1. Use ping to verify that you have connectivity between CE routers over VPLS service 200.

*A:R9# ping 192.168.30.2

PING 192.168.30.2 56 data bytes
64 bytes from 192.168.30.2: icmp_seq=1 ttl=64 time=11.0ms.
64 bytes from 192.168.30.2: icmp_seq=2 ttl=64 time=5.50ms.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

64 bytes from 192.168.30.2: icmp_seq=3 ttl=64 time=5.53ms.
64 bytes from 192.168.30.2: icmp_seq=4 ttl=64 time=5.99ms.
64 bytes from 192.168.30.2: icmp_seq=5 ttl=64 time=6.55ms.

---- 192.168.30.2 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 5.50ms, avg = 6.91ms, max = 11.0ms, stddev = 2.06ms

*A:R9# ping 192.168.30.3

PING 192.168.30.3 56 data bytes
64 bytes from 192.168.30.3: icmp_seq=1 ttl=64 time=10.7ms.
64 bytes from 192.168.30.3: icmp_seq=2 ttl=64 time=5.23ms.
64 bytes from 192.168.30.3: icmp_seq=3 ttl=64 time=5.48ms.
64 bytes from 192.168.30.3: icmp_seq=4 ttl=64 time=5.34ms.
64 bytes from 192.168.30.3: icmp_seq=5 ttl=64 time=5.35ms.

---- 192.168.30.3 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 5.23ms, avg = 6.41ms, max = 10.7ms, stddev = 2.13ms

*A:R9# ping 192.168.30.4

PING 192.168.30.4 56 data bytes
64 bytes from 192.168.30.4: icmp_seq=1 ttl=64 time=10.7ms.
64 bytes from 192.168.30.4: icmp_seq=2 ttl=64 time=4.71ms.
64 bytes from 192.168.30.4: icmp_seq=3 ttl=64 time=5.15ms.
64 bytes from 192.168.30.4: icmp_seq=4 ttl=64 time=6.52ms.
64 bytes from 192.168.30.4: icmp_seq=5 ttl=64 time=4.87ms.

---- 192.168.30.4 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.71ms, avg = 6.40ms, max = 10.7ms, stddev = 2.27ms

2. Create a new subnet, 192.168.50.0/24, on the CE devices by creating new IP interfaces using the
address 192.168.50.x/24, where x is your pod number. Use VLAN ID 50 for the interfaces.

25/122
*A:R9# 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.9/32 n/a
toR5-1 Up Up/Down Network 1/1/2:10
192.168.10.1/24 n/a
toR5-2 Up Up/Down Network 1/1/2:20
192.168.20.1/24 n/a

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

toR5-3 Up Up/Down Network 1/1/2:30
192.168.30.1/24 n/a
toR5-4 Up Up/Down Network 1/1/2:40
192.168.40.1/24 n/a
toR5-5 Up Up/Down Network 1/1/2:50
192.168.50.1/24 n/a
-------------------------------------------------------------------------------
Interfaces : 6
===============================================================================

3. Check whether you have connectivity between CE devices on the new subnet.

*A:R9# ping 192.168.50.2

PING 192.168.50.2 56 data bytes
Request timed out. icmp_seq=1.
Request timed out. icmp_seq=2.
Request timed out. icmp_seq=3.
Request timed out. icmp_seq=4.
Request timed out. icmp_seq=5.

---- 192.168.50.2 PING Statistics ----

5 packets transmitted, 0 packets received, 100% packet loss

4. Change the SAP in VPLS 200 to be the default SAP (port:*).

5. Check whether you can ping between CE devices on both VLAN 30 and VLAN 50.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 26/122
*A:R9# ping 192.168.30.2
PING 192.168.30.2 56 data bytes
64 bytes from 192.168.30.2: icmp_seq=1 ttl=64 time=4.27ms.
64 bytes from 192.168.30.2: icmp_seq=2 ttl=64 time=4.54ms.
64 bytes from 192.168.30.2: icmp_seq=3 ttl=64 time=5.35ms.
64 bytes from 192.168.30.2: icmp_seq=4 ttl=64 time=5.24ms.
64 bytes from 192.168.30.2: icmp_seq=5 ttl=64 time=5.83ms.

---- 192.168.30.2 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.27ms, avg = 5.05ms, max = 5.83ms, stddev = 0.567ms

*A:R9# ping 192.168.50.2

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

PING 192.168.50.2 56 data bytes
64 bytes from 192.168.50.2: icmp_seq=1 ttl=64 time=11.3ms.
64 bytes from 192.168.50.2: icmp_seq=2 ttl=64 time=5.81ms.
64 bytes from 192.168.50.2: icmp_seq=3 ttl=64 time=5.33ms.
64 bytes from 192.168.50.2: icmp_seq=4 ttl=64 time=5.28ms.
64 bytes from 192.168.50.2: icmp_seq=5 ttl=64 time=5.70ms.

---- 192.168.50.2 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 5.28ms, avg = 6.69ms, max = 11.3ms, stddev = 2.32ms

6. After pinging the remote CE devices, examine the FDB for VPLS service 200.

*A:R5# show service fdb-mac

===============================================================================
Service Forwarding Database
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
200 7a:4c:01:01:00:02 sap:1/1/2:* L/0 01/11/2012 20:18:50
200 7a:4d:01:01:00:02 sdp:6:200 L/0 01/11/2012 19:57:50
200 7a:4e:01:01:00:02 sdp:7:200 L/0 01/11/2012 19:57:59
200 7a:4f:01:01:00:02 sdp:8:200 L/15 01/11/2012 20:25:42
-------------------------------------------------------------------------------
No. of Entries: 4
-------------------------------------------------------------------------------

27/122
Questions

1. What will happen to untagged traffic on the CE to PE network?

_________________________________________________________

2. If the port was set to null encapsulation, how would you define the SAP? What would happen to
tagged traffic on this SAP?

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

_________________________________________________________

3. If the access port encapsulation was changed to qinq on the PE router, what changes would be
required in the services previously configured to make them still work? Are there any changes
required on the CE router?

Notes

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 28/122
LAB 4 Spoke Termination to a VPLS
Objective:
 Configure an epipe spoke that terminates in a VPLS.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 4-1 Spoke Termination to a VPLS

Lab 4 Command List

configure service vpls mesh-sdp <sdp-id> create
configure service vpls spoke-sdp <sdp-id:vc-id> create
configure service vpls <service-id> no shutdown
configure service epipe spoke-sdp <sdp-id:vc-id> create
configure service epipe sap <sap-id> create

29/122
Exercise

In this exercise you will configure a second VPLS with spokes terminating in the VPLS. The routers that
were acting as the P routers in the previous exercises will act as the PE routers for this VPLS. The
spokes will connect the access routers (former PE routers) to the VPLS.

1. Create a full mesh of Service Distribution Paths (SDPs) between all PE routers (formerly P routers).

2. Create a Customer ID of 300 and associate it with the VPLS service when you create the service.
Use a VPLS Service ID of 300 to create the VPLS on your PE router.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. Bind each of the SDPs that go to the other PE routers to the VPLS as mesh SDPs.

4. On your PE router, create an SDP to your access router. Bind that SDP to your VPLS as a spoke SDP.

5. On your access router, create an SDP to your PE router.

6. On the access router, create Customer ID 300 and create an epipe service. Bind the SDP to the
epipe as a spoke SDP. Add a SAP to the epipe service using dot1q encapsulation and VLAN ID of 40.

7. Administratively enable the epipe and VPLS services.

8. Create a new common subnet for the CE routers. Use subnet 192.168.40.0/24 as the common
subnet and configure the CE network interface for VLAN ID 40 with an address of 192.168.40.x/24,
where x is your pod number. You should be able to ping all other CE routers on this common subnet
once all the other students have completed their configurations.

Verification

1. Use the show service id base command on the epipe and VPLS to verify that the service and all
components are operational.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 30/122
*A:R1# show service id 300 base

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 300
SAP Count : 0 SDP Bind Count : 4
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Def. Gateway IP : None
Def. Gateway MAC : None

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:2:300 M(10.10.10.2) Mesh 0 1556 Up Up
sdp:3:300 M(10.10.10.3) Mesh 0 1556 Up Up
sdp:4:300 M(10.10.10.4) Mesh 0 1556 Up Up
sdp:5:300 S(10.10.10.5) Spok 0 1556 Up Up
===============================================================================

*A:R5# show service id 300 base

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

2. Use the show service id all command if you need more information to troubleshoot the service.

31/122
3. Use the show service fdb-mac command on the PE router and on the access router. Compare the
results.

*A:R1# show service fdb-mac

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

No Matching Entries
-------------------------------------------------------------------------------
No. of Entries: 0
-------------------------------------------------------------------------------
Legend: L=Learned; P=MAC is protected
===============================================================================

*A:R5# show service fdb-mac

4. Use the ping command to ensure that your CE router can ping the other CE routers.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 32/122
*A:R9# ping 192.168.40.2
PING 192.168.40.2 56 data bytes
64 bytes from 192.168.40.2: icmp_seq=1 ttl=64 time=9.45ms.
64 bytes from 192.168.40.2: icmp_seq=2 ttl=64 time=4.64ms.
64 bytes from 192.168.40.2: icmp_seq=3 ttl=64 time=4.56ms.
64 bytes from 192.168.40.2: icmp_seq=4 ttl=64 time=4.87ms.
64 bytes from 192.168.40.2: icmp_seq=5 ttl=64 time=4.79ms.

---- 192.168.40.2 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.56ms, avg = 5.66ms, max = 9.45ms, stddev = 1.90ms

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R9# ping 192.168.40.3
PING 192.168.40.3 56 data bytes
64 bytes from 192.168.40.3: icmp_seq=1 ttl=64 time=11.3ms.
64 bytes from 192.168.40.3: icmp_seq=2 ttl=64 time=5.32ms.
64 bytes from 192.168.40.3: icmp_seq=3 ttl=64 time=5.14ms.
64 bytes from 192.168.40.3: icmp_seq=4 ttl=64 time=5.04ms.
64 bytes from 192.168.40.3: icmp_seq=5 ttl=64 time=5.06ms.

---- 192.168.40.3 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 5.04ms, avg = 6.37ms, max = 11.3ms, stddev = 2.45ms

*A:R9# ping 192.168.40.4

PING 192.168.40.4 56 data bytes
64 bytes from 192.168.40.4: icmp_seq=1 ttl=64 time=12.9ms.
64 bytes from 192.168.40.4: icmp_seq=2 ttl=64 time=7.24ms.
64 bytes from 192.168.40.4: icmp_seq=3 ttl=64 time=7.78ms.
64 bytes from 192.168.40.4: icmp_seq=4 ttl=64 time=7.21ms.
64 bytes from 192.168.40.4: icmp_seq=5 ttl=64 time=7.14ms.

---- 192.168.40.4 PING Statistics ----

5 packets transmitted, 5 packets bounced, 5 packets received, 0.00% packet loss
round-trip min = 7.14ms, avg = 8.46ms, max = 12.9ms, stddev = 2.25ms

5. Use the show service fdb-mac command to confirm that the MAC forwarding database now
contains entries.

*A:R1# show service fdb-mac

===============================================================================
Service Forwarding Database
===============================================================================
ServId MAC Source-Identifier Type Last Change
Age
-------------------------------------------------------------------------------
300 7a:4c:01:01:00:02 sdp:5:300 L/60 01/11/2012 23:46:46
300 7a:4d:01:01:00:02 sdp:2:300 L/135 01/11/2012 23:46:46
300 7a:4e:01:01:00:02 sdp:3:300 L/630 01/11/2012 23:47:06
300 7a:4f:01:01:00:02 sdp:4:300 L/630 01/11/2012 23:47:06
-------------------------------------------------------------------------------
No. of Entries: 4
-------------------------------------------------------------------------------
Legend: L=Learned; P=MAC is protected

6. Use the show router ldp bindings command on the PE and access routers to identify the transport
and service labels used to carry a customer PDU from one access router to another. Identify the
label operations and label values used for each hop.

33/122
*A:R5# show router ldp bindings

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 8 10.10.10.8 131063U 131063S 1500 1500
E-Eth 20 20 8 10.10.10.8 131062U 131062S 1500 1500
V-Eth 200 200 6 10.10.10.6 131061U 131061 1500 1500
V-Eth 200 200 7 10.10.10.7 131060U 131061 1500 1500
V-Eth 200 200 8 10.10.10.8 131059U 131061 1500 1500
E-Eth 300 300 1 10.10.10.1 131058U 131060S 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 6

Check egress label for epipe service to 10.10.10.1 and transport tunnel to 10.10.10.1. Service label is
131060, transport label is 131071.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 34/122
*A: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
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
TLV - (Type, Length: Value)
===============================================================================
LDP Prefix Bindings
===============================================================================

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
10.10.10.1/32 10.10.10.2 131071U -- -- --
10.10.10.1/32 10.10.10.3 131071U -- -- --
10.10.10.1/32 10.10.10.4 131071U -- -- --
10.10.10.1/32 10.10.10.5 131071U -- -- --
10.10.10.2/32 10.10.10.2 -- 131071 1/1/2 10.1.2.2
10.10.10.2/32 10.10.10.3 131070U 131069 -- --
10.10.10.2/32 10.10.10.4 131070U 131069 -- --
10.10.10.2/32 10.10.10.5 131070U 131069 -- --
10.10.10.3/32 10.10.10.2 131069U 131069 -- --
10.10.10.3/32 10.10.10.3 -- 131071 1/1/3 10.1.3.3
10.10.10.3/32 10.10.10.4 131069U 131068 -- --
10.10.10.3/32 10.10.10.5 131069U 131068 -- --
10.10.10.4/32 10.10.10.2 131068U 131068 -- --
10.10.10.4/32 10.10.10.3 131068U 131068 -- --
10.10.10.4/32 10.10.10.4 -- 131071 1/1/4 10.1.4.4
10.10.10.4/32 10.10.10.5 131068U 131067 -- --
10.10.10.5/32 10.10.10.2 131067U 131067 -- --
10.10.10.5/32 10.10.10.3 131067U 131067 -- --
10.10.10.5/32 10.10.10.4 131067U 131067 -- --
10.10.10.5/32 10.10.10.5 -- 131071 1/1/1 10.1.5.5
10.10.10.6/32 10.10.10.2 131066N 131066 1/1/2 10.1.2.2
10.10.10.6/32 10.10.10.3 131066U 131066 -- --
10.10.10.6/32 10.10.10.4 131066U 131066 -- --
10.10.10.6/32 10.10.10.5 131066U 131066 -- --
10.10.10.7/32 10.10.10.2 131065U 131065 -- --
10.10.10.7/32 10.10.10.3 131065N 131065 1/1/3 10.1.3.3
10.10.10.7/32 10.10.10.4 131065U 131065 -- --
10.10.10.7/32 10.10.10.5 131065U 131065 -- --
10.10.10.8/32 10.10.10.2 131064U 131064 -- --
10.10.10.8/32 10.10.10.3 131064U 131064 -- --
10.10.10.8/32 10.10.10.4 131064N 131064 1/1/4 10.1.4.4
10.10.10.8/32 10.10.10.5 131064U 131064 -- --
-------------------------------------------------------------------------------
No. of Prefix Bindings: 32

===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
V-Eth 300 300 2 10.10.10.2 131063U 131063 1500 1500
V-Eth 300 300 3 10.10.10.3 131062U 131063 1500 1500
V-Eth 300 300 4 10.10.10.4 131061U 131063 1500 1500
V-Eth 300 300 5 10.10.10.5 131060U 131058S 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 4

35/122
Check egress label for VPLS service to 10.10.10.2 and transport tunnel to 10.10.10.2. Service label is
131063, transport label is 131071.

*A:R2# show router ldp bindings

===============================================================================
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 Service, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

TLV - (Type, Length: Value)
===============================================================================
LDP Prefix Bindings
===============================================================================
Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
10.10.10.1/32 10.10.10.1 -- 131071 1/1/2 10.1.2.1
10.10.10.1/32 10.10.10.3 131070U 131070 -- --
10.10.10.1/32 10.10.10.4 131070U 131070 -- --
10.10.10.1/32 10.10.10.6 131070U 131070 -- --
10.10.10.2/32 10.10.10.1 131071U -- -- --
10.10.10.2/32 10.10.10.3 131071U -- -- --
10.10.10.2/32 10.10.10.4 131071U -- -- --
10.10.10.2/32 10.10.10.6 131071U -- -- --
10.10.10.3/32 10.10.10.1 131069U 131069 -- --
10.10.10.3/32 10.10.10.3 -- 131071 1/1/4 10.2.3.3
10.10.10.3/32 10.10.10.4 131069U 131068 -- --
10.10.10.3/32 10.10.10.6 131069U 131068 -- --
10.10.10.4/32 10.10.10.1 131068U 131068 -- --
10.10.10.4/32 10.10.10.3 131068U 131068 -- --
10.10.10.4/32 10.10.10.4 -- 131071 1/1/3 10.2.4.4
10.10.10.4/32 10.10.10.6 131068U 131067 -- --
10.10.10.5/32 10.10.10.1 131067N 131067 1/1/2 10.1.2.1
10.10.10.5/32 10.10.10.3 131067U 131067 -- --
10.10.10.5/32 10.10.10.4 131067U 131067 -- --
10.10.10.5/32 10.10.10.6 131067U 131066 -- --
10.10.10.6/32 10.10.10.1 131066U 131066 -- --
10.10.10.6/32 10.10.10.3 131066U 131066 -- --
10.10.10.6/32 10.10.10.4 131066U 131066 -- --
10.10.10.6/32 10.10.10.6 -- 131071 1/1/1 10.2.6.6
10.10.10.7/32 10.10.10.1 131065U 131065 -- --
10.10.10.7/32 10.10.10.3 131065N 131065 1/1/4 10.2.3.3
10.10.10.7/32 10.10.10.4 131065U 131065 -- --
10.10.10.7/32 10.10.10.6 131065U 131065 -- --
10.10.10.8/32 10.10.10.1 131064U 131064 -- --
10.10.10.8/32 10.10.10.3 131064U 131064 -- --
10.10.10.8/32 10.10.10.4 131064N 131064 1/1/3 10.2.4.4
10.10.10.8/32 10.10.10.6 131064U 131064 -- --
-------------------------------------------------------------------------------
No. of Prefix Bindings: 32

===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
V-Eth 300 300 1 10.10.10.1 131063U 131063 1500 1500
V-Eth 300 300 3 10.10.10.3 131062U 131062 1500 1500
V-Eth 300 300 4 10.10.10.4 131061U 131062 1500 1500
V-Eth 300 300 6 10.10.10.6 131060U 131058S 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 4

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

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 36/122
Check egress label for epipe service to 10.10.10.6 and transport tunnel to 10.10.10.6. Service label is
131058, transport label is 131071.

*A:R6# show router ldp bindings

===============================================================================
LDP LSR ID: 10.10.10.6
===============================================================================
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 Service, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 7 10.10.10.7 131063U 131063S 1500 1500
E-Eth 20 20 7 10.10.10.7 131062U 131062S 1500 1500
V-Eth 200 200 5 10.10.10.5 131061U 131061 1500 1500
V-Eth 200 200 7 10.10.10.7 131060U 131060 1500 1500
V-Eth 200 200 8 10.10.10.8 131059U 131060 1500 1500
E-Eth 300 300 2 10.10.10.2 131058U 131060S 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 6

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

Verify that the ingress label for epipe service matches egress from 10.10.10.6, and that the ingress
label for transport tunnel matches egress from 10.10.10.6. Service ingress label is 131058, transport
ingress label is 131071.

To summarize, the egress labels used by R5-Access1, R1-PE1 and R2-PE2 are:

Egress router Transport label Service label

R5 131071 131060
R1 131071 131063
R2 131071 131058

37/122
Questions

1. How does the VPLS learn MAC addresses if it does not have any SAPs?
______________________________________________________________

2. Describe the signaling of service labels to create the service between two access routers.
______________________________________________________________

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. If each access and PE router in this scenario participated in a full mesh VPLS service, how many
SDPs would be required on each router?
______________________________________________________________

Notes

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 38/122
LAB 5 OAM Tools
Objective:
 Explore OAM tools available for managing and troubleshooting service networks.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 5-1 Epipe 10

Exercise I

This exercise explores OAM commands using the epipe service.

SDP Ping

SDP Ping performs in-band unidirectional or round-trip connectivity tests on SDPs. The SDP Ping OAM
packets are sent in-band in the tunnel encapsulation, so they will follow the same path as traffic within
the service. The SDP Ping response can be received out-of-band in the control plane, or in-band using
the data plane for a round-trip test.

1. Use the oam sdp-ping command to verify the connectivity to the local service SDP.

Note: This will test the local SDP but does not perform a round-trip test.

39/122
*A:R5# oam sdp-ping 8
Err SDP-ID Info Local Remote
--------------------------------------------------
SDP-ID: 8 N/A
Administrative State: Up N/A
Operative State: Up N/A
Path MTU: 1556 N/A
Response SDP Used: No

IP Interface State: Up
Actual IP Address: 10.10.10.5 10.10.10.8
Expected Peer IP: 10.10.10.8 10.10.10.5

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Forwarding Class be be
Profile Out Out

Request Result: Sent - Reply Received

RTT: 2.56(ms)

2. Use the oam sdp-ping resp-sdp command to perform a round-trip SDP ping test.

*A:R5# oam sdp-ping 8 resp-sdp 5

Err SDP-ID Info Local Remote
--------------------------------------------------
SDP-ID: 8 5
Administrative State: Up Up
Operative State: Up Up
Path MTU: 1556 N/A
Response SDP Used: Yes

IP Interface State: Up
Actual IP Address: 10.10.10.5 10.10.10.8
Expected Peer IP: 10.10.10.8 10.10.10.5

Forwarding Class be be
Profile Out Out

Request Result: Sent - Reply Received

RTT: 2.47(ms)

3. Use the oam sdp-mtu size-inc command to determine the maximum MTU size that your SDP can
support.

Note: The Path MTU Discovery tool enables service providers to get the exact MTU supported
between the service ingress and service termination points (accurate to one byte). It is important to
understand the MTU path end-to-end when provisioning services, especially for VPWS services where
the service must support the ability to transmit the largest customer packet.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 40/122
*A:R5# oam sdp-mtu 8 size-inc 1500 1590 step 10
Size Sent Response
----------------------------
1500 . Success
1510 . Success
1520 . Success
1530 . Success
1540 . Success
1550 . Success
1560 ... Request Timeout

Maximum Response Size: 1550

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5# oam sdp-mtu 8 size-inc 1550 1560 step 1
Size Sent Response
----------------------------
1550 . Success
1551 . Success
1552 . Success
1553 . Success
1554 . Success
1555 . Success
1556 . Success
1557 ... Request Timeout

Maximum Response Size: 1556

4. Use the oam svc-ping command to verify the operation of your service. Use the control plane to
send and receive the OAM messages.
Alcatel-Lucent’s Service Ping feature provides end-to-end connectivity testing for an individual
service. Service Ping operates at a higher level than the SDP diagnostics in that it verifies an
individual service and not the connection of services carried within an SDP.
Service Ping is initiated from a 7750 SR router to verify round-trip connectivity and delay to the far-
end of the service. Alcatel-Lucent’s implementation functions for both GRE and MPLS tunnels and
tests edge-to-edge parameters.
Note: This version of the Service Ping test uses the control plane to send and receive OAM messages
rather than the data plane.

*A:R5# show service service-using

===============================================================================
Services
===============================================================================
ServiceId Type Adm Opr CustomerId Service Name
-------------------------------------------------------------------------------
10 Epipe Up Up 1
20 Epipe Up Up 1
200 VPLS Up Up 200
300 Epipe Up Up 300
2147483648 IES Up Down 1 _tmnx_InternalIesService
-------------------------------------------------------------------------------
Matching Services : 5
-------------------------------------------------------------------------------

41/122
*A:R5# show service id 10 base

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

MTU : 1514
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled

*A:R5# oam svc-ping 10.10.10.8 service 10

Service-ID: 10

Err Info Local Remote

-----------------------------------------------------
Type: EPIPE EPIPE
Admin State: Up Up
Oper State: Up Up
Service-MTU: 1514 1514
Customer ID: 1 1

IP Interface State: Up
Actual IP Addr: 10.10.10.5 10.10.10.8
Expected Peer IP: 10.10.10.8 10.10.10.5

SDP Path Used: No No

SDP-ID: 8 5
Admin State: Up Up
Operative State: Up Up
Binding Admin State:Up Up
Binding Oper State: Up Up
Binding VC ID: 10 10
Binding Type: Spoke Spoke
Binding Vc-type: Ether Ether
Binding Vlan-vc-tag:N/A N/A

Egress Label: 131063 131063

Ingress Label: 131063 131063
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled

Request Result: Sent - Reply Received

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 42/122
Use the oam svc-ping local-sdp remote-sdp command to send the OAM packets over the same path as
the customer traffic.
Note: The SDP Path Used is showing “yes”.

*A:R5# oam svc-ping 10.10.10.8 service 10 local-sdp remote-sdp

Service-ID: 10

Err Info Local Remote

-----------------------------------------------------
Type: EPIPE EPIPE

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Admin State: Up Up
Oper State: Up Up
Service-MTU: 1514 1514
Customer ID: 1 1

IP Interface State: Up
Actual IP Addr: 10.10.10.5 10.10.10.8
Expected Peer IP: 10.10.10.8 10.10.10.5

SDP Path Used: Yes Yes

Egress Label: 131063 131063

Ingress Label: 131063 131063
Egress Label Type: Signaled Signaled
Ingress Label Type: Signaled Signaled

Request Result: Sent - Reply Received

43/122
Questions

1. What is value of the SDP-ID? __________________________

2. What is the value of the VC-ID? _____________________ Where did it come from? __________

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. Is the Admin state Up or Down? ______________ What should it be at this point? _______________

4. What binding type is being used? _______________________

5. What is the state of “SDP Path Used?” ____________ What does this mean? __________________

6. What is the significance of the SDP Path being used?

__________________________________________________________________________________

7. Do the ingress and egress labels have to be the same (as in the example above)? Explain.
__________________________________________________________________________________

Notes

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 44/122
Exercise II
This exercise will explore the use of the oam sdp-mtu command and MTU issues related to a Layer 2
service.

1. In the previous exercise you used the oam sdp-mtu size-inc command to find the maximum MTU
size that your SDP could support. What was the maximum MTU size?
_____________________________

2. What is the service MTU of your epipe service? ___________________________________________

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. What is the SDP path MTU? How is this MTU determined? __________________________________

4. Set the MTU to 1514 on the network port of the P router to P router on the diagonal link. Check the
service status, service MTU and the SDP path MTU. What has changed? ________________________

5. Use oam sdp-mtu size-inc to find the maximum MTU size that your SDP now supports. What is this
value? Considering the MPLS encapsulation overhead, does this make sense? ____________________

6. Validate your results by pinging between the CE routers with different size packets.

7. Configure an RSVP LSP using a loose path from your PE router to the diagonally opposite PE router.
You need to enable MPLS on the interfaces.

8. Change the SDP created in Lab 2 to use this LSP instead of LDP. Verify that the LSP and the SDP
come up.

9. How is the path MTU of the SDP different from its previous state? ____________________________

10. Change the LSP to use ADSPEC. This should cause RSVP to signal MTU along the LSP. What is the
path MTU of the SDP with ADSPEC enabled?

11. What is the status of the service and what can you do about it?
_______________________________

12. At the end of this exercise change the port back to its default value.

Notes

45/122
LAB 6 Mirror Service
Objective:

 Configure a local and remote mirror service and examine the result on a protocol analyzer.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 6-1 Local Mirror Service

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 46/122
Lab 6 Command List
configure mirror mirror-dest <service-id> create
configure mirror mirror-dest <service-id> sap <sap--id> create
configure mirror mirror-dest <service-id> spoke-sdp <sdp-id:vc-id> create
configure mirror mirror-dest <service-id> remote-source far-end <ip-address>
configure mirror mirror-dest <service-id>no shutdown

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure mirror mirro-dest <service-id> slice-size <slice-size>
debug mirror-source <service-id>
debug mirror-source port <port--id> egress ingress
show mirror mirror-dest <service-id>
show debug mirror
Table 6-1 Mirror Service Command List

Exercise I – Local Mirroring

In this exercise you will work together to configure local mirror service.
 Pod 1 and Pod 3 will be configuring a local mirror service
 Pod 2 and Pod 4 will be configuring the IP filters to capture the ICMP packets. In other words,
PE2 and PE4 will be acting as sniffers for traffic on PE1 and PE3 respectively.

1. The following instructions are for creating the local mirror service (Pod 1 and Pod 3)
a) On your PE router, configure port 1/1/3 as the mirror destination. Use Service ID 103.
b) Ensure that the mirror service 103 is enabled and operational.
c) On your PE router, configure the port connected to your CE router as the mirror source
for both egress and ingress traffic.

2. The following instructions are for creating the IP filter (Pod 2 and Pod 4)

a) Create a filter log with a log-id of 100 + your Pod number. For example: Pod 2 will have
a log-id of 102. Use memory as the destination for this filter log.
b) Create an IP filter with a filter-id value that equals your pod number. For example: Pod
2 will have filter-id 2.
c) Configure the IP filter to match packets sent to the CE router across the configured
epipe 10 service. For example, the filter configured on R6-PE2 should be configured to
match packets sent from R9-CE1 to R12-CE4 across epipe 10 service.
d) Create a local epipe service on your PE router; use service id 2000 on PE2, and 4000 on
PE4. Create two SAPs under this service: SAP 1/1/3 and 1/1/2:100.
e) Apply the filter under the ingress of SAP 1/1/3.

Verification:

1. Use the show mirror command to confirm that the mirror service is operational and that it is
bound to the correct source port.

47/122
*A:R5# show mirror mirror-dest 103
===============================================================================
Mirror Service
===============================================================================
Service Id : 103 Type : Ether
Description : (Not Specified)
Admin State : Up Oper State : Up
Forwarding Class : be Remote Sources: No
Slice : 0
Destination SAP : 1/1/3 Egr QoS Policy: 1

-------------------------------------------------------------------------------
Local Sources

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

-------------------------------------------------------------------------------
Admin State : Up

-Port 1/1/2 Egr Ing

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

2. Use the show debug command to confirm that the correct mirror source is being used.

*A:R5# show debug mirror

debug
mirror-source 103
port 1/1/2 egress ingress
no shutdown
exit
exit

3. Ping the opposite CE router from your Pod CE router and verify connectivity.

*A:R9# ping 192.168.10.4

PING 192.168.10.4 56 data bytes
64 bytes from 192.168.10.4: icmp_seq=1 ttl=64 time=4.99ms.
64 bytes from 192.168.10.4: icmp_seq=2 ttl=64 time=5.05ms.
64 bytes from 192.168.10.4: icmp_seq=3 ttl=64 time=5.04ms.
64 bytes from 192.168.10.4: icmp_seq=4 ttl=64 time=6.09ms.
64 bytes from 192.168.10.4: icmp_seq=5 ttl=64 time=4.47ms.

4. The IP filter acting as a sniffer for your pod should capture the ICMP packets. Verify that the
filter has captured the ICMP packets using command show filter log <log-id>.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 48/122
*A:R6# show filter log 102
===============================================================================
Filter Log
===============================================================================
Admin state : Enabled
Description : (Not Specified)
Destination : Memory
Wrap : Enabled
-------------------------------------------------------------------------------
Maximum entries configured : 100
Number of entries logged : 8
2012/03/08 07:28:27 Ip Filter: 2:10 Desc:
SAP: 1/1/3 Direction: Ingress Action: Forward
Src MAC: 7c-6c-01-01-00-02 Dst MAC: 7c-6f-01-01-00-02 EtherType: 0800

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Src IP: 192.168.10.1 Dst IP: 192.168.10.4 Flags: 0 TOS: 00 TTL: 64
Protocol: ICMP Type: Echo Request Code: 0

2012/03/08 07:28:27 Ip Filter: 2:10 Desc:

SAP: 1/1/3 Direction: Ingress Action: Forward
Src MAC: 7c-6f-01-01-00-02 Dst MAC: 7c-6c-01-01-00-02 EtherType: 0800
Src IP: 192.168.10.4 Dst IP: 192.168.10.1 Flags: 0 TOS: 00 TTL: 64
Protocol: ICMP Type: Echo Reply Code: 0

2012/03/08 07:28:28 Ip Filter: 2:10 Desc:

SAP: 1/1/3 Direction: Ingress Action: Forward
Src MAC: 7c-6c-01-01-00-02 Dst MAC: 7c-6f-01-01-00-02 EtherType: 0800
Src IP: 192.168.10.1 Dst IP: 192.168.10.4 Flags: 0 TOS: 00 TTL: 64
Protocol: ICMP Type: Echo Request Code: 0

2012/03/08 07:28:28 Ip Filter: 2:10 Desc:

2012/03/08 07:28:29 Ip Filter: 2:10 Desc:

2012/03/08 07:28:30 Ip Filter: 2:10 Desc:

49/122
Exercise II – Remote Mirroring

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 6-2 Remote Mirror Service

In this exercise you will work together to configure remote mirror service. We will use the epipe
service configured between Pod 1 and Pod 4 and between Pod 2 and Pod 3 to perform remote
mirroring. The mirror source will be configured on PE1. The mirror destination will be configured on
PE4. For this remote mirror service, PE3 will be configured as a sniffer.

For the second remote mirror service between Pod 2 and Pod 3, the mirror source will be on PE3, while
the mirror destination will be configured on PE2; for this mirror service, PE1 will be configured as a
sniffer.

Note: Before you proceed to the step 1, remove the local mirror and local epipe services configured in
exercise I.

1. The following instructions are for creating the mirror source (Pod 1 and Pod 3)

a. Configure a mirror destination. Take note of the Service ID you used for your
destination mirror service.
b. Bind this mirror destination to the SDP used for the epipe to your partner’s PE router in
order to send mirrored traffic over the SDP.
c. Enable the mirror service.
d. Use the debug command to enable a mirror source for both egress and ingress traffic.
Use the same Service ID as used in step a.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 50/122
2. The following instructions are for creating the mirror destination (Pod 2 and Pod 4)
a. Configure a mirror destination Service ID using the same Service ID that was configured in
step 1 above.
b. Configure a remote source on this router by specifying the system address of the source PE
router
c. Bind this mirror destination to the SAP port toward your sniffer router.
d. Enable the destination mirror service.
e. Ensure that the mirror service is enabled and operational.

*A:R5# show mirror mirror-dest

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

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Mirror Services
=============================================================================
Id Type Adm Opr Destination SDP Lbl/
Slice
SAP QoS
-----------------------------------------------------------------------------
104 Ether Up Up SDP 8 (10.10.10.8) 131056 0
=============================================================================

*A:R8# show mirror mirror-dest

=============================================================================
Mirror Services
=============================================================================
Id Type Adm Opr Destination SDP Lbl/
Slice
SAP QoS
-----------------------------------------------------------------------------
104 Ether Up Up SAP 1/1/3 1 0
=============================================================================

3. The following instructions are for creating the IP filter (Pod 1 and Pod 3)

a. Create a filter log with a log ID of 100 + your pod number. For example: Pod 3 will have
a log ID of 103. Use memory as the destination for this filter log.
b. Create an IP filter with a filter ID value that equals your Pod number. For example: Pod
3 will have filter ID 3.
c. Configure the IP filter to match packets sent between the CE routers across the
configured epipe 10 service. The sniffer on PE3 should capture the traffic between CE1
and CE4, while the sniffer on PE1 should capture the traffic between CE2 and CE3.
d. Create a local epipe service on the sniffer router; use Service ID 1000 on PE1, and 3000
on PE3. Create two SAPs under this service, SAP 1/1/3 and 1/1/2:100.
e. Apply the filter under the ingress of SAP 1/1/3.

Verification
1. Issue a ping request from CE1 to CE4 and from CE2 to CE3 to verify that remote mirroring is
working.

51/122
*A:R9# ping 192.168.10.4
PING 192.168.10.4 56 data bytes
64 bytes from 192.168.10.4: icmp_seq=1 ttl=64 time=5.03ms.
64 bytes from 192.168.10.4: icmp_seq=2 ttl=64 time=4.59ms.
64 bytes from 192.168.10.4: icmp_seq=3 ttl=64 time=4.61ms.
64 bytes from 192.168.10.4: icmp_seq=4 ttl=64 time=5.12ms.
64 bytes from 192.168.10.4: icmp_seq=5 ttl=64 time=5.73ms.

---- 192.168.10.4 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.59ms, avg = 5.01ms, max = 5.73ms, stddev = 0.419ms

2. Verify the mirrored traffic on the sniffer routers.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R7# show filter log 103
===============================================================================
Filter Log
===============================================================================
Admin state : Enabled
Description : (Not Specified)
Destination : Memory
Wrap : Enabled
-------------------------------------------------------------------------------
Maximum entries configured : 100
Number of entries logged : 10
2012/03/08 08:40:57 Ip Filter: 3:10 Desc:
SAP: 1/1/3 Direction: Ingress Action: Forward
Src MAC: 7c-6c-01-01-00-02 Dst MAC: 7c-6f-01-01-00-02 EtherType: 0800
Src IP: 192.168.10.1 Dst IP: 192.168.10.4 Flags: 0 TOS: 00 TTL: 64
Protocol: ICMP Type: Echo Request Code: 0

2012/03/08 08:40:57 Ip Filter: 3:10 Desc:

2012/03/08 08:40:58 Ip Filter: 3:10 Desc:

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 52/122
Exercise III - Mirror Slicing
1. Clear the filter IP counters and verify there are no packets matched.

*A:R7# clear filter ip 3

*A:R7# show filter ip 3 counters
===============================================================================
IP Filter
===============================================================================
Filter Id : 3 Applied : Yes

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Scope : Template Def. Action : Drop
Radius Ins Pt: n/a
CrCtl. Ins Pt: n/a
Entries : 1
Description : (Not Specified)
-------------------------------------------------------------------------------
Filter Match Criteria : IP
-------------------------------------------------------------------------------
Entry : 10
Ing. Matches : 0 pkts
Egr. Matches : 0 pkts

2. Enable mirror slicing by selecting only the first 128 bytes of a packet to be mirrored.
3. Issue a ping request from CE1 to CE4 and from CE2 to CE3 with a packet size of 1200 bytes.

*A:R9# ping count 1 192.168.10.4 size 1200

PING 192.168.10.4 1200 data bytes
1208 bytes from 192.168.10.4: icmp_seq=1 ttl=64 time=7.08ms.

---- 192.168.10.4 PING Statistics ----

1 packet transmitted, 1 packet received, 0.00% packet loss
round-trip min = 7.08ms, avg = 7.08ms, max = 7.08ms, stddev = 0.000ms

4. Verify that mirror slicing is working using the command show filter ip 11 counters

*A:R7# show filter ip 3 counters

=============================================================================
IP Filter
=============================================================================
Filter Id : 3 Applied : Yes
Scope : Template Def. Action : Drop
Radius Ins Pt: n/a
CrCtl. Ins Pt: n/a
Entries : 1
Description : (Not Specified)
-----------------------------------------------------------------------------
Filter Match Criteria : IP
-----------------------------------------------------------------------------
Entry : 10
Ing. Matches : 2 pkts (264 bytes)
Egr. Matches : 0 pkts

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

53/122
Notes

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 54/122
LAB 7 Internet Enhanced Service (IES)
Objective:
 Configure an IES service and verify the effects on IP routing.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 7-1 IES Service

55/122
Lab 7 Command List
configure port <port -id>
configure port <port -id> Ethernet mode access
configure port <port -id> Ethernet mtu <mtu-bytes>
configure service ies <service-id> customer <customer-id> create
configure service ies <service-id> interface < ip-int-name > create
configure service ies <service-id> interface < ip-int-name > address <ip address>

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure service ies <service-id> interface < ip-int-name > sap <sap-id> create
show service sap-using
show service sdp-using
show service service-using
show service id <service-id> base
show service id <service-id> all
oam svc-ping <ip address> service <service-id>

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 56/122
Exercise

1. Create an IES service with Service ID 500 on your PE router.

2. Create a new interface within the IES context and give it a name. Assign an IP address to this
new interface. Use the IP address 172.16.x.1/24, where x is your pod number.

3. Create a SAP for the interface using VLAN ID 60. Enable the IES service.

4. Add the IES interface to your PE router IS-IS configuration

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

5. Create a network interface on your CE router with IP address 172.16.x.2/24 and VLAN ID 60,
where x is your pod number.

6. Create a loopback interface on the CE router with IP address 100.100.x.1/24, where x is your
pod number. This is intended to represent a local customer network.

7. Verify that you can ping the IES interface from the CE router.

8. Verify that the IES interface is in the route table on the PE router. Check for the loopback
network.

9. Configure your CE router as an L1 router in IS-IS, including the link towards the provider
network and your local loopback network in IS-IS.

10. Try to ping the system address of one of the P routers. If your network is being distributed into
the service provider network you should be able to reach any address there, as well as the
other CE loopback networks. Try a traceroute to another CE loopback.

11. Compare the traceroute above with a traceroute between the interfaces that use your epipe.
(traceroute 192.168.10.4 from CE1, for example)

57/122
Questions:

1. Explain the difference between the CE to CE ping through the IES interface and the CE to CE
ping through your epipe.___________________________________________________________

Notes

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 58/122
LAB 8 VPLS Spoke Termination on IES
Objective:
 Configure and verify layer 3 termination for a VPLS service.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Figure 8-1 VPLS 1000 Terminating on IES

Lab 8 Command List

Configure service ies <service-id> interface <ip-int-name> spoke-sdp <sdp-id:vc-id>
Configure service ies <service-id> interface <ip-int-name> ip-mtu <octets>
Table 8-1 VPLS with Spoke SDP Commands

Exercise:
Note: Before you start this exercise, shutdown the IES service you created in the previous exercise.

1. On your PE router, configure a VPLS service x100, where x is your pod number.

2. Bind a SAP for the CE router to the VPLS using VLAN ID 70. Bind a spoke SDP for your P router.

3. On your CE router, configure a network interface with an address of 172.17.x.2/24 and a VLAN ID
of 70, where x is your pod number. Add the interface to IS-IS.

59/122
4. On your P router, configure an IES service with an address of 172.17.x.1/24, where x is your pod.
Bind the IES interface to a spoke SDP for your PE router.

5. Use the command show service id svc-id base to verify that the service is up.

6. If the service does not come up as expected, use the commands show service id svc-id all and
show router ldp bindings to identify the problem.

7. On your P router, put the IES interface created in step 4 into IS-IS.

Verification:

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

From your CE router you should be able to ping all other CE router interfaces created in step 3.

*A:R9# ping 172.17.2.2

PING 172.17.2.2 56 data bytes
64 bytes from 172.17.2.2: icmp_seq=1 ttl=62 time=4.26ms.
64 bytes from 172.17.2.2: icmp_seq=2 ttl=62 time=5.11ms.
64 bytes from 172.17.2.2: icmp_seq=3 ttl=62 time=5.06ms.
64 bytes from 172.17.2.2: icmp_seq=4 ttl=62 time=4.99ms.
64 bytes from 172.17.2.2: icmp_seq=5 ttl=62 time=4.92ms.

---- 172.17.2.2 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 4.26ms, avg = 4.87ms, max = 5.11ms, stddev = 0.314ms

*A:R9# ping 10.10.10.4

PING 10.10.10.4 56 data bytes
64 bytes from 10.10.10.4: icmp_seq=1 ttl=63 time=2.27ms.
64 bytes from 10.10.10.4: icmp_seq=2 ttl=63 time=2.32ms.
64 bytes from 10.10.10.4: icmp_seq=3 ttl=63 time=2.20ms.
64 bytes from 10.10.10.4: icmp_seq=4 ttl=63 time=2.39ms.
64 bytes from 10.10.10.4: icmp_seq=5 ttl=63 time=2.65ms.

---- 10.10.10.4 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 2.20ms, avg = 2.36ms, max = 2.65ms, stddev = 0.159ms

Questions

1. What MAC address is being used as the destination MAC address when you ping from your CE router
to any other CE router?
__________________________________________________________________________________

2. What happens to the Layer 2 Header when it reaches the IES interface when you ping from your CE
router to any other CE router?
__________________________________________________________________________________

3. Use the traceroute command to trace the path between your CE router and the CE router beside
your POD.
__________________________________________________________________________________

4. What table is being used for each router along the path to make the forwarding decision? (e.g.
route-table, FDB)
__________________________________________________________________________________

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 60/122
Notes

61/122
Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute
LAB 9 IPv4 VPRNs
Enabling the Provider Core for MPLS

Objective:
 Configure the provider core, including the PE and CE devices, to enable a Layer 3 VPRN using
LDP.

AS 64497 AS 64499

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Blue VPN Site 1 Red VPN Site 1

BGP
Pod 2
Pod 1
R9-CE 1 R10-CE 2

Blue Site 1 LAN R6-PE 2 Red Site 1 LAN

10.10.1.0/24 R5-PE 1 10.10.2.0/24

MP-BGP
LDP

Red Site 2 LAN Blue Site 2 LAN

10.10.3.0/24 R7-PE 3 R8-PE 4 10.10.4.0/24

Pod 3 Pod 4

R11-CE 3 BGP R12-CE

AS 64500 AS 64498
Red VPN Site 2 Blue VPN Site 2

Figure 9-1 IPv4 VPRNs

Syntax
Configuration commands required for the labs are provided in each section. Further details can be
found in Services Architecture Module 5. Verification commands for each lab are also provided. It is
possible for each command to have additional parameters. Use the ‘?’ character for help and to
explore all command line options. Other commands may also be used, including those from previous
exercises and courses.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 62/122
Exercise
Configure loopback interfaces on the CE routers as shown in Table 9.1. These loopback interfaces will
be used to simulate the customer LAN.

Parameter Value
Pod Number x = 1, 2, 3, or 4 (Circle your Pod number)
CE loopback interface (Customer LAN) 10.10.x.1/24

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Table 9-1 IPv4 Addresses

Verification
Note: The sample screen shots below may not be identical to the screen shots from your routers.

1. On the CE, verify that all required physical ports and interfaces are active and operational.
*A:R9# show router interface
===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
Blue_Site_1 Up Up/Down Network loopback
10.10.1.1/24 n/a
loopback_1 Up Up/Down Network loopback
100.100.1.1/24 n/a
system Up Up/Down Network system
10.10.10.9/32 n/a
toR5-1 Up Up/Down Network 1/1/2:10
192.168.10.1/24 n/a
toR5-2 Up Up/Down Network 1/1/2:20
192.168.20.1/24 n/a
toR5-3 Up Up/Down Network 1/1/2:30
192.168.30.1/24 n/a
toR5-4 Up Up/Down Network 1/1/2:40
192.168.40.1/24 n/a
toR5-5 Up Up/Down Network 1/1/2:50
192.168.50.1/24 n/a
to_IES Up Up/Down Network 1/1/2:60
172.16.1.2/24 n/a
to_ISP_7 Up Up/Down Network 1/1/2:70
172.17.1.2/24 n/a
-------------------------------------------------------------------------------
Interfaces : 10

63/122
Configuring MP-BGP as the PE to PE Protocol
Exercise
Configure a full mesh of MP-BGP sessions between provider core PE routers.
On each PE, perform the following tasks:
1. Configure the provider Autonomous System (AS) number. Use AS number 64496.
2. Configure all other PE routers as MP-BGP neighbors. Establish all peering sessions using PE
system addresses.
3. Enable support for the exchange of VPN-IPv4 prefixes between PE neighbors.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Verification
1. Ensure that the full mesh of MP-BGP has been established between PE routers.

*A:R5# show router bgp summary

===============================================================================
BGP Router ID:10.10.10.5 AS:64496 Local AS:64496
===============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total BGP Paths : 9 Total Path Memory : 1080
Total IPv4 Remote Rts : 0 Total IPv4 Rem. Active Rts : 0
Total IPv6 Remote Rts : 0 Total IPv6 Rem. Active Rts : 0
Total Supressed Rts : 0 Total Hist. Rts : 0
Total Decay Rts : 0

Total VPN Peer Groups : 0 Total VPN Peers : 0

Total VPN Local Rts : 0
Total VPN-IPv4 Rem. Rts : 0 Total VPN-IPv4 Rem. Act. Rts: 0
Total VPN-IPv6 Rem. Rts : 0 Total VPN-IPv6 Rem. Act. Rts: 0
Total L2-VPN Rem. Rts : 0 Total L2VPN Rem. Act. Rts : 0
Total VPN Supp. Rts : 0 Total VPN Hist. Rts : 0
Total VPN Decay Rts : 0
Total MVPN-IPv4 Rem Rts : 0 Total MVPN-IPv4 Rem Act Rts : 0
Total MDT-SAFI Rem Rts : 0 Total MDT-SAFI Rem Act Rts : 0

===============================================================================
BGP Summary
===============================================================================
Neighbor
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-------------------------------------------------------------------------------
10.10.10.6
64496 6 0 00h02m14s 0/0/0 (VpnIPv4)
7 0
10.10.10.7
64496 4 0 00h01m26s 0/0/0 (VpnIPv4)
5 0
10.10.10.8
64496 3 0 00h00m48s 0/0/0 (VpnIPv4)
4 0
===============================================================================

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 64/122
2. View the Base BGP table of the PE routers and ensure that there are no routes present at this
time.
*A:R5# show router bgp routes
===============================================================================
BGP Router ID:10.10.10.5 AS:64496 Local AS:64496
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

===============================================================================
BGP IPv4 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop VPNLabel
As-Path
-------------------------------------------------------------------------------
No Matching Entries Found
===============================================================================

65/122
Enabling the VPRN Service on the PE
Exercise
Configure the VPRN Service for the customer connected to your PE router using the parameters from
Table 9.2.
Note: Pods 1 and 4 will be part of the Blue VPRN while Pods 2 and 3 will be part of the Red VPRN.

On each PE, perform the following tasks:

1. Create a customer service description for the VPRN customer.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

2. Create a VPRN service instance using auto-bind LDP for the transport tunnel. As shown in Table
9-2, Blue VPRN instances will be configured on PE1 and PE4 while Red VPRN instances will be
configured on PE2 and PE3.
3. Assign a router ID, route-distinguisher, and route target to the VPRN.
4. Create a customer interface in the VPRN instance and assign a SAP (the PE to CE port) to the
interface.
a. Use VLAN ID of 110 for a Blue Customer CE router and VLAN ID of 120 for a Red
Customer CE router with the SAP configuration.
5. Configure an IP address on the service interface.
6. Enable the VPRN service instance.

Provisioning parameters Blue Customer Red Customer

Customer ID 110 120
VPRN ID 110 120
Router ID <PE system address> <PE system address>
Route Distinguisher 64496:110 64496:120
Route Target 64496:110 64496:120
VPRN Interface IP address Same as PE-CE interface as shown in Table 1.2
Table 9-2 Customer Provisioning Parameters

Verification
Ensure that the VPRN service instance is enabled and operational. A sample is shown on the
following page.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 66/122
*A:R5# show service id 110 base

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Admin State : Up Oper State : Up

Route Dist. : 64496:110 VPRN Type : regular

AS Number : 64496 Router Id : 10.10.10.5
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:64496:110
Vrf Import : None
Vrf Export : None
MVPN Vrf Target : None
MVPN Vrf Import : None
MVPN Vrf Export : None

SAP Count : 1 SDP Bind Count : 0

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

67/122
PE BGP Configuration
Exercise
Configure BGP as the PE to CE routing protocol and the associated policy requirements on the PE using
the parameters from Table 9-3.

Provisioning parameters Value

VPRN Service ID Customer Blue 110
VPRN Service ID Customer Red 120

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Provider Autonomous System Number 64496
Customer Blue Autonomous System Number 64497 and 64498
Customer Red Autonomous System Number 64499 and 64500
Table 9-3 Configuration Parameters

On each PE, perform the following tasks:

1. Shut down the VPRN Service.
2. Configure an export route policy to exchange prefixes in the VRF received from the remote PE
via MP-BGP with BGP.
3. Configure the following under the VPRN Service instance of the PE:
a. Enable BGP and define a peer of the adjacent CE using the physical interface addresses
for the peering sessions. The peer will not be operational until the completion of the
following task
b. Apply the configured policy as an export route policy in the VPRN BGP context.
4. Re-enable the VPRN Service.

Verification
1. Verify that the policy has been configured and applied to the VPRN BGP instance on the PE.
2. Verify that BGP has been enabled under the VPRN service instance. An example is shown on the
following page.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 68/122
A:R5# show router 110 status
================================================================
Router Status (Service: 110)
================================================================
Admin State Oper State
----------------------------------------------------------------
Router Up Up
OSPF Down Down
RIP Down Down
ISIS Not configured Not configured
MPLS Not configured Not configured
RSVP Not configured Not configured

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

LDP Not configured Not configured
BGP Up Up
IGMP Not configured Not configured
PIM Not configured Not configured

Max Routes No Limit

Total Routes 2
Max Multicast Routes No Limit
Total Multicast Routes PIM not configured
ECMP Max Routes 1
Triggered Policies No
================================================================

69/122
CE BGP Configuration
Exercise
Configure BGP as the PE to CE routing protocol and the associated policy requirements on the CE.

On each CE, perform the following tasks:

1. Configure an export policy to show only the customer LAN prefix into BGP.
2. Configure the BGP Autonomous System number for the customer from Table 9-3.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. Configure an interface to the PE router, use VLAN 110 for customer Blue and 120 for customer
Red
4. Enable a BGP routing process and apply the configured policy to the BGP process.
5. Configure the adjacent PE interface as a BGP neighbor.

Verification
1. Verify that the PE and the CE have become BGP peers and are exchanging IPv4 prefixes. An
example is shown below.
*A:R5# show router 110 bgp summary
===============================================================================
BGP Router ID:10.10.10.5 AS:64496 Local AS:64496
===============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 1
Total BGP Paths : 4 Total Path Memory : 512
Total IPv4 Remote Rts : 1 Total IPv4 Rem. Active Rts : 1
Total IPv6 Remote Rts : 0 Total IPv6 Rem. Active Rts : 0
Total Supressed Rts : 0 Total Hist. Rts : 0
Total Decay Rts : 0

===============================================================================
BGP Summary
===============================================================================
Neighbor
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-------------------------------------------------------------------------------
10.5.9.9
64497 33 0 00h13m53s 1/1/2 (IPv4)
35 0
===============================================================================

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 70/122
2. Verify that the PEs are exchanging VPN-IPv4 prefixes. An example is shown below.
*A:R5# show router bgp routes vpn-ipv4
===============================================================================
BGP Router ID:10.10.10.5 AS:64496 Local AS:64496
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

===============================================================================
BGP VPN-IPv4 Routes
===============================================================================
Flag Network LocalPref MED
Nexthop VPNLabel
As-Path
-------------------------------------------------------------------------------
u*>i 64496:110:10.8.12.0/24 100 None
10.10.10.8 131054
No As-Path
u*>? 64496:110:10.10.4.0/24 100 None
10.10.10.8 131054
64498
-------------------------------------------------------------------------------
Routes : 2
===============================================================================

3. Verify that the PE VRF table contains the customer LAN route received from the local CE. An
example is shown below.
*A:R5# show router 110 route-table
===============================================================================
Route Table (Service: 110)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.5.9.0/24 Local Local 00h48m41s 0
PE1_to_CE1 0
10.8.12.0/24 Remote BGP VPN 00h04m02s 170
10.10.10.8 (tunneled) 0
10.10.1.0/24 Remote BGP 00h14m43s 170
10.5.9.9 0
10.10.4.0/24 Remote BGP VPN 00h01m40s 170
10.10.10.8 (tunneled) 0
-------------------------------------------------------------------------------
No. of Routes: 4
===============================================================================

71/122
4. Verify that the CE is receiving routes from the remote site in the same VPN.
*A:R9# show router route-table
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
…
10.5.9.0/24 Local Local 00h16m51s 0

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

to_PE1 0
10.8.12.0/24 Remote BGP 00h04m33s 170
10.5.9.5 0
10.10.1.0/24 Local Local 01h16m21s 0
Blue_Site_1 0
10.10.4.0/24 Remote BGP 00h02m05s 170
10.5.9.5
…
===============================================================================

5. Ensure connectivity between customer sites over the VPN by using PE-based diagnostic tools
such as oam vprn-ping and oam vprn-trace.
*A:R5# oam vprn-trace 110 source 10.5.9.5 destination 10.8.12.8

TTL Seq Rcvd-on Reply-Path RTT

----------------------------------------------------------------------------
[Send request TTL: 1, Seq. 1.]
1 1 cpm In-Band 2.73ms
Node-Id 10.10.10.8
Requestor 10.10.10.5
Route: 10.8.12.0/24
Vpn Label: 131054 Metrics 0 Pref 170 Owner bgpVpn
Next Hops: [1] ldp tunnel
Route Targets: [1]: target:64496:110
Responder 10.10.10.8
Route: 10.8.12.8/32
Vpn Label: 0 Metrics 0 Pref 0 Owner local
Next Hops: [1] ifIdx 2 nextHopIp none

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

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 72/122
Questions

1. Why are route policies required to enable the exchange of routes across a VPRN service?
_________________________________________________________________________________________
2. Which commands will display the route distinguisher?
_________________________________________________________________________________________

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

3. Which command will display the route target?
_________________________________________________________________________________________
4. Are any service related commands required on the CE? Why or why not?
_________________________________________________________________________________________
5. What makes up a VPN-IPv4 prefix?
_________________________________________________________________________________________
6. Does the CE receive VPN-IPv4 prefixes in BGP? Why or why not?
_________________________________________________________________________________________
7. Under which command context is the local Autonomous System number configured?
_________________________________________________________________________________________

Notes

_________________________________________________________________________________________

73/122
LAB 10 IPv6 VPRNs (6VPE)
Objective:
 Configure and verify IPv6 VPN (6VPE) routing over IPv4 MPLS infrastructure with BGP routing
between CE and PE. 6VPE operation is very similar to VPRN for IPv4. The main difference is
that the advertised customer routes are IPv6 instead of IPv4. The PE routers must run IPv4 (to
communicate with the IPv4 MPLS core) and IPv6 (to communicate with customers).

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

AS 64497 AS 64499
Blue VPN Site 1 Red VPN Site 1

BGP
Pod 2
Pod 1 R10-CE 2
R9-CE 1
R6-PE 2
R5-PE 1

MP-BGP
LDP

R7-PE 3 R8-PE 4

Pod 3 Pod 4

R11-CE 3 BGP R12-CE 4

AS 64500 AS 64498
Red VPN Site 2 Blue VPN Site 2

Figure 10-1 IPv6 VPRNs

Syntax
Configuration commands required for the labs are provided in each section. Further details may be
found in Services Architecture Module 5. Verification commands for each lab are also provided. It is
possible for each command to have additional parameters. Use the ‘?’ character for help and to
explore all command line options. Other commands may also be used, including those from previous
exercises and courses.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 74/122
Parameter Value
Pod Number x = 1, 2, 3, or 4 (Circle your Pod number)
7750 SR router you are configuring Core___ or Edge___
Last octet of management address from Table 1-1 y = ______ (Use as the last octet of system address)
IPv6 System IP address 2001:db8::y/128
Core 1 to Edge 1 IPv6 subnet 2001:db8:11::/64
Core 2 to Edge 2 IPv6 subnet 2001:db8:22::/64

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Core 3 to Edge 3 IPv6 subnet 2001:db8:33::/64
Core 4 to Edge 4 IPv6 subnet 2001:db8:44::/64
CE loopback interface (Customer LAN) 2001:db8:x::x/48
Table 10-1 IPv6 Addresses

In the setup, there are two separate sites of two IPv6 VPN customers. These customer sites (CE1, CE2,
CE3 and CE4) are running IPv6 only. They are separated in the middle by the IPv4 network. PE1, PE2,
PE3, and PE4 are dual stack (IPv4/IPv6) routers, which have interfaces connected to both IPv6 and IPv4
networks.

Exercises
Note: Prior to starting these exercises, configure the IPv6 address on the CE routers for the system
interface, loopback interface, and interface to PE using the addresses found in Table 10-1.
On the PE routers, configure the IPv6 address for the system interface.

CE BGP Configuration
On the CE routers, BGP is already configured from a previous lab. However, since the CE routers are
currently running IPv6, you will need to use the IPv6 family and the IPv6 address for neighbor
declaration.
1. Modify the BGP configuration on the CE routers to support the IPv6 family.
2. Use the addresses from Table 10-1 to configure the neighboring PE router.
3. Configure a policy to export directly-connected routes into BGP.

PE VPRN Configuration
Some changes are needed for the VPRN configuration on the PE routers.
1. Configure the IPv6 address for the customer interface in the VPRN instance.
2. Modify the VPRN BGP configuration to support IPv6.

75/122
PE BGP Configuration
Make necessary changes to the PE BGP configurations to support IPv6 VPN.

Verification
1. On the PE routers, verify that the BGP sessions to the CE routers are established and that the
VPN IPv6 routes are exchanged.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5# show router 110 bgp summary
===============================================================================
BGP Router ID:10.10.10.5 AS:64496 Local AS:64496
===============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 2
Total BGP Paths : 6 Total Path Memory : 760
Total IPv4 Remote Rts : 0 Total IPv4 Rem. Active Rts : 0
Total IPv6 Remote Rts : 3 Total IPv6 Rem. Active Rts : 2
Total Supressed Rts : 0 Total Hist. Rts : 0
Total Decay Rts : 0

===============================================================================
BGP Summary
===============================================================================
Neighbor
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-------------------------------------------------------------------------------
10.5.9.9
64497 2108 0 00h05m39s 0/0/5 (IPv6)
2160 0
2001:DB8:11::1
64497 13 0 00h05m07s 3/2/0 (IPv6)
12 0
===============================================================================

2. On the PE routers, verify that the BGP sessions to the other PE routers are established and that
the VPN IPv6 routes are exchanged.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 76/122
*A:R5# show router bgp summary
===============================================================================
BGP Router ID:10.10.10.5 AS:64496 Local AS:64496
===============================================================================
BGP Admin State : Up BGP Oper State : Up
Total Peer Groups : 1 Total Peers : 3
Total BGP Paths : 21 Total Path Memory : 2584
Total IPv4 Remote Rts : 0 Total IPv4 Rem. Active Rts : 0
Total IPv6 Remote Rts : 0 Total IPv6 Rem. Active Rts : 0
Total Supressed Rts : 0 Total Hist. Rts : 0
Total Decay Rts : 0

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Total VPN Peer Groups : 1 Total VPN Peers : 2
Total VPN Local Rts : 4
Total VPN-IPv4 Rem. Rts : 1 Total VPN-IPv4 Rem. Act. Rts: 1
Total VPN-IPv6 Rem. Rts : 3 Total VPN-IPv6 Rem. Act. Rts: 3
Total L2-VPN Rem. Rts : 0 Total L2VPN Rem. Act. Rts : 0
Total VPN Supp. Rts : 0 Total VPN Hist. Rts : 0
Total VPN Decay Rts : 0
Total MVPN-IPv4 Rem Rts : 0 Total MVPN-IPv4 Rem Act Rts : 0
Total MDT-SAFI Rem Rts : 0 Total MDT-SAFI Rem Act Rts : 0

===============================================================================
BGP Summary
===============================================================================
Neighbor
AS PktRcvd InQ Up/Down State|Rcv/Act/Sent (Addr Family)
PktSent OutQ
-------------------------------------------------------------------------------
10.10.10.6
64496 347 0 00h02m27s 0/0/1 (VpnIPv4)
364 0 0/0/3 (VpnIPv6)
10.10.10.7
64496 345 0 00h02m07s 0/0/1 (VpnIPv4)
361 0 0/0/3 (VpnIPv6)
10.10.10.8
64496 355 0 00h01m51s 1/1/1 (VpnIPv4)
361 0 3/3/3 (VpnIPv6)
===============================================================================

3. On the CE routers, verify that the VPN IPv6 routes are acquired via PE-CE BGP sessions and
installed in the route table.

77/122
*A:R9# show router route-table ipv6

===============================================================================
IPv6 Route Table (Router: Base)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
2001:DB8::35/128 Remote BGP 00h01m39s 170
2001:DB8:11::2 0
2001:DB8::37/128 Local Local 00h23m22s 0
system 0

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

2001:DB8:1::/48 Local Local 00h30m20s 0
BlueSite1 0
2001:DB8:4::/48 Remote BGP 00h01m39s 170
2001:DB8:11::2 0
2001:DB8:11::/64 Local Local 00h22m49s 0
toR1 0
2001:DB8:44::/64 Remote BGP 00h01m39s 170
2001:DB8:11::2 0
-------------------------------------------------------------------------------
No. of Routes: 6
===============================================================================

4. On the PE routers, verify that the VPN IPv6 routes are acquired via MBGP from the remote PE
routers.
*A:R5# show router 110 route-table ipv6

===============================================================================
IPv6 Route Table (Service: 110)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
2001:DB8::35/128 Remote BGP VPN 00h02m38s 170
10.10.10.8 (tunneled) 0
2001:DB8::37/128 Remote BGP 00h07m07s 170
2001:DB8:11::1 0
2001:DB8:1::/48 Remote BGP 00h07m07s 170
2001:DB8:11::1 0
2001:DB8:4::/48 Remote BGP VPN 00h02m38s 170
10.10.10.8 (tunneled) 0
2001:DB8:11::/64 Local Local 00h08m39s 0
PE1_to_CE1 0
2001:DB8:44::/64 Remote BGP VPN 00h02m38s 170
10.10.10.8 (tunneled) 0
-------------------------------------------------------------------------------
No. of Routes: 6
==============================================================================

5. Verify that the VPN IPv6 routes are received by the remote PE routers.

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 78/122
*A:R8# show router bgp routes vpn-ipv6
===============================================================================
BGP Router ID:10.10.10.8 AS:64496 Local AS:64496
===============================================================================
Legend -
Status codes : u - used, s - suppressed, h - history, d - decayed, * - valid
Origin codes : i - IGP, e - EGP, ? - incomplete, > - best

===============================================================================
BGP VPN-IPv6 Routes
===============================================================================
Flag Network LocalPref MED

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Nexthop VPNLabel
As-Path
-------------------------------------------------------------------------------
u*>? 64496:10:2001:DB8::37/128 100 None
::FFFF:A0A:A01 131062
64497
u*>? 64496:10:2001:DB8:1::/48 100 None
::FFFF:A0A:A01 131062
64497
u*>i 64496:10:2001:DB8:11::/64 100 None
::FFFF:A0A:A01 131062
No As-Path
-------------------------------------------------------------------------------
Routes : 3
===============================================================================

6. Use the ping command at the CE router to verify the accessibility of the remote CE.
*A:R12# ping 2001:db8:1::1
PING 2001:DB8:1::1 56 data bytes
64 bytes from 2001:DB8:1::1 icmp_seq=1 hlim=62 time=2.83ms.
64 bytes from 2001:DB8:1::1 icmp_seq=2 hlim=62 time=1.96ms.
64 bytes from 2001:DB8:1::1 icmp_seq=3 hlim=62 time=3.14ms.
64 bytes from 2001:DB8:1::1 icmp_seq=4 hlim=62 time=3.08ms.
64 bytes from 2001:DB8:1::1 icmp_seq=5 hlim=62 time=2.51ms.

---- 2001:DB8:1::1 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 1.96ms, avg = 2.70ms, max = 3.14ms, stddev = 0.433ms

79/122
Questions

1. What makes up a VPN-IPv6 prefix?

__________________________________________________________________________________
2. What does a PE BGP table contain?
__________________________________________________________________________________

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Notes

_________________________________________________________________________________________

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 80/122
VPRN Lab Commands
Lab Configuration Commands List
configure router autonomous-system <autonomous-system-number>
configure router bgp family <address-family>
configure router interface <interface name> [no] shutdown
configure router no interface <interface name>
configure router <protocol>

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure router <protocol> group <group name>
configure router <protocol> group <group name> neighbor <neighbor ip-address>
configure router <protocol> group <group name> peer-as <peer autonomous system number>
configure router <protocol> group <group name> local-address <ip-address>
configure router ldp interface-parameters interface <interface-name>
configure router <protocol> shutdown
configure router [no] <protocol>
configure service vprn <vprn-id> customer <customer-id> create
configure service vprn <vprn-id> description <vprn description>
configure service customer <customer-id> contact <text>
configure service customer <customer-id> phone <text>
configure service vprn <vprn-id> router-id <value>
configure service vprn <vprn-id> route-distinguisher <value>
configure service vprn <vprn-id> vrf-target target: <value>
configure service vprn <vprn-id> auto-bind [option]
configure service vprn <vprn-id> interface <interface-name> create
configure service vprn <vprn-id> interface <interface-name> description <interface description>
configure service vprn <service-id> [no] shutdown
configure service vprn <service-id> [no] <protocol>
configure service vprn <service-id> interface [no] <ip-int-name>
configure service vprn <service-id> interface <ip-int-name> [no] shutdown
configure port <slot/mod/num> [no] shutdown
configure port <slot/mod/num> ethernet mode access
configure port <slot/mod/num> ethernet mtu <mtu-value>
configure router ospf area <area-id> interface <ip-int-name> [no] shutdown
configure router ospf asbr
configure service vprn <vprn-id> interface <interface-name> address <ip address>
configure service vprn <vprn-id> interface <interface-name> sap <slot/mod/num> create
configure service vprn <vprn-id> no shutdown

81/122
Lab Configuration Commands List
configure service vprn <service-id> [no] <protocol>
configure service vprn <service-id> <protocol> group <group name>
configure service vprn <service-id> <protocol> group <group name> {import | export} <policy name>
configure service vprn <service-id> <protocol> group <group name> neighbor <neighbor name>
configure service vprn <service-id>
configure service vprn <service-id> bgp group <group-name> family ipv6

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

configure router bgp family ipv4 ipv6 vpn-ipv6
configure service vprn <service-id> bgp interface <ip-int-name> ipv6

Lab Verification Commands List

show port
show router status
show router interface [options]
show router route-table [options]
show router bgp [options]
show router bgp neighbor <neighbor-ip> advertised-routes
show router bgp neighbor <neighbor-ip> received-routes
show router bgp routes
show router bgp routes <prefix> [hunt [brief]]
show router mpls [options]
show router ldp [options]
show router tunnel-table
oam vprn-trace <service-id> [options]
oam vprn-ping <service-id> [options]
traceroute <destination ip address> router <service-id>
ping <destination ip address> router <service-id>
traceroute <destination ip address> [source <source ip address>]
ping <destination ip address> [source <source ip address>]
show router <service-id> [options]
show router <service-id> route-table [options]
show router <service-id> interface [options]
show router <service-id> status
show router <router-instance> route-table
show router policy admin
show router <router-instance> ospf neighbor

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 82/122
Lab Verification Commands List
show router <router-instance> ospf database
show router <service-id> bgp summary
show router bgp summary
show router route-table ipv6
show router <service-id> route-table ipv6
show router bgp routes vpn-ipv6

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

show router <service-id> fib < slot-number> ipv6

83/122
Answers to Review Questions
Lab 2 - Distributed Epipe Service

1. When you do show router ldp bindings, you see labels for the system address of the P routers as
well as the PE routers. A label is required for the PE router because it is the end of the transport
tunnel. Why are there labels for the P routers as well?

The default behavior on the Alcatel-Lucent 7750 SR is to generate labels for the system interface

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

when LDP is enabled on the router. The P routers are LDP-enabled so that they can perform MPLS
label switching, but the labels they generate for their system interfaces are not required unless a
service is configured there.

2. The show router ldp bindings command shows the LMTU and RMTU for the service. What is the
meaning of these values? Why is the value 1500?

These values are sometimes known as the VC-MTU and are signaled when the service labels are
signaled. Martini signaling was originally developed for IP VPNs, therefore the value signaled is the
MTU of the Layer 3 payload. For an Ethernet service, add 14 bytes to get the service MTU.

3. CE1, CE2, CE3 and CE4 are all in the same subnet. Why is it possible to ping CE4 from CE1, but not
from CE2 or CE3?

CE1 and CE4 are connected by an epipe and can therefore ping each other. CE2 and CE3 are
connected by a different epipe and can ping each other. However, these are effectively two
separate networks even if they are addressed with the same network addresses.

LAB 3 – VPLS Service Exercise I

1. What command can you use to find the service type of a service?

show service service-using

show service id 200 base
show service id 200 all

2. What is the MTU for this service?

Use show service id base or show service id 200 all to find that the MTU is 1514.

3. What will happen if you try to send a frame larger than this MTU to the service?

Configure the CE port and the SAP with MTUs of 5000 and send a large ping to the other CE device.
The ping will be dropped because it exceeds the size of the service MTU. Check the SAP statistics
for the service.

*A:CE1# ping 192.168.30.3 size 4500

*A:PE1# show service id 200 all

... etc ...

Sap Statistics
-------------------------------------------------------------------------------
Last Cleared Time : N/A

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 84/122
Packets Octets
Forwarding Engine Stats
Dropped : 6 22814
Off. HiPrio : 0 0
Off. LowPrio : 13 1184
Off. Uncolor : 0 0

Queueing Stats(Ingress QoS Policy 1)

Dro. HiPrio : 0 0
Dro. LowPrio : 0 0
For. InProf : 0 0
For. OutProf : 13 1184

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Queueing Stats(Egress QoS Policy 1)
Dro. InProf : 0 0
Dro. OutProf : 0 0
For. InProf : 0 0
For. OutProf : 15 1296
-------------------------------------------------------------------------------
Sap per Queue stats
… etc …

LAB 3 – VPLS Service Exercise II

1. What will happen to untagged traffic on the CE to PE network?

Untagged traffic will be captured by the default SAP and carried on VPLS 200.

2. If the port was set to null encapsulation, how would you define the SAP? What would happen to
tagged traffic on this SAP?

To define a SAP for a null encapsulated port, it is simply *A:PE1>config>service>vpls# sap 1/1/2
create
All traffic is captured by this SAP, including any tagged traffic.

All the SAPs must be changed to the qinq format. In the service VPLS 200, for example, the SAP
command would change to *A:PE1>config>service>vpls# sap 1/1/2:30.* create
No changes are required on the CE router. This SAP will still capture any dot1q encapsulated
traffic.

LAB 4 – Spoke Termination to a VPLS

1. How does the VPLS learn MAC addresses if it does not have any SAPs?

The VPLS learns the MAC addresses from the SDPs that the frames arrive on.

2. Describe the signaling of service labels to create the service between two access routers

If we look at the signaling between access router PE1 and access router PE2, there are three
Martini signaling sessions that are required to enable the service. PE1 signals to P1 to exchange

85/122
service labels for the epipe service. P1 signals to P2 to exchange service labels for the VPLS
service. P2 signals with PE2 to exchange labels for the second epipe service.

3. If each access and PE router in this scenario participated in a full mesh VPLS service, how many
SDPs would be required on each router?

Each router would require an SDP to each other router in the VPLS service, therefore seven SDPs
are required on each router.

LAB 5 – OAM Tool Exercise II

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

1. In the previous exercise, you used the oam sdp-mtu size-inc command to find the maximum MTU
size that your SDP could support. What was the maximum MTU size?

1556 bytes

2. What is the service MTU of your epipe service?

1514 bytes

3. What is the SDP path MTU? How is this MTU determined?

*A:R5# show service sdp 8

By default the SDP path MTU is calculated from the MTU of the egress port of the PE router. The
path MTU is the port MTU minus the encapsulation overhead (frame header plus two MPLS labels).
In this case the path MTU is calculated as 1578 – (14 + 4 + 4) = 1556 bytes.

4. Set the MTU to 1514 on the network port of the P router to P router link for your epipe. Check the
service status, service MTU and the SDP path MTU. What has changed?

*A:R1# configure port 1/1/4 ethernet mtu 1514

Nothing has changed with the service or SDP MTU. The service is not aware of the port MTU change
in the provider network

5. Use oam sdp-mtu size-inc to find the maximum MTU size that your SDP now supports. What is this
value? Considering the MPLS encapsulation overhead, does this make sense?

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 86/122
*A:R5# oam sdp-mtu 8 size-inc 1450 1550 step 10
Size Sent Response
----------------------------
1450 . Success
1460 . Success
1470 . Success
1480 . Success
1490 . Success
1500 ... Request Timeout

Maximum Response Size: 1490

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5# oam sdp-mtu 8 size-inc 1490 1500 step 1
Size Sent Response
----------------------------
1490 . Success
1491 . Success
1492 . Success
1493 ... Request Timeout

Maximum Response Size: 1492

The new MTU size supported is now 1492 bytes. Adding 14 bytes for the Ethernet header and 8
bytes for the MPLS labels equals 1514 bytes, which is the expected size of the port MTU on the
provider port.

6. Validate your results by pinging between the CE routers with different size packets.

It is possible to specify the size of the data bytes in the ping packet. This value does not include
the 8 bytes of the ICMP header, the 20 bytes of the IP header or the 14 bytes of the Ethernet
frame. Subtracting 42 from 1492 means that a ping size of 1450 should generate the maximum size
frame of 1492 bytes.

*A:R9# ping 192.168.10.4 size 1450

PING 192.168.10.4 1450 data bytes
1458 bytes from 192.168.10.4: icmp_seq=1 ttl=64 time<10ms.
1458 bytes from 192.168.10.4: icmp_seq=2 ttl=64 time<10ms.
1458 bytes from 192.168.10.4: icmp_seq=3 ttl=64 time<10ms.
1458 bytes from 192.168.10.4: icmp_seq=4 ttl=64 time<10ms.
1458 bytes from 192.168.10.4: icmp_seq=5 ttl=64 time<10ms.

---- 192.168.10.4 PING Statistics ----

5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min < 10ms, avg < 10ms, max < 10ms, stddev < 10ms

*A:R91# ping 192.168.10.4 size 1451

PING 192.168.10.4 1451 data bytes
Request timed out. icmp_seq=1.
Request timed out. icmp_seq=2.
Request timed out. icmp_seq=3.
Request timed out. icmp_seq=4.
Request timed out. icmp_seq=5.
---- 192.168.10.4 PING Statistics ----
5 packets transmitted, 0 packets received, 100% packet loss

Note: If you use a significantly larger value for the size parameter, the ping may work. This is
because the frame is too large for the Ethernet MTU and is fragmented. If you specify “do-not-
fragment” no value larger than 1450 will work.

87/122
7. Configure an RSVP LSP from your PE router to the diagonally opposite PE router. Change the SDP
created in Lab 2 to use this LSP instead of LDP. Verify that the LSP and the SDP come up.

8. How is the path MTU of the SDP different from before?

Path MTU is not changed, nor is the service. The SDP still thinks it can transport a 1514 byte
payload.

9. Change the LSP to use adspec. This should cause RSVP to signal MTU along the LSP. What is the
path MTU of the SDP with adspec enabled?

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Path MTU becomes 1492.

10. What is the status of the service and what can you do about it?

Service is operationally down because the service MTU is larger than the path MTU. The service can
be brought up by adjusting the service MTU to match the path MTU on both ends; however, the
service will drop any frames it receives that are larger than the service MTU.

LAB 7 – Internet Enhanced Service (IES)

1. Explain the difference between the CE to CE ping through the IES interface and the CE to CE ping
through your epipe.

The ping through the IES interface is routed through the service provider network to the other IES
interface. The ping through the epipe service is carried across the service provider’s network in an
MPLS tunnel.

LAB 8 –VPLS Spoke Termination on IES

1. What MAC address is being used as the destination MAC address when you ping from your CE
router to any other CE router?

The default gateway for the CE router is the IES interface on the P router. Therefore the chassis
MAC address of the P router is used.

===============================================================================
ARP Table (Router: Base)
===============================================================================
IP Address MAC Address Expiry Type Interface
-------------------------------------------------------------------------------
10.10.10.9 7a:4c:ff:00:00:00 00h00m00s Oth system
192.168.10.1 7a:4c:01:01:00:02 00h00m00s Oth[I] toR5-1
192.168.10.4 7a:4f:01:01:00:02 00h25m47s Dyn[I] toR5-1
192.168.20.1 7a:4c:01:01:00:02 00h00m00s Oth[I] toR5-2
192.168.30.1 7a:4c:01:01:00:02 00h00m00s Oth[I] toR5-3
192.168.40.1 7a:4c:01:01:00:02 00h00m00s Oth[I] toR5-4

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

192.168.40.2 7a:4d:01:01:00:02 00h37m02s Dyn[I] toR5-4
192.168.50.1 7a:4c:01:01:00:02 00h00m00s Oth[I] toR5-5
172.16.1.1 7a:48:01:01:00:02 00h24m39s Dyn[I] to_IES
172.16.1.2 7a:4c:01:01:00:02 00h00m00s Oth[I] to_IES
100.100.1.1 7a:4c:ff:00:00:00 00h00m00s Oth loopback_1
172.17.1.1 7a:44:ff:00:00:00 02h58m33s Dyn[I] to_ISP_7
172.17.1.2 7a:4c:01:01:00:02 00h00m00s Oth[I] to_ISP_7
-------------------------------------------------------------------------------
No. of ARP Entries: 13
===============================================================================

*A:R1# show chassis

===============================================================================
Chassis Information
===============================================================================
Name : R1
Type : 7750 SR-7
Location :
Coordinates :
CLLI code :
Number of slots : 7
Number of ports : 20
Critical LED state : Off
Major LED state : Off
Minor LED state : Off
Over Temperature state : OK
Base MAC address : 7a:44:ff:00:00:00
Admin chassis mode : c
Oper chassis mode : c

2. What happens to the Layer 2 header when it reaches the IES interface when you ping from your CE
router to any other CE router?

The ping is routed at the IES interface, therefore the Layer 2 header is replaced with another Layer
2 header for transmission to the next hop.

3. Use the traceroute command to trace the path between your CE router and the CE router beside
your pod.

*A:R9# traceroute 172.17.2.2

traceroute to 172.17.2.2, 30 hops max, 40 byte packets
1 172.17.1.1 (172.17.1.1) 2.07 ms 2.24 ms 2.14 ms
2 10.1.2.2 (10.1.2.2) 3.53 ms 3.92 ms 3.74 ms
3 172.17.2.2 (172.17.2.2) 5.59 ms 5.58 ms 6.64 ms

89/122
4. What table is being used for each router along the path to make the forwarding decision? (e.g.
route-table, FDB)

The packet travels from the CE router to the VPLS on the PE router. The VPLS FDB is used to
forward the packet on the spoke SDP to the IES interface. From the IES interface, the packet is
routed through the provider network to the IES interface for the next pod. The packet is forwarded
at the IES interface to the spoke SDP based on a routing decision. When the packet arrives at the
VPLS, it is forwarded out the SAP towards the CE router based on the VPLS FDB.

Lab 9 – IPv4 VPRNs

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

1. Why are route policies required to enable the exchange of routes across a VPRN service?
Route policies are required to enable the exchange of routes because different routing
protocols do not usually exchange routes with each other by default. In a VPRN service,
Alcatel-Lucent routers automatically exchange routes from OSPF to MP-BGP and BGP to MP-
BGP. Route Policy is required to exchange the routes in a VRF with the PE-CE protocol (MP-BGP
to OSPF in this case). It is also mandatory on the CE to advertise the site routes into the PE-CE
protocol.
2. Which commands will display the route distinguisher?
The show service id <vprn id> base or the show router bgp routes commands will display the
route distinguisher.
3. Which command will display the route target?
The show service id <vprn id> base command will display the route target.
4. Are any service- related commands required on the CE? Why or why not?
No service related commands are required on the CE because the CE is not aware of the VPRN
service.
5. What makes up a VPN-IPv4 prefix?
A VPN-IPv4 prefix is made up of a 64 bit route distinguisher and a 32 bit IPv4 address.
6. Does the CE receive VPN-IPv4 prefixes in BGP? Why or why not?
The CE does not receive VPN-IPv4 prefixes in BGP because it is configured with BGP but not MP-
BGP. Only MP-BGP exchanges VPN-IPv4 prefixes and is configured in the provider core.
7. Under which command context is the local Autonomous System number configured?
The local Autonomous System number is configured under the router global command context.

Lab 10 – IPv6 VPR (6VPE)

1. What makes up a VPN-IPv6 prefix?
A VPNv6 address is a 16-byte IPv6 address prepended with an 8-byte RD to form a 24-byte
address.
2. What does a PE BGP table contain?
A PE BGP table contains entries from all customer-specific IPv6 routing tables.

IS-IS configuration on R1 and R5

*A:R1# configure router isis
*A:R1>config>router>isis$ area-id 0
*A:R1>config>router>isis$ interface "toR2" interface-type point-to-point
*A:R1>config>router>isis$ interface "toR3" interface-type point-to-point
*A:R1>config>router>isis$ interface "toR4" interface-type point-to-point

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R1>config>router>isis$ interface "system"
*A:R1>config>router>isis>if$ exit

*A:R1>config>router>isis$ area-id 1
*A:R1>config>router>isis$ interface "toR5" interface-type point-to-point

*A:R1>config>router>isis$ info
----------------------------------------------
area-id 00
area-id 01
interface "system"
exit
interface "toR2"
interface-type point-to-point
exit
interface "toR3"
interface-type point-to-point
exit
interface "toR4"
interface-type point-to-point
exit
interface "toR5"
interface-type point-to-point
exit
----------------------------------------------

LDP configuration on R1 and R5

*A:R1# configure router ldp
*A:R1>config>router>ldp$ interface-parameters
*A:R1>config>router>ldp>if-params$ interface "toR2"
*A:R1>config>router>ldp>if-params>if$ back
*A:R1>config>router>ldp>if-params# interface "toR3"
*A:R1>config>router>ldp>if-params>if$ back
*A:R1>config>router>ldp>if-params# interface "toR4"
*A:R1>config>router>ldp>if-params>if$ back
*A:R1>config>router>ldp>if-params# interface "toR5"
*A:R1>config>router>ldp>if-params>if$ back
*A:R1>config>router>ldp>if-params# back

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

91/122
Lab 2 Distributed Epipe Service
Phase I
Configure the CE routers

*A:R9# configure port 1/1/2 ethernet encap-type dot1q

*A:R9# configure router interface toR5
*A:R9>config>router>if$ address 192.168.10.1/24
*A:R9>config>router>if$ port 1/1/2:10

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R9>config>router>if$ exit
*A:R9# configure port 1/1/2 no shutdown

Configure SDP on the PE routers

*A:R5# configure service sdp 8 mpls create

*A:R5>config>service>sdp$ far-end 10.10.10.8
*A:R5>config>service>sdp$ ldp
*A:R5>config>service>sdp$ no shutdown

Configure Epipe on the PE routers

*A:R5# configure port 1/1/2 ethernet mode access

*A:R5# configure port 1/1/2 ethernet encap-type dot1q
*A:R5# configure port 1/1/2 no shutdown
*A:R5# configure service epipe 10 customer 1 create
*A:R5>config>service>epipe$ sap 1/1/2:10 create
*A:R5>config>service>epipe>sap$ exit
*A:R5>config>service>epipe# spoke-sdp 8:10 create
*A:R5>config>service>epipe>spoke-sdp$ exit
*A:R5>config>service>epipe# no shutdown

Phase II
Configure the CE routers

*A:R9# configure router interface toR5-2

*A:R9>config>router>if$ address 192.168.20.1/24
*A:R9>config>router>if$ port 1/1/2:20
*A:R9>config>router>if$ exit

Configure Epipe on the PE routers

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

Configure full mesh of SDPs (sdp 8 was previously created)

*A:R5>config>service# sdp 6 mpls create

*A:R5>config>service>sdp$ far-end 10.10.10.6
*A:R5>config>service>sdp$ ldp
*A:R5>config>service>sdp$ no shutdown
*A:R5>config>service>sdp$ exit
*A:R5>config>service# sdp 7 mpls create

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>service>sdp$ far-end 10.10.10.7
*A:R5>config>service>sdp$ ldp
*A:R5>config>service>sdp$ no shutdown
*A:R5>config>service>sdp$ exit
*A:R5>config>service#

Configure VPLS service

*A:R5# configure service customer 200 create

*A:R5>config>service>cust$ exit
*A:R5# configure service vpls 200 customer 200 create
*A:R5>config>service>vpls$ sap 1/1/2:30 create
*A:R5>config>service>vpls>sap$ back
*A:R5>config>service>vpls# mesh-sdp 6 create
*A:R5>config>service>vpls>mesh-sdp$ exit
*A:R5>config>service>vpls# mesh-sdp 7 create
*A:R5>config>service>vpls>mesh-sdp$ back
*A:R5>config>service>vpls# mesh-sdp 8 create
*A:R5>config>service>vpls>mesh-sdp$ back
*A:R5>config>service>vpls# no shutdown

Create CE interface

*A:R9# configure router interface toR5-3

*A:R9>config>router>if$ address 192.168.30.1/24
*A:R9>config>router>if$ port 1/1/2:30
*A:R9>config>router>if$ exit

Lab 3 VPLS Service Exercise II

Configure interface on the CE routers

*A:R9# configure router interface toR5-5

*A:R9>config>router>if$ address 192.168.50.1/24
*A:R9>config>router>if$ port 1/1/2:50
*A:R9>config>router>if$ exit

Change the SAP to the default SAP

*A:R5>config>service# vpls 200
*A:R5>config>service>vpls# sap 1/1/2:30 shutdown
*A:R5>config>service>vpls# no sap 1/1/2:30
*A:R5>config>service>vpls# sap 1/1/2:* create
*A:R5>config>service>vpls>sap$ exit

93/122
Lab 4 Spoke Termination to a VPLS

Configure SDPs on PE routers (former P routers (R1-R4))

*A:R1>config>service# sdp 2 mpls create

*A:R1>config>service>sdp$ far-end 10.10.10.2
*A:R1>config>service>sdp$ ldp
*A:R1>config>service>sdp$ no shutdown
*A:R1>config>service>sdp$ exit
*A:R1>config>service# sdp 3 mpls create

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R1>config>service>sdp$ far-end 10.10.10.3
*A:R1>config>service>sdp$ ldp
*A:R1>config>service>sdp$ no shutdown
*A:R1>config>service>sdp$ exit
*A:R1>config>service# sdp 4 mpls create
*A:R1>config>service>sdp$ far-end 10.10.10.4
*A:R1>config>service>sdp$ ldp
*A:R1>config>service>sdp$ no shutdown
*A:R1>config>service>sdp$ exit
*A:R1>config>service# sdp 5 mpls create
*A:R1>config>service>sdp$ far-end 10.10.10.5
*A:R1>config>service>sdp$ ldp
*A:R1>config>service>sdp$ no shutdown
*A:R1>config>service>sdp$ exit

Configure VPLS on PE routers (former P routers)

*A:R1>config>service# customer 300 create

*A:R1>config>service>cust$ description Spoke_VPLS_Customer
*A:R1>config>service>cust$ back
*A:R1>config>service# vpls 300 customer 300 create
*A:R1>config>service>vpls$ mesh-sdp 2 create
*A:R1>config>service>vpls>mesh-sdp$ exit
*A:R1>config>service>vpls# mesh-sdp 3 create
*A:R1>config>service>vpls>mesh-sdp$ exit
*A:R1>config>service>vpls# mesh-sdp 4 create
*A:R1>config>service>vpls>mesh-sdp$ exit
*A:R1>config>service>vpls# spoke-sdp 5:300 create
*A:R1>config>service>vpls>spoke-sdp$ exit
*A:R1>config>service>vpls# no shutdown

Configure SDP and Epipe on Access routers (former PE routers (R5-R8)

*A:R5>config>service# sdp 1 mpls create

*A:R5>config>service>sdp$ far-end 10.10.10.1
*A:R5>config>service>sdp$ ldp
*A:R5>config>service>sdp$ no shutdown
*A:R5>config>service>sdp$ back
*A:R5>config>service# customer 300 create
*A:R5>config>service>cust$ description Spoke_VPLS_Customer
*A:R5>config>service>cust$ exit
*A:R5>config>service# epipe 300 customer 300 create
*A:R5>config>service>epipe$ sap 1/1/2:40 create
*A:R5>config>service>epipe>sap$ exit
*A:R5>config>service>epipe# spoke-sdp 1:300 create

Configure interface on CE the routers (R9-R12))

*A:R9# configure router interface toR5-4

*A:R9>config>router>if$ address 192.168.40.1/24
*A:R9>config>router>if$ port 1/1/2:40
*A:R9>config>router>if$ exit

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

95/122
Lab 5 OAM Tools

Exercise II

Configuring an RSVP LSP for the SDP

*A:R5>config>router>mpls$ interface "toR1"

*A:R5>config>router>mpls>if$ exit
*A:R5>config>router>mpls# path loose
*A:R5>config>router>mpls>path$ no shutdown

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>router>mpls>path$ exit
*A:R5>config>router>mpls# lsp R5-R8
*A:R5>config>router>mpls>lsp$ to 10.10.10.8
*A:R5>config>router>mpls>lsp$ primary "loose"
*A:R5>config>router>mpls>lsp>primary$ exit
*A:R5>config>router>mpls>lsp# no shutdown
*A:R5>config>router>mpls>lsp# exit
*A:R5>config>router>mpls# no shutdown
*A:R5>config>router# rsvp no shutdown

*A:R1# configure router mpls

*A:R1>config>router>mpls$ interface "toR5"
*A:R1>config>router>mpls>if$ back
*A:R1>config>router>mpls# interface "toR4"
*A:R1>config>router>mpls>if$ exit
*A:R1>config>router>mpls# no shutdown
*A:R1>config>router# rsvp no shutdown
*A:R4# configure router mpls
*A:R4>config>router>mpls$ interface "toR8"
*A:R4>config>router>mpls>if$ back
*A:R4>config>router>mpls# interface "toR1"
*A:R4>config>router>mpls>if$ exit
*A:R4>config>router>mpls# no shutdown
*A:R4>config>router# rsvp no shutdown
*A:R8>config>router>mpls$ interface "toR4"
*A:R8>config>router>mpls>if$ exit
*A:R8>config>router>mpls# path loose
*A:R8>config>router>mpls>path$ no shutdown
*A:R8>config>router>mpls>path$ exit
*A:R8>config>router>mpls# lsp R8-R5
*A:R8>config>router>mpls>lsp$ to 10.10.10.5
*A:R8>config>router>mpls>lsp$ primary "loose"
*A:R8>config>router>mpls>lsp>primary$ exit
*A:R8>config>router>mpls>lsp# no shutdown
*A:R8>config>router>mpls>lsp# exit
*A:R8>config>router>mpls# no shutdown
*A:R8>config>router# rsvp no shutdown

Configuring the SDP

*A:R5# configure service sdp 8

*A:R5>config>service>sdp# no ldp
*A:R5>config>service>sdp# lsp "R5-R8"

===============================================================================
MPLS LSPs (Originating)
===============================================================================
LSP Name To Fastfail Adm Opr
Config
-------------------------------------------------------------------------------
R5-R8 10.10.10.8 No Up Up
-------------------------------------------------------------------------------
LSPs : 1
===============================================================================

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5# show service sdp

==============================================================================
Services: Service Destination Points
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
1 0 1556 10.10.10.1 Up Up LDP TLDP
6 0 1556 10.10.10.6 Up Up LDP TLDP
7 0 1556 10.10.10.7 Up Up LDP TLDP
8 0 1556 10.10.10.8 Up Up MPLS TLDP
------------------------------------------------------------------------------
Number of SDPs : 4
------------------------------------------------------------------------------

*A:R5# show service id 10 base

Using adspec in an RSVP LSP

*A:R5# configure router mpls

*A:R5>config>router>mpls# info
----------------------------------------------
interface "system"
exit
interface "toR1"

97/122
exit
path "loose"
no shutdown
exit
lsp "R5-R8"
to 10.10.10.8
primary "loose"
exit
no shutdown
exit
no shutdown
----------------------------------------------
*A:R5>config>router>mpls# lsp "R5-R8"

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>router>mpls>lsp# adspec
*A:R5>config>router>mpls>lsp# exit all

*A:R5# show service sdp

==============================================================================
Services: Service Destination Points
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
1 0 1556 10.10.10.1 Up Up LDP TLDP
6 0 1556 10.10.10.6 Up Up LDP TLDP
7 0 1556 10.10.10.7 Up Up LDP TLDP
8 0 1492 10.10.10.8 Up Up MPLS TLDP
------------------------------------------------------------------------------
Number of SDPs : 4
-----------------------------------------------------------------------------

*A:R5# show service id 10 base

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:10 q-tag 1518 1518 Up Up
sdp:8:10 S(10.10.10.8) Spok 0 1492 Up Down
==============================================================================

Note the “flags” field: PathMTUTooSmall

**A:R5# configure service epipe 10

*A:R5>config>service>epipe# service-mtu 1492

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 98/122
*A:R5# show service id 10 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 10 Vpn Id : 0
Service Type : Epipe
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 01/11/2012 22:48:37
Last Mgmt Change : 01/10/2012 21:00:02
Admin State : Up Oper State : Down
MTU : 1514
Vc Switching : False

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
Sdp Id 8:10 -(10.10.10.8)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 8:10 Type : Spoke
Spoke Descr : (Not Specified)
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 1492
Far End : 10.10.10.8 Delivery : MPLS
Hash Label : Disabled

Admin State : Up Oper State : Down

Acct. Pol : None Collect Stats : Disabled
Ingress Label : 131063 Egress Label : 131063
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
Admin BW(Kbps) : 0 Oper BW(Kbps) : 0
Last Status Change : 01/11/2012 22:48:37 Signaling : TLDP
Last Mgmt Change : 01/10/2012 20:59:51 Force Vlan-Vc : Disabled
Endpoint : N/A Precedence : 4
Class Fwding State : Down
Flags : PathMTUTooSmall
Peer Pw Bits : pwNotForwarding
Peer Fault Ip : None
Peer Vccv CV Bits : lspPing
Peer Vccv CC Bits : mplsRouterAlertLabel
Application Profile: None

99/122
*A:R5# 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: 01/11/2012 23:04:39
Last Mgmt Change : 01/11/2012 22:58:01
Admin State : Up Oper State : Down
MTU : 1492
Vc Switching : False

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

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:8:10 S(10.10.10.8) Spok 0 1492 Up Down
===============================================================================

*A:R5# show service id 10 all

===============================================================================
Service Detailed Information
===============================================================================
Service Id : 10 Vpn Id : 0
Service Type : Epipe
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 01/11/2012 23:04:39
Last Mgmt Change : 01/11/2012 22:58:01
Admin State : Up Oper State : Down
MTU : 1492
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
Per Svc Hashing : Disabled
Force QTag Fwd : Disabled
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
Sdp Id 8:10 -(10.10.10.8)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 8:10 Type : Spoke
Spoke Descr : (Not Specified)
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 1492
Far End : 10.10.10.8 Delivery : MPLS
Hash Label : Disabled

Admin State : Up Oper State : Down

Acct. Pol : None Collect Stats : Disabled
Ingress Label : 131063 Egress Label : 131063
...
Admin BW(Kbps) : 0 Oper BW(Kbps) : 0
Last Status Change : 01/11/2012 23:04:39 Signaling : TLDP
Last Mgmt Change : 01/11/2012 22:58:01 Force Vlan-Vc : Disabled
Endpoint : N/A Precedence : 4
Class Fwding State : Down
Flags : ServiceMTUMismatch
Peer Pw Bits : pwNotForwarding

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 100/122
*A:R5# show router ldp bindings
===============================================================================
LDP LSR ID: 10.10.10.5
===============================================================================
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 Service, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service
TLV - (Type, Length: Value)
===============================================================================
LDP Prefix Bindings
===============================================================================
Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

LspId
-------------------------------------------------------------------------------
10.10.10.1/32 10.10.10.1 -- 131071 1/1/1 10.1.5.1
10.10.10.2/32 10.10.10.1 131069N 131070 1/1/1 10.1.5.1
10.10.10.3/32 10.10.10.1 131068N 131069 1/1/1 10.1.5.1
10.10.10.4/32 10.10.10.1 131067N 131068 1/1/1 10.1.5.1
10.10.10.5/32 10.10.10.1 131071U -- -- --
10.10.10.6/32 10.10.10.1 131066N 131066 1/1/1 10.1.5.1
10.10.10.7/32 10.10.10.1 131065N 131065 1/1/1 10.1.5.1
10.10.10.8/32 10.10.10.1 131064N 131064 1/1/1 10.1.5.1
-------------------------------------------------------------------------------
No. of Prefix Bindings: 8
===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 8 10.10.10.8 131063U 131063D 1478 1500
E-Eth 20 20 8 10.10.10.8 131062U 131062D 1500 1500
V-Eth 200 200 6 10.10.10.6 131061U 131061 1500 1500
V-Eth 200 200 7 10.10.10.7 131060U 131061 1500 1500
V-Eth 200 200 8 10.10.10.8 131059U 131061 1500 1500
E-Eth 300 300 1 10.10.10.1 131058U 131060S 1500 1500
-------------------------------------------------------------------------------
No. of VC Labels: 6
===============================================================================
LDP Service FEC 129 Bindings
===============================================================================

Note that LMTU and RMTU do not match for Epipe 10. The service will not come up if these are not
equal.

*A:R8# configure service epipe 10 service-mtu 1492

101/122
*A:R5> 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: 01/11/2012 22:59:41
Last Mgmt Change : 01/11/2012 22:58:01
Admin State : Up Oper State : Up
MTU : 1492
Vc Switching : False

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

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:8:10 S(10.10.10.8) Spok 0 1492 Up Up
===============================================================================

Put the port and SDP back to normal (you need to resignal the lsp)

*A:R1# configure port 1/1/4 ethernet no mtu

*A:R5# show service sdp 8

==============================================================================
Service Destination Point (Sdp Id : 8)
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
8 0 1492 10.10.10.8 Up Up MPLS TLDP
==============================================================================

*A:R5# tools perform router mpls resignal lsp "R5-R8" path "loose"

*A:R5# show service sdp 8

==============================================================================
Service Destination Point (Sdp Id : 8)
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
8 0 1556 10.10.10.8 Up Up MPLS TLDP
==============================================================================

On your PE router, configure port 1/1/3 as the mirror destination. Use service-id 103
*A:R5# configure port 1/1/3 shutdown
*A:R5# configure port 1/1/3 ethernet mode access
*A:R5# configure port 1/1/3 no shutdown
*A:R5# configure mirror mirror-dest 103 create
*A:R5>config>mirror>mirror-dest$ sap 1/1/3 create
*A:R5>config>mirror>mirror-dest>sap$ exit
*A:R5>config>mirror>mirror-dest# no shutdown

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>mirror>mirror-dest# exit all

Ensure that the mirror service is enabled and operational.

*A:R5# show service service-using mirror

===============================================================================
Services [mirror]
===============================================================================
ServiceId Type Adm Opr CustomerId Service Name
-------------------------------------------------------------------------------
103 Mirror Up Up 1
-------------------------------------------------------------------------------
Matching Services : 1
-------------------------------------------------------------------------------

On the PE router, configure the port connected to your CE router as the mirror source
for both egress and ingress

*A:R5# debug mirror-source 103

*A:R5>debug>mirror-source# port 1/1/2 egress ingress
*A:R5>debug>mirror-source# no shutdown
*A:R5>debug>mirror-source# exit

Creating the IP filter

*A:R6>config>filter# info
----------------------------------------------
log 102 create
destination memory 100
exit
ip-filter 2 create
entry 10 create
match
dst-ip 192.168.10.4/24
exit
log 102
action forward
exit
exit
----------------------------------------------

*A:R6# configure service epipe 2000

*A:R6>config>service>epipe# info
----------------------------------------------
sap 1/1/3 create

103/122
ingress
filter ip 2
exit
exit
sap 1/1/2:100 create
exit
no shutdown
----------------------------------------------

Configuring Remote Mirror Service

Removing the local mirror and epipe services

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>mirror# mirror-dest 103 shutdown
*A:R5>config>mirror# no mirror-dest 103

*A:R6# configure service epipe 2000

*A:R6>config>service>epipe# shutdown
*A:R6>config>service>epipe# sap 1/1/3 shutdown
*A:R6>config>service>epipe# sap 1/1/2:100 shutdown
*A:R6>config>service>epipe# no sap 1/1/3
*A:R6>config>service>epipe# no sap 1/1/2:100
*A:R6>config>service>epipe# back
*A:R6>config>service# no epipe 2000
*A:R6>config>service# exit all

Creating the mirror source

*A:R5>config>mirror# info
----------------------------------------------
mirror-dest 104 create
description "sending_mirrored_traffic_to_remote_site-R8-PE4"
spoke-sdp 8:104 create
exit
no shutdown
exit
----------------------------------------------
*A:R5# show debug mirror
mirror-source 104
port 1/1/2 egress ingress
no shutdown
exit
exit

Creating the mirror destination

*A:R8# configure mirror mirror-dest 104 create
*A:R8>config>mirror>mirror-dest$ remote-source
*A:R8>config>mirror>mirror-dest>remote-source$ far-end 10.10.10.5
*A:R8>config>mirror>mirror-dest>remote-source$ exit
*A:R8>config>mirror>mirror-dest$ sap 1/1/3 create
*A:R8>config>mirror>mirror-dest>sap$ back
*A:R8>config>mirror>mirror-dest# no shutdown
*A:R8>config>mirror>mirror-dest# info
----------------------------------------------
remote-source

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 104/122
far-end 10.10.10.5
exit
sap 1/1/3 create
exit
no shutdown
----------------------------------------------

Creating the IP filter

*A:R7>config>filter# info
----------------------------------------------
log 103 create

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

destination memory 100
exit
ip-filter 3 create
entry 10 create
match
dst-ip 192.168.10.4/24
exit
log 103
action forward
exit
exit
----------------------------------------------

*A:R7# configure service epipe 3000

*A:R7>config>service>epipe# info
----------------------------------------------
sap 1/1/3 create
ingress
filter ip 3
exit
exit
sap 1/1/2:100 create
exit
no shutdown
----------------------------------------------

Configuring Mirror Slicing

*A:R5# configure mirror mirror-dest 104

*A:R5>config>mirror>mirror-dest# slice-size 128
*A:R5>config>mirror>mirror-dest# info
----------------------------------------------
spoke-sdp 8:104 create
exit
slice-size 128
no shutdown
----------------------------------------------

105/122
Lab 7 Internet Enhanced Service (IES)

Configure IES interface on PE router and add to IS-IS

*A:R5>config>service# customer 500 create

*A:R5>config>service>cust$ description IES_Customer
*A:R5>config>service>cust$ back
*A:R5>config>service# ies 500 customer 500 create
*A:R5>config>service>ies$ interface customer_500 create
*A:R5>config>service>ies>if$ address 172.16.1.1/24

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>service>ies>if$ sap 1/1/2:60 create
*A:R5>config>service>ies>if>sap$ exit
*A:R5>config>service>ies>if$ exit
*A:R5>config>service>ies# no shutdown
*A:R5>config>service>ies# show router interface

*A:R5>config>service>ies# show router interface

*A:R5>config>router>isis# info
----------------------------------------------
area-id 01
interface "system"
exit
interface "toR1"
interface-type point-to-point
exit
----------------------------------------------
*A:R5>config>router>isis# area-id 01
*A:R5>config>router>isis# interface "customer_500"
*A:R5>config>router>isis>if# interface-type point-to-point
*A:R5>config>router>isis>if# exit

*A:R5>config>router>isis# show router isis interface

===============================================================================
ISIS Interfaces
===============================================================================
Interface Level CircID Oper State L1/L2 Metric
-------------------------------------------------------------------------------
system L1L2 1 Up 0/0
toR1 L1L2 2 Up 10/10
customer_500 L1L2 3 Up 10/10
-------------------------------------------------------------------------------
Interfaces : 3

*A:R9# configure router interface to_IES

*A:R9>config>router>if$ address 172.16.1.2/24
*A:R9>config>router>if$ port 1/1/2:60
*A:R9>config>router>if$ exit
*A:R9# configure router interface loopback_1
*A:R9>config>router>if$ address 100.100.1.1/24
*A:R9>config>router>if$ loopback
*A:R9>config>router>if$ exit

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R9# ping 172.16.1.1
PING 172.16.1.1 56 data bytes
64 bytes from 172.16.1.1: icmp_seq=1 ttl=64 time=3.06ms.
64 bytes from 172.16.1.1: icmp_seq=2 ttl=64 time=1.10ms.
64 bytes from 172.16.1.1: icmp_seq=3 ttl=64 time=0.983ms.
64 bytes from 172.16.1.1: icmp_seq=4 ttl=64 time=1.01ms.
64 bytes from 172.16.1.1: icmp_seq=5 ttl=64 time=0.934ms.
---- 172.16.1.1 PING Statistics ----
5 packets transmitted, 5 packets received, 0.00% packet loss
round-trip min = 0.934ms, avg = 1.42ms, max = 3.06ms, stddev = 0.822ms

*A:R9# show router interface

===============================================================================
Interface Table (Router: Base)
===============================================================================
Interface-Name Adm Opr(v4/v6) Mode Port/SapId
IP-Address PfxState
-------------------------------------------------------------------------------
loopback_1 Up Up/Down Network loopback
100.100.1.1/24 n/a
system Up Up/Down Network system
10.10.10.9/32 n/a
toR5-1 Up Up/Down Network 1/1/2:10
192.168.10.1/24 n/a
toR5-2 Up Up/Down Network 1/1/2:20
192.168.20.1/24 n/a
toR5-3 Up Up/Down Network 1/1/2:30
192.168.30.1/24 n/a
toR5-4 Up Up/Down Network 1/1/2:40
192.168.40.1/24 n/a
toR5-5 Up Up/Down Network 1/1/2:50
192.168.50.1/24 n/a
to_IES Up Up/Down Network 1/1/2:60
172.16.1.2/24 n/a
-------------------------------------------------------------------------------
Interfaces : 8
===============================================================================

*A:R9# configure router isis

*A:R9>config>router>isis$ area-id 1
*A:R9>config>router>isis$ level-capability level-1
*A:R9>config>router>isis# interface "system"
*A:R9>config>router>isis>if# exit
*A:R9>config>router>isis$ interface "to_IES"
*A:R9>config>router>isis>if$ interface-type point-to-point
*A:R9>config>router>isis>if$ exit

107/122
*A:R9>config>router>isis$ interface "loopback_1"
*A:R9>config>router>isis>if$ exit

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 108/122
*A:R9# show router route-table
===============================================================================
Route Table (Router: Base)
===============================================================================
Dest Prefix Type Proto Age Pref
Next Hop[Interface Name] Metric
-------------------------------------------------------------------------------
10.1.2.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 30
10.1.3.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 30
10.1.4.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 30
10.1.5.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 20
10.2.3.0/24 Remote ISIS 00h30m48s 15

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

172.16.1.1 40
10.2.4.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.2.6.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.3.4.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.3.7.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.4.8.0/24 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.10.10.1/32 Remote ISIS 00h30m48s 15
172.16.1.1 20
10.10.10.2/32 Remote ISIS 00h30m48s 15
172.16.1.1 30
10.10.10.3/32 Remote ISIS 00h30m48s 15
172.16.1.1 30
10.10.10.4/32 Remote ISIS 00h30m48s 15
172.16.1.1 30
10.10.10.5/32 Remote ISIS 00h30m48s 15
172.16.1.1 10
10.10.10.6/32 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.10.10.7/32 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.10.10.8/32 Remote ISIS 00h30m48s 15
172.16.1.1 40
10.10.10.9/32 Local Local 09d01h20m 0
system 0
10.10.10.10/32 Remote ISIS 00h08m40s 15
172.16.1.1 50
10.10.10.5/32 Remote ISIS 00h08m26s 15
172.16.1.1 50
10.10.10.12/32 Remote ISIS 00h07m57s 15
172.16.1.1 50
100.100.1.0/24 Local Local 00h40m09s 0
loopback_1 0
100.100.2.0/24 Remote ISIS 00h28m46s 15
172.16.1.1 50
100.100.3.0/24 Remote ISIS 00h28m13s 15
172.16.1.1 50
100.100.4.0/24 Remote ISIS 00h27m47s 15
172.16.1.1 50
172.16.1.0/24 Local Local 00h41m06s 0
to_IES 0
172.16.2.0/24 Remote ISIS 00h30m50s 15
172.16.1.1 50
172.16.3.0/24 Remote ISIS 00h30m50s 15
172.16.1.1 50
172.16.4.0/24 Remote ISIS 00h30m50s 15
172.16.1.1 50
192.168.10.0/24 Local Local 01d21h13m 0
toR5-1 0
192.168.20.0/24 Local Local 01d21h09m 0
toR5-2 0
192.168.30.0/24 Local Local 01d19h19m 0
toR5-3 0
192.168.40.0/24 Local Local 01d01h00m 0
toR5-4 0
192.168.50.0/24 Local Local 22h33m47s 0
toR5-5 0
-------------------------------------------------------------------------------
No. of Routes: 35
===============================================================================

109/122
Verify network reachability

*A:R9# ping 10.10.10.1

PING 10.10.10.1 56 data bytes
64 bytes from 10.10.10.1: icmp_seq=1 ttl=63 time=1.63ms.
64 bytes from 10.10.10.1: icmp_seq=2 ttl=63 time=1.66ms.
64 bytes from 10.10.10.1: icmp_seq=3 ttl=63 time=1.53ms.
64 bytes from 10.10.10.1: icmp_seq=4 ttl=63 time=1.55ms.
^C
ping aborted by user

*A:R9# ping 100.100.2.1

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

PING 100.100.2.1 56 data bytes
64 bytes from 100.100.2.1: icmp_seq=1 ttl=60 time=5.02ms.
64 bytes from 100.100.2.1: icmp_seq=2 ttl=60 time=5.20ms.
^C
ping aborted by user

*A:R9# traceroute 100.100.2.1

traceroute to 100.100.2.1, 30 hops max, 40 byte packets
1 172.16.1.1 (172.16.1.1) 1.61 ms 0.970 ms 1.39 ms
2 10.1.5.1 (10.1.5.1) 1.86 ms 1.74 ms 2.01 ms
3 10.1.2.2 (10.1.2.2) 2.99 ms 2.88 ms 2.78 ms
4 10.2.6.6 (10.2.6.6) 3.64 ms 3.55 ms 3.27 ms
5 100.100.2.1 (100.100.2.1) 5.23 ms 5.20 ms 6.08 ms

*A:R9# traceroute 192.168.40.2

traceroute to 192.168.40.2, 30 hops max, 40 byte packets
1 192.168.40.2 (192.168.40.2) 11.7 ms 5.62 ms 5.90 ms

*A:R5# configure service ies 500 shutdown

Configure VPLS on PE router

*A:R5# configure service vpls 1100 customer 1 create

*A:R5>config>service>vpls$ sap 1/1/2:70 create
*A:R5>config>service>vpls>sap$ exit
*A:R5>config>service>vpls# spoke-sdp 1:1000 create

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R5>config>service>vpls>spoke-sdp$ exit
*A:R5>config>service>vpls# no shutdown

Configure interface on CE router and add to IS-IS

*A:R9# configure router interface to_ISP_7

*A:R9>config>router>if$ address 172.17.1.2/24
*A:R9>config>router>if$ port 1/1/2:70
*A:R9>config>router>if$ exit
*A:R9# configure router isis
*A:R9>config>router>isis# area-id 1
*A:R9>config>router>isis# interface "to_ISP_7"
*A:R9>config>router>isis>if# interface-type point-to-point
*A:R9>config>router>isis>if# exit

Configure IES interface on P router and add to IS-IS

*A:R1# configure service ies 600 customer 1 create

*A:R1>config>service>ies$ interface IES_600
*A:R1>config>service>ies$ interface IES_600 create
*A:R1>config>service>ies>if# address 172.17.1.1/24
*A:R1>config>service>ies>if$ spoke-sdp 5:1100 create
*A:R1>config>service>ies>if>spoke-sdp$ exit
*A:R1>config>service>ies>if# exit
*A:R1>config>service>ies# no shutdown
*A:R1# configure router isis
*A:R1>config>router>isis# area-id 1
*A:R1>config>router>isis# interface "IES_600" interface-type point-to-point

*A:R1# show service id 600 base

===============================================================================
Service Basic Information
===============================================================================
Service Id : 600 Vpn Id : 0
Service Type : IES
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 01/03/2012 23:15:08
Last Mgmt Change : 01/13/2012 01:23:28
Admin State : Up Oper State : Down
SAP Count : 0
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:5:1100 S(10.10.10.5) Spok 0 1556 Up Down
===============================================================================

Identify and correct MTU problem

111/122
*A:R5# show service id 1100 base

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

MTU : 1514 Def. Mesh VC Id : 1100
SAP Count : 1 SDP Bind Count : 1
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Def. Gateway IP : None
Def. Gateway MAC : None
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/2:70 q-tag 1518 1518 Up Up
sdp:1:1100 S(10.10.10.1) Spok 0 1556 Up Down
===============================================================================

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 112/122
*A:R5# show service id 1100 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 1100 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 01/12/2012 19:04:09
Last Mgmt Change : 01/12/2012 19:04:09
Admin State : Up Oper State : Up

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

MTU : 1514 Def. Mesh VC Id : 1100
SAP Count : 1 SDP Bind Count : 1
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Def. Gateway IP : None
Def. Gateway MAC : None
-------------------------------------------------------------------------------
Split Horizon Group specifics
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
Sdp Id 1:1100 -(10.10.10.1)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 1:1100 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 : 1556
Far End : 10.10.10.1 Delivery : LDP
Hash Label : Disabled

Admin State : Up Oper State : Down

Acct. Pol : None Collect Stats : Disabled
Ingress Label : 131056 Egress Label : 131059
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 : 01/03/2012 17:12:19 Signaling : TLDP
Last Mgmt Change : 01/12/2012 19:04:02 Force Vlan-Vc : Disabled
Endpoint : N/A Precedence : 4
Class Fwding State : Down
Flags : ServiceMTUMismatch
Time to RetryReset : never Retries Left : 3
Mac Move : Blockable Blockable Level : Tertiary
Peer Pw Bits : pwNotForwarding
Peer Fault Ip : None
Application Profile: None
…
-------------------------------------------------------------------------------

113/122
*A:R5# show router ldp bindings
===============================================================================
LDP LSR ID: 10.10.10.5
===============================================================================
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 Service, R - VPRN service
P - Ipipe Service, WP - Label Withdraw Pending, C - Cpipe Service
TLV - (Type, Length: Value)
===============================================================================
LDP Prefix Bindings

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

===============================================================================
Prefix Peer IngLbl EgrLbl EgrIntf/ EgrNextHop
LspId
-------------------------------------------------------------------------------
10.10.10.1/32 10.10.10.1 -- 131071 1/1/1 10.1.5.1
10.10.10.2/32 10.10.10.1 131069N 131070 1/1/1 10.1.5.1
10.10.10.3/32 10.10.10.1 131068N 131069 1/1/1 10.1.5.1
10.10.10.4/32 10.10.10.1 131067N 131068 1/1/1 10.1.5.1
10.10.10.5/32 10.10.10.1 131071U -- -- --
10.10.10.6/32 10.10.10.1 131066N 131066 1/1/1 10.1.5.1
10.10.10.7/32 10.10.10.1 131065N 131065 1/1/1 10.1.5.1
10.10.10.8/32 10.10.10.1 131064N 131064 1/1/1 10.1.5.1
-------------------------------------------------------------------------------
No. of Prefix Bindings: 8
===============================================================================
LDP Service FEC 128 Bindings
===============================================================================
Type VCId SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
E-Eth 10 10 8 10.10.10.8 131063U 131063S 1478 1478
E-Eth 20 20 8 10.10.10.8 131062U 131062S 1500 1500
V-Eth 200 200 6 10.10.10.6 131061U 131061 1500 1500
V-Eth 200 200 7 10.10.10.7 131060U 131061 1500 1500
V-Eth 200 200 8 10.10.10.8 131059U 131061 1500 1500
E-Eth 300 300 1 10.10.10.1 131058U 131060S 1500 1500
V-Eth 1100 1000 1 10.10.10.1 131056U 131059D 1500 1542
M-Mirr 104 104 1 10.10.10.8 1U 131056S 0 0
-------------------------------------------------------------------------------
No. of VC Labels: 8
===============================================================================
LDP Service FEC 129 Bindings
===============================================================================
AGI SAII TAII
Type SvcId SDPId Peer IngLbl EgrLbl LMTU RMTU
-------------------------------------------------------------------------------
No Matching Entries Found
===============================================================================

After show service id 1100 all note the “ServiceMTUMismatch” in the flags section. Also, note LMTU of
1500 and RMTU of 1542 in the service label output of show router ldp bindings. Correct the problem
by specifying MTU of 1500 in the IES service to match the Layer 2 MTU.

*A:R1>config>service# ies 600

*A:R1>config>service>ies# interface customer-2
*A:R1>config>service>ies>if# ip-mtu 1500
*A:R1>config>service>ies>if# exit all

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 114/122
*A:R5# show service id 1000 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1100 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 03/27/2012 08:56:58
Last Mgmt Change : 03/27/2012 08:56:58
Admin State : Up Oper State : Up

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

MTU : 1514 Def. Mesh VC Id : 1100
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

*A:R1# show service id 600 base

-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sdp:5:1100 S(10.10.10.5) Spok 0 1556 Up Up
===============================================================================

115/122
Lab 9 IPv4 VPRNs

Enabling the Provider Core for MPLS

This lab requires configuring the provider core (which consists only of PE routers) for MPLS support. The
port facing the customer will be reconfigured as a service port, therefore the interface must be
deleted and the port mode changed to access.

Configuring the loopback interfaces on the CE routers - The configuration below is for R9-CE1

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

*A:R9# configure router interface Blue_Site_1
*A:R9>config>router>if$ address 10.10.1.1/24
*A:R9>config>router>if$ loopback
*A:R9>config>router>if$ exit

Configuring MP-BGP as the PE to PE Protocol

This lab will establish MP-BGP peering between PE’s. A full mesh of MP-BGP must be established in the
provider core to ensure propagation of VPRN routes. The peer sessions across the provider core should
always be established between system addresses.

The configuration below is for R5-PE1.

#------------------------------------------
# "Router (Network Side) Configuration"
#------------------------------------------
configure
router
autonomous-system 64496

*A:R5>config>router>bgp# info
----------------------------------------------
family vpn-ipv4
group "MP-iBGP"
peer-as 64496
neighbor 10.10.10.6
exit
neighbor 10.10.10.7
exit
neighbor 10.10.10.8
exit
exit
----------------------------------------------

Enabling the VPRN Service on the PE

This lab requires configuring the customer description and VPRN service. The router-ID, route-
distinguisher, and Route Target need to be defined for each customer VPRN of the PE. An interface will
be defined in the VPRN service context using the SAP facing the local CE.

The configuration below is for R5-PE1.

#------------------------------------------
# "Service Configuration"
#------------------------------------------

Alcatel-Lucent Services Architecture Lab Guide v 3.2 | All rights reserved © 2012 Alcatel-Lucent 116/122
configure
service
customer 110 create
description "VPRN Service for Customer Blue"
contact "Administrator"
phone "1-888-555-1212"
exit
vprn 110 customer 110 create
description "VPRN Service for Customer Blue"
router-id 10.10.10.5
autonomous-system 64496

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

route-distinguisher 64496:110
vrf-target target:64496:110
auto-bind ldp
interface "PE1_to_CE1" create
description "Customer_Blue_Site_1"
address 10.5.9.5/24
sap 1/1/2:110 create
exit
exit
no shutdown
exit all

PE BGP Configuration

BGP will be enabled between the PE and the CE. Route policy must be defined to enable the exchange
of routes on the PE from MP-BGP to BGP.

The configuration below is for R5-PE1.

*A:R5# configure service vprn 110 shutdown

# "Policy Configuration"
#------------------------------------------
configure
router
policy-options
begin
policy-statement "MPBGP-BGP"
entry 10
from
protocol bgp-vpn
exit
to
protocol bgp
exit
action accept
exit
exit
exit
commit
exit all

*A:R5>config>service>vprn# bgp
*A:R5>config>service>vprn>bgp$ group to_CE1_Blue
*A:R5>config>service>vprn>bgp>group$ export "MPBGP-BGP"
*A:R5>config>service>vprn>bgp>group$ neighbor 10.5.9.9

117/122
*A:R5>config>service>vprn>bgp>group>neighbor$ peer-as 64497
*A:R5>config>service>vprn>bgp>group>neighbor$ exit
*A:R5>config>service>vprn>bgp>group# exit
*A:R5>config>service>vprn>bgp# exit all
*A:R5# configure service vprn 110 no shutdown

CE BGP Configuration

This lab is performed on the CE.BGP is enabled between the PE and the CE. Route policy will be
defined to enable the exchange of routes on the CE between the directly connected interfaces and
BGP.

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

The configuration below is for R9-CE1.

"Policy Configuration"
--------------------------------------------------
policy-options
begin
prefix-list "prefixBlue"
prefix 10.10.1.0/24 exact
exit
policy-statement "exportBlue"
entry 10
from
prefix-list "prefixBlue"
exit
action accept
exit
exit
default-action reject
exit
exit

------------------------------------------
*A:R9# configure router autonomous-system 64497
------------------------------------------

*A:R9# configure router interface to_PE1

*A:R9>config>router>if$ address 10.5.9.9/24
*A:R9>config>router>if$ port 1/1/2:110
*A:R9>config>router>if$ exit all

"BGP Configuration"
------------------------------------------
*A:R9# configure router bgp
*A:R9>config>router>bgp$ group to_PE1
*A:R9>config>router>bgp>group$ peer-as 64496
*A:R9>config>router>bgp>group$ neighbor 10.5.9.5
*A:R9>config>router>bgp>group>neighbor$ export "exportBlue"
*A:R9>config>router>bgp>group>neighbor$ exit all

Pre-Requisites Configuration

A:R9>config>router# info
#--------------------------------------------------
interface "BlueSite1"
loopback
ipv6
address 2001:DB8:1::1/48

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

exit
exit
interface "Blue_Site_1"
address 10.10.1.1/24
loopback
exit
interface "system"
address 10.10.10.9/32
ipv6
address 2001:DB8::37/128
exit
exit
interface "to_PE1"
address 10.5.9.9/24
port 1/1/2:110
ipv6
address 2001:DB8:11::1/64
exit
exit
autonomous-system 64497
#--------------------------------------------------

PE IPv6 Configuration

*A:R5>config>router# info
----------------------------------------------
echo "IP Configuration"
#--------------------------------------------------
interface "system"
address 10.10.10.5/32
ipv6
address 2001:DB8::36/128
exit
exit

CE BGP Configuration

*A:R9>config>router>bgp# info
----------------------------------------------
group "to_PE1"
family ipv6
peer-as 64496
neighbor 10.5.9.5
export "exportBlue"
exit

119/122
neighbor 2001:DB8:11::2
export "direct_to_bgp"
exit
exit
----------------------------------------------

echo "Policy Configuration"

#--------------------------------------------------
policy-options
begin
policy-statement "direct_to_bgp"

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

entry 10
from
protocol direct
exit
to
protocol bgp
exit
action accept
exit
exit
exit
commit
exit
#--------------------------------------------------

PE VPRN Configuration

A:R5>config>service>vprn# info
----------------------------------------------
description "Customer_Blue"
router-id 10.10.10.5
autonomous-system 64496
route-distinguisher 64496:110
auto-bind ldp
vrf-target target:64496:110
interface "PE1_to_CE1" create
description "Customer_BlueSite1"
address 10.5.9.5/24
ipv6
address 2001:db8:11::2/64
exit
sap 1/1/2:110 create
exit
exit
no shutdown
----------------------------------------------

PE BGP Configuration

A:R5>config>service>vprn>bgp# info
----------------------------------------------
group "to_CE1"
family ipv6
export "MPBGP-BGP"
neighbor 10.5.9.9
peer-as 64497

*A:R5>config>router>bgp# info
----------------------------------------------
group "MP-BGP"
family vpn-ipv4 vpn-ipv6
peer-as 64496

Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute

neighbor 10.10.10.6
exit
neighbor 10.10.10.7
exit
neighbor 10.10.10.8
exit
exit
----------------------------------------------

121/122
Alcatel-Lucent Confidential for Internal Use ONLY - Do Not Distribute
http://www.alcatel-lucent.com/src

Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2-1
100% (1)
Alcatel-Lucent Multiprotocol Label Switching Lab Guide v2-1
104 pages
NRSII Lab Workshop A OSPF
No ratings yet
NRSII Lab Workshop A OSPF
92 pages
SRA LabExam 1
No ratings yet
SRA LabExam 1
10 pages
Alcatel-Lucent Services Lab Guide v3-1
No ratings yet
Alcatel-Lucent Services Lab Guide v3-1
128 pages
TER36065SROS Basic Service Router Troubleshooting Student Lab Guide PDF
No ratings yet
TER36065SROS Basic Service Router Troubleshooting Student Lab Guide PDF
126 pages
Ank 157q
No ratings yet
Ank 157q
72 pages
Ctual4 Est: Actual4test - Actual Test Exam Dumps-Pass For IT Exams
No ratings yet
Ctual4 Est: Actual4test - Actual Test Exam Dumps-Pass For IT Exams
6 pages
Alcatel-Lucent Test4prep 4A0-104 v2019-03-12 by Elwell 178q
No ratings yet
Alcatel-Lucent Test4prep 4A0-104 v2019-03-12 by Elwell 178q
88 pages
VPRN Protocols & Configurations Guide
No ratings yet
VPRN Protocols & Configurations Guide
27 pages
Evpn Architecture Guide
No ratings yet
Evpn Architecture Guide
48 pages
Alcatel Lucent - Pass4sure.4a0 101.v2015!04!05.by - Granville.335q
No ratings yet
Alcatel Lucent - Pass4sure.4a0 101.v2015!04!05.by - Granville.335q
160 pages
JN0 643 Q&A Troytec
No ratings yet
JN0 643 Q&A Troytec
157 pages
Lead2Pass 400-101 827 Questions
100% (2)
Lead2Pass 400-101 827 Questions
328 pages
DCI Using VXLAN EVPN Multi-Site W/ VPC BGW
No ratings yet
DCI Using VXLAN EVPN Multi-Site W/ VPC BGW
16 pages
VyOS Certification Blueprint
No ratings yet
VyOS Certification Blueprint
3 pages
B. False: (Right Answers)
No ratings yet
B. False: (Right Answers)
59 pages
LDP VPLS Using BGP-Auto Discovery
No ratings yet
LDP VPLS Using BGP-Auto Discovery
21 pages
Nokia 4A0-103
No ratings yet
Nokia 4A0-103
132 pages
Mellanox SN2100 - Hardware
No ratings yet
Mellanox SN2100 - Hardware
112 pages
JN0-681 Exam Questions & Answers
No ratings yet
JN0-681 Exam Questions & Answers
35 pages
Nokia 4A0-102
No ratings yet
Nokia 4A0-102
103 pages
JN0-647 Exam Dumps for Professionals
No ratings yet
JN0-647 Exam Dumps for Professionals
11 pages
JRE-12.b SG
No ratings yet
JRE-12.b SG
174 pages
Nokia 4A0-104
No ratings yet
Nokia 4A0-104
134 pages
Juniper Switching Update: Jose J Navarro T Sr. Systems Engineer - Caribbean November 2014
No ratings yet
Juniper Switching Update: Jose J Navarro T Sr. Systems Engineer - Caribbean November 2014
34 pages
Nokia 4A0-100
No ratings yet
Nokia 4A0-100
155 pages
B Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide 7x Chapter 0100
No ratings yet
B Cisco Nexus 9000 Series NX-OS VXLAN Configuration Guide 7x Chapter 0100
44 pages
Nokia CMD
No ratings yet
Nokia CMD
29 pages
Elastic MPLS: Rationale and Benefits
No ratings yet
Elastic MPLS: Rationale and Benefits
8 pages
IS-IS Routing Process: Update Decision Q W e
No ratings yet
IS-IS Routing Process: Update Decision Q W e
1 page
Nokia EVPN Services Lab Guide v1.0 Liberado
No ratings yet
Nokia EVPN Services Lab Guide v1.0 Liberado
166 pages
Deploying IP Anycast
No ratings yet
Deploying IP Anycast
78 pages
Wireless Cloud Element: Product Description
No ratings yet
Wireless Cloud Element: Product Description
34 pages
Juniper Datasheet MX5!10!40-80
No ratings yet
Juniper Datasheet MX5!10!40-80
4 pages
Alcatel-Lucent 4A0-100 Exam Guide
No ratings yet
Alcatel-Lucent 4A0-100 Exam Guide
62 pages
Juniper 400G Portfolio: Satish Surapaneni, Director, Product Management Dmitry Shokarev, Principal Product Manager
No ratings yet
Juniper 400G Portfolio: Satish Surapaneni, Director, Product Management Dmitry Shokarev, Principal Product Manager
30 pages
DO NorthStarController2
No ratings yet
DO NorthStarController2
78 pages
Versa Ds Flex VNF 01 5
No ratings yet
Versa Ds Flex VNF 01 5
4 pages
Ethernet Services for Network Engineers
No ratings yet
Ethernet Services for Network Engineers
15 pages
Cisco 4500 Config Guide
No ratings yet
Cisco 4500 Config Guide
1,120 pages
350 501 Demo
No ratings yet
350 501 Demo
9 pages
Ethernet VPN (Evpn) : Overlay Networks For Ethernet Services
No ratings yet
Ethernet VPN (Evpn) : Overlay Networks For Ethernet Services
34 pages
JSEC 12.a-R LD PDF
No ratings yet
JSEC 12.a-R LD PDF
16 pages
L2VPN Services Over Segment Routing For Traffic Engineering Policy
No ratings yet
L2VPN Services Over Segment Routing For Traffic Engineering Policy
50 pages
Alcatel Lucent - Braindumps.4a0 100.v2019!01!16.by - Joseph.143q
No ratings yet
Alcatel Lucent - Braindumps.4a0 100.v2019!01!16.by - Joseph.143q
63 pages
Mpls l2vpn VLL
No ratings yet
Mpls l2vpn VLL
24 pages
04-Chapter4 OSPF Configuration
No ratings yet
04-Chapter4 OSPF Configuration
70 pages
4a0 100
No ratings yet
4a0 100
24 pages
Compal Confidential: Broadwell M/B Schematics Document
No ratings yet
Compal Confidential: Broadwell M/B Schematics Document
61 pages
ExtremeXOS 21.1.5-Patch1-2 RelNotes
No ratings yet
ExtremeXOS 21.1.5-Patch1-2 RelNotes
126 pages
Alcatel-Lucent PracticeTest 4A0-104 v2018-11-11 by Boone 173q
No ratings yet
Alcatel-Lucent PracticeTest 4A0-104 v2018-11-11 by Boone 173q
88 pages
02 Huawei Campus Switch Products Pre-Sales Training - 2021
No ratings yet
02 Huawei Campus Switch Products Pre-Sales Training - 2021
98 pages
Services Architecture v3.2 Student Guide Download
100% (1)
Services Architecture v3.2 Student Guide Download
430 pages
Answer: C: Exam Name: Exam Type: Exam Code: Total Questions
No ratings yet
Answer: C: Exam Name: Exam Type: Exam Code: Total Questions
4 pages
Qfx5200 Deepdive TDM Presentation
No ratings yet
Qfx5200 Deepdive TDM Presentation
51 pages
Huawei H12-891 - V1 0 v2022-07-06 q191
No ratings yet
Huawei H12-891 - V1 0 v2022-07-06 q191
55 pages
CCNP SP Adv Route Configurations
No ratings yet
CCNP SP Adv Route Configurations
41 pages
Huawei H12 891 V1.0 ENU Exam Questions
No ratings yet
Huawei H12 891 V1.0 ENU Exam Questions
17 pages
Datacenter Scaling with Dragonfly+
No ratings yet
Datacenter Scaling with Dragonfly+
9 pages
Alcatel-Lucent Interior Routing Protocols Lab Guide: Revision 2.3 Sep 22nd, 2010
No ratings yet
Alcatel-Lucent Interior Routing Protocols Lab Guide: Revision 2.3 Sep 22nd, 2010
64 pages
Services Architecture Release Notes - v3.2 Download
No ratings yet
Services Architecture Release Notes - v3.2 Download
4 pages
Alcatel-Lucent ISAM Shelf Types Guide
100% (1)
Alcatel-Lucent ISAM Shelf Types Guide
79 pages
TAC03001-HO06-I1.3 5520 AMS Intro
No ratings yet
TAC03001-HO06-I1.3 5520 AMS Intro
45 pages
TAC03001-HO23-I1.4 STP Tech
No ratings yet
TAC03001-HO23-I1.4 STP Tech
31 pages
Toggl Time Tracking Guide
No ratings yet
Toggl Time Tracking Guide
151 pages
PowerEdge T430 Spec Sheet
No ratings yet
PowerEdge T430 Spec Sheet
2 pages
220-1102 Updated Dumps - CompTIA A+ Core 2 Exam
100% (3)
220-1102 Updated Dumps - CompTIA A+ Core 2 Exam
61 pages
DevOps & Cloud Engineer Expertise
No ratings yet
DevOps & Cloud Engineer Expertise
5 pages
Unit - I Iot
No ratings yet
Unit - I Iot
36 pages
All TCP & UDP Protocols and Ports
No ratings yet
All TCP & UDP Protocols and Ports
35 pages
Cusat Btech Ece S8 Syllabus
No ratings yet
Cusat Btech Ece S8 Syllabus
4 pages
Secret Code Fujitsu
No ratings yet
Secret Code Fujitsu
6 pages
Data Transfer, IP and DNS
No ratings yet
Data Transfer, IP and DNS
4 pages
Senso Control
No ratings yet
Senso Control
80 pages
Website Security 101: Real-World Examples, Tools & Techniques For Protecting & Securing Websites
100% (1)
Website Security 101: Real-World Examples, Tools & Techniques For Protecting & Securing Websites
12 pages
Manual IOL Master EN PDF
No ratings yet
Manual IOL Master EN PDF
8 pages
Cisco CP 8945 Phone - Cleaned
No ratings yet
Cisco CP 8945 Phone - Cleaned
5 pages
Network Topology
No ratings yet
Network Topology
30 pages
40.reefer Container Monitoring System (Zigbee-2019)
No ratings yet
40.reefer Container Monitoring System (Zigbee-2019)
6 pages
Cyclades TS v3.0.0-2b Release Notes
No ratings yet
Cyclades TS v3.0.0-2b Release Notes
4 pages
Intro to ICT: Course Syllabus
No ratings yet
Intro to ICT: Course Syllabus
5 pages
Alteryx 160923184340
No ratings yet
Alteryx 160923184340
25 pages
NC 2 CSS DETAILED GUIDE - Simplified
No ratings yet
NC 2 CSS DETAILED GUIDE - Simplified
3 pages
PS404 4PMBGW
No ratings yet
PS404 4PMBGW
2 pages
XE101
No ratings yet
XE101
1 page
SES-92 Slave Protocol: Reference Manual
No ratings yet
SES-92 Slave Protocol: Reference Manual
17 pages
System Architecture Auto Control Panel r000
No ratings yet
System Architecture Auto Control Panel r000
1 page
Mishael Lim CSS Quarter 3 Module 1 LO1
No ratings yet
Mishael Lim CSS Quarter 3 Module 1 LO1
15 pages
Computer Science MCQs: Essentials
100% (1)
Computer Science MCQs: Essentials
14 pages
Self-Supervised Learning: Pretext Tasks
No ratings yet
Self-Supervised Learning: Pretext Tasks
3 pages
Descarga de Scribd
No ratings yet
Descarga de Scribd
4 pages
Internet Basics Powerpoint
100% (1)
Internet Basics Powerpoint
20 pages
CV - Nguyen Ngoc Chau
No ratings yet
CV - Nguyen Ngoc Chau
2 pages
Physics Project 1
No ratings yet
Physics Project 1
26 pages