Laboratorios MPLS

CONFIGURANDO REDES MPLS
LABORATORIOS
Laboratorio 1: Estableciendo el CORE IGP - Ambiente de enrutamiento

OBJETIVO:
Implementar el IGP en el backbone del proveedor del servicio y establecer el
enrutamiento necesario, para ello utilizar los comandos necesarios.
Tareas:
1. Interconectar las interfaces de los routers
2. Configurar las interfaces con el direccionamiento establecido en el siguiente
diagrama:
3. Configurar OSPF en los Ps y PEs en el rea 0 y verificar la correcta

operacin en cada uno de los routers, todas las redes de backbone deberan
aparecer en las tablas de enrutamiento de todos los routers incluidas las
loopback.
Ejecutar el comando sh ip route en cada router
PE1#SH IP ROUTE
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
Laboratorio MPLS
o - ODR, P - periodic downloaded static route

Gateway of last resort is not set
O
C
O
C
O
O
O
10.0.0.0/29 is subnetted, 3 subnets

10.1.2.0 [110/3] via 10.1.1.1, 00:01:49, FastEthernet0/0
10.1.1.0 is directly connected, FastEthernet0/0
192.168.0.11 is directly connected, Loopback0
PE1#SH IP OSPF NEIGHbor

Neighbor ID
192.168.0.1
Pri State
1 FULL/DR
Dead Time Address

00:00:38 10.1.1.1
Interface
FastEthernet0/0
P1#SH IP ROUTE
O
C
C
O
O
C
O
P1#SH IP OSPF NEIGHbor
Neighbor ID
192.168.0.11
192.168.0.2
Pri State
Dead Time Address
1 FULL/BDR
00:00:31 10.1.1.2
1 FULL/BDR
00:00:32 10.1.0.2
Laboratorio MPLS
Interface
FastEthernet0/0
FastEthernet1/0
P2#SH IP ROUTE
C
O
C
O
O
O
C

P2#SH IP OSPF NEIGHBOR

Neighbor ID
192.168.0.12
192.168.0.1
Pri State
Dead Time Address
1 FULL/DR
00:00:37 10.1.2.2
1 FULL/DR
00:00:35 10.1.0.1
Interface
FastEthernet1/0
FastEthernet0/0
PE2#SH IP ROUTE
C
O
O
O

Laboratorio MPLS
C
O
O

PE2#SH IP OSPF NEIGHBOR

Neighbor ID
192.168.0.2
Pri State
1 FULL/DR
Laboratorio MPLS
Dead Time Address

00:00:38 10.1.2.1
Interface
FastEthernet0/0
Laboratorio 2: Estableciendo el CORE MPLS

OBJETIVO:
Utilizar los comandos necesarios para implementar MPLS en el backbone de la
red del proveedor de servicios.
La siguiente figura ilustra la tarea a cumplir:
Tareas:
1. Habilitar LDP en los routers PE
a. Habilitar CEF
b. Habilitar LDP sobre las subinterfaces que estn conectadas entre P y
PE
2. Habilitar LDP en los routers P
a. Habilitar CEF
b. Habilitar LDP sobre las subinterfaces que estn conectadas entre P P y P - PE
Laboratorio MPLS
Verificacin:
En cada uno de los routers verificar que las interfaces hayan sido configuradas
para usar LDP, ejecutar el comando
routerP#sh mpls interface
PE1#SH MPLS INTERFAces
Interface
IP
Tunnel Operational
FastEthernet0/0
Yes (ldp) No
Yes
P1#SH MPLS INTERFACES
Interface
IP
Tunnel Operational
FastEthernet0/0
Yes (ldp) No
Yes
FastEthernet1/0
Yes (ldp) No
Yes
P2#SH MPLS INTERFAces
Interface
IP
Tunnel Operational
FastEthernet0/0
Yes (ldp) No
Yes
FastEthernet1/0
Yes (ldp) No
Yes
PE2#SH MPLS INTERFACES
Interface
IP
Tunnel Operational
FastEthernet0/0
Yes (ldp) No
Yes
En cada uno de los routers verificar el establecimiento de la relacin de vecinos

LDP, para ello ejecutar los comandos
routerP#show mpls ldp discovery
PE1#SH MPLS LDP DISCOVERY

Local LDP Identifier:
192.168.0.11:0
Discovery Sources:
Interfaces:
FastEthernet0/0 (ldp): xmit/recv
LDP Id: 192.168.0.1:0
P1#SH MPLS LDP DISCOVERY
192.168.0.1:0
Laboratorio MPLS
Discovery Sources:
Interfaces:
LDP Id: 192.168.0.11:0
LDP Id: 192.168.0.2:0
P2#SH MPLS LDP DISCOVERY
192.168.0.2:0
Discovery Sources:
Interfaces:
LDP Id: 192.168.0.1:0
LDP Id: 192.168.0.12:0
PE2#SH MPLS LDP DISCOVERY

192.168.0.12:0
Discovery Sources:
Interfaces:
LDP Id: 192.168.0.2:0
routerP#show mpls ldp neighbor
PE1#SH MPLS LDP NEIGHBOR

