761d6b7150
We originally had it such that if the connection topology was FL-loop (public loop), we never looked at any local loop addresses. The reason for not doing that was fear or concern that we'd see the same local loop disks reflected from the name server and we'd attach them twice. However, when I recently hooked up a JBOD and a system to an ANCOR SA-8 switch, the disks did *not* show up on the fabric. So at least the ANCOR is screening those disks from appearing on the fabric. Now, it's possible this is a 'feature' of the ANCOR. When I get a chance, I'll check the Brocade (it's hard to do this on a low budget). In any case, if they *do* also show up on the fabric, we should simply elect to not log into them because we already have an entry for the local loop. There is relatively unexercised code just for this case. MFC after: 2 weeks |
||
|---|---|---|
| .. | ||
| isp_freebsd.c | ||
| isp_freebsd.h | ||
| isp_inline.h | ||
| isp_ioctl.h | ||
| isp_pci.c | ||
| isp_target.c | ||
| isp_target.h | ||
| isp_tpublic.h | ||
| isp.c | ||
| ispmbox.h | ||
| ispreg.h | ||
| ispvar.h | ||