Le 26 avr. 06 ` 18:49, Claudio Jeker a icrit :
On Wed, Apr 26, 2006 at 04:29:19PM +0200, Xavier Beaudouin wrote:
Hello,
Stupid question indeed, but I see we can set a route reflector server
in bgpd.conf, but there is not hint on how to set a router reflector
client in it.
The clients don't need a special config. Just point them to your
route-reflector(s). All the magic is done on the servers.
Hum... Doesn't seems to work :
neighbor 80.67.ZZZ.X {
descr "PouIX_routecollector"
remote-as 65432
local-address 80.67.ZZZ.AA
announce self
set localpref 490
passive
}
log :
Apr 27 12:02:47 core-rdb-1 bgpd[20023]: neighbor 80.67.ZZZ.X
(PouIX_routecollector): state change None -> Idle, reason: None
Apr 27 12:02:47 core-rdb-1 bgpd[20023]: neighbor 80.67.ZZZ.X
(PouIX_routecollector): state change Idle -> Active, reason: Start
Apr 27 12:03:10 core-rdb-1 bgpd[22756]: RDE reconfigured
Apr 27 12:04:25 core-rdb-1 bgpd[20023]: neighbor 80.67.ZZZ.X
(PouIX_routecollector): state change Active -> OpenSent, reason:
Connection opened
Apr 27 12:04:25 core-rdb-1 bgpd[20023]: neighbor 80.67.ZZZ.X
(PouIX_routecollector): state change OpenSent -> OpenConfirm, reason:
OPEN message received
Apr 27 12:04:25 core-rdb-1 bgpd[20023]: neighbor 80.67.ZZZ.x
(PouIX_routecollector): state change OpenConfirm -> Established,
reason: KEEPALIVE message received
Apr 27 12:04:25 core-rdb-1 bgpd[20023]: neighbor 80.67.ZZZ.X
(PouIX_routecollector): state change Established -> Idle, reason:
Fatal error
The route reflector is a Zebra / Quagga... Maybe there is a problem
somewhere ?
/Xavier
