[j-nsp] BGP session is not coming up

[Truman Boyes]

You might want to turn on more traceoptions. You are receiving a  
notification message which should indicate the problem. The  
notification code and subcode will help to find out the issue.


Truman Boyes

On 22/07/2009, at 3:16 AM, Matthias Gelbhardt wrote:

> Hi!
>
> After deleting the local-address (and testing with multihop) I get
>
> Jul 22 09:13:41.322465 advertising receiving-speaker only capabilty  
> to neighbor x.x.x.x (External AS xx)
> Jul 22 09:13:41.323342 bgp_send: sending 59 bytes to x.x.x.x  
> (External AS xx)
> Jul 22 09:13:41.323954
> Jul 22 09:13:41.323954 BGP SEND x.x.x.x+52277 -> x.x.x.x+179
> Jul 22 09:13:41.325172 BGP SEND message type 1 (Open) length 59
> Jul 22 09:13:41.327835
> Jul 22 09:13:41.327835 BGP RECV x.x.x.x+179 -> x.x.x.x+52277
> Jul 22 09:13:41.329110 BGP RECV message type 1 (Open) length 29
> Jul 22 09:13:41.329866
> Jul 22 09:13:41.329866 BGP RECV x.x.x.x+179 -> x.x.x.x+52277
> Jul 22 09:13:41.331374 BGP RECV message type 3 (Notification) length  
> 21
>
> The strange thing: That has stopped working out of the blue. As this  
> is a provider, we are unable to get the other side.
>
> Matthias
>
> Am 22.07.2009 um 09:04 schrieb Muhammad Aamir:
>
>> Dear matthias,
>>
>> Have u tried this with "multihop", Because you have used local- 
>> address in your ebgp config. If local address is your loopback  
>> interface then you need to configure multihop. Also please share  
>> the remote end config as well if possible.
>>
>> Regards.
>>
>> Aamir
>>
>> On Wed, Jul 22, 2009 at 12:55 PM, Matthias Gelbhardt <matthias at commy.de 
>> > wrote:
>> Hi!
>>
>> We have a problem with a BGP session. The session is not coming up,  
>> and I dont know why. It is a eBGP session:
>>
>> Log:
>>
>> Jul 22 08:30:08  muenster /kernel: tcp_auth_ok: Packet from x.x.x.x: 
>> 179 missing MD5 digest
>>
>> tracelog:
>>
>> Jul 22 08:50:16.426122 bgp_connect_complete: error connecting to  
>> x.x.x.x (External AS x): Socket is not connected
>>
>> tcpdump;
>>
>> 08:49:07.632649 Out IP x.x.x.x.60582 > x.x.x.x.179: S  
>> 594093001:594093001(0) win 16384 <mss 1460,nop,wscale  
>> 0,nop,nop,timestamp[|tcp]>
>>
>> config:
>>
>> group external {
>>   type external;
>>   neighbor xx {
>>       description uplink_;
>>       local-address xx;
>>       import import_bgp_;
>>       inactive: authentication-key "$9$u-xxx"; ## SECRET-DATA
>>       export [ export_prepend export_bgp_external ];
>>       peer-as xx;
>>   }
>> }
>>
>> Any ideas?
>>
>> Leaving the MD5 does not work, I even have restartet the routing  
>> process with no luck.
>>
>> Matthias
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>