From: damien (damien@xxxxxxxxxxx)
Date: Wed Dec 13 2000 - 11:24:01 GMT-3
I think it makes sense that it will transition from Idle to the first state,
i.e. connect (the first state after kick off), it has to start to know its
configured wrong......and the connect state is only waiting on the TCP
connect to set up.....so the fact that it does not get by this state makes
sense...........it should eventually fall back to idle........it doesn't
really explain where the decision process decides that an EBGP neighbor is
not directly connected, it doesn't really explain in Halabi or RFC
1771....but it obviously has something to do with the route table...
----- Original Message -----
From: "Robert DeVito" <robertdevito@hotmail.com>
To: <ccielab@groupstudy.com>
Sent: Wednesday, December 13, 2000 7:48 AM
Subject: BGP ebgp-multihop
> Has anyone noticed if your ebgp router is not directly connected, they
> become in the "connect" state even if you do no define the ebgp-multihop
> command. Thoughts?
>
> Thank you,
> Robert DeVito
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:26:02 GMT-3