[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

887.0. "query on enabling all 4 target id's hangs NT cluster . HSZ50" by KAOT01::B_CORBIN (dtn 640-7420 ) Mon May 26 1997 20:00

    Forgive the vagueness of my query since it is based on second hand
    information 
    
    Problem:
    A new storageworks box(BA356 with 16bit personality)
    using  RZ29B-VA disks was attached to an unused HSZ50 port
    The HSZ50  did  not see any of the new disks, The HSZ50 is
    connected to 2 alpha4100's running NT. Prior to the add on
    there was one storageworks BA356 installed with  RZ29B-VA
    setup as a raidset.
    
    The HSZ50 only had one target id setup (id6)  Host ID was 6 also.
    So I recommended they setup the HSZ40 to use all 4 possible target
    ID's since it is not in a dual-redundant configuration. So that was
    done and the HSZ50 was shutdown and restarted. They next ran
    CFMENU to configure the disks. At this point I let them carry on 
    and figured problem solved.  But I hear back that later 
    when they were trying to boot their NT cluster it would hang.
    
    They say they fixed the problem by only using 2 of the possible
    4 target id's . Can this be so??   Any recomdations on the 
    usage of target port Id's , Use them as you need them?
    What about the termination of the 6 physical target ports.
    From what I see normally unused parts are not terminated.
    Would this have any effect if all 4 SCSI target id's were
    enabled?  
    
    What I don't known is what version NT they use , the revison of
    firmware on the HSZ50 , KZPSA, 4100. I don't know the
    details of where in the boot process it hung.
    
    Brian
T.RTitleUserPersonal
Name		DateLines
887.1SSDEVO::T_GONZALESTue May 27 1997 11:0817
    The host port target id's can be any target id's that are not in use.
    The rule of thumb is that the scsi adapters on the host systems should
    use the higher target id's.  The host part target id's would have
    nothing to do with whether the hsz's can see any of the disks on its
    ports, those host port target id's would affect the ability of the host
    systems to see "units" on the hsz's; units being any storage
    containers, raid5, mirror, stripe, jbods, etc.
    
    As far as termination on the hsz ports, if you have ba356 shelves and
    personality modules, the personality modules have the termination,
    unless you put the shelves in a split bus mode, or you plug another
    cable into the "b" connector on the personality module.
    
    If you have ba350 shelves then the termination is supplied by
    terminator modules on the back of the shelf.  See ba350 users guides
887.2MSE1::PCOTEpress one now for personal nameWed May 28 1997 09:5013
>    The HSZ50 only had one target id setup (id6)  Host ID was 6 also.
>    So I recommended they setup the HSZ40 to use all 4 possible target
>    ID's since it is not in a dual-redundant configuration. So that was

     NT Cluster configurations typically have the two SCSI controllers
     configured with Host IDs 6 and 7. From above, it appears that you
     are also using host ID 6 as one of the possible Host IDs on the
     hsz50. Generally, Host IDs 0 through 3 are used for the HSZ.
   
     Since you're using Windows NT, it would be prudent to verify
     the the HSZ is configured with HOST_FUNCTION_ID set to
     "D" and that the HSZDISK SCSI class driver is installed.
887.3followup KAOT01::B_CORBINdtn 640-7420 Wed May 28 1997 16:5525
    Thanks for the replys..
    
    I want to followup on one issue to make sure I understand.
    
    The hsz50 configuration manual also states that the HSZ50 
    can declare up to 4 target ID's that are not already being used on the 
    host SCSI bus.  
    
    From what I was told the customer had used a target 
    id of 6. The host bus had 2 Alphaservers 4100 using KZPSA's with
    host bus id' of 5 and 7. The host bus Id of the HSZ50 was 6.
    So they have a conflict between the host bus id of 6 and the 
    target ID of 6. What are the issues here? It does appear
    to be functional. The site currently has 2 target ids defined
    (0,6)  
    
    Also are the HSZ50/40 controller slots hard wired for SCSI id's
    6 and 7?  On this customers site they have a Host Id 7 taken by 
    a KZPSA. So this could be a future problem if a second HSZ50
    were installed without checking the host bus.
    
    Brian
887.4You are confusing the host side with the device sideSSDEVO::RMCLEANWed May 28 1997 17:133
The host Id's are NOT hardwired!  You are confusing the HSZ device bus with the
Host bus.  In a dual controller pair the Device bus HSZ's are 6 & 7.  For the
host side you can configure them with CLI.
887.5SSDEVO::T_GONZALESThu May 29 1997 18:188
    The basic rule: Don't use scsi id's that are not being used.
    
    Normally the kzpsa adapters on the host systems get the high target
    id's, however since the target id's can be set by software there are
    no "enforcers" to make sure that the host systems get the high id's.
    
    If the scsi adapters on the host systems are set to 5 and 7,the
    hsz id's can include up to four id's selected from 0,1,2,3,4 or 6.
887.6SSDEVO::T_GONZALESFri May 30 1997 11:446
    the last note needs be corrected;
    
    basic rule of thumb: Only use id's that are not already assigned !
    
    sorry,
887.7A block diagram helpsKAOT01::B_CORBINdtn 640-7420 Sun Jun 01 1997 18:3728
re: .4
Yes I was a bit confused between the SCSI target ID's and the 
HSZ device ID's . I found it helped to draw a simple block diagram.
Thanks for you assistance.
Brian 

Device Scsi Bus			HSZxxx Dual Redundant Pair					
Fast wide Single ended

SCSI ID's 0-5	_________________
 0 1 2 3 4 5 --<|6	|7	|		
		|       |       |
 0 1 2 3 4 5 --<|6      |7      |
                |       |       | 
 0 1 2 3 4 5 --<|6      |7      |
                |       |       | 
 0 1 2 3 4 5 --<|6      |7      |                KSPSA		KSPSA
		|       |       |  		__________	__________
 0 1 2 3 4 5 --<|6      |7      |		|HOST SCSI|	|HOST SCSI|
                |       |       |  		|_ID 6 ___|	|__ID 7___|
 0 1 2 3 4 5 --<|6      |7      |		|		|
		|	|	|		|		|
		_________________		|		|
		|_______^________|--------------		|
		  |						|
		  |Target id's for host bus (0,1,2,3)		|
		  |---------------------------------------------|		
			differental scsi bus  ( fast wide)