Question on Cluster network configuration

Hi Guys,
Just wanted to know the best practices for configuring network for clusters.
As far as I know, recommended is to have a separate network for Public/client communications and separate network for private heartbeat communication.
Does this change for Win 2008 & Win 2012 Clusters? I say this because I heard that there is no more need to have 2 dedicated networks and only 1 network is enough.
Is this true? If it is true , does it not a single point of failure ? What is the best practices for configuring sql clusters?
Thanks in advance.

Hi Samantha v,
You can first start with this video you can get an over view about cluster.
How Do I: Build a highly available virtualization cluster with Microsoft Windows Server 2008 R2 and Hyper-V?
http://technet.microsoft.com/en-us/video/how-do-i-build-a-highly-available-virtualization-cluster-with-microsoft-windows-server-2008-r2-and-hyper-v.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

VSA Manager 5.1 stuck in "Validating VSA Cluster Network Configuration"

Hi all!
I am experiencing a problem with VSA Manager 5.1.3.0 running on a Win2008R2 server with vCenter 5.1 build 1123961. When I open the VSA Mananger tab in the VI Client it displays "Validating VSA Cluster Network Configuration".
When trying to close the window it says:
I have tried to open the VSA Manager tab on another server with the VI Client installed but the result is the same. I have also tried to upgrade the VSA Manager to 5.5 but it stayed the same.
The cluster with the VSA nodes is working normally but I cannot manage VSA or upgrade the environment. Any advice or help would be greatly appreciated!
Best regards
Kenneth

Sorted with HP support, needed some extra tagging, jumbo frames and flow control.

Server 2008 R2 Failover cluster network configuration

Hi
We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
"Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
"Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
/Lasse

It will cause a lost network connection for any client that is accessing through that network. Those clients would need to reconnect.
Did you configure both IPs on the cluster resource name that clients are accessing? If you only configured the one you want, there should be no issue. If you configured both, then it is possible some clients might be connected via the private
network.
Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through. If the clients can only find the resource
through the DNS name registered, that is the way they will be coming in. In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
. : | : . : | : . tim

Hyper-V Failover Cluster Networking Configuration After Install

Hello All,
Is it possible to install hyper-v and failover or in other words create a hyper-v failover cluster and then configure the networking part of the solution later? As I am coming into
terms with the networking part of it, wanted to do it later after the install. Is it possible?
And from later configuration, I am trying to say, creation of NIC Team, Virtual NICs, VLAN tagging, etc.

Hi,
Failover cluster deployment requires network connectivity between cluster nodes. You can't create a cluster without properly configured TCP\IP on cluster nodes.
http://OpsMgr.ru/

Terminology for cluster networks

Hello!
I've already asked the question on cluster communication network here
http://social.technet.microsoft.com/Forums/windowsserver/en-US/2f650bfb-3544-4290-84e0-7138159e4cf2/cluster-heartbeat?forum=winserverfiles
"Q2:
Do all of these three types of cluster communication (including heartbeat) occur via the cluster network configured as in the preceeding screenshot (10.1.1.0) or, for example,
Network Health monitoring (including heartbeats) uses one network while
Intra-Cluster communication uses some other?"
and got the answer, but now I'd like to clearify one more thing: if all types of cluster communication (heartbeat + InterClusterCommunication+CSV) occur via the single network (it's often called "Heartbeat" network) why do some admins designate
two different networks for both Heartbeat and CSV
traffic simultaneously:
http://andreagx.blogspot.ru/2011/12/hyper-v-cluster-network-configuration.html
...while others do NOT designate separate network for the Heartbeat:
http://social.technet.microsoft.com/Forums/windowsserver/en-US/078950b0-b9e8-44a9-9f90-71a67df92cad/nic-assignments-for-2012-hyperv-cluster?forum=winserverClustering
"NIC 1 Management LAN
NIC 2 Cluster Shared Volume
NIC 3 Live Migration
NIC 4 iSCSI /MPIO
NIC 5 iSCSI /MPIO
NIC 6 Virtual Switch - Teamed
NIC 7 Virtual Switch - Teamed
NIC 8 Virtual Switch - Teamed"
So either the terms "Heartbeat network/nic" and
"CSV network/nic" are used interchangeably or I don't understand what
CSV network means...
Thank you in advance,
Michael

