On Thu, May 21, 2009 at 10:37:30AM -0700, Cord MacLeod wrote:
> 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.
For what it's worth, I've been running some interim 9.3R
On May 21, 2009, at 11:36 AM, Kevin Oberman wrote:
It makes the thread very hard to follow.
Why not?
Please don't top-post!
From: Cord MacLeod
Date: Thu, 21 May 2009 11:21:46 -0700
Umm, being that this post was about the ex4200... the platform was
the
ex4200.
After I submitted a few
It makes the thread very hard to follow.
> Why not?
>> Please don't top-post!
> From: Cord MacLeod
> Date: Thu, 21 May 2009 11:21:46 -0700
>
> 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 mes
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
> From: Cord MacLeod
> Date: Thu, 21 May 2009 10:37:30 -0700
> Sender: juniper-nsp-boun...@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.
>
>
Um
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,
accordi
-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 som
Much appreciated.
On May 20, 2009, at 5:37 PM, Malte von dem Hagen wrote:
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...?
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
>
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 thi
10 matches
Mail list logo
