IOS next-hop trouble

[Jesper Skriver]

On Fri, Mar 29, 2002 at 03:04:57PM +0100, Erik Bos wrote:
> On Fri, Mar 29, 2002 at 04:13:52AM -0500, owens@nysernet.org wrote:
> > On Fri, 29 Mar 2002, Pim van Pelt wrote:
> > > The logs state:
> > > Mar 28 22:47:36 fe2-0.4.sara.ams-ix.network.bit.nl 2288: 3d12h:
> > > %BGP-6-NEXTHOP: Invalid next hop (0.0.0.0) received from
> > > 2001:7F8:1::A500:3265:1: martian next hop
> > > 
> > > for our peerings the AMS-IX. How can I solve this. Clearly IPv6
> > > BGP has nothing to do with the IPv4 nexthop so the Juniper at :3265:1
> > > leaves it empty. Why does my box complain ?
> > 
> > If the Juniper is running JUNOS 5.1 this is a known bug; I don't have the
> > PR number handy but I can get it from my archives tomorrow. It appeared
> > cosmetic but we did fix it by upgrading to 5.2. 
> > 
> > However, that fix, or some other related change in 5.2, will tickle a bug
> > in some versions of IOS and cause v4 multicast BGP to break. The symptom
> > we observed was the BGP session establishing and immediately closing down,
> > but working once we disabled multicast. We fixed that by upgrading that
> > particular Cisco, which was on a ~1 year old IOS; if your boxes are all
> > recent you shouldn't have a problem. I can dig up that bug number as well
> > if you're interested.
> 
> A. I'd like to know both PRs. We're 2001:7F8:1::A500:3265:1 and are running
> JUNOS 5.1R1.4. We can't upgrade to 5.2 yet of PRs that are fixed in this
> release but are not yet fixed in the latest version of 5.2.

5.1R3.4 is out, it's the latest bugfix release in the 5.1 branch, we're
running it with success, but without IPv6 though.

/Jesper

-- 
Jesper Skriver, jesper(at)skriver(dot)dk  -  CCIE #5456
Work:    Network manager   @ AS3292 (Tele Danmark DataNetworks)
Private: FreeBSD committer @ AS2109 (A much smaller network ;-)

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.