Peer LDP Ident: 192.168.0.1:0; Local LDP Ident 192.168.0.11:0
TCP connection: 192.168.0.1.646 - 192.168.0.11.64084
State: Oper; Msgs sent/rcvd: 16/16; Downstream
Up time: 00:05:32
LDP discovery sources:
FastEthernet0/0, Src IP addr: 10.1.1.1
Addresses bound to peer LDP Ident:
10.1.1.1
10.1.0.1
192.168.0.1
P1#SH MPLS LDP NEIGHBOR

TCP connection: 192.168.0.11.64084 - 192.168.0.1.646
Laboratorio MPLS

Up time: 00:07:50
10.1.1.2
192.168.0.11
TCP connection: 192.168.0.2.19048 - 192.168.0.1.646
Up time: 00:04:47
10.1.0.2
10.1.2.1
192.168.0.2
P2#SH MPLS LDP NEIGHBOR

TCP connection: 192.168.0.1.646 - 192.168.0.2.19048
Up time: 00:11:59
10.1.1.1
10.1.0.1
192.168.0.1
TCP connection: 192.168.0.12.19349 - 192.168.0.2.646
Up time: 00:11:38
10.1.2.2
192.168.0.12
PE2#SH MPLS LDP NEIGHBOR

TCP connection: 192.168.0.2.646 - 192.168.0.12.19349
Up time: 00:14:48
10.1.0.2
10.1.2.1
192.168.0.2
Laboratorio MPLS
En cada uno de los routers, verificar que el LDP haya asignado una etiqueta
para cada prefijo en la tabla de rutas, incluidas las subredes y loopbacks de los
otros routers de core.
routerPE#sh ip route
PE1#SH IP ROUTE
O
C
O
C
O
O
O

P1#SH IP ROUTE
O
C
C
O

Laboratorio MPLS
10
O
C
O

P2#SH IP ROUTE
C
O
C
O
O
O
C

PE2#SH IP ROUTE
C
O
O
O
C
O
O

Laboratorio MPLS
11
routerP#sh mpls ldp bindings

PE1#SH MPLS LDP BINDINGS
tib entry: 10.1.0.0/29, rev 6
local binding: tag: 17
remote binding: tsr: 192.168.0.1:0, tag: imp-null
tib entry: 10.1.1.0/29, rev 4
local binding: tag: imp-null
tib entry: 10.1.2.0/29, rev 2
remote binding: tsr: 192.168.0.1:0, tag: 16
tib entry: 192.168.0.1/32, rev 12
tib entry: 192.168.0.2/32, rev 14
tib entry: 192.168.0.11/32, rev 8
tib entry: 192.168.0.12/32, rev 10
P1#SH MPLS LDP BINDINGS

tib entry: 10.1.0.0/29, rev 6
tib entry: 10.1.1.0/29, rev 4
tib entry: 10.1.2.0/29, rev 2
tib entry: 192.168.0.1/32, rev 12
tib entry: 192.168.0.2/32, rev 14
Laboratorio MPLS
12

tib entry: 192.168.0.11/32, rev 8
tib entry: 192.168.0.12/32, rev 10
P2#SH MPLS LDP BINDINGS
tib entry: 10.1.0.0/29, rev 6
tib entry: 10.1.1.0/29, rev 4
tib entry: 10.1.2.0/29, rev 2
tib entry: 192.168.0.1/32, rev 12
tib entry: 192.168.0.2/32, rev 14
tib entry: 192.168.0.11/32, rev 8
tib entry: 192.168.0.12/32, rev 10
Laboratorio MPLS
13
PE2#SH MPLS LDP BINDINGS

tib entry: 10.1.0.0/29, rev 6
tib entry: 10.1.1.0/29, rev 4
tib entry: 10.1.2.0/29, rev 2
tib entry: 192.168.0.1/32, rev 12
tib entry: 192.168.0.2/32, rev 14
tib entry: 192.168.0.11/32, rev 8
tib entry: 192.168.0.12/32, rev 10
Realizar un traceroute desde el PE hacia la direccin de loopback del otro PE,

verificar que el resultado muestre las etiquetas asociadas
PE1#TRACERoute 192.168.0.12
Type escape sequence to abort.
Tracing the route to 192.168.0.12
1 10.1.1.1 [MPLS: Label 18 Exp 0] 92 msec 32 msec 16 msec
3 10.1.2.2 44 msec 24 msec *
3 10.1.1.2 16 msec 24 msec *
Laboratorio MPLS
14
3. Deshabilitar la Propagacin de TTL

