VPRN Services
7705 SAR OS Services Guide Page 415
Route Reflector
As defined in RFC 2547bis, the use of route reflectors is supported in the service provider
core. The support uses multiple sets of route reflectors for different types of BGP data,
including IPv4 and VPN-IPv4.
CE to PE Route Exchange
Routing information between the Customer Edge (CE) and Provider Edge (PE) can be
exchanged by static routes that are configured on the PE.
Route Redistribution
Routing information learned from the configured static routes is injected in the associated
local VPN routing/forwarding table (VRF). In the case of dynamic routing protocols, there
may be protocol-specific route policies that modify or reject certain routes before they are
injected into the local VRF.
The advertisement or redistribution of routing information from the local VRF to or from the
MP-BGP instance is specified per VRF and is controlled by VRF route target associations or
by VRF route policies.
A route belonging to a VPRN must use the protocol owner, VPN-IPv4, to denote that it is a
VPRN route. This can be used within the route policy match criteria.
Type 1 Administrator subfield (4 bytes) The Administrator field must contain an IP address (using
private IP address space is discouraged)
Assigned number subfield (2 bytes) The Assigned field contains a number assigned by the
service provider
Type 2 Administrator subfield (4 bytes) The Administrator field must contain a 4-byte AS number
(using private AS numbers is discouraged)
Assigned number subfield (2 bytes) The Assigned field contains a number assigned by the
service provider
Table 55: Route Distinguisher Type-Value Fields (Continued)
Type Field Value Field Notes
To Next Page
Loading...
