Home > Hyper-V, Hyper-V R2, Windows 2008 R2 > Windows 2008 R2 Cluster Validation validation fail with the error, “Found duplicate physical address …”

Windows 2008 R2 Cluster Validation validation fail with the error, “Found duplicate physical address …”

This one was new for me, MS does not support teaming and this is well known. but most of the customers are looking to have redundant solution for their clusters. This would be easy if you have multiple NICs and you are building your teaming with them.

While I was building my 4 nodes cluster with 2 NICs on them..the network team decided to create teaming on all the servers so I have now 1 NIC teaming on every server.

We use HPs network configuration utility to team the two network adapters as well as setup 802.1Q technology on them.

VLAN settings:

VLAN Id & VLAN Name are 1.  This is our native VLAN and Public Network

VLAN Id & VLAN Name are 2 this is our private connection

VLAN Id & VLAN Names are 3. and this is our live migration network

When I run a validation report against the cluster I get a failure on validating IP configuration.  It states the following:

Found duplicate physical address xx-xx-xx-xx-xx-xx on node Server Name adapter VLAN 2 and same Server node adapter VLAN3.

Since the teaming is creating the new VLANs with the same MAC for the physical teaming we were runnig in this situation. Actually this was not new as I have been seen this error a lot since Windows 2008 Failover clustering.

The new thing that I found MS supporting that and you can ignore this error as per the KB

Cluster configurations using IEEE 802.1Q VLAN Tagging fail the cluster validation tests in Server 2008 and Server 2008R2

A configuration which uses IEEE 802.1Q VLAN Tagging to connect to multiple VLANs for the public network interfaces, and has a seperate heartbeat network, will fail the cluster validation tests.

The validaton test fails because the test detects that the same MAC address is in use on the 802.1Q VLAN networks.   However, this configuration is valid and is supported if this is the only failure in the validation tests and the failure is due to the use of IEEE 802.1Q VLAN Tagging .  All other cluster requirements still apply.

The validation will fail with the error, “Found duplicate physical address …”, and will detail which address is duplicate.
In future product versions, this failure will be changed to a warning.

So you can enjoy your teaming without any worry about support.

Advertisements
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: