hi we have 2 node clustering node 1(10.11.11.111) and node 2(10.11.11.112)
now here how to find the both nodes common "VIRTUAL IP " Address.
↧
how to find the Virtual IP address...
↧
Different but compatible version of the cluster service software
We have two physical servers in FCI and third server in different datacenter for DR with SQL Always On Configuredwhich is VM running same version of windows, we are getting the below alert
Node 'N1' which is physical established a communication session with node 'N3' which is VM and detected that it is running a different but compatible version of the cluster service software. It is recommended that the same version of the cluster service software be installed on all nodes in the cluster.
Can we ignore this safely?
↧
↧
How to create a local, non-clustered storage pool
Hello,
I have setup a two-node Failover Cluster, with a shared SAS DAS. So far so good.
One of the nodes also has internal disks that I wish to use for system backups.
This storage pool should not be clustered, as the disks cannot be seen from the other node. The trouble is that as soon as I create the pool it gets added to the cluster (in failed state).
In fact, the "Storage Pools" window in the server manager will only show me the "clustered storage spaces", with my internal disks in the Primordial pool.
Get-StorageSubSystem will show me both subsystems (Clustered Storage Space on ... + Storage Spaces on node-1) but fails to create a storage pool on the "local" subsystem.
How can I create a local, non clustered storage pool on internal disks ?
Cheers
alex
↧
Cluster Disk i/o Timeout
Hi ,
We are stuck in problem with our private cloud protection , when ever DPM trying to backup virtual machines the cluster shared volume i.o timeout and the disk disappeared for a moment and that cause my virtual machine rebooted unexpectedly and move to different nodes of cluster .
Follow are the configuration of my Infrastructure .
1. Windows server 2012 Cluster X 6 nodes
2. DPM 2012 SP1
Event Generated when backup initiate :
Cluster Shared Volume 'Volume2' ('CSV 7TB Cluster Disk Production') is no longer available on this node because of 'STATUS_CLUSTER_CSV_AUTO_PAUSE_ERROR(c0130021)'. All I/O will temporarily be queued until a path to the volume is reestablished.
I have applied hot fix as Microsoft recommended
http://support.microsoft.com/kb/2813630/en-us
Disabled ODX as well , because my storage doesn't support this feature .
please help me out to resolve this matter .
Best Regards,
Muzammil Ubaray
↧
Cluster Shared Volume is no longer accessible from cluster node
Hello,
We have a 3 nodes Hyper-v Cluster running Windows Server 2012. Recently we start having error below intermittently on a node, and the VMs running on this host and LUN will power off.
Alert: Cluster Shared Volume is no longer accessible from cluster node
Source: Cluster Service
Path: HV01.itl.local
Last modified by: System
Last modified time: 12/1/2013 12:27:18 AM
Alert description: Cluster Shared Volume 'Volume1' ('Cluster_Vol1_R6') is no longer accessible from this cluster node because of error 'ERROR_TIMEOUT(1460)'. Please troubleshoot this node's connectivity to the storage device and network connectivity.
The only changes made recently is we installed VEEAM on test basis for DR replication. We switched off the Veeam server and stop the Veeam Services on the Hyper-V Hosts but we are still having same issue.
We are using an EMC SAN connected via FC as Shared storage and Powerpath as Multi-Pathing. No errors were found on the SAN.
I don't think the issue is related to the number of IO as we also experienced the issue at midnight during the week-end where no one was working.
Any help would be very much appreciated.
Thanks.
Irfan
Irfan Goolab SALES ENGINEER (Microsoft UC) MCP, MCSA, MCTS, MCITP, MCT
↧
↧
Hyper-V Failover Cluster - Inconsistent Network Availability
We've got a Small cluster with, 7 hosts and a dozen or two VM's. For some reason i'm getting inconsistent availability with the Cluster networks. The host seem to function fine on there own but theres all types of issues using Migration which i'm assuming is because certain hosts think other hosts are unavailable. For Example:
Cluster Network 1 - From Host 8
Cluster Network 1 - From Host 10
As far as I can tell all of the networks are UP. I can ping all hosts on all interfaces. What criteria goes into determining host availability?
↧
Linux NFS share to Windows 2008 R2 cluster as a resource
Hello,
I would like to share a directory on RHEL 5 Linux server with Windows 2008 R2 server cluster having 2 nodes via NFS read only access to make it as a cluster resource to be accessible by cluster users.
Tried sharing in /etc/exports file as following, got permission denied at Windows server node when tried to open the folder after connecting to it.
/etc/exports file look like following:
/user/test_share windows_server.com(async)
Kindly let me know the best practice to accomplish this.
Thanks in advance.
↧
DNS name for sql clustering instance name
Hi all,
sql 2005 or sql 2008 clustering on windows 2008 R2
We create sql 2005 or sql 2008 clustering. The sql clustering
instance name (DNS name) was created manaully or created automatically in DNS.
is it issue if sql instance name was created manaully in DNS?
Thank you.
↧
Windows 2003 Clustrer- Resources in Evict node
We had a Windows 2003 cluster environment where we have evicted one node (1b) now.when user tires to take a RDP connection to the active node (1a) it says Socket error.The active node (1a) was rebooted.The issue is when the user connects to the evicted node
(1b) he is able to view Q drive, Z drive which is actually residing on the active node (1a).Could someone please let me know why is this happening ?
↧
↧
event id -5120
Hi All,
Can any one help me to resolve this issue. iam not geting 100% validation report for my cluster configaration...
DCluster Shared Volume 'Volume1' ('Cluster Disk 1') is no longer available on this node because of 'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the volume is reestablished.
↧
Moving a VM
How do you move a VM server from one hyper V manager to another?
↧
Windows 2012 Hyper-v Cluster Live Migration Failure
This is a fairly new deployment. When I first started having this issue, I foundhttp://support.microsoft.com/kb/2779204, which suggests that gpupdate /force will temporarily resolve the issue. That worked for me for several weeks, but no longer. It was always temporary and I had to do it at least once a day, but even that doesn’t work anymore and my Hyper-V guests are stuck. I also suspect if I have a Hyper-V host failure, the guests on the failed system will not come back up on the operational host.
kb2779204 suggest adding NT Virtual Machine\Virtual Machines in the entries for Log on as a Service. I have created a dedicated OU for the virtual hosts (as suggested by the kb article) and moved them to the new OU. I then addedNT Virtual Machine\Virtual Machines in the entries for Log on as a Service, then gpupdate /force and then wait minutes, then hours. It still doesn’t work. I get 2 slightly different depending on which server I initiate the live migration.
If from the server that currently is running the guest (HV1):
Live migration of 'Virtual Machine vg1' failed.
Virtual machine migration operation for 'dc4' failed at migration source 'HV1'. (Virtual machine ID 140C8893-44EC-481B-B8D5-52FCB8D422DC)
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration with host 'HV2': General access denied error (0x80070005).
The Virtual Machine Management Service failed to establish a connection for a Virtual Machine migration because the destination host rejected the request: General access denied error (0x80070005).
If from the server attempting to move the guest to (HV2):
Live migration of 'Virtual Machine vg1' failed.
Virtual machine migration operation for 'vg1' failed at migration destination 'HV1'. (Virtual machine ID 140C8893-44EC-481B-B8D5-52FCB8D422DC)
'vg1' Failed to create Planned Virtual Machine at migration destination: Logon failure: the user has not been granted the requested logon type at this computer. (0x80070569). (Virtual machine ID 140C8893-44EC-481B-B8D5-52FCB8D422DC)
↧
Windows Server 2012 licensing and storage for a cluster
Experts,
I have a some questions, hope someone can help me. One comment before I start, I am not a systems person but I am the one that pays for it and I like to know what I´m buying (so please forgive me if I make some mistakes on terminology or concepts). We will start migrating our infrastructure to VDIs (zero terminals). One consultant wishes to use Linux to get rid of Windows to reduce cost but I´m not so sure it will be so, because of open source consulting costs, but I need to know if Windows will cover everything we need.
1. I´m about to buy 2 servers with 2 processors to have them clustered for availability, we will have 2 VMs with critical applications. How Many licenses do I need to support this? my answer is 2 because each license cover 1 physical server with 2 processors, right? 2012 or 2012 R2 and why?
2. We want to attach a storage solution to better protect our data, I read that WS2012R2 doesn´t support NAS under a cluster scenario, why? then what should I use a DAS or a SAN? and why?
3. We have 'n' number of users connecting local and remote using zero terminals, how many and what kind of CALs do we need? and what will happen if one server fails do I need 'n' CALs in each server or can I make a pool of CALs (license server) that work in the cluster environment no matter wich node is up?
Thank you very much for any help you can povide me with.
FJ
↧
↧
Clustering times out when attempting MSCS for Exchange 2007 SCC
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 . :
↧
IIS is not failover when I stop IIS
I configured HA and I have resource of IIS configured(because I have few virtual web sites hosted on it) via the below link (through generic script, provided by MIcrosoft). Then I stop the IIS via iisreset /stop command to verify that when the service stops there should be a failover happen. But still the IIS services are not failing over to other node.
http://support.microsoft.com/kb/887417/en-us
====================================
I have also noticed one thing. I created a generic service resource for WWW service. Now when I stop it via "net stop W3svc" (multiple times) , the WWW service gets stop and the cluster group failover to another node...
Now I dont need the below script which provided by the below link:
http://support.microsoft.com/kb/887417/en-us
Any comment will be appreciated. Thanks. Zahid Haseeb.
↧
Failover Cluster Manager Missing
I created new Windows 2012 R2 Servers (non-core) and configured a functional failover cluster.
I then removed the GUI using the Powershell command:
Remove-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
After testing applications, it was determined that the applications would not run properly without the server GUI shell. I added it back using the following PowerShell command:
Add-WindowsFeature Server-Gui-Shell, Server-Gui-Mgmt-Infra
I notice that after this, when I go into Server Manager, Failover Cluster Manager is no longer available.
How do I restore it?
↧
Windows Server 2008 R2 Cluster - Network Adapter Teaming
Hi !
I´ve got a little question regarding NIC Adapter Teaming
in a Windows Server 2008 R2 WSFC Cluster for SQL Server 2008 R2.
In KB254101 I read, that there are no restrictions that
are associated with NIC teaming since Windows Server 2008
Failover Clusters.
Here is an example, in which way I would implement it:
Server: HP Proliant DL380 G7 with two (seperate) onboard
adapters (each dual-port).
Adapter A: Port 1 + 2
Adapter B: Port 3 + 4
I would team ...
Port 1+3 for the public network
and
Port 2+4 for the heartbeat network.
The Adapters were connected to different switches.
I think, this could be a good configuration.
What do you think?
Is this a supported configuration?
Many thanks in advance!
Greetings,
Karsten Mueller
↧
↧
disk failover works only in one direction winserver 2012R2
I have been banging my head against the wall trying to figure this out...
I have a cluster with WS2012R2
The cluster is on 2 HP DL360 G7 all latest rom drivers etc..
Connection to the disks is via emulex AH403A dual port fiber cards (the servers are identical)
3 disks are presented in the failover cluster manager.
When I try to move the disk from server1 (owner) to server2 it goes to status failed and owner as server2.
The error is :
Cluster resource 'Cluster Disk 1' of type 'Physical Disk' in clustered role '103f5606-e10d-46bd-83b7-2e4e770b5112' failed. The error code was '0x80070490' ('Element not found.').
I try to bring on line and stays failed. I then move it back to server1 and it goes online.
To move it I need to take it off line then move then take it online and this works.
If I then move the disk whose owner is now server2 to server1 it works without any problems (like it should)
I cant figure out why this move only work correctly in one direction.. I have all drivers and roms up to date.
Any help would be appreciated....
↧
How to test node failover in Windows 2008 R2 Failover Cluster?
Can anyone give me advice on how to properly test a node failure with a 2 mode Failover Cluster in Windows 2008 R2?
↧
Clustering times out when attempting MSCS for Exchange 2007 SCC
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 . :
↧