Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
VMSMP EventID 28

Answered VMSMP EventID 28

  • Monday, January 25, 2010 2:26 PM
     
     
    Sign In to Vote
    0
    I have a Windows 2008 R2 DC Hyper-V server that this weekend decided to give us a BSOD.

    After recovering the server reports a lot of VMSMP EvenID 28: Port 'SWITCHPORT-SM-A6285CC8-5521-4180-BEE9-59C9929D26CB-1-1' was prevented from using MAC address '00-15-5D-64-3A-16' because it is pinned to port '27263E05-4CB3-4751-9' in the eventlog. Always this MAC address.

    I found the virtual server that has this MAC address set in the settings. However all our servers, including this one, use dynamic MAC addresses. I do not know if it is better to set them static or not but that is not the issue. The server that has this MAC address set to is not accessable on that virtual NIC from the outside. I can send a ping to any virtual machine on that psysical server but to no other server on the network.

    So connectivity ends at the virtual switch.

    I searched the internet but it seems not a widespread problem. Has anybody experienced this problem also. How did you fix this?


    Thnx in advance

    Update:
    I got a message that http://social.technet.microsoft.com/Forums/en-US/virtualmachinemanager/thread/c09a683f-9a17-4623-8647-0caafa8b86da might help. In it is a link to http://blogs.technet.com/jhoward/archive/2008/07/15/hyper-v-mac-address-allocation-and-apparent-network-issues-mac-collisions-can-cause.aspx. This seems to be the solution. I changed the MAC address and not connectivity is restored.


    Frank
     

