the signalling infrastructure in the Service provider uses multiprotocol iBGP:
L3 VPN prefixes are sent by PE routers as VPNv4 prefixes that is made of:
64 bit or RD + 32 bit IP address
this is to manage address overlapping
other PEs import vpnv4 routes in their locally defined VRFs, only if at least one route target extended community associated with the vpnv4 prefix matches a rt value that can be imported in the local VRF(s).
In case of import the RD is removed the ipv4 prefix is inserted in the VRF routing table.
The prefix appears as BGP [200 x] via the remote PE loopback (general routing table next-hop not provided to the CE)
PE-CE routing protocols choices include:
eBGP sessions (in VRF on the PE side)
RIP ( in address-family vrf vrf-name on PE side)
EIGRP ( in address-family vrf vrf-name on PE side)
OSPF (one process is associated to the VRF)
when using a protocol different then eBGP redistribution is mutual on PE between BGP in af vrf vrf-name and the IGP in the appropriate context (see above).
iBGP betweeen two VRFs:
this is a recent feature that allows to have a back to back iBGP session between a PE and a multi-VRF CE.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...