Hi Shaon,
Thank you for the reply!
Rather strange... I failed to find any information on msdn regarding separate CSV and Heartbeat traffic... The MSCA 2012 guide says there should be only ONE network adapter dedicated for inter-cluster communication:
And I don't understand what option should I choose to dedicate a Nic for CSV OR Heratbeat only - as far as I see there's only one option
"Allow cluster network communication on this network" that allows both CSV and heartbeat:
What option allows separation of CSV and Heartbeat? Would you please provide me with a link?
Regards,
Michael

Question on 11.2 RAC Networking Configuration

I have a random question regarding the network interface configuration for (specifically 11.2) an Oracle RAC requirement. Is there a requirement anywhere that states that all nodes in the cluster must have the same named interface on each distinct node serving the same purpose in order for all nodes of the cluster to communicate properly?
Here is an example of my question - My curiosity is, is this a requirement?
Node 1
eth1 - 10.0.0.1 (public)
eth1:1 10.0.0.25 (vip)
eth2: 192.168.1.25 (priv/interconnect)
Node 2
eth1 10.0.0.2 (public)
eth1:2 10.0.0.26 (vip)
eth5: 192.168.1.35 (priv/interconnect)
Note: eth2 is private on node 1, where eth5 is private on node 2.
Does node 2 have to follow the same pattern where eth1 is public, and eth2 is private, or for node 2, can eth5 be assigned to the private subnet and eth1 be assigned to the public subnet?
Odd question I know. Any means to clarify for me would be most helpful and appreciated.
Thanks,
CJ

Hi,
DBA wrote:
I have a random question regarding the network interface configuration for (specifically 11.2) an Oracle RAC requirement. Is there a requirement anywhere that states that all nodes in the cluster must have the same named interface on each distinct node serving the same purpose in order for all nodes of the cluster to communicate properly?
Here is an example of my question - My curiosity is, is this a requirement?
Node 1
eth1 - 10.0.0.1 (public)
eth1:1 10.0.0.25 (vip)
eth2: 192.168.1.25 (priv/interconnect)
Node 2
eth1 10.0.0.2 (public)
eth1:2 10.0.0.26 (vip)
eth5: 192.168.1.35 (priv/interconnect)
Note: eth2 is private on node 1, where eth5 is private on node 2.
Does node 2 have to follow the same pattern where eth1 is public, and eth2 is private, or for node 2, can eth5 be assigned to the private subnet and eth1 be assigned to the public subnet?
Doc 11.2.0.2 says:
About Network Hardware Requirements
* Public interface names must be the same for all nodes. If the public interface on one node uses the network adapter eth0, then you must configure eth0 as the public interface on all nodes. Network interface names are case-sensitive.
* You should configure the same private interface names for all nodes as well. If eth1 is the private interface name for the first node, then eth1 should be the private interface name for your second node. Network interface names are case-sensitive.
http://download.oracle.com/docs/cd/E11882_01/rac.112/e17264/preparing.htm#TDPRC123
Network Hardware Requirements (Linux Installation)
If you install Oracle Clusterware using OUI, then the public interface names associated with the network adapters for each network must be the same on all nodes, and the private interface names associated with the network adaptors should be the same on all nodes. This restriction does not apply if you use cloning, either to create a new cluster, or to add nodes to an existing cluster.
For example: With a two-node cluster, you cannot configure network adapters on node1 with eth0 as the public interface, but on node2 have eth1 as the public interface. Public interface names must be the same, so you must configure eth0 as public on both nodes. You should configure the private interfaces on the same network adapters as well. If eth1 is the private interface for node1, then eth1 should be the private interface for node2.
http://download.oracle.com/docs/cd/E11882_01/install.112/e17212/prelinux.htm#CWLIN209
As the documentation says this restriction is valid when Install using the OUI, but have different interface name is supported if configured manually.
Anyway if you are installing using the OUI you have the option to rename the interface thus like Bjoern said.
Can We Rename a Solaris Network Interface To Fit a New Node Into an Oracle RAC ? [ID 1288614.1]
Far as I Know using Solaris/AIX/Linux this is possible but depending on the OS and type of Kernel may not be supported.
Regards,
Levi Pereira

