| Title: | + OpenVMS Clusters - The best clusters in the world! + |
| Notice: | This conference is COMPANY CONFIDENTIAL. See #1.3 |
| Moderator: | PROXY::MOORE |
| Created: | Fri Aug 26 1988 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5320 |
| Total number of notes: | 23384 |
I have a SCSI cluster problem, which many people have talked about.
Since this customer cannot go 7.1, we are searching for a solution.
AS8400 with 6 KZPSAs
to AS8400 with 6 KZPSAs
to AS4100 with n KZPSAs
There are 4 options in connecting the 4100 to the AS8400s as outlined
below.
If the KZPBA were supported on OVMS 6.2-1hx and available in April. we
could put one of the four channel versions in the 4100 and it would
only take one slot.
Can anyone help with the Customers questions. I know this is on the
fringe of futures but he needs to know whether to order the 4100 by
next Monday.
Customer wants to know:
Will KZPBA be supported as a cluster interconnect?
If yes, when and with what version of OVMS?
Can you put the KZPBA for SCSI A, B, C, D (not connected to anything)
and then start with SCSI E on up for cluster support for OVMS 6.2-1hx?
Does anyone have any other ideas than the ones listed below?
1. Upgrade the planet to OVMS 7.1 and use the new SCSI naming rules.
2. Buy 3 new KZPAA's and stuff them into the AS4100 to come up with
matching SCSI controller letters. (I think the KFTIA takes letters A,
B, C, D)
3. Take the KFTIA out of the AS8400s and replace it with a KFTHA (Cost
about $9K list price.) But then you still he might need 1 KZPAA.
4. Change from the AS4100 (4 CPUs, 4 Memory Slots, 8 PCI) to an AS4000
(2 CPUs, 2 Memory Slots, 16 PCI)
Cheers,
Sandy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5255.1 | With V6.2 you can use ALPCLUSIO kit, SCSI naming | VMSSPT::JENKINS | Kevin M Jenkins VMS Support Engineering | Fri Mar 14 1997 07:54 | 5 |
Just sort of curious but why do they need the 4100 connected to all
the SCSI busses? You don't mention what version they are at but
the ALPCLUSIO kit contains the SCSI naming code from V7.1, perhaps
that's the way to go.
| |||||
| 5255.2 | EEMELI::MOSER | Orienteers do it in the bush... | Fri Mar 14 1997 08:08 | 8 | |
re: .1
hmh, I think I disagree here. ALPCLUSIO only contains the part needed
to allow MSCP-serving of PAC-enabled devices, but not the full PAC
(port allocation class) code at all. i.e. there is no SYSGEN parameter
to turn on the new SCSI device naming in V6.2
/cmos
| |||||
| 5255.3 | Ingres must stay on 6.2 | SLOVAX::NEWMAN | Fri Mar 14 1997 11:51 | 17 | |
Customer has Ingres DB which means he cannot go to 7.1. He is
currently running 6.2-1H3. He wants to add a 4100 to move Ingres
reporting from the main two AS8400s (Online TP order entry systems) to
this new AS4100. He does not need 6 KZPSAs shared but he does need at
least 4.
It would be great if you could do 'ALPCLUSIO kit' in 6.2-1H3 but I
agree with Christian, I don't think there is a way to turn it on.
If someone knows differently, please let me know.
Alternately, if you could just tell OVMS to start at E on the 4100 then
things would be fine. I haven't even thought of a way to do that.
Sandy
| |||||
| 5255.4 | Move the KFTHA and the KFTIA to change names | SLOVAX::NEWMAN | Fri Mar 14 1997 16:45 | 9 | |
An interesting idea came up about making the PCI KZPSAs appear before
the KFTIA scsi's.
If you place the KFTHA connected to the PCI busses in front of KFTIA,
then the KZPSAs become A, B, C, D...and the SCSIs on the KFTIA follow.
Let me know what you think.
Sandy
| |||||