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

Conference ssdevo::hsj40_product

Title:	HSJ30/40 Product Conference

Moderator:	SSDEVO::EDMONDS

Created:	Mon Jul 12 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1264
Total number of notes:	4958

1201.0. "Urgent : MAX HOST parameter clarification" by ATYISA::GHEORGHIN (KGB 007.2 - Double agent...) Fri Jan 31 1997 11:17

    Hello, I would like to be sure about one point concerning the MAXIMUM
    HOSTS parameter on an HSJ, just to verify 'cause we're facing a problem
    without knowing where it comes from.
    
    We have a cluster with 6 AS8400 5/440MHz 6 CPUs and 4 GB memory, 2 Star
    Couplers, 18 HSJ50s (dual-redondant). OpenVMS 6.2-1H3.
    
    The HSJ documentation says the minimum value for the
    MAXIMUM HOSTS is depending the number of hosts (6 in our case), and the
    number of adapters (2 CIXCD per machine in our case) a host has. 
    
    The question is : are we counting only the connections per Star Coupler
    (meaning one host has 2 CIXCD but with one connection to each Star
    Coupler, so only one connection per Star Coupler), in that case our
    value per HSJ has to be at least 6; or for the whole cluster without
    taking care about the number of Star Coupler (in that case I have 6 
    hosts with each 2 adapters meaning 12 and the MAXIMUM HOSTS has to be 
    at least 12) ??????
    I would say only the connection on the Star Coupler is important, so in
    our case 6... but there is a doubt in the understanding of the
    documentation.
    
    Thanks in advance,
    Igor.
    
    ps: since we moved from HSJ40 to HSJ50 we have trouble, but not sure
    it's that point. The MAX HOSTS was 16 on the HSJ40s, it was 32 on the
    50s (because a third Star Coupler will be added). So perhaps a credit
    wait problem, but not sure and not really seen...

T.R Title User Personal
Name Date Lines

1201.1 Mmmmmm?? GEM::SHERGOLD A FOOL'S living PARADISE Sat Feb 01 1997 02:16 12

T.R	Title	User	Personal Name	Date	Lines
1201.1	Mmmmmm??	GEM::SHERGOLD	A FOOL'S living PARADISE	`Sat Feb 01 1997 02:16`	12
	Thinking about this has begged some clarity on my part. Apart from a very few odd ball systems that have that 32 node CI rail system (What was that product? - CISCE or something?) a CI rail can only have 16 nodes on it. Therefore what is the 32 node setting available for. Is this setting for the single access it has to its own CI rail, or is it used for dual redundancy and split rail use (In other words the total number of nodes a pair can see), or maybe that old standby "FUTURE USE". I think it fairly obvious it has nothing to do with total system nodes though as that can be at least 64. Keith

    Thinking about this has begged some clarity on my part. Apart from a
    very few odd ball systems that have that 32 node CI rail system (What
    was that product? - CISCE or something?) a CI rail can only have 16 nodes 
    on it. Therefore what is the 32 node setting available for.  Is this
    setting for the single access it has to its own CI rail, or is it used for
    dual redundancy and split rail use (In other words the total number of
    nodes a pair can see), or maybe that old standby "FUTURE USE". I think it 
    fairly obvious it has nothing to do with total system nodes though as that 
    can be at least 64.
    
    Keith