I have a 2 node Hyper-V environment with failover clustering that I am in the process of adding an additional node to. I have added both the hyper-v and clustering roles to the new node. I have 4 CSV's that I utilize for the vhdx files as well as the quorum/witness drive. These CSV's sit on a netapp filer. My next step was to present the csv luns to the new node. I added the new node as an initiator to one of the luns then did a refresh on the MPIO app. The app as well as disk management both became unresponsive. I noticed the lun came up online and I am guessing this is why the server was struggling with the it. I restarted thte server and removed it from the list of initiators and everything came up fine. I have read the OS see's a disk signature because this is an existing operational lun and because of that wants to bring the lun online by default when it's being added.
Can someone tell me the process and or steps I should be following when it comes to the luns and adding them to the new hyper-v/clustering server that will prevent this from happening?