I a previous job we lacked the identical (juniper) hardware mix in the
lab that we had in the field (mx480s and srx 5600s are expensive). So
for some upgrades things ran fine or were easy to identify, but there
were failure cases whereas we tripped over hardware/software
interactions in the field
On Thursday, April 14, 2011 02:11:07 AM Richard A
Steenbergen wrote:
Honestly, sometimes they get a little too RMA happy and
throw that out as the solution instead of actually
trying to find the real issue. Personally I'd be far
more inclined to believe that the problem is software
than it
On Thursday, April 14, 2011 02:35:01 AM Justin M. Streiner
wrote:
I'll agree that bleeding-edge code should be avoided in
production, however there are cases for some people
where there isn't a choice.
We're using NG-MVPN for Multicast and some features we
needed were only available in
On Thursday, April 14, 2011 12:39:44 AM Chris Evans wrote:
In all of our cases over the years it takes Juniper quite
longer to get us answers. Be aware that we do have a
much larger install base with Cisco so we get higher
support.
I would have to agree, and we are a 50/50 house.
Both sales
On Thursday, April 14, 2011 01:27:15 AM Chris Evans wrote:
Question to you all...
It seems like alot of folks run bleeding edge code with
some if these major bugs popping up.I also get the
impression that a lot of shops don't test code before
they deploy.
Well, in our case, the MX's we're
On Thursday, April 14, 2011 01:48:30 AM Derick Winkworth
wrote:
I'm not saying there haven't been moments of
frustration. There has been great frustration at some
points. Still, overall our support from Juniper has
been great.
We haven't had a terribly poor experience with JTAC per se.
On Thursday, April 14, 2011 12:18:00 AM Keith wrote:
Is this an anomaly and we got a lemon? Or have any others
had to replace this many parts in so short of time?
Like others have mentioned, some batches are good, some
aren't.
We haven't had any hardware issues with a couple of units we
On Wed, Apr 13, 2011 at 09:18:00AM -0700, Keith wrote:
So on a non production box, just sitting in the rack, powered
up for a little more than 8 weeks, passing no traffic at all,
it's on the 3rd MPC and 2nd MIC.
Try this on...we had to RMA a newly-installed-in-production MX960-ECM
chassis
Hi. You folks have been great at answering some of
my questions regarding our MX480, but have come across
some big problems that me and the person who signed
the PO are not very pleased about.
A month or so ago I found we had a bad MPC card. Ok so
we RMA'd it.
This week I came on site to do
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] MX480 troubles.
Hi. You folks have been great at answering some of
my questions regarding our MX480, but have come across
some big problems that me and the person who signed
the PO are not very pleased about.
A month or so ago I found we had a bad
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Keith
Sent: Wednesday, April 13, 2011 9:18 AM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] MX480 troubles.
Hi. You folks have been great at answering some of
my
Keith.
I feel your pain on this. We do not get nearly the support from Juniper
that we do with Cisco. In your case it sounds like this just might be bad
hardware for which anyone is susceptible. However how the manufacturer
steps up to resolve is where it matters.
In all of our cases over the
On Apr 13, 2011, at 1:27 PM, Chris Evans wrote:
Question to you all...
It seems like alot of folks run bleeding edge code with some if these major
bugs popping up.I also get the impression that a lot of shops don't test
code before they deploy.
I'm just curious how this works for you.
On Wed, Apr 13, 2011 at 01:27:15PM -0400, Chris Evans wrote:
Question to you all...
It seems like alot of folks run bleeding edge code with some if these
major bugs popping up.I also get the impression that a lot of shops
don't test code before they deploy.
I'm just curious how this
On Wed, Apr 13, 2011 at 10:48:30AM -0700, Derick Winkworth wrote:
They don't
1.? immediately just blame you or
2.? just tell you to upgrade and sit and do nothing until you do
3.? or tell you that you should have known that with some very narrow set of
unlikely circumstances after two
On Wed, Apr 13, 2011 at 10:09:12AM -0700, Keith wrote:
We saw random reboots, sometimes hourly, with the first MPC
and this was on 10.4R2.6. Juniper wanted to RMA it.
When the latest MPC and MIC arrive I will update to 10.4R3.4
and see how that goes.
Honestly, sometimes they get a little
On Wed, 13 Apr 2011, Chris Evans wrote:
It seems like alot of folks run bleeding edge code with some if these major
bugs popping up.I also get the impression that a lot of shops don't test
code before they deploy.
That depends on your definition of 'test' :) Seriously, though. I've
seen
On 4/13/2011 11:11 AM, Richard A Steenbergen wrote:
On Wed, Apr 13, 2011 at 10:09:12AM -0700, Keith wrote:
We saw random reboots, sometimes hourly, with the first MPC
and this was on 10.4R2.6. Juniper wanted to RMA it.
When the latest MPC and MIC arrive I will update to 10.4R3.4
and see how
this will happen.
From: Richard A Steenbergen r...@e-gerbil.net
To: Derick Winkworth dwinkwo...@att.net
Cc: juniper-nsp@puck.nether.net
Sent: Wed, April 13, 2011 1:08:52 PM
Subject: Re: [j-nsp] MX480 troubles.
On Wed, Apr 13, 2011 at 10:48:30AM -0700, Derick Winkworth
Me Hi, when this bgp neighbor flaps it sometimes doesn't syslog the
event correctly, and instead records garbage messages.
ATAC The bgp neighbor is flapping, that is why you are logging the
neighbor down, can I close this case?
Oh-yah! )
Are your sure it wasn an ATAC guy really, not
20 matches
Mail list logo
