CSC part 2

I do something wrong on last post, the backbone carrier pop the label , because the label is pop too early, the ipv4 packet will not reach the correct PE router. so the traffic isn't work.

I check the configuration again, 2 key points on it,
1, In junos, The BGP inet-vpn update will base on inet.3 table, if the next-hop isn't on the table it will not update to peer.

2, The bgp peer configuration include the "resolve-vpn" this mean this prefix will using for next-hop resolve.

example @PE LSR
3:9:192.168.90.0/24 (1 entry, 0 announced)
*BGP Preference: 140/-101
Route Distinguisher: 3:9
Next-hop reference count: 6
Source: 123.123.2.2
Next hop: 123.123.12.2 via fe-0/1/0.12, selected
Label operation: Push 100032, Push 100112, Push 100016(top)
Protocol next hop: 2.2.9.9
Push 100032
Indirect next hop: 8738378 262147
State:
Local AS: 1 Peer AS: 1
Age: 35:47 Metric2: 1
Task: BGP_1.123.123.2.2+179
AS path: 3 I
Communities: target:3:9
VPN Label: 100032
Localpref: 100
Router ID: 123.123.2.2
Secondary Tables: ce1.inet.0
Indirect next hops: 1
Protocol next hop: 2.2.9.9 Metric: 1
Push 100032
Indirect next hop: 8738378 262147
Indirect path forwarding next hops: 1
Next hop: 123.123.12.2 via fe-0/1/0.12
2.2.9.9/32 Originating RIB: inet.3
Metric: 1 Node path count: 1
Indirect nexthops: 1
Protocol Nexthop: 123.123.3.3 Metric: 1 Push 100112
Indirect nexthop: 87381bc 262160
Indirect path forwarding nexthops: 1
Nexthop: 123.123.12.2 via fe-0/1/0.12
123.123.3.3/32 Originating RIB: inet.3
Metric: 1 Node path count: 1
Forwarding nexthops: 1
Nexthop: 123.123.12.2 via fe-0/1/0.12