From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Thu Dec 02 2004 - 14:40:52 EST
Thanks to everyone who replied!
What I have learned is that some people have upgraded to 5.1a using
HSZ controllers and have had no problems; however, the 70 does not have the
ability to create WWIDs, so chances are, having a null vendor ID string is
going to be a show stopper. What I don't know is whether or not someone has
checked to see if the vendor ID string said DEC or not and then done the
upgrade. I do know for sure that an empty string will cause an HSZ40 or 50
not to work, and one person has seen an HSZ70 fail this way, the fix being
to have a hardware tech use the "dangerous" command to fix it.
We are going to have a hardware tech on site, we'll shut down the
box, boot from a 5.1a CD and see if we can view the LUNs. If not, the HW
tech will have to do whatever he does to rebuild the vendor ID string,
replace firmware or whatever. Apparently, running the dangerous command is,
as the name implies, not a safe thing for a person who is not experienced
with it to do. It may require contacting HP for more information that is
needed to make it work.
-denise
"Customer service may be the only way that a
company can distinguish itself from its
competition these days." -H. Frank Gibbard
Denise McCracken, Systems Software Specialist
Misys Healthcare Systems, Tucson, AZ
Certified Tru64 v5 Systems Administrator
Comptia Network+ Certified Professional
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:12 EDT