[j-nsp] ex4200 log message question

Cord MacLeod cordmacleod at gmail.com
Thu May 21 14:21:46 EDT 2009


Umm, being that this post was about the ex4200... the platform was the  
ex4200.

After I submitted a few PRs on 9.3R2 for the EX platform, the message  
was these would be fixed in 9.3R3 and would be exceptionally stable.

On May 21, 2009, at 11:19 AM, Kevin Oberman wrote:

>> From: Cord MacLeod <cordmacleod at gmail.com>
>> Date: Thu, 21 May 2009 10:37:30 -0700
>> Sender: juniper-nsp-bounces at puck.nether.net
>>
>> 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.
>>
>>
> Umm. On which platform?
>
> On non-EX platforms, 9.3 looks pretty good, although there were
> show-stoppers for us in 93r2, r3 seems to have fixed them.
>
> This message was about the EX software and it is a VERY different  
> beast.
> -- 
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman at es.net			Phone: +1 510 486-8634
> Key fingerprint:059B 2DDF 031C 9BA3 14A4  EADA 927D EBB3 987B 3751
>
>
>> On May 21, 2009, at 2:13 AM, Thomas Eichhorn wrote:
>>
>>> 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
>>>>
>>>>



More information about the juniper-nsp mailing list