Hi ,
I have a simple BGP Query , I have got 2 routers : r2 and r5 , which are
connected to each other via serial link and are on different AS , there
routing configs are as follows :
for r2 :
interface Loopback0
ip address 202.202.1.1 255.255.255.255
router ospf 100
log-adjacency-changes
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 111
no synchronization
bgp router-id 202.202.1.1
bgp log-neighbor-changes
network 202.202.1.1 mask 255.255.255.255
neighbor 101.101.101.77 remote-as 4799
neighbor 101.101.101.77 ebgp-multihop 5
neighbor 101.101.101.77 update-source Loopback0
!
and for R5 :
interface Loopback0
ip address 101.101.101.77 255.255.255.255
!
router ospf 100
log-adjacency-changes
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 4799
no synchronization
bgp router-id 101.101.101.77
bgp log-neighbor-changes
network 101.101.101.77 mask 255.255.255.255
neighbor 202.202.1.1 remote-as 111
neighbor 202.202.1.1 ebgp-multihop 5
neighbor 202.202.1.1 update-source Loopback0
!
when i see there routing tables , this output is as follows :
on R2
Network Next Hop Metric LocPrf Weight Path
* 101.101.101.77/32
101.101.101.77 0 0 4799 i
*> 202.202.1.1/32 0.0.0.0 0 32768 i
r2#
r2#
On r5 it is :
Network Next Hop Metric LocPrf Weight Path
*> 101.101.101.77/32
0.0.0.0 0 32768 i
*> 202.202.1.1/32 202.202.1.1 0 0 111 i
r5#
why is the route of : * 101.101.101.77/32 not coming as the best path
with > on R2 as in the table of r5 it is displaying the path of *>
202.202.1.1/32 as best path ,
I dont want to do redistribution of BGP in OSPF and plus I dont want to give
any static routes to the peers , as they are getting the path of destination
loopback is known via OSPF , and the routes are there in the routing table .
Is there any other solution for this solution , by peering with loopbacks .
thanks,
Navin Parwal
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=61756&t=61756
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
