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

Conference ssdevo::hsz40_product

Title:	HSZ40 Product Conference

Moderator:	SSDEVO::EDMONDS

Created:	Mon Apr 11 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	902
Total number of notes:	3319

750.0. "HSZ50 says it's an HSZ40" by WBC::STASSE (Glenn Stasse, 339-7780) Tue Jan 28 1997 18:23

    Hi Folks,
    
    One of my new HSZ50's is having an identity crisis.Todays bizzarre deal 
    goes as follows:
    
    We got a bunch of new HSZ50's in to replace our HSZ40s. In one
    controller shelf, we put two HSZ50s. One seems OK but complains about
    the other, paticularly when you try to do SET FAILOVER ... . It says
    the other one is an HSZ40 and you can't mix 'em. SHOW THIS when the
    console is plugged into the other controller tells me that it thinks
    it's an HSZ40! The boards are the same. It's not comming from the
    firmware card 'cause I tried different ones, including one from an HSZ50
    that SAYS it's an HSZ50. There doesn't seem to be a jumper to set "HSZ50
    mode" nor can I find a command that says 'SET THIS "I'm an HSZ50,
    honest, no kiddin', REALLY!"', so I'm at a loss.
    
    Any ideas? Thanks in advance...
    
    Regards,
    Glenn

T.R	Title	User	Personal Name	Date	Lines
750.1		SSDEVO::ROLLOW	Dr. File System's Home for Wayward Inodes.	`Wed Jan 29 1997 01:34`	5
	What does the SCSI Inquiry data say it is? If Digital UNIX you can use the scu(8) "show device" command to get it. As I recall, the SCSI Inquiry data is set at the factory. It probably wouldn't an uncommon mistake to set it incorrectly. Not noticing it set incorrectly is another matter...
750.2	It looks like an HSZ40 no matter what	WBC::STASSE	Glenn Stasse, 339-7780	`Wed Jan 29 1997 11:10`	10
	Yo, SCU, file /dev/rrz25a, the >>> show device command ALL say HSZ40 V50Z. Also, it complains bitterly about missing keys for RAID and mirroring. Does it seem like this is just a cross-dresser that need to be sent back for re-programming? Should we just send this back through Field Service and get another? Thanks...Glenn
750.3	Yup sounds like a MFG problem	SSDEVO::RMCLEAN		`Wed Jan 29 1997 14:41`	18
	>> <<< Note 750.2 by WBC::STASSE "Glenn Stasse, 339-7780" >>> >> -< It looks like an HSZ40 no matter what >- >> >> Yo, >> >> SCU, file /dev/rrz25a, the >>> show device command ALL say HSZ40 V50Z. >> Also, it complains bitterly about missing keys for RAID and mirroring. >> >> Does it seem like this is just a cross-dresser that need to be sent >> back for re-programming? Should we just send this back through Field >> Service and get another? >> >> Yes get another module. Submit an IPMT case so that it is noticed that MFG has made a mistake and we can prevent it from happening again. There is no way you can fix this in the field and we should get the module back.
750.4	What's an IPMT case?	WBC::STASSE	Glenn Stasse, 339-7780	`Wed Jan 29 1997 15:28`	9
	Howdy, What's an IPMT case? How do I submit one? Should the Field Service guy know what this is? So far the plan was to just hand it back in to logistics when the replacement gets in. Should we do something more/less/different? Please advise... Glenn
750.5	yup	SSDEVO::RMCLEAN		`Thu Jan 30 1997 12:51`	2
	Yup talk to F/S