Qlogic QLA 2342 Bedienungsanleitung Seite 21

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 22
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 20
6.5 Failover
Use the QLogic SANsurfer Manager application to enable and control the driver's ability to perform failover. Persistent
binding are enforced only when the driver has not been configured by QLogic SANsurfer Manager application;
otherwise, the configuration that QLogic SANsurfer Manager sets is used.
6.6 FC-SP Security
You can use the hbaN-security-protocols parameter to enable the driver's ability to perform DH-CHAP security
protocols on a per adapter. The security protocol used is DH-CHAP (Diffie Hellman - Challenge Handshake
Authentication Protocol). DH-CHAP with a NULL DH exchange is currently support for bidirectional authentication.
Hashing algorithm used is MD5, which has been ported from "RSA Data Security, Inc. MD5 Message-Digest
Algorithm". User must set the security keys for the HBA and device (ex. switch). Security keys must be 128 bits long,
which is the size of the hashing algorithm used. User must also associate the device node name with the security key
for the driver. This is done through the driver configuration file as a string containing the node name and security key
for a device. At minimum there would be at least two keys one for the adapter and one for the device. If there were a
switch between the device and the adapter there would have to be a key for it also. Boot is not currently supported
with security paths.
Security Key string = "WorldWideNodeName,SecurityKey";
Security Key Parameter Example:
Device-0-security-key="200000c0dd00c6be,88776655443322118877665544332211";
Device-1-security-key="200000e08b05a164,11223344556677881122334455667788";
7. Frequently Asked Questions
Q:
I installed an additional QLogic adapter in a system with a preexisting QLogic adapter, which is controlled by
the SUN qlc (leadville) driver. Why is the second adapter failing to attach?
A:
If you installed the additional adapter before installing the QLogic driver, initially both adapters are controlled
by Sun's qlc driver. When the QLogic driver is installed it indicates that driver has installed but failed to attach.
This is OK, since the second QLogic adapter is being temporarily controlled by Sun's qlc driver. The QLogic
adapter attaches itself to the second adapter after another reboot is done with the reconfigure (-r) option.
Q:
How are SCSI target ID's assigned for fabric devices?
A:
For devices on switches, if the adapter connection is F_Port then the target ID's start at zero, but if the
connection is FL_Port then the target ID's start at 129 and go up to 254.
Q:
Why do some of the devices connected to a switch fail to show up and how can I fix this?
A:
Some switches have known firmware problems that prevent the driver from detecting devices on the first try.
To work around this problem, you should add Persistent Name Binding entries for the devices connected to the
switch. This forces the driver to perform retries when the specified devices are not found during the fabric
configuration process.
Seitenansicht 20
1 2 ... 16 17 18 19 20 21 22

Kommentare zu diesen Handbüchern

Keine Kommentare