Problem solved. no mpls mls tunnel-recir and then applied command back. Once I did this it worked.
Yeah all other stuff was in place, that was really weird. On Tue, Mar 18, 2014 at 1:52 PM, Michele Bergonzoni <[email protected]> wrote: > Could anyone explain why the following setup is not working, maybe there is >> a limitation on 7600 for this? >> >> >> PE1-------[MPLS]----------PE2----tun99------CE >> >> Basically, Tunnel 99 is in VRF. All routes including tunnel are visible in >> VRF. Ping sourced from tunnel99 to CE works (directly connected), but when >> I ping from PE1 tunnel99 on CE, or any other route behind tunnel99 on CE, >> it doesn't work. >> I have mls mpls tunnel-recir configured on PE routers. >> > > You should probably take a very close look at the CEF and adjacency > entries for the routes in Tu99 on PE2, and to the LFIB for the > corresponding labels with "sh mpls forwarding-table". > > If the labels for those routes are the same, and are the aggregate label > for the VRF, I would try "mls mpls recir-agg", if you can spare some switch > capacity. > > If they aren't, I would try to make PE2 use only the aggregate for that > VRF (if it is possible in you environment) with "mpls label mode <yourvrf> > protocol bgp-vpnv4 per-vrf", in addition to "mls mpls recir-agg". > > If this doesn't work, try to post your routes, CEF, adjacencies, labels > and mpls forwarding-table (for PE2). > > Best luck, > > Bergonz > > -- > Ing. Michele Bergonzoni - Laboratori Guglielmo Marconi S.p.a. > Phone:+39-051-6781926 e-mail: [email protected] > alt.advanced.networks.design.configure.operate > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
