Ethernet over MPLS(ATOM)

[shailendra.gupta]

Dear Friends

would like to seek your help to resolve one Ethernet ATOM case. The details are as follows.

Physical Connectivity:

PC1---Connected--->Vlan Switch--->Fas 4/0/0.1 of 7507-1(PE1)---> Connected to 7507-1 over Multil-Link PPP, with single E1 Link.

PC2---> Connected--->Vlan Switch Fas 1/0/0.1 of 7502-2(PE-2)---> Connected to 7507-1 over Multil-Link PPP, with single E1 Link.

Objective: To create L2 VPN to transport VLAN Traffic across PC1 & PC2, using Ethernet over MPLS.

„h In a way both 7507 i.e. PE1 & PE2 are connected back to back.

„h IP of PC1: 10.0.0.1/24 & PC2: 10.0.0.2/24

Configuration of PE1 & PE2:

PE1:

Interface Loopback 4

ip address a.b.c.d/32

mpls label protocol ldp

tag-switching tdp router-id Loopback4 force

Interface Fas 4/0/0.1---> This connects to PC1

encapsulation dot1q 10

mpls l2transport route p.q.r.s 100

Interface Multi-Link 2

ip address 192.168.0.1 255.255.255.252

no ip directed-broadcast

mpls label protocol both

tag-switching ip

no cdp enable

ppp authorization noauth

ppp multilink

multilink-group 1

PE2:

Interface Loopback 5

ip address p.q.r.s/32

mpls label protocol ldp

tag-switching tdp router-id Loopback5 force

Interface Fas 4/0/0.1---> This connects to PC2

encapsulation dot1q 10

mpls l2transport route p.q.r.s 100

Interface Multi-Link 2

ip address 192.168.0.2 255.255.255.252

no ip directed-broadcast

mpls label protocol both

tag-switching ip

no cdp enable

ppp authorization noauth

ppp multilink

multilink-group 1

Observations:

„h While we see that Local & Remote End Tags are being exchanged, however Vc remains down(sh mpls l2transport vc) & Ping between PC1 & PC2 does not take place.

„h when we run debug, while every thing seems to be OK for MPLS establishment, however one line seems to be reporting some error:

At PE1 AToM SMGR [p.q.r.s, 100]: Imposition setup incomplete because unable to find a tunnel label

At PE2 AToM SMGR [a.b.c.d, 100]: Imposition setup incomplete because unable to find a tunnel label

It would your great help to share your advise & input to make this work.

Thanks & Regards

Shailendra

[vkapoor5]

I think the VC is declared down since the tunnel label is not known by the device as shown in the debug. Since your PE devices are connected back-to-back, the IGP label should be an implicit null in your case.

[shailendra.gupta]

Dear All

Problem got resolved by inducting a "P" Router between two PE Routers. Yes, VC Label was getting exchanged, however there was no Tunnel Label being PE Router connected back to back (Label POPing).

Due to various connectivity need, we need to make this work with PE to PE, any suggestion how can we make this work.[we tried mpls explicit null too]

Shailendra

[addiekaul75]

Try binding the remote Pe address's with static MPLS labels.

Pls chek the url.

http://www.cisco.com/en/US/customer/products/sw/iosswrel/ps1829/products_feature_guide09186a008010dd41.html

[shailendra.gupta]

Thanks. I am sorry for late response.

We will try yr suggestion(it seems to be an alternate, like what we have static routing) and share the results.

Shailendra