carrier support carrier ( csc )

m_marmaash · ‎06-22-2011

Dear All

I'm trying to configure a csc scenario with 3 routers. Two routers at the edge presents the customer carriers while the 3rd router in between presents the backbone carrier. at the 3rd router ( the backbone carrier ) I configured vrf and assigned this vrf under each interface facing the edge routers ( customer Carrier ) at the same time I enabled under these interfaces the mpls ip . I enabled mpls label protocol on all the routers and at the edge routers I enabled mpls ip under the interface facing the backbone carrier router.

the following is the configuration on each router

backbone carrier

ip vrf fast

rd 1:1

route-target export 1:1

route-target import 1:1

mpls label protocol ldp

interface Serial0/1/0.200 point-to-point

ip vrf forwarding fast

ip address 2.2.15.242 255.255.255.252

snmp trap link-status

mpls ip

frame-relay interface-dlci 200

interface FastEthernet0/0

ip vrf forwarding fast

ip address 23.23.23.2 255.255.255.252

duplex auto

speed auto

mpls ip

end

on edge router 1

mpls label protocol ldp

interface Serial0/3/0.100 point-to-point

ip address 2.2.15.241 255.255.255.252

snmp trap link-status

mpls ip

frame-relay interface-dlci 100

on edge router 2

interface FastEthernet0/0

ip address 23.23.23.1 255.255.255.252

duplex auto

speed auto

mpls ip

end

I cant see that the LDB neighbor is up at any router as follows:

backbone carrier router :

Rack02R2#show mpls interfaces vrf fast

Interface IP Tunnel Operational

VRF fast:

FastEthernet0/0 Yes (ldp) No Yes

Serial0/1/0.200 Yes (ldp) No Yes

Rack02R2#show mpls ldp neighbor vrf fast

Rack02R2#

on both edge routers

Rack02R1#show mpls interfaces

Interface IP Tunnel Operational

Serial0/3/0.100 Yes (ldp) No Yes

Rack02R1#

Rack02R1#show mpls ldp neighbor

Rack02R1#

yashfaqu · ‎06-26-2011

Hi,

Are you advertising the loopbacks in IGP ?

What is the output of following command on both Backbone_PE and Customer_CE?

show mpls ldp discovery

m_marmaash · ‎06-26-2011

Dear Yaser

thank you , you are correct with the command show mpls ldp discovery , I discovered that there is no route for the MPLS LDP Identifier of each router on the other routers. I fixed this issue and the output on all the routers as follows :

on the backbone carrier

Rack02R2#show mpls ldp discovery vrf fast

Local LDP Identifier:

2.2.15.242:0

Discovery Sources:

Interfaces:

FastEthernet0/0 (ldp): xmit/recv

LDP Id: 2.2.3.3:0

Serial0/1/0.200 (ldp): xmit/recv

LDP Id: 2.2.1.1:0

Rack02R2#show mpls ldp neighbor vrf fast

Peer LDP Ident: 2.2.1.1:0; Local LDP Ident 2.2.15.242:0

TCP connection: 2.2.1.1.646 - 2.2.15.242.34414

State: Oper; Msgs sent/rcvd: 16/22; Downstream

Up time: 00:12:06

LDP discovery sources:

Serial0/1/0.200, Src IP addr: 2.2.15.241

Addresses bound to peer LDP Ident:

13.13.13.1 2.2.15.161 2.2.15.249 2.2.1.1

2.2.15.241

Peer LDP Ident: 2.2.3.3:0; Local LDP Ident 2.2.15.242:0

TCP connection: 2.2.3.3.646 - 2.2.15.242.14271

State: Oper; Msgs sent/rcvd: 10/15; Downstream

Up time: 00:07:03

LDP discovery sources:

FastEthernet0/0, Src IP addr: 23.23.23.1

Addresses bound to peer LDP Ident:

23.23.23.1 2.2.15.193 2.2.3.3

and on the CE routers

router 1

Rack02R1#show mpls ldp neighbor

Peer LDP Ident: 2.2.15.242:0; Local LDP Ident 2.2.1.1:0

TCP connection: 2.2.15.242.34414 - 2.2.1.1.646

State: Oper; Msgs sent/rcvd: 23/17; Downstream

Up time: 00:12:46

LDP discovery sources:

Serial0/3/0.100, Src IP addr: 2.2.15.242

Addresses bound to peer LDP Ident:

2.2.15.242 23.23.23.2

router 2

Rack02R3#show mpls ldp neighbor

Peer LDP Ident: 2.2.15.242:0; Local LDP Ident 2.2.3.3:0

TCP connection: 2.2.15.242.14271 - 2.2.3.3.646

State: Oper; Msgs sent/rcvd: 16/12; Downstream

Up time: 00:08:04

LDP discovery sources:

FastEthernet0/0, Src IP addr: 23.23.23.2

Addresses bound to peer LDP Ident:

2.2.15.242 23.23.23.2

Rack02R3#

Every thing is working fine now thank you very much

Regards

Mohammed Marmash

m_marmaash · ‎06-26-2011

In the same manar the LDB neighbor is up but the forwarding table is empty at the backbone carrier which make the CE router unable to forward packet to the backbone carrier router as follows

at the backbone router

Rack02R2#show mpls ldp neighbor vrf fast

Peer LDP Ident: 2.2.1.1:0; Local LDP Ident 2.2.2.2:0

TCP connection: 2.2.1.1.646 - 2.2.2.2.43755

