It comes down to whether your storage processors are active/active or active/passive to how many paths you will see traffic using at one time. However, even on an active/passive array such as a VNX, your second path shouldn't be showing as dead.
Of course, zoning your fabric to the VM instead of the host will have an impact on the mobility of the VM. Whilst one of the use cases for NPIV is to be able to zone down to the VM for security reasons, typically I see zoning done to the host level only.
My requirement is to get all the paths visible at guest level(Linux). Is NPIV is the correct way to achieve that ?
>>> Of course, zoning your fabric to the VM instead of the host will have an impact on the mobility of the VM.
So, if I zone the physical paths at VM level, vMotion will not be supported. Is my understanding correct ?