Can I change which nic is used for a cluster network when more than one nic on the node is on same subnet?

This cluster has been up and working for maybe a year and a half the way it is. There are two nodes, running Server 2012. In addition to a couple network interfaces devoted to VM traffic each node has:
Management Interface: 192.168.1.0/24
iSCSI Interface: 192.168.1.0/24
Internal Cluster Interface: 192.168.99.0/24
The iSCSI interfaces have to be on same subnet as management interfaces due to limitations in the shared storage. Basically if I segregate it I wouldn't be able access the shared storage itself for any kind of management or maintenance tasks.
I have restricted the iSCSI traffic to only use the one interface on each cluster node but I noticed that one of the cluster networks is connecting the management interface on one cluster node member with the iSCSI interface on the other cluster node member.
I would like for the cluster network to be using the management interface on both cluster node members so as not to interfere with iSCSI traffic. Can I change this?
Binding order of interfaces is the same on both boxes but maybe I did that after I created the cluster, not sure.

Hi MnM Show,
Tim is correct, if you are using ISCSI Storage and using the network to get to it, it is recommended that the iSCSI Storage fabric have a dedicated and isolated network. This
network should be disabled for Cluster communications so that the network is dedicated to only storage related traffic.
This prevents intra-cluster communication as well as CSV traffic from flowing over same network. During the creation of the Cluster, ISCSI traffic will be detected and the network
will be disabled from Cluster use. This network should set to lowest in the binding order.
The related article:
Configuring Windows Failover Cluster Networks
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Multihomed network configuration

So, when I say multihomed what I really mean is that Macbook Air is configured to use two network interfaces -- Wi-Fi and USB ethernet -- in one Location. Each interface is configured to work on a different subnet. In fact, wi-fi is assigned a public IP address of 195.88.xxx.xxx, and USB ethernet NIC a private address of 192.168.0.252/24. Wi-Fi is en0, and USB ethernet is en2. Both interfaces are in active state.
My goal is to have MBA to route all traffic to en0, except for 192.168.0.0/24 network which I want to go via en2, the USB ethernet card.
The topology is pretty simple:
Linux Laptop <--- Linksys Cisco Router <---   en2 via <--- MBA ---> via en0   ---> Linksys Cisco Router ---> <Internet>
Essentially, I need to put en2 on the ethernet segment where the Linux laptop is to be able to talk to it directly. No routing needed. This apporach works without any problems in Linux environment. However, on Mac OS X it doesn't work and it makes me wonder why.
A few details on what happens on the network:
tcpdump output from Linux machine (it is assigned 192.168.0.253/24):
13:08:17.476326 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 46
13:08:17.476354 ARP, Reply 192.168.0.253 is-at 00:13:77:49:00:be, length 28
13:08:18.476885 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 46
13:08:18.476911 ARP, Reply 192.168.0.253 is-at 00:13:77:49:00:be, length 28
13:08:19.478089 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 46
13:08:19.478113 ARP, Reply 192.168.0.253 is-at 00:13:77:49:00:be, length 28
13:08:20.478393 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 46
13:08:20.478417 ARP, Reply 192.168.0.253 is-at 00:13:77:49:00:be, length 28
13:08:21.479522 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 46
13:08:21.479551 ARP, Reply 192.168.0.253 is-at 00:13:77:49:00:be, length 28
and this is tcpdump output from Macbook Air:
13:08:17.473933 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 28
13:08:18.474507 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 28
13:08:19.475732 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 28
13:08:20.475968 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 28
13:08:21.477168 ARP, Request who-has 192.168.0.253 tell 192.168.0.252, length 28
I tried Service Reorder (in System Settings->Network) and set en2 as the first device on the list, or one position behind en0. It doesn't change anything.
My question is similar to these discussions:
https://discussions.apple.com/thread/2297388?start=0&tstart=0
https://discussions.apple.com/message/9984744?messageID=9984744#9984744?messageI D=9984744
and in one of them it is implied that no extra configuration should be made beyond what I've already done, but clearly Mac OS X doesn't see ARP request reply from the Linux machine.
BTW, firewalls are down on both systems.
I also found this network configuration manual for Princeton University campus network
http://www.net.princeton.edu/mac/network-config-x-10.8/caveats.html#ip-weakend
that claims that Mac OS X actually cannot do what I'm attempting to and refers to Weak End System Model which in essence is described in RFC4907 as:
In the Weak End System model, addresses refer to a host. As a
        result, packets sent on an outgoing interface need not
        necessarily have a source address configured on that interface,
        and incoming packets whose destination address does not
        correspond to the physical interface through which it is
        received are accepted.
