Thanks for all the links for information. I reviewed them and found that the only thing I was missing was the VS= command... so far... HAHA

We opened a ticket...

Thanks for the useful command...

Would it be as simple as adding the VS= command since I have them setup as A/A... Virtual Server = PSQLA, Instance = INST1..

So alter...

If I detatch the nodes or stop the cluster service I loose the resources, i.e. no disk access and will not be able to see the system databases.

Okay all... thank you very much for your time but I figured it out...

It was a resource configuration issue.

Old Settings:

SQL Server (INST) Resource

- Dependencies

--- Disk

--- SQL Network Name (INST)

New...

Yes the new disks were added as cluster resources in there assigned group

In addition, all local disks have identical security permissions

Both the nodes are clustered...

After adding the new SAN disk both nodes are unable to see them in the management studio when changing log path.

Thanks for everyones help, we are up and running with no issues using the above firewall rules...

Also does that mean if I reboot either of the nodes it may pick a different port?

Is there any way to create an alias on the network so I don't have to reconfigure all the ODBC connections with the new ports as I migrate databases to...