State: Oper; Msgs sent/rcvd: 39/48; Downstream

Up time: 00:31:58

LDP discovery sources:

Serial0/1/0.200, Src IP addr: 2.2.15.241

Addresses bound to peer LDP Ident:

13.13.13.1 2.2.15.161 2.2.15.241 2.2.1.1

2.2.15.249

Peer LDP Ident: 2.2.3.3:0; Local LDP Ident 2.2.2.2:0

TCP connection: 2.2.3.3.52736 - 2.2.2.2.646

State: Oper; Msgs sent/rcvd: 39/45; Downstream

Up time: 00:31:34

LDP discovery sources:

FastEthernet0/0, Src IP addr: 23.23.23.1

Addresses bound to peer LDP Ident:

23.23.23.1 2.2.3.3 43.43.43.1

Rack02R2#show mpls ldp bindings vrf fast

tib entry: 2.2.1.1/32, rev 4

remote binding: tsr: 2.2.1.1:0, tag: imp-null

remote binding: tsr: 2.2.3.3:0, tag: 16

tib entry: 2.2.2.2/32, rev 3

remote binding: tsr: 2.2.1.1:0, tag: 17

remote binding: tsr: 2.2.3.3:0, tag: 17

tib entry: 2.2.3.3/32, rev 5

remote binding: tsr: 2.2.1.1:0, tag: 18

remote binding: tsr: 2.2.3.3:0, tag: imp-null

tib entry: 2.2.4.4/32, rev 11

remote binding: tsr: 2.2.3.3:0, tag: 18

tib entry: 2.2.15.160/27, rev 7

remote binding: tsr: 2.2.1.1:0, tag: imp-null

tib entry: 2.2.15.240/30, rev 2

remote binding: tsr: 2.2.1.1:0, tag: imp-null

tib entry: 2.2.15.242/32, rev 12

remote binding: tsr: 2.2.3.3:0, tag: 19

tib entry: 2.2.15.248/30, rev 9

remote binding: tsr: 2.2.1.1:0, tag: imp-null

tib entry: 2.2.15.250/32, rev 8

remote binding: tsr: 2.2.1.1:0, tag: 16

tib entry: 13.13.13.0/30, rev 6

remote binding: tsr: 2.2.1.1:0, tag: imp-null

tib entry: 23.23.23.0/30, rev 1

remote binding: tsr: 2.2.3.3:0, tag: imp-null

tib entry: 43.43.43.0/30, rev 10

remote binding: tsr: 2.2.3.3:0, tag: imp-null

Rack02R2#show mpls forwarding-table vrf fast

Local Outgoing Prefix Bytes tag Outgoing Next Hop

tag tag or VC or Tunnel Id switched interface

Rack02R2#

now at the CE router

Rack02R1#show ip bgp summary

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

2.2.3.3 4 300 41 38 19 0 0 00:34:58 11

Rack02R1#

Rack02R1#show ip route bgp

34.0.0.0/32 is subnetted, 1 subnets

B 34.34.34.34 [20/0] via 2.2.3.3, 00:35:28

35.0.0.0/32 is subnetted, 1 subnets

B 35.35.35.35 [20/0] via 2.2.3.3, 00:35:28

32.0.0.0/32 is subnetted, 1 subnets

B 32.32.32.32 [20/0] via 2.2.3.3, 00:35:28

2.0.0.0/8 is variably subnetted, 9 subnets, 3 masks

B 2.2.4.4/32 [20/0] via 2.2.3.3, 00:35:28

B 2.2.15.64/27 [20/0] via 2.2.3.3, 00:35:28

33.0.0.0/32 is subnetted, 1 subnets

B 33.33.33.33 [20/0] via 2.2.3.3, 00:35:28

36.0.0.0/32 is subnetted, 1 subnets

B 36.36.36.36 [20/0] via 2.2.3.3, 00:35:28

23.0.0.0/30 is subnetted, 1 subnets

B 23.23.23.0 [20/0] via 2.2.3.3, 00:35:28

43.0.0.0/30 is subnetted, 1 subnets

B 43.43.43.0 [20/0] via 2.2.3.3, 00:35:28

31.0.0.0/32 is subnetted, 1 subnets

B 31.31.31.31 [20/0] via 2.2.3.3, 00:35:28

Rack02R1#show mpls ldp neighbor

Peer LDP Ident: 2.2.2.2:0; Local LDP Ident 2.2.1.1:0

TCP connection: 2.2.2.2.43755 - 2.2.1.1.646

State: Oper; Msgs sent/rcvd: 53/44; Downstream

Up time: 00:36:00

LDP discovery sources:

Serial0/3/0.100, Src IP addr: 2.2.15.242

Addresses bound to peer LDP Ident:

23.23.23.2 2.2.2.2 2.2.15.242

Rack02R1#show mpls forwarding-table

Local Outgoing Prefix Bytes tag Outgoing Next Hop

tag tag or VC or Tunnel Id switched interface

16 Untagged 2.2.15.250/32 0 Se0/2/0 point2point

17 Untagged 2.2.2.2/32 0 Se0/3/0.100 point2point

18 Untagged 2.2.3.3/32 0 Se0/3/0.100 point2point

note that the outgoing is untagged

Rack02R1#traceroute 31.31.31.31

Type escape sequence to abort.

Tracing the route to 31.31.31.31

1 2.2.15.242 24 msec 24 msec 28 msec

2 2.2.15.242 !H * !H

it is stopped at the backbone router? any ideas ?

regards