VRFs, route policy and IPv6 provider VPNs
Keep routing context explicit
A virtual routing and forwarding instance maintains relevant customer routing/forwarding separation on the provider edge. Customer networks can use overlapping addresses because the service context distinguishes them. A route distinguisher helps create a distinct VPN route representation; it is not the policy that decides every permitted import. Route targets are attributes used by the configured import/export policy. Two VRFs with different distinguishers can deliberately exchange selected routes when the actual target policy permits it.
Trace a route before tracing a packet
A provider edge learns a customer prefix through the supported PE-CE routing or static configuration, associates the relevant VPN context and advertises applicable information through the selected multiprotocol BGP family. The remote edge must receive, select and import the route appropriately, with a resolvable transport next hop and service forwarding information. A route visible in one BGP table does not prove it appears in the intended customer VRF or that the return path exists. Avoid indiscriminate redistribution that violates the service’s isolation requirement.
Separate IPv6 customer and provider transport
VPNv6 carries the relevant VPN-associated IPv6 routing information in its supported BGP model. A 6VPE arrangement can provide IPv6 customer VPN service over an appropriate MPLS provider infrastructure without requiring the core to maintain every customer IPv6 route. Which peers or AS boundary routers carry which families depends on the selected inter-AS option; not every ASBR universally needs every VPN family. Verify actual next-hop representation, label reachability and address-family negotiation rather than infer them solely from a customer prefix’s version.
Interpret routing behavior in context
BGP neighbor AS expectations, route reflection, path selection and policy influence what is advertised or selected. They do not automatically establish application reachability or encryption. IOS XE and IOS XR express related concepts through different configuration structures, so a versioned command-recognition question is not a portable deployment recipe. For troubleshooting, correlate the customer attachment, VRF, learned prefix, distinguishers/targets, BGP family, next-hop resolution, labels and return path. Shared-service or extranet designs require intentional route policy and governance. This is conceptual provider-VPN preparation and executes no route, neighbor, policy or forwarding change.