IOS next-hop trouble

[owens@nysernet.org]

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.

Bill.