ITEM: AZ3597L
RISCOHW: How to physically connect a 3995-C60 to 2 7205/F30's
Question:
I am looking to attach a 3995-C60 to two 7025/F30's. I need to know
two things. How do you cable the 3995-C60 for a twin tailed
environment and Does HACMP support the 3995-C60?
Here is the cabling that would be required for the configuration
you've proposed.
______________
! !
! 7025-F30 ! T
! ______! /
! !_2409_>----\< \#2114
! ! \\
! ! \\_____
!______________! !
!
! \#2424 or \#2425
!
______________ !
! ! _____!
! 7025-F30 ! /
! ______! /
! !_2409_>----\< \#2114
! ! \\
! ! \\_____
!______________! !
! \#2424 or \#2425
______________ !
! ! !
! 3995-C60 ! !
! _________! !
! ! DE SCSI >------------/
! ! (7201) ! \^\#7218
! !_DE_SCSI_>-T
!______________!
EXPLANATION OF FEATURE CODES:
2409 (F30): SCSI-2 Differential Fast/Wide PCI Adapter
2114 (F30): PCI SCSI Adapter 16-Bit Differential External Y-Cable
2424 (F30): 0.6m 16-Bit SCSI-2 System-to-System Cable
2425 (F30): 2.5m 16-Bit SCSI-2 System-to-System Cable
7201 (C60): Differential SCSI-2 Interface
7218 (C60): 8m Cable (68/50 Pin) for SCSI-2 Differential Fast/Wide
Adapter/A (\#2409)
When the 2114 Y-cables are ordered against the F30, they will include
a terminator. The terminator used in the 3995-C60 is shipped with the
3995 unit.
Attachment of multiple libraries to a SCSI adapter (daisy-chaining)
is supported for the 3995 with a differential SCSI interface only.
(A SCSI address is required for the autochanger and for each optical
drive within the library.) It is highly recommended that the 3995 be
attached to a dedicated SCSI bus with no other devices on the bus
(except additional 3995 libraries). The sharing of a bus with non-
3995 devices may cause potentially severe performance degradation,
and you do so at your own risk.
HACMP does not support the failover of the 3995-C60 or any other
model of the 3995. Whether or not it will work is another story.
Most likely you will be able to perform some pre and post events that
will allow the 3995 to be attached and failed over.
HACMP does not interact with the 3995 but it can provide the umbrella
for automation of the application recovery/restart provided by the
application that is writing to the 3995 (such as QSTAR, ADSM, etc).
Support Line: RISCOHW: How to physically connect a 3995-C60 to 2 7205/F30's ITEM: AZ3597L
Dated: May 1996 Category: N/A
This HTML file was generated 99/06/24~13:30:24
Comments or suggestions?
Contact us