That could explain why ARP request reply never makes it back to Mac OS X.
So, any ideas? Any tips?
I'd highly appreciate help of the community because I'm stuck

I dont have a PSC2210 but one of the documents I saw said to go to the front panel of the printer, press the Setup button, press 6 and then press 1 to print the Network Configuration page.
Binary_Zen (worked at HP )
Click the white Kudos star to say thanks
Please mark Accept As Solution if it solves your problem

HT203192 "networksetup is trying to modify the system network configurations" type your password to allow this.

"networksetup is trying to modify the system network configurations" type your password to allow this.Type your password to allow this. No amount of password typing seems to satisfy the request. The pop up box will not go away!!!!

Hi Glenyse,
Did you find the answer to your question? I have the same problem. Or can anyone else help?
My wife’s 2012 Macbook Pro has Yosemite and is using Wi Fi for the internet connection.
Every time, both on startup and awaking from sleep, a window appears on the desktop with a locked icon saying, “Networksetup is trying to modify this system. Type your password in to allow this”.
The window (which can’t be moved or dragged) shows the computer’s user name. The password has to be repeatedly typed in as many as 10 times and the highlighted ‘modify configuration’ box clicked before the window disappears and the computer then functions normally.
Needless to say, this is driving my wife up the wall… I would certainly appreciate information on how to get rid of this troublesome window!

Failover Cluster networking issue

Normally when configuring a SQL cluster you put the communication to the shared storage (usually a SAN) on a separate network, and so your config looks something like this (long live ms paint!):
So in this example the 192.168.100.0/28 subnet is used for cluster inter-communication (heartbeat) and for access to the shared storage. Access to the shared storage is kept completely isolated from the corporate network and everyone's happy.
On the corporate network side the cluster registers itself onto DNS on the 10.0.0.0/24 subnet and clients can resolver the cluster name and connect to it.
My configuration is slightly different though and I am having some problems with the networking side.
In my configuration my shared storage is a file server cluster with two nodes. So the "clients" of the file server cluster are the SQL servers themselves. As such, the network configuration should, as I see it, be something like this:
In this setup the SQL servers would still connect to the shared storage on a separate subnet, as per best practices, therefore keeping the cluster traffic separate from the corporate subnet.
However, for this to work the file server cluster IP address needs to be on the 192.168.100.0/28 subnet, and still be able to register on the DNS server on 10.0.0.0/24 subnet. Now this already involves setting up a lot more things than you would normally
on the cluster NICs, it is no longer just an IP address and a subnet mask, now you need a DNS server and a gateway, as well as ensuring that the DNS server is contactable from clients on the 192.168.100.0/28 subnet, meaning complete isolation is gone.
I can't find any best practices on how to get this done, and I don't think that the solution is to put this on a the cluster communication on the corporate network, nor to create a DNS server on the 192.168.100.0/28 subnet, so does someone have any ideas
how to get this done or how to improve the design of the setup?

Hi cogumel0,
In your case personal advice is you can add the additional NICs on SOFS computers and SQL cluster then make all this NIC at a same separate subnet such as 192.168.101.0/24,
disable the default settings with new added NICs: DNS register AND NetBios over TCPIP, then create a static DNS A record point to the new added NICs IP address.
Since the SQL on SMB storage only support the UNC path, we need create a another CAP On SOFS cluster (192.168.101.0/24 subnet CAP), after that we can create a static DNS A record
for this CAP and configure the SQL cluster access this CAP only.
The related information:
Install SQL Server with SMB Fileshare as a Storage Option
https://msdn.microsoft.com/en-us/library/hh759341.aspx?f=255&MSPPError=-2147217396
Using Multiple Client Access Points (CAP) in a Windows Server 2008 (R2) Failover Cluster
http://blogs.technet.com/b/askcore/archive/2010/08/24/using-multiple-client-access-points-cap-in-a-windows-server-2008-r2-failover-cluster.aspx
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Hyper-V internal (1 of 2, NOT Cluster) network unavailable in Failover Cluster Manager 2008R2

