A warning: this is kinda long. Hope you'll excuse the length, but if I
can spare anyone else the hassles I've gone through on this, I think it
should be on the record and in the archives. If you don't anticipate
putting 100BT on your 3000 and/or you don't like some mild ranting,
(whoops, that's two warnings) hit delete. Also, I don't have a solution
yet, so if you're looking for one it's not here; I'll post one when I
get one from HP. (Okay, so that's three warnings. Don't say you weren't
warned!)
Jeff Kell wrote:
> I installed the 100BT patches with AUTOINST. There was some file
> (sorry, I've slept since then) that had to be restored from the PP tape
> first that had the "installation template" for the *new* 100BT product.
> The original AUTOINST install attempt aborted with a message saying that
> the product number was not found in file [whatever.it.was].
Hmmm... "new" 100BT product? That's very interesting. The subsys tape I
got listed product number 73811, has a date code of 3732 and "Rep. Date"
(repro date?) of 8/18/98. The product file on the tape says, "B5427AA
- NIO 100BASE-T LINK", and HP says that's right. But one of HP's
recommendations was that we go to PP6; perhaps this is the reason.
Thanks Jeff, now at least I have an intelligent question to ask HP.
(Though in our case, we got through the subsys update with AUTOINST and
didn't start having problems till we tried to do the patches.)
Gary Paveza added:
> Yes, we have a 997/200 on a 100Base-T. But, I warn you, it took me 24
> hours straight to do it. Kinda annoying to have to work with three
> different shifts of support, but we finally got it working.
Thanks Gary, at least that tells me it's not some kind of weird
incompatibility between the 997 and the 100Base-T software. It also
tells me HP still has some bugs to work out with this product (or at
least its installation).
<mild_rant>
Our total down time for this attempted installation is already higher
than Gary's, and our users are not happy about it. So far we've had our
system down three times and each time been unable to complete the
installation. The first time in November was for the hardware, but for
some reason we didn't have the subsys tape, just some patches. Didn't
work, for obvious reasons.
The second time, in December, we got as far as the subsys update but
then couldn't get Patch/iX to run. We're on PP4, remember, so HP said,
"Just install these patches [after the subsys update] using your PP6
tape and Patch/iX." My manager has said in the past that he doesn't
trust Patch/iX. And I was sure it would work. Guess that's why he's the
boss. ;-) He's still ribbing me about it.
This last weekend we used AUTOINST for the subsys and AUTOPAT for the
patches, to no avail. Now I'm beginning to suspect the subsys tape is
bad, or at least doesn't play well with AUTOINST for some reason. After
the update, some of our third party utilities started getting "Data
Memory Protection Trap" errors. This is the same error, coincidentally,
that the $STDLIST shows in the PATCHSYS job, causing the errors
displayed in the first post in this thread. It's also the same error
Patch/iX had last month. Seems to be a pattern here...
</mild_rant>
At this point we may not try again till we can update to PP6, but we're
still pursuing a resolution with HP. I'll let you know.
Thanks again,
Patrick ("It's going to be a loooong Monday.")
--
Patrick Santucci
Technical Services Systems Programmer
KVI, a division of Seabury & Smith, Inc.
Visit our site! http://www.kvi-ins.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If they try to rush me, I always say, 'I've only got
one other speed -- and it's slower.'" ~ Glenn Ford
|