a. Sobre los routers P y PE deshabilitar el MPLS TTL propagation
utilizando el comando:
PE y P(config) #no tag-switching ip propagate-ttl
Verificacin:
Realizar un traceroute desde el PE hacia la loopback del otro PE y anote el
resultado.
PE#traceroute .
1 10.1.2.2 24 msec 12 msec *
1 10.1.1.2 36 msec 12 msec *
Laboratorio MPLS
15
Laboratorio 3: Configurando Multiprotocol BGP
OBJETIVO:
Configurar MP-BGP entre los routers PE
La siguiente figura ilustra la tarea a cumplir:
Loop0
Loop0
130.1.1.0 /24
CE1
.2
AS 2
Loop0
172.1.1.0 /29
192.168.0.11/32
.2
Loop0
Loop0
192.168.0.1/32
192.168.0.2/32
192.168.0.12/32
.1
172.1.2.0 /29
.1
10.1.1.0 /29
PE1
CE2
Loop0
.2
.1
10.1.2.0 /29
.2
.1
.1
10.1.0.0 /29
P1
.2
PE2
P2
iBGP
Tareas:
1. Activar el proceso BGP en los routers usando el AS 2, deshabilite la
caracterstica de auto summary.
2. Activar las sesiones VPNv4 BGP entre los routers PE, deshabilite el auto
summary
Verificacin:
Verificar la informacin de los vecinos BGP y asegurar que las sesiones BGP
hayan sido establecidas entre los dos routers PE, ejecutar el comando:
Laboratorio MPLS
16
PE#sh ip bgp summary

PE1#SH IP BGP SUMMARY
BGP router identifier 192.168.0.11, local AS number 2
BGP table version is 1, main routing table version 1
Neighbor
V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.0.12 4 2
5
5
1
0 0
00:02:28
0
PE2#SH IP BGP SUMM

Neighbor
192.168.0.11 4 2
6
6
1
0 0
00:03:39
0
PE#sh ip bgp neighbor

PE1#SH IP BGP NEIGHBOR
BGP neighbor is 192.168.0.12, remote AS 2, internal link
BGP version 4, remote router ID 192.168.0.12
BGP state = Established, up for 00:05:00
Last read 00:00:59, last write 00:00:59, hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
Route refresh: advertised and received(old & new)
Address family IPv4 Unicast: advertised and received
Address family VPNv4 Unicast: advertised and received
Message statistics:
InQ depth is 0
OutQ depth is 0
Sent
Rcvd
Opens:
1
1
Notifications:
0
0
Updates:
0
0
Keepalives:
6
6
Route Refresh:
0
0
Total:
7
7
Default minimum time between advertisement runs is 0 seconds
For address family: IPv4 Unicast
BGP table version 1, neighbor version 1/0
Output queue size: 0
Index 1, Offset 0, Mask 0x2
Laboratorio MPLS
17
1 update-group member
Sent
Rcvd
Prefix activity:
------Prefixes Current:
0
0
Prefixes Total:
0
0
Implicit Withdraw:
0
0
Explicit Withdraw:
0
0
Used as bestpath:
n/a
0
Used as multipath:
n/a
0
Outbound Inbound
Local Policy Denied Prefixes: -------- ------Total:
0
0
Number of NLRIs in the update sent: max 0, min 0
For address family: VPNv4 Unicast
NEXT_HOP is always this router
Community attribute sent to this neighbor
Sent
Rcvd
Prefix activity:
0
0
Prefixes Total:
0
0
Implicit Withdraw:
0
0
Explicit Withdraw:
0
0
Used as bestpath:
n/a
0
Used as multipath:
n/a
0
Outbound Inbound
0
0
Connections established 1; dropped 0
Last reset never
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Connection is ECN Disabled, Mininum incoming TTL 0, Outgoing TTL 255
Local host: 192.168.0.11, Local port: 61796
Foreign host: 192.168.0.12, Foreign port: 179
Connection tableid (VRF): 0
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x7455DC):
Laboratorio MPLS
18
Timer
Starts
Retrans
9
TimeWait
0
AckHold
7
SendWnd
0
KeepAlive
0
GiveUp
0
PmtuAger
0
DeadWait
0
Linger
0
ProcessQ
0
Wakeups
0
0
6
0
0
0
0
0
0
0
Next
0x0
0x0
0x0
0x0
0x0
0x0
0x0
0x0
0x0
0x0
iss: 3418116995 snduna: 3418117182 sndnxt: 3418117182 sndwnd: 16198

irs: 3516328250 rcvnxt: 3516328437 rcvwnd: 16198 delrcvwnd: 186
SRTT: 222 ms, RTTO: 896 ms, RTV: 674 ms, KRTT: 0 ms
minRTT: 12 ms, maxRTT: 512 ms, ACK hold: 200 ms
Status Flags: active open
Option Flags: nagle
IP Precedence value : 6
Datagrams (max data segment is 536 bytes):
Rcvd: 10 (out of order: 0), with data: 7, total data bytes: 186
Sent: 16 (retransmit: 0, fastretransmit: 0, partialack: 0, Second Congestion: 0), with data: 8,
total data bytes: 186
Packets received in fast path: 0, fast processed: 0, slow path: 0
fast lock acquisition failures: 0, slow path: 0
PE2#SH IP BGP NEIGHBOR

