GroupStudy.com GroupStudy.com - A virtual community of network engineers
 Home  BookStore  StudyNotes  Links  Archives  StudyRooms  HelpWanted  Discounts  Login
Rép. : BGP Route-Reflector Peers posted 01/15/2001
[Chronological Index] [Thread Index] [Top] [Date Prev][Date Next] [Thread Prev][Thread Next]


Hi,

ONLY  ONE  Route Reflector  by  Cluster-ID.

RR is use for reduce peering.

In large BGP network, use confederation , and RR in each confederation for reduce peering.

Best Regard
Thierry

>>> "Horton, Jeff" <jhorton@xxxxxxxx> 15/01/01 14h46 >>>
Hello all,

I was trying to build a BGP scenario in the lab where I had two routers, R1
& R2 that are both route reflectors. R3, R4, and R5 are route-reflector
clients. R1 and R2 are both in cluster ID 100. Peer groups are set up for
both route reflectors and route reflector clients. The idea was that should
R1 or R2 fail, the routes would still be reflected to the clients. R1 and R2
are able to ping R3, R4, and R5 just fine.

Loopbacks are 1.1.1.1, 2.2.2.2, 3.3.3.3, etc. On RR clients R3 , R4, and R5
I also have 30.30.30.3, 40.40.40.4, 50.50.50.5 that are advertised in BGP. I
seem to have mixed results and I am not quite sure where I have gone wrong.
R3 routes seem to be reflected but not R4 or R5. 

I would appreciate suggestions. 

Thanks,

Jeff

R1
router ospf 1
 network 1.1.1.0 0.0.0.255 area 0
 network 172.168.14.0 0.0.0.255 area 0
 network 172.168.125.0 0.0.0.255 area 0
!
router bgp 1
 no synchronization
 bgp cluster-id 100
 neighbor reflectors peer-group
 neighbor reflectors remote-as 1
 neighbor reflectors update-source Loopback0
 neighbor clients peer-group
 neighbor clients remote-as 1
 neighbor clients ebgp-multihop 255
 neighbor clients update-source Loopback0
 neighbor clients route-reflector-client
 neighbor 2.2.2.2 peer-group reflectors
 neighbor 3.3.3.3 peer-group clients
 neighbor 4.4.4.4 peer-group clients
 neighbor 5.5.5.5 peer-group clients
 no auto-summary
!

R2
router ospf 1
 network 2.2.2.0 0.0.0.255 area 0
 network 172.168.125.0 0.0.0.255 area 0
!
router bgp 1
 no synchronization
 bgp cluster-id 100
 neighbor clients peer-group
 neighbor clients remote-as 1
 neighbor clients update-source Loopback0
 neighbor clients route-reflector-client
 neighbor reflectors peer-group
 neighbor reflectors remote-as 1
 neighbor reflectors update-source Loopback0
 neighbor 1.1.1.1 peer-group reflectors
 neighbor 3.3.3.3 peer-group clients
 neighbor 4.4.4.4 peer-group clients
 neighbor 5.5.5.5 peer-group clients
 no auto-summary
!

R3
router ospf 1
 network 3.3.3.0 0.0.0.255 area 0
 network 192.168.23.0 0.0.0.255 area 0
!
router bgp 1
 no synchronization
 network 3.3.3.0 mask 255.255.255.0
 network 30.30.30.0 mask 255.255.255.0
 neighbor 1.1.1.1 remote-as 1
 neighbor 1.1.1.1 update-source Loopback0
 neighbor 1.1.1.1 next-hop-self
 neighbor 2.2.2.2 remote-as 1
 neighbor 2.2.2.2 update-source Loopback0
 neighbor 2.2.2.2 next-hop-self
 no auto-summary

R4
router ospf 1
 network 4.4.4.0 0.0.0.255 area 0
 network 172.168.14.0 0.0.0.255 area 0
 network 192.168.23.0 0.0.0.255 area 0
!
router bgp 1
 no synchronization
 network 4.4.4.0 mask 255.255.255.0
 network 40.40.40.4 mask 255.255.255.0
 neighbor 1.1.1.1 remote-as 1
 neighbor 1.1.1.1 update-source Loopback0
 neighbor 1.1.1.1 next-hop-self
 neighbor 2.2.2.2 remote-as 1
 neighbor 2.2.2.2 update-source Loopback0
 neighbor 2.2.2.2 next-hop-self
 no auto-summary

R5
router ospf 1
 network 5.5.5.0 0.0.0.255 area 0
 network 172.168.125.0 0.0.0.255 area 0
!
router bgp 1
 no synchronization
 network 5.5.5.0 mask 255.255.255.0
 network 50.50.50.0 mask 255.255.255.0
 neighbor 1.1.1.1 remote-as 1
 neighbor 1.1.1.1 update-source Loopback0
 neighbor 1.1.1.1 next-hop-self
 neighbor 2.2.2.2 remote-as 1
 neighbor 2.2.2.2 update-source Loopback0
 neighbor 2.2.2.2 next-hop-self
 no auto-summary



_______________________________________________________
To unsubscribe from the CCIELAB list, send a message to
majordomo@xxxxxxxxxxxxxx with the body containing:
unsubscribe ccielab

_______________________________________________________
To unsubscribe from the CCIELAB list, send a message to
majordomo@xxxxxxxxxxxxxx with the body containing:
unsubscribe ccielab