[c-nsp] VRF Lite Route Propagation
Nick Griffin
nick.jon.griffin at gmail.com
Thu Aug 14 12:26:37 EDT 2008
I must be missing something, see below:
C1#sh ip route vrf I1
Gateway of last resort is 1.1.111.1 to network 0.0.0.0
1.0.0.0/24 is subnetted, 1 subnets
C 1.1.111.0 is directly connected, Ethernet0/0.111
3.0.0.0/24 is subnetted, 1 subnets
B 3.3.3.0 is directly connected, 02:26:01, Ethernet0/0.333
5.0.0.0/24 is subnetted, 1 subnets
B 5.5.5.0 is directly connected, 02:26:01, Ethernet0/0.555 <---- Want
this in I1 Vrf on R1
O*E2 0.0.0.0/0 [110/1] via 1.1.111.1, 02:26:01, Ethernet0/0.111
C1#
router eigrp 1
no auto-summary
!
address-family ipv4 vrf VRF3
network 3.3.3.1 0.0.0.0
no auto-summary
autonomous-system 1
exit-address-family
!
router ospf 1 vrf I1
log-adjacency-changes
redistribute static metric 1 subnets
redistribute bgp 1 metric 5 subnets <------- Do this you said
network 1.1.111.2 0.0.0.0 area 0
!
router bgp 1
no synchronization
bgp router-id 3.3.3.3
bgp log-neighbor-changes
no auto-summary
!
address-family ipv4 vrf VRF5
redistribute connected
no auto-summary
no synchronization
exit-address-family
!
address-family ipv4 vrf VRF3
redistribute connected
no auto-summary
no synchronization
exit-address-family
!
address-family ipv4 vrf I1
redistribute connected
redistribute ospf 1 vrf I1 metric 5 match internal external 1 external 2
default-information originate
no auto-summary
no synchronization
exit-address-family
R1#sh ip ospf nei
Neighbor ID Pri State Dead Time Address Interface
1.1.111.2 1 FULL/DR 00:00:33 1.1.111.2
FastEthernet0/0.111
R1#sh ip route vrf I1
Gateway of last resort is 1.1.11.254 to network 0.0.0.0
1.0.0.0/24 is subnetted, 2 subnets
C 1.1.11.0 is directly connected, FastEthernet0/0.11
C 1.1.111.0 is directly connected, FastEthernet0/0.111
2.0.0.0/24 is subnetted, 1 subnets
S 2.2.2.0 [1/0] via 1.1.12.2
3.0.0.0/24 is subnetted, 1 subnets
S 3.3.3.0 [1/0] via 1.1.111.2
S* 0.0.0.0/0 [1/0] via 1.1.11.254
R1#sh ip ospf database
OSPF Router with ID (1.1.111.1) (Process ID 1)
Router Link States (Area 0)
Link ID ADV Router Age Seq# Checksum Link count
1.1.111.1 1.1.111.1 1524 0x80000028 0x0072CB 1
1.1.111.2 1.1.111.2 1473 0x80000028 0x00131F 1
Net Link States (Area 0)
Link ID ADV Router Age Seq# Checksum
1.1.111.2 1.1.111.2 1473 0x80000027 0x000F38
Type-5 AS External Link States
Link ID ADV Router Age Seq# Checksum Tag
0.0.0.0 1.1.111.1 1524 0x80000027 0x00CB4E 1
3.3.3.0 1.1.111.2 141 0x80000001 0x000A57 3489660929
5.5.5.0 1.1.111.2 141 0x80000001 0x00C199 3489660929
R1#
On Thu, Aug 14, 2008 at 10:39 AM, Jeff Kell <jeff-kell at utc.edu> wrote:
> Nick Griffin wrote:
>
>> I've figured out how to exchange routes between VRF's with the bgp address
>> family configuration coupled with redistribute static|connected, etc
>> however
>> I'm trying to propagate this information and I'm having problems getting
>> it
>> to work as desired.
>>
>
> I'll take a "guess" at your problem...
>
> If you have everything "centralized" into one PE doing your intra-VRF iBGP,
> and also providing VRF-specific routing processes...
>
> The intra-VRF routes are propagated locally via iBGP and the vrf
> route-target import/export specifications.
>
> To redistributed "learned" routes from the VRF-specific routing processes
> into the iBGP mesh, you must 'redistribute [protocol]' in the BGP
> address-family ipv4 vrf specification.
>
> To redistributed "learned" routes from the iBGP import/export process back
> into the VRF-specific routing processes, you must 'redistribute bgp [asn]'
> in the routing process vrf specification.
>
> Jeff
>
>
>
More information about the cisco-nsp
mailing list