On Tue, Nov 11, 2008 at 02:35:30PM +0100, Antonio Del Bianco wrote: > > Hi Richard, > > thanks for pointing that out. In fact that is a known PR (problem > report) which is tracked with number 397439 and the fix for it is > currently being included into 9.1. > > We found that out last month as soon as we got a Customer reporting > a similar problem through a case opened with the Juniper Technical > Assistance Center.
Afraid not. My case was opened November 6 2007, led to PR286089, and has the same symptoms of exporting dst ifindex and nexthop fields populated with 0's on certain MX interfaces (around 3/4th of them for me). It is definitely not fixed in any current code. > If you happen to hit an issue or discover any misbehaviour in JunOS > which hasnt been caught during our systesting prior the official release, > please let us know and we can work on getting that fixed. I'll be polite and not answer that one. -- Richard A Steenbergen <[EMAIL PROTECTED]> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
