[j-nsp] BGP over GRE

[Scott Morris]

Well, how entirely psychotic is that???  :)

Adding the peer-as to the neighbor (not group) AND multihop made it come up.

#$*&#$*&ing things.  Thanks!  I'll have to keep that in my reprotoire of
oddball troubleshooting magic!

Thanks everyone for their help and questions making sure >I< wasn't going
crazy!

Scott
 

-----Original Message-----
From: Kevin Day [mailto:toasty at dragondata.com] 
Sent: Friday, May 04, 2007 3:52 PM
To: swm at emanon.com
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] BGP over GRE


On May 4, 2007, at 7:57 AM, Scott Morris wrote:


> Protocols {
>   bgp  {
>         group STDIO {
>             type external;
>             traceoptions {
>                 file STDIO;
>                 flag packets send receive detail;
>             }
>             local-address 10.255.255.1;
>             import No-Routes-In;
>             authentication-key "$9$Opu01IcreWLxdhSs4aZq.5QF/A0IEy"; ## 
> SECRET-DATA
>             export BadMyLinks;
>             peer-as 7963;
>             neighbor 10.255.255.2;
>         }
>     }
>
>
> Yes, my autonomous-system is defined...  My other eBGP peers work 
> perfectly fine (one directly connected, two multihop) without issue.
>

The only reasons I've sen for the "no group for x.x.x.x" are:

1) The BGP traffic is being received on an interface different from where
it's expecting, based on where local-address/neighbor IP is set when it's
not multihop. That doesn't seem too likely here, but it's bit me before.
2) There's already a BGP session for that IP up
3) Your AS numbers aren't matched up. You get a correct message if you apply
the remote-as line to the neighbor section itself, but a "no group" message
if the peer-as line is attached to a group instead.

Do you have the config on the other end? I'd check to make sure their
local-as and remote-as are correct?

Or you might just have some gremlins in your config that a "commit full"
might purge? :)

-- Kevin