Troubleshooting 4-9
Private Loop Device Mapping
In a private loop environment (FCAL, 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 Table
#define TARGETS_PER_BUS 32
i =
Table
Current Private Loop Device Mapping
Bus # |
| Target# |
| Lun# |
| *AL_PA |
| *SEL_ID |
| **AL_PA |
| **SEL_ID |
0 |
| None |
| None |
| None |
| None | ||||
|
|
|
|
|
|
|
|
|
|
|
|
|
1*** | 0 |
| 0x01 |
| 0x7D |
| 0xEF |
| 0x00 | |||
|
|
|
|
|
|
|
|
|
|
| ||
| 1 |
| 0x02 |
| 0x7C |
| 0xE8 |
| 0x01 | |||
|
|
|
|
|
|
|
|
|
|
| ||
| 2 |
| 0x04 |
| 0x7B |
| 0xE4 |
| 0x02 | |||
|
|
|
|
|
|
|
|
|
|
| ||
| 3 |
| 0x08 |
| 0x7A |
| 0xE2 |
| 0x03 | |||
|
|
|
|
|
|
|
|
|
|
| ||
| 4 |
| 0x0F |
| 0x79 |
| 0xE1 |
| 0x04 | |||
|
|
|
|
|
|
|
|
|
|
| ||
| 5 |
| 0x10 |
| 0x78 |
| 0xE0 |
| 0x05 | |||
|
|
|
|
|
|
|
|
|
|
| ||
| 6 |
| 0x17 |
| 0x77 |
| 0xDC |
| 0x06 | |||
|
|
|
|
|
|
|
|
|
|
|
|
|
*Use this translation if registry ScanDown = 0 (default)
**Use this translation if registry ScanDown = 1
***If MapBus0=1;, then device addressing starts with Bus #0, not #1
continued