Re: Netscreen ScreenOS

From: Somebody. (somebody._at_spamout.russdoucet.com)
Date: 10/13/05


Date: Thu, 13 Oct 2005 08:09:39 -0400


"Triffid" <triffid@nebula.net> wrote in message
news:J9k3f.4917$vD4.349465@news20.bellglobal.com...
>
>
> Somebody. wrote:
>
>> "Triffid" <triffid@nebula.net> wrote in message
>> news:%703f.4875$S43.569621@news20.bellglobal.com...
>>
>>>
>>>Leythos wrote:
>>>
>>>
>>>>In article <I5l1f.8308$2F2.972520@news20.bellglobal.com>,
>>>>triffid@nebula.net says...
>>>>
>>>>
>>>>>Agreed, but in this case the vendor is not offering the update, via a
>>>>>support contract or otherwise, at any price. I fail to see a downside
>>>>>to their making it freely available on an as-is (unsupported) basis,
>>>>>indeed doing so might enhance their reputation somewhat and reduce the
>>>>>probability of complaints from users of illicit (potentially
>>>>>compromised) firmware.
>>>>
>>>>
>>>>I have a support contract for my WatchGuard firewall units, with the
>>>>support contract I can download any version of their software for any
>>>>appliance that I am marked as owning - you register their serial numbers
>>>>and they provide access to the firmware/software. All updates, supported
>>>>or not, are available to me because I have kept the support agreement on
>>>>at least one current product.
>>>>
>>>
>>>Netscreen used to work that way. I'm not sure anyone is entirely clear
>>>how Juniper works it.
>>>
>>>Triffid
>>
>>
>> Yes, and they still do.
>
> Not consistently, IME - see below
>
>> The question is how they are handling obsolete products for which
>> customers run but don't have the last (old) firmware.
>>
>> -Russ.
>
> Indeed - especially cases where the user obtained the unit as a discard
> from work, or perhaps on ebay, and would like to update and run it at
> home. Not state of the art, but still safer than the NAT router they
> probably have now, and an opportunity to learn. Overall, a good thing for
> both user and vendor IMHO.
>
> I bought new-in-box 5GT on ebay to replace my NAT router - came with
> 4.something, and the DI and AV subscriptions had expired since it
> originally shipped just over 12 months before I bought it. Juniper said I
> would have to ship the unit to them (at my cost both ways) for
> 'inspection' before they would take my $ for a support contract. They
> refused to sell updates or subscriptions otherwise - send it to us, or run
> it as-is. Screw that.
>
> So I log into my TAC account and grab the latest 5GT firmware. Legal? I
> dunno, AFAIK the smallest unit registered on my account is a 500, but I
> appear to have access to all firmware for all boxes. The other day a
> colleague at work needed to update a 208, he's sure he has several
> registered, but his TAC account wouldn't give him the file. Mine did.
> Fouled up or what?
>
> You're even worse off if you own a unit Juniper considers obsolete - so I
> won't be berating individuals who own one old NS box for asking after
> firmware updates on the newsgroups. I won't give (or sell) them firmware
> updates either - but Juniper should IMHO.
>
> Triffid

We've been beating on them hard to offer non-hardware support, but so far
they won't budge. Imagine your 500 was off support and you realize that
your needs have changed, you need tech support and firmware support, but the
same thing happens -- they won't debundle it from the hardware support and
you have to pay all the back-dues since the hardware support went off, or,
send it to them for inspection. Now imagine it's a 5200 and a year of
back-support is gonna cost you five figures... just to earn the privledge of
paying another 5 figures for the current year's support...

Juniper really, really has to just give themselves a shake and put
themselves in their customer's shoes for a bit... they have great products
that they are somehow managing to turn into a nightmare for their clients.
Hopefully somebody up there will fix it soon. The fixes truly aren't that
complicated.

1. Offer 1-time obsolete firmware purchase option for very little money, or
even free
2. Break up tech support, software support, hardware support into separate
packages
3. Publish DI and AV throughput number ranges
4. Track ticket response times and FIX them when they see how broken they
are

-Russ.



Relevant Pages

  • Re: Computer not Recognizing that the DVD-RW drive can record
    ... Check here for a program that I have used in the past to update my firmware. ... there are updates that are needed for DVD drives as they add support for more stuff. ...
    (microsoft.public.windowsxp.hardware)
  • Re: What next?
    ... Latest firmware flash is 6.3MB in size, I guess the 8MB of flash really is needed. ... Note the support for FAT32/NTFS on one port and FAT32/EXT3 on the other. ... Also, the USB ports should be USB2.0, although the datasheet for the IXP420 mentions 1.1 ... Fix bug that cannot copy large zip file into FAT HDD. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: PCI bus numbering and orphaned devices
    ... >> beginning) is to write an OFW PCI bus, analogous to the ACPI one. ... We do not support hotplugging at the moment anyway. ... would implement that in the future without using any firmware support ... > bus drivers in favor of OFW specific ones like ACPI? ...
    (freebsd-current)
  • Re: Leopard
    ... Leopard will probably require the latest ... and won't run if the earlier 4.1.9 firmware was still ... USB boot support. ... you can even boot an oldie like the PM 9600/350 from an external Firewire ...
    (comp.sys.mac.apps)
  • Re: dat40
    ... support DAT40 only an A/N-Class? ... worried about the device stressing the SCSI_DAM driver in new ... firmware and hardware package is SCSI-1 ... Later code was added for DLT and finally the changes for Ultrium. ...
    (comp.sys.hp.mpe)