Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
mfemenel
Professor Frink
1421 Posts |
 Posted - 2009-07-29 : 19:38:06
|
| I just spent most of my day trying to figure out why a sql 2008 cluster validation report was complaining to me that I had a duplicate address on 2 of my servers. I'm running 2 hyper v instances on a dell 900 and I wanted to test clustering them together. I created hyper v instance one, installed the os, setup my roles and features for clustering and then imported/exported the hyper v files and created a new machine. after changing IP's, joining the domain and such I was ready to go. however when I ran the validation test it gave me an error similar to this: Found duplicate physical address 02-10-18-39-6D-38 on node servername.domainname.com adapter Local Area Connection* 9 and node server2name.domainname.com adapter Local Area Connection* 9. Here is the lesson learned. When you create an image of a hyper v server with failover clustering involved it essentially records the mac address of the first server and so when you stand up the 2nd instance you end up with a duplicate mac address. The fix is simple enough. Remove failover clustering feature and reinstall on the copied instance. (I removed/reinstalled on both to be doubly careful). Worked like a charm and I now have 2 hyper v instances as part of a cluster on the same box. Hope this saves someone else some time and some hair. Found the answer on this link if you want to read more.[url]http://kbalertz.com/969256/validation-fails-cluster-validation-wizard-Windows-Server-cluster.aspx[/url]Mike"oh, that monkey is going to pay" |
|
|
|
|
|
Fun with hyper v