All Replies

  • Wednesday, January 27, 2010 6:57 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

     

    This is not an error but a Warning. By the way, how often does it happen? Is something “not working” because of the Warning?

     

    The following event means that the switch port to which this machine is connected is preventing to assign that MAC address for the NIC of the machine. This sometimes happens if MAC addresses for the machine are being assigned dynamically. It's possible that another Hyper-V VM is plugged to the same switch and generated similar MAC address. You might want to assign an alternate static MAC address for this VM.

     

     

    Best Regards,

    Vincent Hu

     

     
  • Wednesday, January 27, 2010 10:02 AM
     
     Answered
    Sign In to Vote
    1

    Hi,

     

    This is not an error but a Warning. By the way, how often does it happen? Is something “not working” because of the Warning?

     

    The following event means that the switch port to which this machine is connected is preventing to assign that MAC address for the NIC of the machine. This sometimes happens if MAC addresses for the machine are being assigned dynamically. It's possible that another Hyper-V VM is plugged to the same switch and generated similar MAC address. You might want to assign an alternate static MAC address for this VM.

     

     

    Best Regards,

    Vincent Hu

     


    Hi Vincent,

    The event might be a warning. However it still is an error as the interface is not working and I thing Hyper-V should check if the MAC it is assigning to an interface is being used on the network. I fixed it by modifing the MAC address to an other fixed address. I found that I had a second Hyper-V server which uses the same range of MAC addresses. On that server I also got messages about the same MAC address. After changing the MAC address on the first server all messages disappeared.

    That I could not connect to the second server with the same MAC address might be that our Cisco PIX blocked access due to the same MAC address.

    Frank
     
  • Sunday, November 28, 2010 6:00 PM
     
     
    Sign In to Vote
    0

    If anyone is interested - I experienced the same problem today and found a different solution.  I have a 3 node cluster and was getting these VMSP warnings.  My VMs and host servers would drop about 5 pings every couple of minutes.  I realized that I recently moved the switches my cluster connects to and on the old switch I had ether channel configured and the new switches did not have ether channel configured.  So I changed the NIC teaming via the HP NCU from Switch-assisted to Transmit LB w/ Fault Tolerance.   That resolved the issue.  Of course I could have re-created my port-channel interfaces on the switch - but the switches I'm using now are not stackable so that is not an option.

    So check your nic teaming / switch configuration - that worked for me.

    Zach

    Zach Smith
     
  • Wednesday, December 29, 2010 11:03 AM
     
     
    Sign In to Vote
    1
    I had this same issue with my virtual NIC bound to my hardware NIC. I was receiving a warning four times a second. The MAC addresses were set to be generated dynamically. I checked conflicts for all my virtual NICs and did not find any. I switched the type for the NIC with conflicting MAC from External to Internal and back. That got the virtual NIC reset and fixed the issue.
     
  • Thursday, March 24, 2011 4:18 AM
     
     
    Sign In to Vote
    0

    I am facing similar issue with windows 2008 R2 DE. computer is getting unexpected shutdown error and vmsp warnings.

     

     

    Regards

    Suchit Gawali

    Suchit Gawali. Sr System Engineer
     
  • Thursday, March 31, 2011 8:05 AM
     
     
    Sign In to Vote
    0

    Good day.

    My fastest fix was to go virtual netw mgr  and deleted all my v/networks and recreated them. 

    And then all the VM guests, reassigned the new v/networks and made the MAC's static. 

    Resolved my issue immediately. 

    Hope this works for you.

    Allen. 

     
  • Thursday, September 01, 2011 3:25 PM
     
     
    Sign In to Vote
    0
    Vincent Hu; though you have mentioned several times about this being a warning; the affect of the MAC conflict causes recurring periods of time for VM to lose network connectivity.  Since one of our VMs is a high-volume and requires daily access for web updates; it is quite noticeable the "Connection Timeouts" received through the client browsers such as IE, FF, etc.  This MAC issue causes severe inconveniences to our customer base and internal access to manage the transactions on this server. There is a distinct pattern between the error log warnings on the Host and the connection timeouts in client browsers.  Hopefully, this blog will help resolve the problem for us; however, the error log Warning should actually be displayed as an Error since causes severe network error with Hyper-V.


     
  • Wednesday, September 21, 2011 7:41 AM
     
     
    Sign In to Vote
    0

    i tried this and now my network is totally unusable.   After switching from External to Internal i did "Apply" and OK.  Then i open the Virt Net Mgr again and swiched back to External.

    Now, i don't know how to fix it.  i thnk the NIC Team may be part of the problem.

    i have 6 Exchange VMs on ths network and it will be painful to recreate the networks.

    Any idea what went wrong and how to fix it?  The network now is enabled but does not connect to anything.  A network test says the gateway is the problem - no surprise i guess.

    Linda

     
  • Wednesday, September 21, 2011 8:10 AM
     
      Has Code
    Sign In to Vote
    0

    Hi Linda,

    Try deleting your virtual network switches one by one and creating new ones starting from that one, that switches to external network.

    1. Start the Hyper-V Manager snap-in and click the Virtual Network Manager... in the right-hand Actions panel.

    2. In the Virtual Network Manager dialog box select External in the Virtual Networks panel and click remove. Create the new virtual switch.

    3. In your virtual machine (the child partition) try executing the following:

    C:>ipconfig/flushdns && ipconfig/release && ipconfig/renew

    My guess is that this error may happen when bindings of virtual network that has External connection type to your physical adapter gets lost.

    I know, that doesn't seem to be a good solution but...

    Well this is the world we live in And these are the hands we're given...
     
  • Monday, November 07, 2011 8:22 PM
     
     
    Sign In to Vote
    0

    Hi all!

    I had the same error you mention, what I did was turn off each of the virtual machines in Network Adapter for each virtual machine, select the option "static" select Apply and OK, then restart my server and lit each of the VM and it can resolve the problem.

    Hope you can help.

    Greetings.

    • Edited by balfar27 Monday, November 07, 2011 8:23 PM
    •  
     
  • Tuesday, November 08, 2011 4:56 PM
     
     
    Sign In to Vote
    0

    No luck. I tried what Rafel did, and now am getting the identical error message referring to the newly generated static MAC address.

    In my case we have exactly ONE Hyper-V server, with exactly two virtual machines on it. The first one was migrated over from a VMWare server, using SCVMM, and it works fine aside from throwing these error messages 11 times a second. The VM on the VMWare server is off, of course. And the one NIC on the VMWare server does not have a mac address corresponding to the error

    either of the error-generating MAC addresses.

     

    Registry hack didn't work.

     

    Maybe I shouldn't worry, since it's only a 'warning' but when it fills the event log, it effectively removes the System Event Log as a functional resource for anything else.

     

    Typical Microsoft stuff -- when it works, it's brilliant; when it doesn't, troubleshooting is virtually impossible.

     

    tom
     
  • Monday, May 07, 2012 11:21 PM
     
     
    Sign In to Vote
    0
    I think I can trump that last post: not only one Hyper-V Server (R2): one VM!  Confusingly, the MAC that's listed in the system log error messages is from one of the server's physical NICs, not from the 00-15-5D dynamic range configured in the Virtual Network Manager. The VM is configured for dynamic. This error started and stopped today apropos of nothing. The VM was up before and after.
     
  • Monday, May 28, 2012 2:48 PM
     
     Proposed Answer
    Sign In to Vote
    0
    I might of found another alternative to fixing this issue without touching your physical Hyper v trunks. I was experiencing the same issue on 1 vm only in a newly created 4 node environment, all others vm's were fine. After live migrating from host to host error kept apearing. After further troubleshooting I noticed this one vm i flagged in scvmm under the hardware properties --> network adapters "enable virtual network optimizations". After removing this flag the issue disapperated and no more event id 28 VMSMP. I then live migrated from host to host and still no issue.
    • Proposed As Answer by Nick Renz Monday, May 28, 2012 2:48 PM
    •  
     
  • Wednesday, December 05, 2012 5:45 PM
     
     Proposed Answer
    Sign In to Vote
    0
    I had this same issue with my virtual NIC bound to my hardware NIC. I was receiving a warning four times a second. The MAC addresses were set to be generated dynamically. I checked conflicts for all my virtual NICs and did not find any. I switched the type for the NIC with conflicting MAC from External to Internal and back. That got the virtual NIC reset and fixed the issue.

    This worked for me, however when I did it the static NIC settings on my VM Host machine were changed, just like the warning message said when I changed from External to Internal, and back. No big deal, only the DNS entries had changed. I changed them back and now all is good, the VMSNP warning messages have stopped.
    • Proposed As Answer by KSosz Wednesday, December 05, 2012 5:46 PM
    • Edited by KSosz Wednesday, December 05, 2012 5:47 PM mistake
    •  
     
  • Sunday, December 09, 2012 10:44 PM
     
     
    Sign In to Vote
    1

    Had similar problem. Have Realtek NIC on MB and Intel Gigabit card. Had some problems witht he gigabit card in the past and had tried other cards.

    I have tried deleting and recreating the virtual switch in the past. This time, I:

    1. Deleted the virtual switch.

    2. Stopped the three Hyper-v services.

    3. Deleted remaining entries under the SwitchList Key and All NICs under the NicList Key of HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\VMSMP\Parameters.

    4. Restarted the services.

    5. Recreated the virtual switch.

    Now the events stopped filling my logs.

    Bob.