BGP neighbor is 192.168.0.11, remote AS 2, internal link
BGP version 4, remote router ID 192.168.0.11
BGP state = Established, up for 00:05:57
Last read 00:00:57, last write 00:00:57, hold time is 180, keepalive interval is 60 seconds
Neighbor capabilities:
Route refresh: advertised and received(old & new)
Address family IPv4 Unicast: advertised and received
Address family VPNv4 Unicast: advertised and received
Message statistics:
InQ depth is 0
OutQ depth is 0
Sent
Rcvd
Opens:
1
1
Notifications: 0
0
Updates:
0
0
Laboratorio MPLS
19
Keepalives:
7
7
Route Refresh: 0
0
Total:
8
8
Default minimum time between advertisement runs is 0 seconds
For address family: IPv4 Unicast
Sent
Rcvd
Prefix activity:
0
0
Prefixes Total:
0
0
Implicit Withdraw:
0
0
Explicit Withdraw:
0
0
Used as bestpath:
n/a
0
Used as multipath: n/a
0
Outbound Inbound
0
0
For address family: VPNv4 Unicast
NEXT_HOP is always this router
Community attribute sent to this neighbor
Sent
Rcvd
Prefix activity:
0
0
Prefixes Total:
0
0
Implicit Withdraw: 0
0
Explicit Withdraw: 0
0
Used as bestpath:
n/a
0
Used as multipath: n/a
0
Outbound Inbound
0
0
Connections established 1; dropped 0
Last reset never
Laboratorio MPLS
20
Connection state is ESTAB, I/O status: 1, unread input bytes: 0

Connection is ECN Disabled, Mininum incoming TTL 0, Outgoing TTL 255
Local host: 192.168.0.12, Local port: 179
Foreign host: 192.168.0.11, Foreign port: 61796
Connection tableid (VRF): 0
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x2CEDA0):
Timer
Starts Wakeups
Next
Retrans
8
0
0x0
TimeWait
0
0
0x0
AckHold
8
2
0x0
SendWnd
0
0
0x0
KeepAlive
0
0
0x0
GiveUp
0
0
0x0
PmtuAger
0
0
0x0
DeadWait
0
0
0x0
Linger
0
0
0x0
ProcessQ
0
0
0x0
iss: 3516328250 snduna: 3516328437 sndnxt: 3516328437 sndwnd: 16198
irs: 3418116995 rcvnxt: 3418117182 rcvwnd: 16198 delrcvwnd: 186
SRTT: 197 ms, RTTO: 984 ms, RTV: 787 ms, KRTT: 0 ms
minRTT: 44 ms, maxRTT: 300 ms, ACK hold: 200 ms
Status Flags: passive open, gen tcbs
Option Flags: nagle
IP Precedence value : 6
Datagrams (max data segment is 536 bytes):
Rcvd: 18 (out of order: 0), with data: 9, total data bytes: 205
Sent: 11 (retransmit: 0, fastretransmit: 0, partialack: 0, Second Congestion: 0), with data: 8,
total data bytes: 205
Packets received in fast path: 0, fast processed: 0, slow path: 0
fast lock acquisition failures: 0, slow path: 0
Laboratorio MPLS
21
Laboratorio 4: Configurando las tablas de enrutamiento y envo VRFs

OBJETIVO:
Establecer una VPN simple para comunicar a un cliente utilizando rutas
estticas
Tareas:
1. Disee su propia VPN, para ello escoja la numeracin de RD y RT .
2. Crear la VRF sobre los routers PE y asciela a la interfaz PE-CE en la
apropiada VRF, usar nombres simples en las VRFs
3. El cliente est usando direccionamiento esttico como IGP
4. Configure la redistribucin de las rutas estticas dentro del BGP con el
comando address-family ipv4 vrf [nombre de la vrf]
Verificacin:
Verifique que este correctamente configurado la VRF con el comando show ip
vrf detail
PE#sh ip vrf detail
PE1#sh ip vrf detail
VRF cliente1; default RD 2:1; default VPNID <not set>
Interfaces:
Fa1/0
Connected addresses are not in global routing table
Export VPN route-target communities
RT:2:1
Import VPN route-target communities
RT:2:1
No import route-map
No export route-map
VRF label distribution protocol: not configured
VRF label allocation mode: per-prefix
PE2#sh ip vrf detail

VRF cliente1; default RD 2:1; default VPNID <not set>
Interfaces:
Fa1/0
Connected addresses are not in global routing table
Export VPN route-target communities
Laboratorio MPLS
22
RT:2:1
Import VPN route-target communities
RT:2:1
No import route-map
No export route-map
VRF label distribution protocol: not configured
VRF label allocation mode: per-prefix
Verifique que protocolo est corriendo en la VRF con el comando show ip

protocol vrf
PE#sh ip protocol vrf [nombre de la vrf]
PE1#sh ip protocols vrf cliente1

Routing Protocol is "bgp 2"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
IGP synchronization is disabled
Automatic route summarization is disabled
Redistributing: static
Maximum path: 1
Routing Information Sources:
Gateway
Distance
Last Update
192.168.0.12
200
00:02:53
Distance: external 20 internal 200 local 200
PE2#sh ip protocols vrf cliente1

