I am working in a lab, and had the following configuration:
HOST1-PORT1 connected to MDS1 in VSAN10
HOST2-PORT1 connected to MDS2 in VSAN 20
DISK1-PORT2 connected to MDS2 in VSAN10
DISK2-PORT2 connected to MDS1 in VSAN 20
MDS1 and MDS2 were connected via a FCIP tunnel.
I could see everything as expected in the fcns database. What I wanted to do was have HOST1 use DISK1 from over the FCIP tunnel and HOST2 use DISK2 over the FCIP tunnel.
What I accidently did, was zone as follows:
From HOST1 I could not see DISK1 (windows disk manager), I could see it from HOST2 however, was able to format it and work with it. Once I figured out that I had zoned that drive to two hosts, I immediately went to correct it. And by the way, Sansurfer on HOST1 did show it saw the drive, but windows disk tools did not see it.
So on the MDS, I removed the incorrect pwwn, added the correct one, and activated the zoneset. Still HOST1 could not see the drive. HOST2 however could now see its new (corrected) drive. HOST2's sansurfer topology map was actually still showing both PWWN's, not sure if that was just cached or not as the DISK1 was no longer zoned to it.
So I reboot each HOST. Still no go, HOST1 could not see the DISK1! BTW, I checked the active zoneset and MDS reported all members correct and visible. So then I bounced each VSAN......honestly because I wasn't sure what else to do, and that still did not fix the issue, I tried to tell the disk management to rediscover drives but to no avail. Finally, came the sledgehammer. I bounced the actual FC ports. This fixed the problem.
My question is, is this normal behavior? I thought when I rebooted the windows hosts, it would cause them to do FLOGI again which I thought would be same as bouncing the FC ports. Did bouncing the host ports have anything to do with this resolution? Or was it the bouncing of the DISK ports that was the fix? What situation did I get myself into that the drive could not be seen by windows even though it was zoned to it?