RE: BGP route not synchronized -- WEIRED! Check R7 router-ids

From: support@experttraining.net
Date: Fri May 09 2003 - 16:25:20 GMT-3


No, the bgp router id and the ospf router id are not the same on R7. ( See
exhibits for results)

I thought RFCs were just a waste of time reading for the lab, obviously NOT
!!!!!

MUCH THANKS to every one, I shall start reading RFCs are part of my daily
preparation.

Any suggestions for a RFC must read list. Obviously I cannot read everything
that was

ever written.

Cheers,

Pierre-Alex

Exhibit 9 -- R7 full configurations (before implementing your suggestions)
Exhibit10 -- R1 bgp table after making R7 bgp ID and OSPF ID the SAME.

=============================Exhibit 9 ====================================

R7#show run
Building configuration...

Current configuration : 2076 bytes
!
version 12.1
no service single-slot-reload-enable
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
service udp-small-servers
service tcp-small-servers
!
hostname R7
!
logging rate-limit console 10 except errors
!
ip subnet-zero
no ip finger
no ip domain-lookup
!
ip multicast-routing
cns event-service server
!
!
!
!
!
interface Loopback0
 ip address 7.7.7.7 255.255.255.255
!
interface Loopback100
 ip address 10.0.70.1 255.255.255.255
!
interface Serial0
 ip address 172.16.10.1 255.255.255.252
 ip pim sparse-dense-mode
 no fair-queue
 clockrate 2000000
!
interface Serial1
 ip address 10.7.0.1 255.255.255.252
 ip pim sparse-dense-mode
 clockrate 2000000
!
interface TokenRing0
 ip address 10.0.0.7 255.255.255.0
 ring-speed 16
!
router eigrp 100
 network 10.6.0.0 0.0.255.255
 network 10.7.0.0 0.0.0.3
 network 10.7.0.0 0.0.255.255
 auto-summary
 no eigrp log-neighbor-changes
!
router ospf 100
 router-id 7.7.7.7
 log-adjacency-changes
 redistribute bgp 65531 metric 100 metric-type 1 subnets tag 7
 network 10.0.0.0 0.0.0.255 area 0
 network 10.0.70.1 0.0.0.0 area 0
!
router bgp 65531
 bgp log-neighbor-changes
 neighbor 10.7.0.2 remote-as 65531
 neighbor 10.100.0.1 remote-as 65531
 neighbor 10.100.0.1 update-source Loopback100
 neighbor 10.100.0.1 next-hop-self
 neighbor 10.100.0.1 soft-reconfiguration inbound
 neighbor 10.200.0.1 remote-as 65531
 neighbor 10.200.0.1 next-hop-self
 neighbor 10.200.0.1 soft-reconfiguration inbound
 neighbor 172.16.10.2 remote-as 1
!
ip kerberos source-interface any
ip classless
no ip http server
!
ip mrm manager test1
 manager Serial0 group 239.5.6.7
 beacon interval 2 holdtime 1800
 senders 7
 receivers 8 sender-list 7
ip mrm manager test2
 manager Serial0 group 239.8.9.0
 senders 10
 receivers 11 sender-list 10
!
access-list 7 permit 172.16.10.11
access-list 8 permit 192.168.0.11
access-list 10 permit 172.16.6.1
access-list 11 permit 192.168.0.11
!
!
line con 0
 transport input none
 escape-character 7
line aux 0
 no exec
 transport input all
line vty 0 4
 login
!
end

==========================Exhibit 10 =====================================

R1#show ip bgp
BGP table version is 2, local router ID is 1.1.1.1
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network Next Hop Metric LocPrf Weight Path
*>i188.1.2.0/24 10.0.70.1 0 100 0 1 i
R1#show ip bgp 188.1.2.0
BGP routing table entry for 188.1.2.0/24, version 2
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  Advertised to peer-groups:
     Remote
  1
    10.0.70.1 (metric 7) from 10.0.70.1 (7.7.7.7)
      Origin IGP, metric 0, localpref 100, valid, internal, synchronized,
best
R1#



This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:40 GMT-3