08-23-2011 04:57 AM - edited 03-04-2019 01:22 PM
I have configured two vrf LI and OAM on a 7609 router. and inter vrf routing is enabled. I am able to see corresponding routes in either vrf.
Basically two connected routes from OAM vrf are leaked into LI vrf and vice versa. The following output is seen on across LI vrf for interface routes of OAM vrf.
OKH-MAX_R1#show ip cef vrf LI 10.181.172.194 detail
10.181.172.194/32, epoch 6, flags receive
Interface source: Vlan234
receive for Vlan234
OKH-MAX_R1#show ip cef vrf LI 10.181.172.130 detail
10.181.172.130/32, epoch 6, flags receive
Dependent covered prefix type cover need deagg cover 10.181.172.128/26
Interface source: Vlan210
receive for Vlan210
Vlan 234 and Vlan 210 are part of OAM vrf. I am able to ping 10.181.172.194 from LI vrf but not able to ping 10.181.172.130. The only difference between the two output is highlighted above. Does this output has anything to do with the issue.
08-23-2011 06:22 AM
Can you post the configs for all 3 vrfs and vlans?
08-23-2011 10:54 PM
Below is the configuration for both VRF LI & OAM
ip vrf LI
rd 64800:8000
route-target export 64800:800
route-target import 64800:800
route-target import 64800:260
maximum routes 1000 80
!
!
ip route vrf LI 10.51.16.0 255.255.255.240 10.50.27.2
ip route vrf LI 192.168.163.0 255.255.255.224 10.50.27.2
!
router bgp 64800
!
address-family ipv4 vrf LI
no synchronization
redistribute connected
redistribute static
exit-address-family
!
Controller STM1.AU4/TUG3 3/0/0.1/1
!
interface Serial3/0/0.1/1/2/2:0
ip vrf forwarding LI
ip address 10.50.27.1 255.255.255.252
end
Inter-vrf Route Information
Routing Table: LI
Routing entry for 10.181.172.128/26
Known via "bgp 64800", distance 20, metric 0 (connected, via interface), type external
Routing Descriptor Blocks:
* directly connected, via Vlan210
Route metric is 0, traffic share count is 1
AS Hops 0
Routing Table: LI
Routing entry for 10.181.172.128/26
Known via "bgp 64800", distance 20, metric 0 (connected, via interface), type external
Routing Descriptor Blocks:
* directly connected, via Vlan210
Route metric is 0, traffic share count is 1
AS Hops 0
=============================================================================================
ip vrf OAM
rd 64800:4000
export map OAM_LI
route-target export 64800:400
route-target import 64800:400
route-target import 64800:1400
route-target import 64800:800
route-target import 64800:250
maximum routes 2000 warning-only
!
interface Vlan234
description GCS01_OKHLA_O&M
ip vrf forwarding OAM
ip address 10.181.172.194 255.255.255.192
standby 234 ip 10.181.172.193
standby 234 priority 110
standby 234 preempt
end
interface Vlan210
description MSS03_OKH_O&M
ip vrf forwarding OAM
ip address 10.181.172.130 255.255.255.192
standby 32 ip 10.181.172.129
standby 32 priority 110
standby 32 preempt
end
router bgp 64800
!
address-family ipv4 vrf OAM
no synchronization
redistribute connected
redistribute static
exit-address-family
route-map OAM_LI permit 10
match ip address 40
set extcommunity rt 64800:260 additive
!
route-map OAM_LI permit 20
match ip address 50
set extcommunity rt 64800:270 additive
!
Standard IP access list 40
10 permit 10.181.172.128, wildcard bits 0.0.0.63 (1 match)
20 permit 10.181.172.192, wildcard bits 0.0.0.63 (1 match)
Inter-vrf route information
Routing Table: OAM
Routing entry for 10.50.27.1/32
Known via "connected", distance 0, metric 0 (connected)
Redistributing via bgp 64800
Routing Descriptor Blocks:
* directly connected, via Serial3/0/0.1/1/2/2:0
Route metric is 0, traffic share count is 1
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide