A question, if the Nike drives are not in the system domain, does HP still have to apply the
binary patch or can you reboot, apply the patch, MPEKXD1, reboot and they will now be
reconized by the system?
Bob Schlosser
(504) 219-8134
Ochsner Health Plan
-----Original Message-----
From: [log in to unmask]
Sent: Thursday, October 19, 2000 10:01 AM
To: [log in to unmask]
Subject: Re: Issues with MPE/iX 6.5 Install-PLEAS
<< File: ENVELOPE.TXT >>
-------------------------------------------------------------------------- --
Yes, this is true. We had HPRC dial in and upgrade the SCSI firmware
before
each 6.5 upgrade. The system must be quiet for this but a re-boot is not
required. If you are using a NIKE on the system, HPRC will have to dial
in to install a binary patch as you have described. We have upgraded two
systems thus far and will upgrade another this Sunday. We discovered the
NIKE issue on an earlier upgrade which resulted in delays. For the next
upgrade we have already contacted HP and have them scheduled for the
binary
patch installation.
Thanks,
Tom Genute
-----Original Message-----
From: Michael Hurdle [mailto:[log in to unmask]]
Sent: Thursday, October 19, 2000 10:17 AM
To: [log in to unmask]
Subject: Issues with MPE/iX 6.5 Install-PLEASE READ
I was provided the following information from my HP Acct
Support Engineer
yesterday regarding issues involving updating to MPE/iX
6.5.
Has anybody
else seen these issues surface? If you haven't already
updated to MPE/iX
6.5, it would be a good idea to read this carefully:
Issue #1:
Customers with Nike disks configured as ldev 2, 3, etc.
will see an
AVR error during START NORECOVERY on 6.5 and these disks
will not
mount. A fix from the 5.5 patch MPEKXT8 did not make it
into 6.5.
A 6.5 patch, MPEKXD1, has been created to address this
issue. However,
MPEKXD1 can only be installed after 6.5 is up and
running,
so a
special binary patch needs to be installed to allow the
disks to
mount when booting 6.5.
Issue #2:
Fast/Wide SCSI device adapter firmware can't be updated
after moving
to 6.5. This may not impact the customer immediately,
but
if they
need to update it later they will find that FWSCSIPB
does
not work
properly on 6.5 (CR 8606144043). They will need to
remove
the device
adapters from the 6.5 system and take them to a 5.5 or
6.0
system
to perform the update. All FWSCSI DA's should be
updated
to revision
3944 firmware prior to updating to 6.5 so this problem
can
be avoided.
Recommendations for addressing these two issues:
Issue #1 (Nike mount problem):
The procedures that need to be done for the 6.5 systems
that
have a
Nike disk configured as ldev 2 (and maybe others) are as
follows:
1. Test the remote console (parallel console) facility
prior to
starting the update process.
2. Perform update from 6.5 CSLT. Do not perform START
NORECOVERY.
3. HP will establish remote console (parallel console)
and
use
the passworded utility, SADPATCH, to install a binary
patch to
the START program. An alternative it to have an HP
person
onsite to perform the binary patch since this is a
passworded
utility.
4. A START NORECOVERY can be performed and all disks
should mount.
5. Install beta patch MPEKXD1 (A). Update from the CSLT
created,
but do not perform START NORECOVERY.
6. HP will establish remote console (parallel console)
and
use
the passworded utility, SADPATCH, to remove the
binary
patch
that was installed in step 2.
7. A START NORECOVERY can be performed and all disks
should mount.
8. The customer should create a new CSLT tape reflecting
installation
of the MPEKXD1 fix along with removal of the special
binary fix.
Issue #2 (FWSCSI device adapter firmware):
One option is to notify a CE and request that they
arrange
to acquire
the firmware update file and perform the update. All
device adapters
should be updated to this firmware level.
The CE can do the update either remotely or onsite. An
alternative
would be to request that the response center assist
remotely. The
system needs to be idle during the update. It is not
necessary to be
logged onto the remote console to perform this function.
The update
is performed using the FWSCSIPB utility.
|
