We just finished figuring out how to work with each Hyper-V Server 2008 R2 cluster node having a pair of Intel NICs teamed and then having a set of defined VLANs _on the teams_.
We will publish a post on the proper methodology for NIC teaming and team VLAN creation on the Intel Modular Server soon.
Now, we ran the Validate a Configuration wizard in Failover Cluster Manager (FCM) and ended up being surprised by the following:
Validate a Configuration Wizard
Testing has completed, but one or more tests indicate that the configuration is not suitable for clustering.
When we click the View Report button we see the following:
Network: Failed
Click on the Network hyperlink and we see:
Validate IP Configuration: Failed
When we scroll down to the Valid IP Configuration list for the nodes we see:
Found duplicate physical address 00-15-17-xx-xx-xx on node hv_node-01.xx.local adapter Local Area Connection 9 and node hv_node-01.xx.local adapter Local Area Connection 8.
Found duplicate physical address 00-15-17-xx-xx-xx on node hv_node-02xx.local adapter Local Area Connection 9 and node hv_node-02.xx.local adapter Local Area Connection 8.
Note that the MAC addresses are indeed the same for both Local Area Connections on each node. The MAC address indicated belong to the two VLANs running on Team 1 (the Management team).
So, we searched to see what would come up to work around the problem.
From the KB article:
A configuration which uses IEEE 802.1Q VLAN Tagging to connect to multiple VLANs for the public network interfaces, and has a seperate (sic) heartbeat network, will fail the cluster validation tests.
The validaton (sic) 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.
The article then states that the error will be changed to a warning in future product versions.
So, we can safely ignore the message.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
Co-Author: SBS 2008 Blueprint Book
*Our original iMac was stolen (previous blog post). We now have a new MacBook Pro courtesy of Vlad Mazek, owner of OWN.
No comments:
Post a Comment