User`s guide

● HBA beacon
● Target / LUN list
Workaround: None
7.2 Linux
7.2.1 Information Left After Deleting Persistent Configuration
Issue: Deleting the persistent configuration does not remove the options qla2x00
ConfigRequired=1 ql2xuseextopts=1 string from the /etc/modules file.
Workaround: To fully delete all persistent data, you must manually edit this file .
7.2.2 Non-Failover Driver
Issue: Under Linux, when running with a non-failover driver, the ConfigRequired=1 parameter is
ignored. Consequently, if it does not find a persistent binding entry, the driver automatically configures
the device. When running with a failover driver, the ConfigRequired=1 parameter indicates that a
device must have the matching config entry for it to be configured by the driver.
Workaround: Do one of the following:
● Make sure there is a persistent binding entry.
● Make sure the device has a matching config entry.
7.2.3 Features Not Available When Running IOCTL Module Driver
Issue: When running the input/output control (IOCTL) module driver on a Linux OS, the following
features are not available:
● Persistent binding
● Selective LUN
● HBA port statistics
● Driver settings
● Host topology
7.2.4 Features Not Available when Running Sysfs Inbox Driver
Issue: When running the Sysfs Inbox driver on a Linux OS, the following features are not available:
● Persistent binding
● Selective LUN
● HBA port statistics
● Driver settings
● Host topology
● Link Status
● Loopback test
Workaround: None
SANsurfer FC/CNA HBA Command Line Interface (CLI) Readme
7 of 10