Hi Serge,
1- Yes
- The "real" WWPNs (…1011, …1024, etc.) are storage-to-storage/node-to-node connectivity ports, not designed to carry host I/O.
- The virtual WWPNs (…1015, …1019, etc.) are the actual host I/O ports you must zone to ESXi HBAs. You must zone 10:15's for SCSI 10:19's for NVMe host connection
- If you only zone to the node ports, you'll see the host candidates but paths will be "blocked."
2- No
3- show feature | include npiv
show npiv status
show fcns database vsan <ID>
------------------------------
Nezih Boyacioglu
------------------------------
Original Message:
Sent: Fri September 12, 2025 07:44 AM
From: Serge Kurskov
Subject: FS 7300 connection to CISCO MDS, FC SAN
Dear Team,
Could you please assist me to solve the Riddle Of SAN Connection Between FS7300 and CISCO MDS SAN switch
In short, I am building a POC setup at customer site that includes a FlashSystem 7300 v.9.1.0, production SAN built at CISCO/vsan and couple of ESXi servers. MDS version is 6.2(9a).
In short, storage can see the host candidates but all its pathes are blocked/offline.
I am stuck on basic operation that worked fine for many other vendor's storage and kindly asking for assistance.
Now here comes some details.
- All the hosts are zoned to FS7300 host ports. By checking active memebers at the SAN switch I can confirm that all the initiator WWNs and FS's port WWNs are zoned correctly and active.
- host candidated at storage side are reported correctly. I can see the host names, OS version, and initiators. But its status are offline.

checking more details for host candidate i found that there are some pathes from host to storage, but they are in "blocked" state. (hosts at screens below are from different hosts but situation is all the same)
------------------------------
Serge Kurskov
------------------------------