[j-nsp] ex4200 log message question

[Cord MacLeod]

Can you elaborate on 'the whole routing seems to fail'?  I was  
actually told by JTAC to upgrade to 9.3R3 as soon as it came out as it  
would be exceptionally stable code.


On May 21, 2009, at 2:13 AM, Thomas Eichhorn wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Malte,
> Cord,
>
> according to our SE this is just debugcode - which should have been
> fixed in the 9.3 service release and also 9.3R3 - but at a current  
> state
> I would really recommend not to upgrade to this version - I'm not  
> yet really sure,
> but under some cirumstances the whole routing seems to fail.
>
> I really recommend to everyone to test all the needed features first  
> in a lab.
>
> Tom
>
> Malte von dem Hagen schrieb:
>> Cord,
>>
>> Am 21.05.2009 02:23 Uhr, Cord MacLeod schrieb:
>>> Every now and again I'm seeing the following log message:
>>>
>>> May 20 22:23:34  gsw1 fpc1 Resolve request came for an address
>>> matching on Wrong nh nh:1499, type:Hold...?
>>> May 20 23:08:03  gsw1 fpc1 Resolve request came for an address
>>> matching on Wrong nh nh:1501, type:Hold...?
>>>
>>>
>>> Any ideas what this could mean?
>>
>>> JUNOS Base OS boot [9.3R3.8]
>>
>> this matches PR/412240 and can be ignored (according to JTAC, which  
>> I asked
>> about that in 9.3R2.8). I was not able to get information about the  
>> root cause
>> out of them.
>>
>> Kind regards,
>>
>> Malte
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkoVGycACgkQrUvjMoak8ZdLpQCeK1djeTn5hYxGVeZ2uj9nvMv7
> moIAoKI8yhIZpCE6jyChN+1MSrkdJYOd
> =QDGS
> -----END PGP SIGNATURE-----