Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

Server 2012 R2 - Cluster Failover - Virtual Lab

$
0
0

I'm attempting to setup a failover cluster in my lab for testing. After several attempts to get this to work, I'm now seeking advice. The moment I create the cluster I get the following behavior:

FIRST:

Event ID 1196

Cluster network name resource 'Cluster Name' failed registration of one or more associated DNS name(s) for the following reason:
DNS request not supported by name server.

Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server.

SECOND:

The Disks section of Server manager on both failover nodes reports the following warning:

Incomplete communication with cluster CLUSTER1. The following cluster nodes or clustered roles might be offline or have connectivity issues: CLUSTER1

THIRD:

After the cluster is created, the second node immediately takes ownership of the storage. No errors, but it seems odd that the first node isn't owner by default.

LAB ENVIRONMENT:

Windows 8.1 Desktop running Hyper-V.

  • DC1 - Domain Controller - DHCP/DNS
  • ISCSI - iSCSI target providing the storage
  • SERVER1 - Server 1 in my cluster, accepting storage via iSCSI Initiator
  • SERVER2 - Server 2 in my cluster, accepting storage via iSCSI Initiator

I have configured SERVER1 and SERVER2 with 2 NICS - 1 for regular network traffic and the other for heartbeat. My IP address scheme looks like this:

  • Lab Network: 10.0.1.0/24
  • Heartbeat: 10.10.10.0/24

I can confirm that after the cluster is created the computer object gets created side-by-side with the server objects. In my lab that lives under \Servers\Cluster. However, AD DNS shows no sign of a new record. I've tried manually creating a record, repairing the cluster, but still the 1196 error occurs.


Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>