Routing Protocol is "bgp 2"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
IGP synchronization is disabled
Automatic route summarization is disabled
Redistributing: static
Maximum path: 1
Routing Information Sources:
Gateway
Distance
Last Update
192.168.0.11
200
00:06:31
Distance: external 20 internal 200 local 200
Laboratorio MPLS
23
Verifique la tabla de rutas en la VRF con el comando show ip route vrf

PE#sh ip route vrf [nombre de la vrf]
PE1#sh ip route vrf cliente1

Routing Table: cliente1
140.1.2.0 [200/0] via 192.168.0.12, 00:04:31
C
S
130.1.1.0 [1/0] via 172.1.1.2
B
PE2#sh ip route vrf cliente1

Routing Table: cliente1
S
140.1.2.0 [1/0] via 172.1.2.2
C
B
130.1.1.0 [200/0] via 192.168.0.11, 00:08:01
Laboratorio MPLS
24
Use el comando show ip bgp vpnv4 vrf para mostrar la tabla de rutas asociada
con la VRF
PE#show ip bgp vpnv4 vrf [nombre de la vrf]
PE1#sh ip bgp vpnv4 vrf cliente1

BGP table version is 5, local router ID is 192.168.0.11
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network
Next Hop
Metric LocPrf Weight Path
Route Distinguisher: 2:1 (default for vrf cliente1)
*> 130.1.1.0/24 172.1.1.2
0
32768 ?
*>i140.1.2.0/24 192.168.0.12
0 100
0?
PE2#sh ip bgp vpnv4 vrf cliente1

Network
Next Hop
*>i130.1.1.0/24 192.168.0.11
0 100
0?
*> 140.1.2.0/24 172.1.2.2
0
32768 ?
Use el comando sh ip route en los routers PE para verificar que las rutas del
cliente no se encuentran en la tabla global de rutas
PE#sh ip route
PE1#sh ip route
Laboratorio MPLS
25
O
C
O
C
O
O
O

192.168.0.2 [110/3] via 10.1.1.1, 01:13:01, FastEtherne
PE2#sh ip route
C
O
O
O
C
O
O

Use ping y trace sobre los routers PE para verificar que no se puede alcanzar a
las redes de los clientes desde el espacio de direccionamiento global.
PE#ping 130.1.1.1
PE1#ping 130.1.1.1
Sending 5, 100-byte ICMP Echos to 130.1.1.1, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Laboratorio MPLS
26
PE2#ping 140.1.2.1
.....
Success rate is 0 percent (0/5)
Use el comando ping vrf sobre los routers PE para verificar que se puede
alcanzar a las redes de los clientes.
PE#ping vrf [nombre de la vrf] 130.1.1.1
PE1#ping vrf cliente1 130.1.1.1

!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/19/36 ms
PE#ping vrf [nombre de la vrf] 140.1.2.1

!!!!!
Laboratorio MPLS
27
Laboratorio 5: Configurando EIGRP entre PE y CE
OBJETIVO:
Establecer el protocolo de enrutamiento EIGRP entre el router CE y el router PE
Tareas:
1. Configure EIGRP en los routers CE, con el AS 10
2. Sobre el router PE, configure la redistribucin de EIGRP en BGP con el
comando address-family ipv4 vrf [vrf name], configure la mtrica en 1.
3. Sobre el router PE configure la redistribucin de BGP en EIGRP con el
comando address-family ipv4 vrf [vrf name], deshabilite el auto summary
del EIGRP
Verificacin:
Verifique que el EIGRP ha sido activado sobre las interfaces apropiadas para
ello ejecute el siguiente comando sobre el router PE :
PE#sh ip eigrp vrf [ nombre vrf ] interface
Laboratorio MPLS
28
PE1#sh ip eigrp vrf cliente1 interfaces

IP-EIGRP interfaces for process 10
Interface
Fa1/0
Xmit Queue Mean Pacing Time Multicast Pending

Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
1
0/0
719
0/1
3584
0
PE2#sh ip eigrp vrf cliente1 interfaces

IP-EIGRP interfaces for process 10
Interface
Fa1/0
Xmit Queue Mean Pacing Time Multicast Pending

Peers Un/Reliable SRTT Un/Reliable Flow Timer Routes
1
0/0
274
0/1
1348
0
Verifique que las adyacencias hayan sido establecidas entre el CE y PE

PE#sh ip eigrp vrf [vrf name] neighbor
PE1#sh ip eigrp vrf cliente1 neighbors

IP-EIGRP neighbors for process 10
H Address
Interface
Hold Uptime SRTT RTO Q Seq
(sec)
(ms) Cnt
Num
0 172.1.1.2
Fa1/0
11
00:10:27 719 4314 0 2
PE2#sh ip eigrp vrf cliente1 neighbor

IP-EIGRP neighbors for process 10
H Address
Interface
Hold Uptime SRTT RTO Q Seq
(sec)
(ms)
Cnt Num
0 172.1.2.2
Fa1/0
10
00:22:47 274 1644 0 4
Verifique la base topolgica de EIGRP sobre los routers CE

