# Characteristics of Import and Global Import Maps

Import maps and global import maps can import both labeled and unlabeled routes. If you want to import only one or the other, you can use a match mpls-label command in the global import route map. Furthermore, if BGP imports labeled routes from the global BGP non-VPN RIB into a VRF RIB and then advertises them further upstream as labeled routes, the MPLS cross-connects are correctly created and MPLS forwarding works. The global VPN RIB never contains unlabeled routes, so the issue is moot for import maps.

When a route that was previously imported into the local VRF RIB is modified in the global BGP RIB (VPN or non-VPN) such that it no longer matches the import or global import map, that route is removed from the local VRF RIB.

Imported routes point to the same interface and next hop as the original route. Shared IP interfaces are not created.

Table 89 lists additional characteristics of import and global import maps.

Table 89: Characteristics of Import and Global Import Maps

Characteristic | Import | Global Import
--- | --- | ---
Distributes routes from the global BGP VPN RIB local to the VR. This RIB is often referred to as the core VPN RIB. | Yes | –
Distributes routes from the global BGP non-VPN RIB local to the VR. This RIB is often referred to as the core non-VPN RIB or core RIB. | – | Yes
Imports all types of routes (received routes, redistributed routes, network routes, aggregate routes, and auto-summary routes). | Yes | Yes
Imports both best and non-best routes. The best route selection (including the decision to use or not use ECMP) is made in the VRF after the routes are imported. | Yes | Yes