Situation:
Attempting to build Exchange 2007 SCC environment. The two vmware virtual nodes pass the verification wizard but fail/time out when doing the actual MSCS wizard. I attempt to build the cluster using Failover Cluster Manager and list both systems as nodes for the cluster, the process stalls/"sits there" when it says "building the cluster" (last step of the chain in wizard before finish) and then ultimately times out leading to failure.
Attempted to build the cluster in parts, so I put system A/Eagle/.57 into cluster with zero issue. When I attempt to join system B/Hawk/.58, the join process stops/hangs at "Waiting for notification that node hawk is a fully functional member of the cluster." Running "cluster log /g /level:5" produces an output but the contents do not make any sense. Will post the output following this post for review.
ESX Nodes:
Four physical systems running ESX 4.0 (have not updated to 4.1 or 4.2). Each node in cluster has 2 Quadcore CPU, 48 GB RAM, 12 NIC ports (4 for production network (2 active/2 standby), 2 for FT/HA, 2 for iSCSI, 2 for private isolated network, and 2 unused connections), and a single HBA card with dual connections (port0 connects to controller A of FC SAN, port1 connects to ContollerB of FC SAN). There is not a FC Switch between cluster nodes and SAN.
Virtual Systems:
The non-shard drives are on Dell MD3000i iSCSI SAN and the shard drives (10 total) reside on Dell AX4-5 FC SAN. System-1 has the mappings for the RDM which are used by System-2. DRS is enabled by default but disabled for System1 and System2 so that I can put them both on a single node if necessary. System1 and System2 presently reside on seperate systems to prevent data corruption or connection confusion within the system. System.57 and System.58 are on same networks with same gateway and sub-net mask. Each vm system that will be part of the SCC has two interfaces. One for production network (XXX.XXX.4.__) and one for private network (called MSCS)(192.168.1.__). MSCS network has 192.168.x.x addresses and has no access to the production network as it was intended for internal communication between the two nodes for heartbeats. IPv6 was disabled/unchecked on all interfaces.
Questions:
1) I am lost as to where to look or what is causing the node addition to fail. Any ideas?
2) Does the MSCS even need the second interface to function? Is the second interface the problem?
3) Does the second interface need to be on production network as a method to connect to the systems outside of the interface used for Exchange traffic?
**Please excuse the fact I have sanitized some of the following data for security reasons.**
Did a ipconfig on the system that is already in cluster and the following was the output:
Windows IP Configuration
Ethernet adapter XXXXXX:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : XXX.XXX.4.57
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : XXX.XXX.4.59
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : XXX.XXX.4.1
Ethernet adapter MSCS:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.25
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection* 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{149940B7-9D2B-4B5B-B602-2B44EFC61449}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{9BFBCFA3-01B0-41ED-A4E6-A77ED244E05F}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{1575EC05-3AF4-4409-9076-483A534ABADE}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
ipconfig from system which I am attempting to add:
Windows IP Configuration
Ethernet adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter XXXXXX:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : XXX.XXX.4.58
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : XXX.XXX.4.1
Ethernet adapter Private:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.26
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.{6DB4FDA5-1DF4-4C5D-AACD-91B72681E1E9}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{139F2C67-0167-4286-8A10-D3130014CB03}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{289C9F6E-57A2-48EA-A8AD-BCC3914277CE}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Attempting to build Exchange 2007 SCC environment. The two vmware virtual nodes pass the verification wizard but fail/time out when doing the actual MSCS wizard. I attempt to build the cluster using Failover Cluster Manager and list both systems as nodes for the cluster, the process stalls/"sits there" when it says "building the cluster" (last step of the chain in wizard before finish) and then ultimately times out leading to failure.
Attempted to build the cluster in parts, so I put system A/Eagle/.57 into cluster with zero issue. When I attempt to join system B/Hawk/.58, the join process stops/hangs at "Waiting for notification that node hawk is a fully functional member of the cluster." Running "cluster log /g /level:5" produces an output but the contents do not make any sense. Will post the output following this post for review.
ESX Nodes:
Four physical systems running ESX 4.0 (have not updated to 4.1 or 4.2). Each node in cluster has 2 Quadcore CPU, 48 GB RAM, 12 NIC ports (4 for production network (2 active/2 standby), 2 for FT/HA, 2 for iSCSI, 2 for private isolated network, and 2 unused connections), and a single HBA card with dual connections (port0 connects to controller A of FC SAN, port1 connects to ContollerB of FC SAN). There is not a FC Switch between cluster nodes and SAN.
Virtual Systems:
The non-shard drives are on Dell MD3000i iSCSI SAN and the shard drives (10 total) reside on Dell AX4-5 FC SAN. System-1 has the mappings for the RDM which are used by System-2. DRS is enabled by default but disabled for System1 and System2 so that I can put them both on a single node if necessary. System1 and System2 presently reside on seperate systems to prevent data corruption or connection confusion within the system. System.57 and System.58 are on same networks with same gateway and sub-net mask. Each vm system that will be part of the SCC has two interfaces. One for production network (XXX.XXX.4.__) and one for private network (called MSCS)(192.168.1.__). MSCS network has 192.168.x.x addresses and has no access to the production network as it was intended for internal communication between the two nodes for heartbeats. IPv6 was disabled/unchecked on all interfaces.
Questions:
1) I am lost as to where to look or what is causing the node addition to fail. Any ideas?
2) Does the MSCS even need the second interface to function? Is the second interface the problem?
3) Does the second interface need to be on production network as a method to connect to the systems outside of the interface used for Exchange traffic?
**Please excuse the fact I have sanitized some of the following data for security reasons.**
Did a ipconfig on the system that is already in cluster and the following was the output:
Windows IP Configuration
Ethernet adapter XXXXXX:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : XXX.XXX.4.57
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : XXX.XXX.4.59
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : XXX.XXX.4.1
Ethernet adapter MSCS:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.25
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection* 14:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{149940B7-9D2B-4B5B-B602-2B44EFC61449}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{9BFBCFA3-01B0-41ED-A4E6-A77ED244E05F}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{1575EC05-3AF4-4409-9076-483A534ABADE}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
ipconfig from system which I am attempting to add:
Windows IP Configuration
Ethernet adapter Local Area Connection* 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Ethernet adapter XXXXXX:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : XXX.XXX.4.58
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : XXX.XXX.4.1
Ethernet adapter Private:
Connection-specific DNS Suffix . :
IPv4 Address. . . . . . . . . . . : 192.168.1.26
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . :
Tunnel adapter isatap.{6DB4FDA5-1DF4-4C5D-AACD-91B72681E1E9}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{139F2C67-0167-4286-8A10-D3130014CB03}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Tunnel adapter isatap.{289C9F6E-57A2-48EA-A8AD-BCC3914277CE}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :