Vous êtes sur la page 1sur 5

MPLS configuration is simple:

Step 1:
Run Eigrp on all the six Routers
Router eigrp 10
Network..
Step 2:
Test end to end reachability by PINGING from CE-1 to 10.3.3.1 of CE-2
Step:3
Enable MPLS on PE-1 , P-1, P-2 and PE-2 note CE-1 and CE-2 will not be
running MPLS.
Step: 3.1
Enable CEF on all the Provider routers (CEF is the prerequisite for MPLS) and
verify it as follows

PE-1(config)# ip cef
PE-1(config)#
PE-1(config)#

PE-1(config)# PE-1#sh ip cef


Prefix
0.0.0.0/0
0.0.0.0/32
1.1.1.1/32
2.2.2.2/32
3.0.0.0/8
4.4.4.4/32
10.3.3.0/24

Next Hop
Interface
drop
Null0 (default route handler entry)
receive
receive
192.168.12.2
Serial1/1
192.168.14.4
Serial1/2
192.168.12.2
Serial1/1
192.168.14.4
Serial1/2
192.168.14.4
192.168.12.2

192.168.12.0/24 attached
192.168.12.0/32 receive
192.168.12.1/32 receive
192.168.12.255/32 receive
192.168.14.0/24 attached
192.168.14.0/32 receive
192.168.14.1/32 receive

Serial1/2
Serial1/1
Serial1/1

Serial1/2

Well talk about this subnet received


from CE-2 as the reference of our
configurations

192.168.14.255/32 receive
192.168.15.0/24 attached
192.168.15.0/32 receive
192.168.15.1/32 192.168.15.1
192.168.15.2/32
receive
192.168.15.255/32 receive
192.168.23.0/24 192.168.12.2
192.168.34.0/24 192.168.14.4
192.168.36.0/24 192.168.14.4
192.168.12.2
224.0.0.0/4
drop
224.0.0.0/24
receive
240.0.0.0/4
drop
255.255.255.255/32 receive

FastEthernet0/0
FastEthernet0/0
Serial1/1
Serial1/2
Serial1/2
Serial1/1

PE-1#show ip cef detail


Output is omitted for simplicity
10.3.3.0/24, version 42, epoch 0, per-destination sharing
0 packets, 0 bytes
via 192.168.14.4, Serial1/2, 0 dependencies
traffic share 1
next hop 192.168.14.4, Serial1/2
valid adjacency
via 192.168.12.2, Serial1/1, 0 dependencies
traffic share 1
next hop 192.168.12.2, Serial1/1
valid adjacency
0 packets, 0 bytes switched through the prefix
tmstats: external 0 packets, 0 bytes
internal 0 packets, 0 bytes

Step: 3.2
Now enable MPLS, MPLS must be configured under per interface basis.
Example:
PE-1(config)#interface s1/1
PE-1(config-if)#mpls ip
PE-1(config-if)#mpls label protocol ldp
PE-1(config)#interface s1/2
PE-1(config-if)#mpls ip
PE-1(config-if)#mpls label protocol ldp

VERIFY:
After you have enabled MPLS on all the interfaces of the Providers routers
verify it as follows

PE-1#sh mpls ldp neighbor


Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 1.1.1.1:0
TCP connection: 2.2.2.2.11998 - 1.1.1.1.646
State: Oper; Msgs sent/rcvd: 29/32; Downstream
Up time: 00:11:04
LDP discovery sources:
Serial1/1, Src IP addr: 192.168.12.2
Addresses bound to peer LDP Ident:
192.168.12.2 2.2.2.2
192.168.23.2
Peer LDP Ident: 4.4.4.4:0; Local LDP Ident 1.1.1.1:0
TCP connection: 4.4.4.4.47985 - 1.1.1.1.646
State: Oper; Msgs sent/rcvd: 27/33; Downstream
Up time: 00:09:35
LDP discovery sources:
Serial1/2, Src IP addr: 192.168.14.4
Addresses bound to peer LDP Ident:
4.4.4.4
192.168.14.4 192.168.34.4
Note: PE-1 has ldp identifier 1.1.1.1 and there are two ldp neighbors 2.2.2.2 and 4.4.4.4
which are P-1 and P-2 respectively also take a note of the port no. which ldp uses (TCP
646)

As we said earlier we will be focusing subnet 10.3.3.0(loopback0 of CE-1) for our


reference

PE-1#sh mpls ldp bindings


tib entry: 1.1.1.1/32, rev 8
local binding: tag: imp-null
remote binding: tsr: 2.2.2.2:0, tag: 16
remote binding: tsr: 4.4.4.4:0, tag: 16
tib entry: 2.2.2.2/32, rev 10
local binding: tag: 16
remote binding: tsr: 2.2.2.2:0, tag: imp-null
remote binding: tsr: 4.4.4.4:0, tag: 19
tib entry: 3.0.0.0/8, rev 21
local binding: tag: 21
remote binding: tsr: 4.4.4.4:0, tag: 23
remote binding: tsr: 2.2.2.2:0, tag: 22
tib entry: 4.4.4.4/32, rev 15
local binding: tag: 18
remote binding: tsr: 4.4.4.4:0, tag: imp-null
remote binding: tsr: 2.2.2.2:0, tag: 19
tib entry: 10.3.3.0/24, rev 23
local binding: tag: 22
remote binding: tsr: 4.4.4.4:0, tag: 21
remote binding: tsr: 2.2.2.2:0, tag: 23
tib entry: 192.168.12.0/24, rev 4
local binding: tag: imp-null
remote binding: tsr: 2.2.2.2:0, tag: imp-null
remote binding: tsr: 4.4.4.4:0, tag: 18
tib entry: 192.168.14.0/24, rev 6
local binding: tag: imp-null
remote binding: tsr: 4.4.4.4:0, tag: imp-null
remote binding: tsr: 2.2.2.2:0, tag: 18
tib entry: 192.168.15.0/24, rev 2
local binding: tag: imp-null
remote binding: tsr: 2.2.2.2:0, tag: 17
remote binding: tsr: 4.4.4.4:0, tag: 17
tib entry: 192.168.23.0/24, rev 12
local binding: tag: 17
remote binding: tsr: 2.2.2.2:0, tag: imp-null
remote binding: tsr: 4.4.4.4:0, tag: 20
tib entry: 192.168.34.0/24, rev 17
local binding: tag: 19
remote binding: tsr: 2.2.2.2:0, tag: 20
remote binding: tsr: 4.4.4.4:0, tag: imp-null
tib entry: 192.168.36.0/24, rev 19

local binding: tag: 20


remote binding: tsr: 4.4.4.4:0, tag: 22
remote binding: tsr: 2.2.2.2:0, tag: 21

PE-1#sh mpls ldp bindings 10.3.3.0 24


tib entry: 10.3.3.0/24, rev 23
local binding: tag: 22
remote binding: tsr: 4.4.4.4:0, tag: 21
remote binding: tsr: 2.2.2.2:0, tag: 23
PE-1#
Note: the command shows two remote ldp bindings (tags) are listed one from
P-1(LDP ID 2.2.2.2) = 23 and the other from P-2 (LDP ID 4.4.4.4)=21. This command
also lists the local binding, which is the label that PE-1 allocated and advertised to its
neighbors.