PE#sh ip eigrp vrf [vrf name] topology
PE1#sh ip eigrp vrf cliente1 topology
IP-EIGRP Topology Table for AS(10)/ID(172.1.1.1) Routing Table: cliente1
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
Laboratorio MPLS
29
P 130.1.1.0/24, 1 successors, FD is 156160

via 172.1.1.2 (156160/128256), FastEthernet1/0
via VPNv4 Sourced (156160/0)
via Connected, FastEthernet1/0
PE2#sh ip eigrp vrf cliente1 topology

IP-EIGRP Topology Table for AS(10)/ID(172.1.2.1) Routing Table: cliente1
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
via 172.1.2.2 (156160/128256), FastEthernet1/0
via Connected, FastEthernet1/0
Verifique la conectividad a travs de la VPN usando los comandos ping y trace

sobre los routers CE y ping vrf y trace vrf sobre los routers PE
CE#ping .
CE2#ping 130.1.1.1
!!!!!
Laboratorio MPLS
30
PE#ping vrf [vrf name] ..

!!!!!

!!!!!
Laboratorio MPLS
31
Laboratorio 6: Configurando OSPF entre PE y CE
OBJETIVO:
Establecer el protocolo de enrutamiento OSPF entre el router CE y el router PE
Tareas:
1. Configure OSPF en los routers CE, con el process ID de 20
2. Configure OSPF en la VRF sobre los routers PE usando el comando router
ospf vrf. Use OSPF Area 0 sobre el enlace PE-CE.
3. Configure la redistribucin desde OSPF a MP-BGP usando el comando
redistribute ospf en el address family de la VRF.
4. Configure la redistribucin de MP-BGP a OSPF usando el comando
redistribute bgp subnets en la configuracin de OSPF
Verificacin:
Verifique la adyacencia sobre los routers PE usando el comando show ip ospf
neighbor :
PE#sh ip ospf neighbor
Laboratorio MPLS
32
PE1#sh ip ospf neighbor

Neighbor ID Pri State
192.168.0.1
1 FULL/DR
130.1.1.1
1 FULL/DR
Dead Time Address

00:00:37 10.1.1.1
00:00:39 172.1.1.2
Interface
FastEthernet0/0
FastEthernet1/0
Dead Time Address

00:00:37 10.1.2.1
00:00:34 172.1.2.2
Interface
FastEthernet0/0
FastEthernet1/0
PE2#sh ip ospf neigh

Neighbor ID Pri State
192.168.0.2
1 FULL/DR
140.1.2.1
1 FULL/DR
Verifique el OSPF topology database sobre los routers PE:

PE#sh ip ospf database
PE1#sh ip ospf data
OSPF Router with ID (192.168.0.11) (Process ID 1)
Router Link States (Area 0)
Link ID
ADV Router
Age
192.168.0.1 192.168.0.1 1702
192.168.0.2 192.168.0.2 486
192.168.0.11 192.168.0.11 1832
192.168.0.12 192.168.0.12 479
Seq#
Checksum Link count
0x8000000A 0x00C3D3 3
0x8000000A 0x00068B 3
0x80000007 0x007231 2
0x8000000A 0x008813 2
Net Link States (Area 0)

Link ID
10.1.0.1
10.1.1.1
10.1.2.1
ADV Router
Age
192.168.0.1 1702
192.168.0.1 1955
192.168.0.2 486
Seq#
Checksum
0x80000006 0x00A14E
0x80000006 0x0015D0
0x80000006 0x001CC5

Link ID
130.1.1.1
172.1.1.1
ADV Router
Age
130.1.1.1
577
172.1.1.1
391
Seq#
Checksum Link count
0x80000003 0x0075B8 2
0x80000003 0x00541A 1

Laboratorio MPLS
33
Link ID
172.1.1.2
ADV Router
Age
130.1.1.1
584
Seq#
Checksum
0x80000001 0x0019BC
Summary Net Link States (Area 0)

Link ID
140.1.2.1
172.1.2.0
ADV Router
Age
172.1.1.1
233
172.1.1.1
233
Seq#
Checksum
0x80000001 0x0095E5
0x80000001 0x00D38F
PE2#sh ip ospf database

Link ID
ADV Router
Age
192.168.0.1 192.168.0.1 1772
192.168.0.2 192.168.0.2 553
192.168.0.11 192.168.0.11 1904
192.168.0.12 192.168.0.12 545
Seq#
Checksum Link count
0x8000000A 0x00C3D3 3
0x8000000A 0x00068B 3
0x80000007 0x007231 2
0x8000000A 0x008813 2

Link ID
10.1.0.1
10.1.1.1
10.1.2.1
ADV Router
Age
192.168.0.1 1772
192.168.0.1 29
192.168.0.2 554
Seq#
Checksum
0x80000006 0x00A14E
0x80000007 0x0013D1
0x80000006 0x001CC5

Link ID
140.1.2.1
172.1.2.1
ADV Router
Age
140.1.2.1
546
172.1.2.1
332
Seq#
Checksum Link count
0x80000003 0x00709A 2
0x80000003 0x005812 1

