[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ssag::ask_ssag

Title:	Ask the Storage Architecture Group
Notice:	Check out our web page at http://www-starch.shr.dec.com
Moderator:	SSAG::TERZAN

Created:	Wed Oct 15 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6756
Total number of notes:	25276

6734.0. "How to check HW REVs on SW devices" by CSC32::M_BERNHARDT () Thu May 29 1997 15:43

Greetings,

I have a customer that just reviewed the  release notes for HSOF 3.1 for his
HSD30s. He has mostly HSD and HSJ subsystems thhrought the country and Canada.
On page 3 there is a chart list the HARDWARE MINIMUM VERSION requirements for 
the devices on those controllers. He has many rz26/28/29 of differing varaints.
He want to know how he can check the hardware rev without physically inspecting
the drives. Any help would be greatly appreciated.


Michael Bernhardt

T.R	Title	User	Personal Name	Date	Lines
6734.1	Simple	SSDEVO::RMCLEAN		`Thu May 29 1997 15:57`	1
	Show devices full
6734.2	Couldn't resist	SSDEVO::KOWALL	StorageWorks Engineering Support	`Thu May 29 1997 16:13`	2
	Must be an old DECey. Rather ask engineering than read the users guide.
6734.3		SUBSYS::VIDIOT::PATENAUDE	Ask your boss for ARRAY's...	`Thu May 29 1997 16:42`	9
	But to give the guy some slack ;^) SHOW DEV FULL shows you the firmware rev and that is not HW rev. Although it is all you need. Even I don't bother with HW rev 99% of the time because we do very little hardware changes to drives post-frs and a lot more firmware changes, so, firmware is my key thing to look at. roger.
6734.4	Hmm old is relative ;-.]	SSDEVO::RMCLEAN		`Thu May 29 1997 17:05`	5
	re .-2 What's your definition of OLD??? Mine is 3 digit or less badge ;-.]
6734.5	Run HSUTIL and abort after listing,	JOBURG::HARRIS		`Fri May 30 1997 03:16`	31
	An even neater list with disk and D device name can be obtained by. R2B114>run hsutil *** Available functions are: 0. EXIT 1. FORMAT_DISK 2. DEVICE_CODE_LOAD_DISK 3. DEVICE_CODE_LOAD_TAPE Enter function number (0:3) [0] ? 2 Available single device units on this controller include: Unit Associated Device SCSI Product ID Current Device Rev 1410 DISK100 RZ29B (C) DEC 0016 1411 DISK110 RZ29B (C) DEC 0016 1412 DISK120 RZ29B (C) DEC 0016 1413 DISK130 RZ29B (C) DEC 0016 1414 DISK140 RZ29B (C) DEC 0016 1420 DISK200 RZ29B (C) DEC 0016 1421 DISK210 RZ29B (C) DEC 0016 1422 DISK220 RZ29B (C) DEC 0016 1423 DISK230 RZ29B (C) DEC 0016 1430 DISK300 RZ29B (C) DEC 0016 1431 DISK310 RZ29B (C) DEC 0016 Then CNRL/C to abort code load All data on One line!!! Hope this help Regards Ivan
6734.6	Thanks Rodger!, one more question plz	CSC32::M_BERNHARDT		`Fri May 30 1997 08:04`	8
	Rodger, Thanks for reading my question. I kinda thought that would be the case. Does that stand true for the solid state drives and the TZ family as well? thanks again, Michael Bernhardt
6734.7	ahhhh...	SUBSYS::VIDIOT::PATENAUDE	Ask your boss for ARRAY's...	`Fri May 30 1997 13:10`	27
	I cannot answer for tapes, T Tran probably will... SSD's however... EZ5X Well the ONLY hardware gotcha in all EZ5X land is that EZ58R-VA drives running firmware version 098 have a hardware problem that was fixed in V109 firmware AND a retention drive change. So all versions of firmware are OK. All versions of hardware are OK. WITH THE EXCEPTION of EZ58R's running V098. V098 is not bad, but if the unit is running it then that tells you that it never got FCO'd to the new hardware either. As per the FCO almost a two years ago. EZ3X, EZ6X, All versions of hardware are OK. All versions of firmware are OK. Version V070 is much more robust in handling broken hardware than V064, but with good running hardware either is fine. roger.
6734.8	thanks	CSC32::M_BERNHARDT		`Fri May 30 1997 14:23`	2
	THanks again!