The one I sent you. Configure one end as passive and that end will
never attempt to open TCP connection - or use inbound ACL's.
On Tue, Oct 13, 2009 at 14:37, Ramanpreet Singh
<sikandar.raman_at_gmail.com> wrote:
> so what is the solution?
>
> On Tue, Oct 13, 2009 at 7:57 AM, Bryan Bartik <bbartik_at_ipexpert.com> wrote:
>>
>> I don't think collision detection happens every time. Section 6.8 of RFC
>> 4271 states:
>>
>> "Note that a connection collision cannot be detected with connections that
>> are in Idle, Connect, or Active states."
>>
>> I think some further debugging and packet captures would be required to
>> determine if the router is following the RFC or not.
>>
>> On Tue, Oct 13, 2009 at 3:17 AM, Marcel Lammerse <m.lammerse_at_mac.com>
>> wrote:
>>
>> > I just labbed this up and, to my surprise, I got the same results.
>> > According to rfc 4271, the bgp router-id should determine which side
>> > becomes
>> > the server and which becomes the client during a connection collision.
>> > This
>> > should be a deterministic process. But in my lab it made no difference
>> > and I
>> > got random results. Why?
>> >
>> > The neighbor transport command seems to lock the client/server role
>> > down.
>> > The passive side is the server, the active side is the client.
>> >
>> >
>> > On 13/10/2009, at 15:57 , Marko Milivojevic wrote:
>> >
>> > B Have you tried:
>> >>
>> >> neighbor X.X.X.X transport connection-mode active
>> >>
>> >> Out of curiosity - is this a lab requirement, or are you trying to do
>> >> something weird in real life? :-)
>> >>
>> >> --
>> >> Marko
>> >> CCIE #18427 (SP)
>> >> My network blog: http://cisco.markom.info/
>> >>
>> >> On Tue, Oct 13, 2009 at 03:49, ospfv2 <ospfv2_at_gmail.com> wrote:
>> >>
>> >>> Hi Experts
>> >>>
>> >>> afaik to make bgp router as tcp client, we can set the router-id
>> >>> higher or put update-source command. is that correct ?
>> >>>
>> >>> but i found out if we reload each of the router,sometime the client
>> >>> become the server.
>> >>> how to make the assigment permanent ?
>> >>>
>> >>> any comments ?
>> >>>
>> >>> thx
>> >>>
>> >>>
>> >>>
>> >>> R1# sh run
>> >>> interface FastEthernet0/0
>> >>> B ip address 192.168.1.1 255.255.255.0
>> >>>
>> >>> router bgp 100
>> >>> B no synchronization
>> >>> B neighbor 192.168.1.2 remote-as 200
>> >>> B no auto-summary
>> >>>
>> >>> R1#sh ip bgp nei | in port
>> >>> Local host: 192.168.1.1, Local port: 179
>> >>> Foreign host: 192.168.1.2, Foreign port: 11001
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> R2#sh run
>> >>> interface FastEthernet0/0
>> >>> B ip address 192.168.1.2 255.255.255.0
>> >>>
>> >>> router bgp 200
>> >>> B no synchronization
>> >>> B neighbor 192.168.1.1 remote-as 100
>> >>> B neighbor 192.168.1.1 update-source FastEthernet0/0
>> >>> B no auto-summary
>> >>>
>> >>>
>> >>> R2# sh ip bgp nei | in port
>> >>> Local host: 192.168.1.2, Local port: 11001
>> >>> Foreign host: 192.168.1.1, Foreign port: 179
>> >>>
>> >>
>> >>
>> >> Blogs and organic groups at http://www.ccie.net
>> >>
>> >> _______________________________________________________________________
>> >> Subscription information may be found at:
>> >> http://www.groupstudy.com/list/CCIELab.html
>> >>
>> >
>> >
>> > Blogs and organic groups at http://www.ccie.net
>> >
>> > _______________________________________________________________________
>> > Subscription information may be found at:
>> > http://www.groupstudy.com/list/CCIELab.html
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>>
>> --
>> Bryan Bartik
>> CCIE #23707 (R&S), CCNP
>> Sr. Support Engineer - IPexpert, Inc.
>> URL: http://www.IPexpert.com
>>
>>
>> Blogs and organic groups at http://www.ccie.net
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Tue Oct 13 2009 - 14:40:13 ART
This archive was generated by hypermail 2.2.0 : Sun Nov 01 2009 - 07:50:59 ART