Table of Contents
Advertisement
SCSI Address Mapping
The driver emulates six SCSI buses per HBA to map all 126 possible AL_PA to
Target IDs.
The first bus is a dummy bus used to delay the initial inquiry scan until after
discovery completes. The 31 target IDs per bus are then mapped to either
ascending or descending SEL_IDs (based on the ScanDown registry parameter).
Note:
Fabric Device Mapping
In a fabric (switched) environment, devices are initially created in the order that
they are returned from the Simple Name Server (SNS). Once created (at boot), the
devices continue to be tracked based on:
Private Loop Device Mapping for Windows Platforms
In a private loop environment (FC-AL, no switch), devices are initially created
based on a fixed address ordering. Once created (at boot), the devices continue to
be tracked based on:
This section identifies the initial fixed mapping between the Windows NT
bus/target/lun and a Fibre Channel native address (AL_PA/SEL_ID). There are
two potential mappings based on a registry parameter [ScanDown=0 (driver
default); use *, ScanDown=1;].
Host Bus Adapter for Windows and Linux Installation Guide
The driver uses the first bus if the parameter MapBus0=1 is used.
–WWPN:HardAddress=0;MapNodeName=0
–NodeName:HardAddress=0;MapNodeName=1
–D_ID:HardAddress=1; (MapNodeName=don't care)
–WWPN:HardAddress=0;MapNodeName=0
–NodeName:HardAddress=0;MapNodeName=1
–D_ID:HardAddress=1; (MapNodeName=don't care)
Troubleshooting
57
Advertisement
Table of Contents