Hi all,
I had a very strange situation in my Hyper-V 2 nodes-cluster:
I have one networtk for HertBeat only (10.0.0.0/24) and second for HyperV internal networking for virtual machines (In properties marked "Do not allow clustern network communication")
Machines were working properly and any migration too.
One day, my secon done HyperV2 was marked red in Failover Cluster Manager mmc. I discovered that HyperV LAN is unavailable on this second node. BUT everything war working properly - HyperV2 node was on internet, communicated to AD domain, even culd run any
virtual machine...
Several times I checked the configuration, also check TMG configuratio, I was wondering if it can not be wrong settings on network access rule, I tried to restart this host - no result, ... network was still unavailable.
After about a hour I found the resolutuion:
On my second Hyper-V node Disable / Enable Local Area Connection network adapter, connected to Hyper-V LAN in Network Connections control panel!
Hope this will help to somebody ;)
Marian, just trying to help you

Resolutuion:
On affected Hyper-V node Disable / Enable Local Area Connection network adapter, connected to Hyper-V LAN in Network Connections control panel
I guess, sometnig flush on network configuration and / or some combination with network adapter driver
Marian, just trying to help you

Cluster network name resource error 1196

I have a two-node Hyper-V 2012 Core Server cluster. Initially, the cluster was working fine and I was able to do live migrations with no problem. I first realized that something had gone wrong when I was attempting to move a VM's storage to the Cluster Disk.
When I right click on the VM and select Move > Virtual Machine Storage, the bottom left area of the "move storage" screen says "Loading..." forever and never displays the cluster storage. This happened once before and I was able to correct
the issue by taking the Server Name resource offline and doing More Actions > Repair. However, if I try a repair now I receive the following error messages:
"There was an error repairing the active directory object for 'Cluster Name'. Error Code: 0x800713b8. The cluster request is not valid for this object".
I have verified that the cluster name Active Directory object (CCSDCluster) still exists and each node as well as itself has full permissions to the object. What I am not certain of is whether the object is still in the same Organizational Unit as it was
originally. After the failed repair attempt, I am able to bring the Server Name resource back online successfully.
In addition, I am continually receiving cluster event errors indicating the following:
"Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason: The handle is invalid. Ensure that the network adapters associated with dependent IP address resources are configured
with at least one accessible DNS server."
Each of the two nodes has multiple NICs configured. One for management, one for guest OSs (Hyper-V virtual switch is configured to use this NIC and not allow management OS access), and two for iSCSI (for redundancy and multi-path). Live migration is set
to only use the management NICs. The management NIC on both nodes is configured with valid DNS servers. The CCSDCluster DNS entry has full permissions for both nodes and itself.
Any suggestions on what to try would be greatly appreciated. Thank you!

