Table of Contents
Advertisement
Troubleshooting
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:
–WWPN:HardAddress=0;MapNodeName=0
–NodeName:HardAddress=0;MapNodeName=1
–D_ID:HardAddress=1; (MapNodeName=don't care)
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;].
The index into
#define TARGETS_PER_BUS 32
i = (Srb->PathId > 0) ? Srb->PathId-1 : 0; //Bus 0 = dummy bus nodeInx =
((I * (TARGETS_PER_BUS-1)) + Srb->TargetId;w
Table 4–5: Current Private Loop Device Mapping
Bus #
Target#
0
0-31
IMPORTANT:
0
*
1
2
3
4
5
6
7
8
9
*Use this translation if registry ScanDown = 0 (default).
**Use this translation if registry ScanDown = 1.
***If MapBus0= 1; then the device addressing starts with Bus#0, not Bus#1.
4–8
Table 4–5
can be derived by:
Lun#
*AL_PA
0-7
None
0-7
0x01
0-7
0x02
0-7
0x04
0-7
0x08
0-7
0x0F
0-7
0x10
0-7
0x17
0-7
0x18
0-7
0x1B
0-7
0x1D
host bus adapter for Windows and Linux installation guide
SEL_ID
**AL_PA
None
None
0x7D
0xEF
0x7C
0xE8
0x7B
0xE4
0x7A
0xE2
0x79
0xE1
0x78
0xE0
0x77
0xDC
0x76
0xDA
0x75
0xD9
0x74
0xD6
SEL_ID
None
0x00
0x01
0x02
0x03
0x04
0x05
0x06
0x07
0x08
0x09
Advertisement
Table of Contents
