--- R9 ROUTE TABLE ----

custA_R9#show ip route

      1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        1.9.1.0/24 is directly connected, Ethernet0/0
L        1.9.1.9/32 is directly connected, Ethernet0/0
      9.0.0.0/32 is subnetted, 1 subnets
C        9.9.9.9 is directly connected, Loopback0
      10.0.0.0/32 is subnetted, 1 subnets
B        10.10.10.10 [20/0] via 1.9.1.1, 02:26:21 <<<<<<<<<<<<<<<<


--- R1 (PE) ---

PE_R1#show ip route vrf CUST-A

      1.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C        1.9.1.0/24 is directly connected, Ethernet0/2
L        1.9.1.1/32 is directly connected, Ethernet0/2
      9.0.0.0/32 is subnetted, 1 subnets
B        9.9.9.9 [20/0] via 1.9.1.9, 02:16:44
      10.0.0.0/32 is subnetted, 1 subnets
B        10.10.10.10 [200/0] via 2.2.2.2, 02:27:29 <<<<<<<<<<<<<<< how does R1 know to use the global route table for the next hop?


PE_R1#show ip route ospf
      2.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
O        2.2.2.2/32 [110/11] via 192.1.100.2, 11:26:37, Ethernet0/1 <<<<<<<<<<
O        2.3.2.0/24 [110/20] via 192.1.100.2, 11:26:27, Ethernet0/1
                    [110/20] via 1.3.1.3, 11:26:27, Ethernet0/0
      3.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
O        3.3.3.3/32 [110/11] via 1.3.1.3, 11:26:27, Ethernet0/0
O        3.4.3.0/24 [110/20] via 192.1.100.4, 11:26:37, Ethernet0/1
                    [110/20] via 1.3.1.3, 11:26:27, Ethernet0/0
      4.0.0.0/32 is subnetted, 1 subnets
O        4.4.4.4 [110/11] via 192.1.100.4, 11:26:37, Ethernet0/1

PE_R1#show bgp vpnv4 unicast all
     Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 1000:1 (default for vrf CUST-A)
 *>  9.9.9.9/32       1.9.1.9                  0             0 65001 i
 *>i 10.10.10.10/32   2.2.2.2                  0    100      0 65002 i <<<<<<<<