Could my issues be related to a problematic network configuration? Please see the ipconfig below from one of my Hyper-V host servers.
Ethernet adapter Ethernet 8 = iSCSI
Ethernet adapter Ethernet 6 = iSCSI
Ethernet adapter Ethernet 2 = Management interface
10.1.3.19 = Management IP address, 10.1.3.3 = IP address of Cluster Name Object
Tunnel adapter Local Area Connection *11 = ?? Not sure what this one is
Windows IP Configuration
Host Name . . . . . . . . . . . . : CCSDVM01
Primary Dns Suffix . . . . . . . : clairton.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : clairton.local
Ethernet adapter Ethernet 9:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #4
Physical Address. . . . . . . . . : 28-92-4A-AF-46-34
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 8:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #3
Physical Address. . . . . . . . . : 28-92-4A-AF-61-68
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 7:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter #2
Physical Address. . . . . . . . . : 28-92-4A-AF-61-6C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 6:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : HP NC552SFP Dual Port 10GbE Server Adapter
Physical Address. . . . . . . . . : 28-92-4A-AF-46-30
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 172.16.1.11(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.1.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Ethernet 3:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #55
Physical Address. . . . . . . . . : E4-11-5B-B9-3A-9C
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Ethernet 2:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #58
Physical Address. . . . . . . . . : E4-11-5B-B9-3A-A2
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.1.3.19(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IPv4 Address. . . . . . . . . . . : 10.1.3.3(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.3.100
DNS Servers . . . . . . . . . . . : 10.1.3.10
10.1.3.39
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Failover Cluster Virtual Adapter
Physical Address. . . . . . . . . : 02-AD-4B-6D-A9-FB
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 169.254.2.92(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Remove VSA 5.1 but keep ESXi host network configurations

Hello,
I ran into problems with a 2-node vSphere 5.1 VSA Cluster not coming online after adding more hard disk and RAM to the physical ESXi hosts in the cluster. After talking with VMware Support for over 2 hours, we exported all of the virtual machine data and powered on the VMs running on just local storage on the ESXi hosts. Now I need to remove the broken VSA Cluster and deploy a new VSA Cluster without interrupting the production VMs now running on local storage.
I've looked at the cleanup.bat file, but am concerned about it resetting the network configurations on each of my hosts back to "greenfield" configurations at which time the VMs would all lose network connectivity.
Can the VSA Cluster be manually removed without causing an outage on the VMs? If so, where can I find those procedures?
Thanks!

Hi
Google for the following Subject "[Internal] Manual permanent destructive removal of a VSA cluster (2086522)"
Following this Article I removed an VSA-Cluster and did a brownfield Installation with Networksettings all be there.
Ingo

DAG 2010 Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network replication

Hello,
DAG Exchange 2010 SP3 RU6 with MAPI network and Replication network. All works correctly.
But, when the DAG member restarts , the cluster goes offline and i can't bring it online.
The message error:
Cluster IP address resource 'Cluster IP Address' cannot be brought online because the cluster network 'Cluster Network 1' is not configured to allow client access.
Cluster Network 1 is the replication network and it is normal that allow client access is unchecked
I already tried to check, apply then uncheck apply. it does anything.
Could you please help me to figure out the issue ?
Best regards

Hi,
Check below link.
http://forums.msexchange.org/Cluster_network_name_is_not_online/m_1800552315/tm.htm
I was able to resolve the issue without taking down any resources.
First, I noticed that the Failover Cluster Manager "Cluster Name" had the IP address of the replication network only..
After going back through the guide @
http://technet.microsoft.com/en-us/library/dd638104.aspx I changed the properties on the NICs for file sharing, etc..I then adjusted windows firewall rules to block traffic from my MAPI network destined for the replication network.
I then removed the IP from the replication network on the DAG leaving only the 1 MAPI network IP.
After an hour or so, I ran Get-DatabaseAvailabilityGroupNetwork and seen that the MAPIAccess property was finally set to true on my MAPI network. I went back to Failover Cluster Manager and my Cluster Core Resource Cluster Name dropped the IP address that was
associated (IP from the replication network) I added a new IP from my Mapi network range, updated the DAG IP in Exchange and the DNS record for the DAG and my cluster resource came online.

Routing and Remote access can cause cluster network issues?

After enabling routing and remote access on the servers, we found lots of cluster issues on our server like<o:p></o:p>
Cluster Service stopped
Communication was lost and reestablished between cluster nodes
Unable to access witness resource
Cluster resource failed
can RRAS enabling causes cluster network issues?
Rahul

Hi TwoR,
Please offer more information about your current cluster and RRAS configuration, such as are you installed the RRAS role on any cluster node? Are your cluster in Hyper-V environment?
Or if you want to create the RRAS cluster you can refer the following KB:
Deploy Remote Access in a Cluster
http://technet.microsoft.com/en-us/library/jj134175.aspx
How to configure Network Load Balancing (NLB) based cluster of VPN Servers
http://blogs.technet.com/b/rrasblog/archive/2009/07/02/configuring-network-load-balancing-nlb-cluster-of-vpn-servers.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Question on Cluster network configuration

Similar Messages

Maybe you are looking for