[j-nsp] BGP over GRE

[Scott Morris]

Hehehe...  Correct.  That was when I manually cleared things out and started
the log.  My point being that NOTHING is getting added into this log despite
the traceoptions!  :)

Scott 

-----Original Message-----
From: Guy Davies [mailto:aguydavies at gmail.com] 
Sent: Friday, May 04, 2007 2:30 PM
To: swm at emanon.com
Cc: Kristian Larsson; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP over GRE

Hi Scott,

You are right.  I'm obviously not thinking clearly.  But it appears to say
that it was administratively reset and reset by the management session...

> Apr 18 23:12:37.048543 bgp_peer_mgmt_clear: NOTIFICATION sent to
> 10.255.255.2 (External AS 7963): code 6 (Cease) subcode 4 
> (Administratively Reset), Reason: Management session cleared BGP 
> neighbor

That *looks* like a 'clear bgp neighbor 10.255.255.2'.

Rgds,

Guy

On 04/05/07, Scott Morris <swm at emanon.com> wrote:
> How are you reading that as the other end?  BGP SEND means that my end 
> is sending it out, no?  The administrative clearing is when I issued a 
> clear command on the Juniper side.  The Cisco logs are only showing 
> and authentication mismatch (whether we have authentication configured or
not).
>
> I'll try to get access to the far end router and see if I can get more 
> details from the Cisco side, but there doesn't appear to be much of 
> anything there.
>
> Scott
>
> -----Original Message-----
> From: Guy Davies [mailto:aguydavies at gmail.com]
> Sent: Friday, May 04, 2007 9:10 AM
> To: swm at emanon.com
> Cc: Kristian Larsson; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] BGP over GRE
>
> Hi Scott
>
> On 04/05/07, Scott Morris <swm at emanon.com> wrote:
> > Notice the traceoptions in the config there.  Here is the ENTIRE 
> > file (yes, the date/time on the router is accurate):
> > smorris at Emanon-Edge> show log STDIO
> > Apr 13 15:48:53 trace_on: Tracing to "/var/log/STDIO" started Apr 13
> > 20:42:27.099946 bgp_peer_mgmt_clear: NOTIFICATION sent to
> > 10.255.255.2 (External AS 7963): code 6 (Cease) subcode 4 
> > (Administratively Reset), Reason: Management session cleared BGP 
> > neighbor Apr 13 20:42:27.101386 bgp_send: sending 21 bytes to
> > 10.255.255.2 (External AS 7963) Apr 13 20:42:27.101410 Apr 13 
> > 20:42:27.101410 BGP SEND (null) -> 10.255.255.2 Apr 13 
> > 20:42:27.103228 BGP SEND message type 3 (Notification) length 21 Apr 
> > 13
> > 20:42:27.103288 BGP SEND Notification code 6 (Cease) subcode 4 
> > (Administratively Reset) Apr 13 20:42:27.103566 bgp_send: sending 21 
> > bytes to 10.255.255.2 (External AS 7963) failed: Bad file descriptor 
> > Apr 18 23:12:37.048543 bgp_peer_mgmt_clear: NOTIFICATION sent to
> > 10.255.255.2 (External AS 7963): code 6 (Cease) subcode 4 
> > (Administratively Reset), Reason: Management session cleared BGP 
> > neighbor Apr 18 23:12:37.048719 bgp_send: sending 21 bytes to
> > 10.255.255.2 (External AS 7963) Apr 18 23:12:37.048742 Apr 18
> > 23:12:37.048742 BGP SEND (null) -> 10.255.255.2 Apr 18 
> > 23:12:37.048788 BGP SEND message type 3 (Notification) length 21 Apr 
> > 18
> > 23:12:37.048807 BGP SEND Notification code 6 (Cease) subcode 4 
> > (Administratively Reset) Apr 18 23:12:37.049050 bgp_send: sending 21 
> > bytes to 10.255.255.2 (External AS 7963) failed: Bad file descriptor
>
> Ah, this is a new error.  It's saying that the *far end* is closing 
> the session.  You'll need to look at the logs on the far end to see 
> what the problem might be :-)
>
> Rgds,
>
> Guy
>
>