Link ID
172.1.2.2
ADV Router
Age
140.1.2.1
548
Seq#
Checksum
0x80000001 0x0009B4
Summary Net Link States (Area 0)

Link ID
130.1.1.1
ADV Router
Age
172.1.2.1
331
Laboratorio MPLS
Seq#
Checksum
0x80000001 0x001C69
34
172.1.1.0
172.1.2.1
331
0x80000001 0x00D78B
Revise la tabla de rutas en el CE y note las rutas OSPF interarea (IA) en la

tabla de enrutamiento:
CE#sh ip route
CE2#sh ip route
O IA 172.1.1.0 [110/2] via 172.1.2.1, 00:06:48, FastEthernet0/0
C
C
CE1#sh ip route
C
C
Laboratorio MPLS
35
Verifique la conectividad a travs de la VPN usando los comandos ping y trace

sobre los routers CE y ping vrf y trace vrf sobre los routers PE :
CE#ping .
CE1#ping 140.1.2.1
!!!!!
PE#ping vrf ..

!!!!!
Laboratorio MPLS
36
Laboratorio 7: Configurando BGP entre PE y CE
OBJETIVO:
Establecer el protocolo de enrutamiento BGP entre el router CE y el router PE
Tareas:
1. Active el proceso BGP sobre los routers CE con el AS 65001. Deshabilite el
auto summary del BGP.
2. Configure la relacin BGP entre el CE y el PE.
3. Habilte el AS-override debido a que los dos sitios utilizan el mismo nmero
de AS.
Verificacin:
Verifique la conectividad BGP con el comando show ip bgp summary sobre los
routers CE:
CE#sh ip bgp summary
CE1#sh ip bgp summary
2 network entries using 202 bytes of memory
2 path entries using 96 bytes of memory
2 BGP path attribute entries using 120 bytes of memory
Laboratorio MPLS
37
1 BGP AS-PATH entries using 24 bytes of memory

0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 442 total bytes of memory
BGP activity 2/0 prefixes, 2/0 paths, scan interval 60 secs
Neighbor
172.1.1.1

4 2
17
18
3
0
0
00:08:01
1
CE2#sh ip bgp summ

2 network entries using 202 bytes of memory
2 path entries using 96 bytes of memory
2 BGP path attribute entries using 120 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 442 total bytes of memory
BGP activity 2/0 prefixes, 2/0 paths, scan interval 60 secs
Neighbor
172.1.2.1

4
2
11
11
3
0
0
00:06:28
1
PE#sh ip bgp vpnv4 all
PE2#sh ip bgp vpnv4 all

Network
Next Hop
*>i130.1.1.0/24 192.168.0.11
0 100
0 65001 i
*> 140.1.2.0/24 172.1.2.2
0
0 65001 i
PE1#sh ip bgp vpnv4 all

Laboratorio MPLS
38

Network
Next Hop
*> 130.1.1.0/24 172.1.1.2
0
0 65001 i
*>i140.1.2.0/24 192.168.0.12
0 100
0 65001 i
CE1#sh ip route
B
140.1.2.0 [20/0] via 172.1.1.1, 00:18:03
C
C
CE2#sh ip route
C
C
B
130.1.1.0 [20/0] via 172.1.2.1, 00:18:32
Laboratorio MPLS
39
CE1#ping 140.1.2.1 source 130.1.1.1

Packet sent with a source address of 130.1.1.1
!!!!!
Laboratorio MPLS
40
Laboratorio 8. Configurando QoS entre PE y CE

Objetivo:
Configurar Calidad de servicio entre el PE y CE para garantizar un adecuado
funcionamiento de la VoIP.
El cliente tiene un Gateway de VoIP en cada sitio los cuales necesitan priorizarse para
que la voz funcione, la IP 20.20.20.1 /32 en el CE1 y la IP 30.30.30.1/32.
Tareas:
Sobre el CE:
1. Configurar un access-list 1 para clasificar a los gateway de voz.
2. Configurar un class-map con nombre VoIP para clasificar los paquetes de voz
3. Configurar un policy-map llamado QoS en donde se va a asignar 128 Kbps para la

clase VoIP en donde se marcarn los paquetes con IP Precedence 5
4. Aplicar la poltica de QoS en sentido saliente sobre el interfaz que apunta al PE
Laboratorio MPLS
41
En el PE:
1. Configurar un class-map llamado VoIP que clasifique los paquetes marcados con IP
Precedence 5
2. Configurar un policy-map llamado QoS que asigne 128 Kbps de BW a las clase
VoIP
3. Aplicar la poltica QoS sobre la interfaz que apunta al CE
Verificar que las polticas estan aplicadas en las interfaces del router CE y PE con el
comando sh policy-map interface
PE1# sh policy-map interface f1/0

FastEthernet1/0
Service-policy output: QoS
Class-map: VoIP (match-all)
0 packets, 0 B/bytesytes
30 second offered rate 0 bps, drop rate 0 bps
Match: ip precedente 5
Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 128 (kbps) Burst 3200 (Bytes)
(pkts matched/bytes matched) 0/0
(total props./bytes props) 0/0
Class-map: class-default (match-any)
8 packets, 1358 bytes
Laboratorio MPLS
42
30 second offerred rate 0 bps, drop rate 0 bps

