Customer wants that all traffic to be label forwarded, but PE routers in topology do not have label to forward IP traffic to destinations announced by other PE routers. MPLS VPN traffic is working OK, but normal IP traffic is not being label forwarded, normal IP traffic is being routed. PE routers do not have hot to reach networks received by BGP in their forwarding table.
About the Peru MPLS forwarding problem, based on VRP5, we have two solutions PEA---------P---------PEB | | CEA CEB Note: 1、There is no any VPN in the netwrk 2、LSP is correctly established、loopback interfaces of all the them included in the IGP 3、EBGP or static routing protocol used between PE and CE 4、In PEA, there is a ip routing with destination of CEB and nexthop pointing to the PEB loopback Requirment: We need ping from CEA to CEB Solution: VRP5 V3R2，need to config followed command route recursive-lookup tunnel The routemap for the issued version is the May 2006 VRP5 V3R1 can support now(e.g. telemar version），need commands in PE to assign the label by BGP peer 22.214.171.124 route-policy app-lable export peer 126.96.36.199 label-route-capability route-policy app-lable permit node 0 apply mpls-label In V3R2, we have: disp ip rout 188.8.131.52 32 verbose Routing Table : Public Summary Count : 1 Destination: 184.108.40.206/32 Protocol: BGP Process ID: 0 Preference: 255 Cost: 0 NextHop: 220.127.116.11 Interface: Ethernet2/0/2 RelayNextHop: 18.104.22.168 Neighbour: 22.214.171.124 Label: NULL Tunnel ID: 0x800406 (Tunnel ID ready) SecTunnel ID: 0x0 BkNextHop: 0.0.0.0 BkInterface: BkLabel: NULL Tunnel ID: 0x0 SecTunnel ID: 0x0 State: Active Adv GotQ Age: 00h00m49s Tag: 0 In V3R1, we have: [NE40_Internet]disp ip routing-table 126.96.36.199 32 verbose Routing Table : Public Summary Count : 1 Destination: 188.8.131.52/32 Protocol: BGP Process ID: 0 Preference: 255 Cost: 0 NextHop: 184.108.40.206 Interface: Ethernet2/0/0 RelyNextHop: 220.127.116.11 Neighbour: 18.104.22.168 Tunnel ID: 0x888003 Label: 19456 State: Active Adv GotQ Age: 00h06m35s Tag: 0 [NE40_Internet]en_
this is a special application of MPLS, it is not typical MPLS-VPN, but it can be used for hiding the customer IP address from public network, ther are two forwarding stage, the first is normal ip forwarding, the ip packets are sent to the NE40, when NE40 check the next hop is remote loopback address, and NE40 have the lable for the nexthop. NE40 will send the packets into MPLS forwarding,