User`s guide
2 – System Overview
Troubleshooting
FS0054601-00 E 2-13
Q
2.5.1.2
SANblade Manager
SANblade Manager displays target devices on an HBA, loop topology information,
loop error count information, etc. SANblade Manager displays target devices on an
HBA and is useful for analyzing system configurations. SANblade Manager uses a
feature of the enhanced miniport driver to find and display information about devices
that are not configured on the local host. This feature can display information about
all potential target devices on a fabric or all devices on a loop topology, not just
those that are configured on the local host.
2.5.2
Known Issues
2.5.2.1
Failover of JBOD Dual-Port Writes
Some older dual-ported just a bunch of disks (JBOD) drives have shared logic
between the drive’s A and B ports. If one HBA attempts a write command on port A
when the cable to port A is removed, the drive may wait indefinitely for data on
port A and never respond to failover commands on port B. This problem was
identified and reported to appropriate drive manufacturers. If you suspect this
problem, retry the failover using a read-only test. If this does not correct the problem,
contact your drive manufacturer for new firmware.
2.5.2.2
ConfigRequired Parameter
To maintain backward compatibility with previous versions, if the configuration
cannot be read from the registry, the miniport driver defaults to the previous
operation of configuring and enabling all devices that are found. Some OEMs
indicate that this is an unacceptable risk when adding a new host to a SAN system
and that the desired operation is to configure no devices instead of all devices. A
new parameter was added to miniport registry parameters to indicate that
configuration is required. Find this parameter in special OEM setup files in one of
the following strings, depending on the type of miniport driver:
HKLM\System\CurrentControlSet\Services\ql2200\
Parameters\Devices\DriverParameters
HKLM\System\CurrentControlSet\Services\ql2300\
Parameters\Devices\DriverParameters
The parameter value is ConfigRequired=0 (FALSE) or ConfigRequired=1 (TRUE).
If the parameter is not found, the default value is ConfigRequired=0. Note that this
parameter is used only when configuration information cannot be read from the
persistent storage.