Match: any
CE1# sh policy-map interface f0/0

FastEthernet0/0
Service-policy output: QoS
Class-map: VoIP (match-all)
0 packets, 0 B/bytesytes
30 second offered rate 0 bps, drop rate 0 bps
Match: access-group 1
Queueing
Strict Priority
Output Queue: Conversation 264
Bandwidth 128 (kbps) Burst 3200 (Bytes)
(pkts matched/bytes matched) 0/0
(total props./bytes props) 0/0
QoS Set
Precedente 5
Packets marked 0
Class-map: class-default (match-any)
13 packets, 1185 bytes
30 second offerred rate 0 bps, drop rate 0 bps
Match: any
Laboratorio MPLS
43
Laboratorio 9: Configurando Overlapping VPNs

OBJETIVO:
Establecer comunicacin entre los sitios centrales de los clientes de acuerdo al
siguiente requerimiento:
Tareas:
1. Disee su solucin de VPN.
2. Asigne nuevos RDs para las VRFs a las cuales los routers CE deberan
conectarse.
3. Un nuevo RT es necesario para los sitios centrales.
Laboratorio MPLS
44
Laboratorio MPLS
45

Laboratorios MPLS

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Laboratorios MPLS

Încărcat de

Drepturi de autor:

Formate disponibile

CONFIGURANDO REDES MPLS

Laboratorio 1: Estableciendo el CORE IGP - Ambiente de enrutamiento

3. Configurar OSPF en los Ps y PEs en el rea 0 y verificar la correcta

o - ODR, P - periodic downloaded static route

10.0.0.0/29 is subnetted, 3 subnets

PE1#SH IP OSPF NEIGHbor

Dead Time Address

10.0.0.0/29 is subnetted, 3 subnets

P2#SH IP OSPF NEIGHBOR

10.0.0.0/29 is subnetted, 3 subnets

192.168.0.12 is directly connected, Loopback0

PE2#SH IP OSPF NEIGHBOR

Dead Time Address

Laboratorio 2: Estableciendo el CORE MPLS

En cada uno de los routers verificar el establecimiento de la relacin de vecinos

routerP#show mpls ldp discovery

PE1#SH MPLS LDP DISCOVERY

PE2#SH MPLS LDP DISCOVERY

routerP#show mpls ldp neighbor

PE1#SH MPLS LDP NEIGHBOR

P1#SH MPLS LDP NEIGHBOR

State: Oper; Msgs sent/rcvd: 18/18; Downstream

P2#SH MPLS LDP NEIGHBOR

PE2#SH MPLS LDP NEIGHBOR

10.0.0.0/29 is subnetted, 3 subnets

10.0.0.0/29 is subnetted, 3 subnets

192.168.0.12 [110/3] via 10.1.0.2, 00:17:42, FastEthernet1/0

10.0.0.0/29 is subnetted, 3 subnets

10.0.0.0/29 is subnetted, 3 subnets

routerP#sh mpls ldp bindings

P1#SH MPLS LDP BINDINGS

remote binding: tsr: 192.168.0.11:0, tag: 20

PE2#SH MPLS LDP BINDINGS

Realizar un traceroute desde el PE hacia la direccin de loopback del otro PE,

3. Deshabilitar la Propagacin de TTL

Laboratorio 3: Configurando Multiprotocol BGP

PE#sh ip bgp summary

PE2#SH IP BGP SUMM

PE#sh ip bgp neighbor

iss: 3418116995 snduna: 3418117182 sndnxt: 3418117182 sndwnd: 16198

PE2#SH IP BGP NEIGHBOR

Connection state is ESTAB, I/O status: 1, unread input bytes: 0

Laboratorio 4: Configurando las tablas de enrutamiento y envo VRFs

PE2#sh ip vrf detail

Verifique que protocolo est corriendo en la VRF con el comando show ip

PE1#sh ip protocols vrf cliente1

PE2#sh ip protocols vrf cliente1

Verifique la tabla de rutas en la VRF con el comando show ip route vrf

PE1#sh ip route vrf cliente1

PE2#sh ip route vrf cliente1

PE1#sh ip bgp vpnv4 vrf cliente1

PE2#sh ip bgp vpnv4 vrf cliente1

10.0.0.0/29 is subnetted, 3 subnets

10.0.0.0/29 is subnetted, 3 subnets

PE1#ping vrf cliente1 130.1.1.1

PE#ping vrf [nombre de la vrf] 140.1.2.1

PE2#ping vrf cliente1 140.1.2.1

Laboratorio 5: Configurando EIGRP entre PE y CE

PE1#sh ip eigrp vrf cliente1 interfaces

Xmit Queue Mean Pacing Time Multicast Pending

PE2#sh ip eigrp vrf cliente1 interfaces

Xmit Queue Mean Pacing Time Multicast Pending

Verifique que las adyacencias hayan sido establecidas entre el CE y PE