Wednesday, February 13, 2013 2:15 PM
I got the following error on an HP ML180 g6 server which hosts a single 2003 guest:
Port 'SWITCHPORT-SM-9A3E1BCC-1D22-42EA-BA42-3DCC42C9EC53-0-1' was prevented from using MAC address '00-15-5D-64-08-01' because it is pinned to port '39CFB32B-2760-461D-B'.
No changes were made to either of the servers or to their near environment - after almost a year and a half of flawless operation, this issue came completely out of the blue.
I tried recreating the virtual network, updating network drivers and even removing and adding the Hyper-V role again, but the issue wasn't resolved.
I then moved the 2003 guest to another HP ML350 g5 server, and I get the same error.
HP servers' NICs are NOT teamed, and I disabled all TCP/UDP offloading.
What might it be?...
EDIT: both hosts are 2008 R2
Thursday, February 14, 2013 1:17 PMAnyone?...
Thursday, February 14, 2013 1:20 PMI think you need to define a new static MAC address for the guest.
Thursday, February 14, 2013 1:35 PM
Thank you for your answer, however this is not the case - the problem is that InternalPort and ExternalPort are "fighting" over the same MAC. I get this error even if there's no virtual machine present on the server.
Thursday, February 14, 2013 1:39 PM
You're using a synthetic or emulated network adapter?
Thursday, February 14, 2013 1:41 PM
Is it possible that this is related?
Thursday, February 14, 2013 1:48 PM
I'm not sure what synthetic or emulated mean, in Hyper-v 2008 r2 I have a choice between 'network adapter' and 'legacy network adapter'. Tried them both, got the same error.
I'll try updating HP NCU and see if it helps but teaming is not enabled on the server so I'm a little skeptic...
Thursday, February 14, 2013 2:44 PMSynthetic and emulated mean the same as 'network adapter' and 'legacy network adapter' respectively... just different terms presented in SCVMM (weirdly enough). Okay, let us know how you go. It seems there are quite a number of issues related to this problem. Is there anything coming up in the event logs by the way?
Thursday, February 21, 2013 7:29 AMHow are things going RRonzanski? Any progress with your issue?
Thursday, February 21, 2013 8:19 AM
I ended up liquidating the virtual server, and moving the (only) service that is was running to a physical server. One less server in my environment, so maybe it's all for the best...
- Marked As Answer by Aiden_CaoMicrosoft Contingent Staff, Moderator Friday, February 22, 2013 2:52 AM
Thursday, February 21, 2013 1:21 PM
Well, that's one way to fix things!
Can you please be so kind as to mark the answer and any helpful posts? We really appreciate it.