Routing

Hi

I have strange problem. I configured the 8 logical systems on MX80. I configured the L3VPN between two PE and both PE are getting routes of their routing instance from each other CE but I am not able to ping from one routing instance using source IP of interfaces connected to CE to IP of interface connected to CE to other PE routing instance. Although I can ping using command ping mpls l3vpn <instance name> prefix.

Also from CE to CE I am not able to ping. Kindly some one suggest what could be the reason?

Thanks

Are you using vrf-table-lable in the routing instance? If so, please remove it and try. It is not needed in your configuration I think.

Hi Pavan

Thanks for the reply. Actually I removed the VRF-TABEL-LABEL and now I can ping the remote PE interface IP connected to CE. But when I run the BGP between CE and remote PE then with VRF-TABEL-LABEL, I can still ping the CE and remote PE IP.

When I put the static route on remote PE for CE routes instead of BGP between CE and remote PE, then with VRF-TABEL-LABEL I can not ping the remote PE interface IP connected to CE.

I would appreciate if you could put light on this behaviour. It made me crazy!

Can you post your configurations (both the PE-CE bgp and static)  so that I can understand it better? In my local setup I use /30s for all lt interface addresses, and I dont have to use vrf-table-label on my MX.  

Hi,

Please mention if possible why do u suggest to remove this command. what is the effect that make ping failed. And how do u suspect the problem cause although he just make simple description to the problem without full configuration

Please refer this :

http://www.juniper.net/techpubs/software/junos/junos95/swconfig-vpns/id-10978770.html

You cannot configure the vrf-table-labelstatement within a VRF routing instance if the PE-router-to-P-router interface is any of the following:

• Aggregated SONET/SDH interfaces
• All channelized interfaces
• All tunnel interfaces (for example, generic routing encapsulation [GRE] and IP Security [IPSec])
• Circuit cross-connect (CCC) and translational cross-connect (TCC) encapsulated interfaces
• Logical tunnel interfaces <------------------------------------------------------------***
• Virtual private LAN service (VPLS) encapsulated interfaces

Since lt- interfaces was used in the config, vrf-table-label will not work.

Thanks

Hi Pavan

Thanks for the reply. Actually I am using the the physical gig interfaces with vlan-tagging to connect all the routers. i do not have any lt interfaces. What exactly I observed that:

The PE to CE subnet is not advertised by MBGP (if PE to CE interface is broadcast interface) unless I used the vrf-table-label command OR run BGP or any other static/IGP protocol with CE so that PE to CE subnet is the nexthop for some routes then PE-CE subnet is advertised without vrf-tabel-label. I saw one KB about this behavour which is KB12430 and now I can understand this behaviour.

But my question is that when I used vrf-tabel-label to advertise the PE-CE subnet through MBGP without running any static/IGP/BGP from PE to CE then I am unable to ping the PE-CE interface IP from the remote PE.

Could you please check this for me. Really appreciated your help.

Thanks

Just one note that between PE to CE the interface is gig interface and there are two services on this interface means one unit has virtual switch + VPLS service, other unit  is used for L3VPN between PE and CE (on which I am facing the issue)

Thanks