BGP PEERING ESTABLISHED BUT ROUTES AREN'T SHOWING AS BEST PATH

Hello guys,

Stuck with a problem here. The portion of the diagram with the
issue(R12--back-to-back frame relay-R6)..

R12 and R6 have an established EBGP connection via their loopbacks.Both
routers have a static route to each other's loopback address. I advertise
some prefix from R12,they are received by R6 but aren't showing as best
path,hence they aren't getting installed in the routing table. Here are the
relevant sections of the config:

*R6
interface Loopback1
 ip address 6.6.6.6 255.255.255.0
 ip ospf network point-to-point
 ip ospf 1 area 0
!
interface FastEthernet0/0.68
 encapsulation dot1Q 68
 ip address 68.68.68.6 255.255.255.0
 ip ospf 1 area 0
!
!
interface Serial1/0
 ip address 62.62.62.6 255.255.255.0
 encapsulation frame-relay
 no keepalive
 serial restart-delay 0
 frame-relay interface-dlci 602
!
router bgp 100
 no synchronization
 bgp log-neighbor-changes
 network 100.100.100.0 mask 255.255.255.0
 timers bgp 20 60 20
 neighbor 1.1.1.1 remote-as 100
 neighbor 1.1.1.1 update-source Loopback1
 neighbor 1.1.1.1 next-hop-self
 neighbor 12.12.12.12 remote-as 54
 neighbor 12.12.12.12 ttl-security hops 5
 neighbor 12.12.12.12 update-source Loopback1
 no auto-summary
!
ip forward-protocol nd
ip route profile
ip route 12.12.12.0 255.255.255.0 62.62.62.12*

* R12
interface Loopback0
 ip address 12.12.12.12 255.255.255.0
!
interface Loopback1
 ip address 200.200.1.1 255.255.255.0
!
interface Loopback2
 ip address 200.200.2.1 255.255.255.0
!
interface Loopback3
 ip address 200.200.3.1 255.255.255.0
!
interface Serial1/0
 ip address 62.62.62.12 255.255.255.0
 encapsulation frame-relay
 no keepalive
 serial restart-delay 0
 frame-relay interface-dlci 602
!
!
router bgp 54
 no synchronization
 bgp router-id 12.12.12.12
 bgp log-neighbor-changes
 network 200.200.1.0
 network 200.200.2.0
 network 200.200.3.0
 timers bgp 20 60 20
 neighbor 6.6.6.6 remote-as 100
 neighbor 6.6.6.6 ttl-security hops 5
 neighbor 6.6.6.6 update-source Loopback0
 no auto-summary
!
ip forward-protocol nd
ip route 6.6.6.0 255.255.255.0 62.62.62.6
!

R12
  Network Next Hop Metric LocPrf Weight Path
* 100.100.100.0/24 6.6.6.6 0 0 100 i
*> 200.200.1.0 0.0.0.0 0 32768 i
*> 200.200.2.0 0.0.0.0 0 32768 i
*> 200.200.3.0 0.0.0.0 0 32768 i

R6
  Network Next Hop Metric LocPrf Weight Path

* 200.200.1.0 12.12.12.12 0 0 54 i
* 200.200.2.0 12.12.12.12 0 0 54 i
* 200.200.3.0 12.12.12.12 0 0 54 i

*
There's full layer-2 reachability but the bgp table shows the next hop as
"inaccessible" even though there exists a route to the next hop in the
routing table...It's a bit weird for me.*
*
*

R6(config-router)#do sh ip bgp 200.200.1.0

BGP routing table entry for 200.200.1.0/24, version 0
Paths: (1 available, no best path)
  Not advertised to any peer
  54
    12.12.12.12 (inaccessible) from 12.12.12.12 (12.12.12.12)
      Origin IGP, metric 0, localpref 100, valid, external

R6(config-router)#do sh ip route 12.12.12.12
Routing entry for 12.12.12.0/24
  Known via "static", distance 1, metric 0
  Routing Descriptor Blocks:
  * 62.62.62.12
      Route metric is 0, traffic share count is 1

R6(config-router)#do ping 12.12.12.12

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 12.12.12.12, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 8/48/120 ms
*

Thank you.

Ty.

Blogs and organic groups at http://www.ccie.net
Received on Sat Apr 06 2013 - 20:47:09 ART