cluster shared volume question


i'm standing windows 2012 r2 cluster in vmware environment. 3 cluster members on same subnet, built same image, , basic setup through failover cluster manager went fine.

have 2 iscsi luns, call them b , t. both presented 3 vm's, verified 3 vm's can see both luns in disk management. intention present them both cluster shared volumes cluster members can use them.

can never 3 nodes mount both luns @ same time.  the closest i've gotten 3 seeing b , 2 seeing t.  when lun doesn't mount, still creates entry under c:\clusterstorage, icon folder instead of mount or link.  doing dir command verifies folders, get-clustersharedvolume on non-mounting node shows both online.

enabled mpio feature , installed kb3172614 (roll-up update clustering). multiple reboots, no change.

several technet articles said check networks , make sure client ms networks , file/print sharing enabled. was. said make sure smb allowed; checked firewall , manually checked port 445 telnet between 3 cluster members measure.

other technet articles said if 1 of networks presented cluster storage network, set network no cluster traffic goes on it.  did that, no change.

failover cluster manager isn't reporting errors. nothing obvious in event log. missing??


"built same image,"

hopefully sysprepped image.  method microsoft supports cloning images.  in domain environment, can run issues when creating new vms 1 virtual hard disk.

"i can never 3 nodes mount both luns @ same time"

that's way cluster works.  single node mounts disk @ time.  owning, or controlling, node handles meta-data updates, such creating files, deleting files, creating directories, extending files, etc.  other nodes access csv write existing files.

suggest run cluster validation wizard on cluster.  point out potential or real problems have in configuration.


. : | : . : | : . tim



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607