Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Event ID 28 Source VMSMP

提議的解答 Event ID 28 Source VMSMP

  • Tuesday, June 01, 2010 10:01 AM
     
     
    Sign In to Vote
    0

    VMSPM error 28
    Port 'DAC3B97C-9274-46F6-A097-05200E9B2E3B' was prevented from using MAC
    address '00-15-5D-10-FC-03' because it is pinned to port
    '1E2A1849-F339-4C93-96D7-BF75E016692D'

    I'm having this error in a Windows 2008 R2 hyper v cluster with all mac
    adresses of all guest servers. Besides I'm having the same error on both
    nodes of the cluster with the physical adapter of the parent partition and
    the virtual switch created over that network adapter.

    Any help will be apreciated.

    Thanks in advance

     

All Replies

  • Tuesday, June 01, 2010 12:24 PM
     
     
    Sign In to Vote
    0

    Hi Eduardo,

    Did you configure the MAC Adress Range in the Virtual Network Manager ? 

    David LACHARI
     
  • Tuesday, June 01, 2010 2:13 PM
     
     
    Sign In to Vote
    0

    The mac Address Range in the Virtual Network Manager is Dynamic and it's different in both nodes of the cluster. Besides I have tried changing the mac address from one guest server to static but I keep on getting the same error (with the static mac address obviosly)

     
  • Monday, December 20, 2010 9:01 AM
     
     
    Sign In to Vote
    0

    Hi Eduardo,

     

    I am getting similar warnings Event ID 28 on both of the 2 hyper-v hosts on my cluster. The mac address range in VNM is also dynamics.

    Have you found any solution yet?

    Zay Yar
     
  • Monday, December 20, 2010 10:10 AM
     
     
    Sign In to Vote
    0
    This normally happens when two VM(having different ports on the Switch) try to get hold of the same MAC Address. If your MAC are being assigned dynamically in the VMs, trying changing the MAC Address (of one of the two) affected VMs, to a static (slightly different) MAC.

    http://social.technet.microsoft.com/Forums/en/winserverhyperv/thread/0e2a51e7-12ad-4014-805d-28f0e6c0c823
     
  • Tuesday, December 21, 2010 1:14 AM
     
     
    Sign In to Vote
    0

    Hi Kumar,

    Thanks for your reply. There's only one VM running on each host and I am still getting the warning.

    Zay Yar
     
  • Tuesday, January 25, 2011 10:00 AM
     
     
    Sign In to Vote
    0

    Hi i am having the same issue on an hyper-v Cluster does anyone has a solution for this ?

    regards,

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread
     
  • Tuesday, February 08, 2011 3:54 PM
     
     
    Sign In to Vote
    0
    I just want to share this, since I did not find this answer anywhere else. I too was having this error message on my Hyper-V server.  The odd thing is that everything had been working for almost a year, when all the sudden one afternoon connectivity to the server was sporatic and I was getting this message about once every 2 seconds.  Bottom line is, it ended up to have nothing to do with the server.  I had a network cable that had had the end pulled off of it where it plugged in to the computer in one of our computer labs (I work for a school) but was still plugged in to the switch on the other end.  All the wires  were touching each other causing a network loop.  Once this was fixed, the server quit shooting up errors.
     
  • Tuesday, March 27, 2012 2:27 AM
     
     
    Sign In to Vote
    0
    I just ran into this issue.  I tried to set the vms I had to use static macs and this did not work.  I powered off all the vms and unplugged the physical server nics from the network.  I was still receiving errors at this point.  I changed the MAC address of the physical NIC being reported in the error.  The events then changed to report the new mac address.  I deleted the virtual switch.  The errors stopped immediately.  I created a new virtual switch and assigned it back to all the vms.  I have had no issues since.
     
  • Thursday, June 07, 2012 7:00 AM
     
     
    Sign In to Vote
    0
    I appear to be having the same problem as well.
     
  • Thursday, June 28, 2012 10:27 AM
     
     Proposed
    Sign In to Vote
    2

    Just wanted to let you know that I just had the same issue, and it's only been around 15 mins since we seemingly got it resolved, but no messages are seen in the logs yet so that's a good sign. 

    What tried ALL sorts of things but what seems to have done the trick in the end was to power off all VM's, set them all to dynamic MAC, then uninstall the physical NIC from Device Manager, scan for hardware changes so it got installed again, delete the virtual network in HyperV manager and then create a new one, and then connect the vm's to the new virtual network. 

    Lumbago
    www.thefirstsql.com

    • Proposed As Answer by cbattis Thursday, September 13, 2012 2:14 AM
    •  
     
  • Thursday, September 13, 2012 2:13 AM
     
     
    Sign In to Vote
    0

    Excellent!!

    Lumbago's solution worked like a charm.  Been dealing with these events since November.

    • Edited by cbattis Thursday, September 13, 2012 2:13 AM
    •