VMSMP Event ID 28 Warnings
Chris M
I am receiving several of these warnings in my system log. I have checked
seevral posts and have not found any useful information on how to resolve
this. It produces approximately one of these events a second. It happens
whether there is 1 VM running on a host or 5 VMs running. It logs n warning
for each VM repeatedly. There are no MAC address collisions; all cluster
hosts use different dynamic MAC ranges they assign to VMs and no two VMs are
using the same MAC address. There are no connectivity problems to the VMs
themselves, just thousands of these warnings happening on the Hyper-V hosts.
I have 7 nodes in my cluster and no matter which host I move the VMs to, this
just keeps occurring. If I recall, this has been happening since the
beginning. I have 4 physical NICs divided into 2 teams. 1 team is for OS
management and the cluster network. The other team is used for VM traffic
only. I do not have an IP assigned to this interface and am using VLAN
tagging configured in the HP Network Config Utility. VLAN tagging is also
configured for each VM in the VM settings. Does anyone know how I can
correct this?
Log Name: System
Source: VMSMP
Date: 6/17/2010 12:18:47 PM
Event ID: 28
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: *******7.dev.*****.com
Description:
Port 'C36380C5-FAEC-4CA3-AEB4-98ADFD2214DB' was prevented from using MAC
address '00-15-5D-C7-45-08' because it is pinned to port
'8E59BE88-007F-4BE8-A25F-BC4316D98C25'.
When additional VMs are on a host the same event gets generated except that
the MAC address is different and the 'pinned to port' is different. The
first port listed in the description is always the same on a particular
hyper-v host.
Eduardo
to have connectivity problems in the virtual machines. It's urgent to solve
this problem. Any help will be apreciated.
I have a two node cluster with Hyper-V R2 and a team with 3 network
adapters.
Thank you very much
"Chris M" <Chr...@discussions.microsoft.com> escribió en el mensaje de
noticias:4666D025-B4FF-47F9...@microsoft.com...
Manuel Leonhardt
We have solved this problem by deleting the external Network in Hyper-V. Deleteting the Team.Config on our Intel-Network-Cards (on your Virutal Host) (Pro/1000 PT Dualportadapters are not VLAN supportet) and Reboot your Server.
Next, create a new Team (use Fault-Tolerance! and not Virtual-Server Loadbalancign Mode for Team)
Create new external Network in Hyper-V and use the new Team-Adapter.
Now apply the new Network on the virtual-Clients und configure the V-LAN. While booting up, no errors should be written to the System-Log of your virutal-Host System.
Hope this helps you.
Manuel
>> On Friday, July 30, 2010 4:07 AM Eduardo wrote:
>> I have the same problem and I have not been able to solve it. I am beginning
>> to have connectivity problems in the virtual machines. it is urgent to solve
>> this problem. Any help will be apreciated.
>>
>> I have a two node cluster with Hyper-V R2 and a team with 3 network
>> adapters.
>>
>> Thank you very much
>>
>> noticias:4666D025-B4FF-47F9...@microsoft.com...
>> Submitted via EggHeadCafe
>> Custom task processes in SharePoint Designer Workflows
>> http://www.eggheadcafe.com/tutorials/aspnet/872c3a54-cc00-4fa0-b98b-2e9ea9a559dd/custom-task-processes-in-sharepoint-designer-workflows.aspx
Manuel Leonhardt
(From a Intel White-Paper: Those Nics dont support V-Lan Config. on virtualisation)
We changed the TEAM-Setting to "Switch Fault Tolerance"
And the Warnings in the System-Log are gone!
Greetiongs
Manuel
> On Thursday, June 17, 2010 12:38 PM Chris M wrote:
>> On Friday, July 30, 2010 4:07 AM Eduardo wrote:
>> I have the same problem and I have not been able to solve it. I am beginning
>> to have connectivity problems in the virtual machines. it is urgent to solve
>> this problem. Any help will be apreciated.
>>
>> I have a two node cluster with Hyper-V R2 and a team with 3 network
>> adapters.
>>
>> Thank you very much
>>
>> noticias:4666D025-B4FF-47F9...@microsoft.com...
>>> On Wednesday, November 24, 2010 5:51 AM Manuel Leonhardt wrote:
>>> In case you Problem is still there:
>>>
>>>
>>>
>>> We have solved this problem by deleting the external Network in Hyper-V. Deleteting the Team.Config on our Intel-Network-Cards (on your Virutal Host) (Pro/1000 PT Dualportadapters are not VLAN supportet) and Reboot your Server.
>>>
>>>
>>>
>>> Next, create a new Team (use Fault-Tolerance! and not Virtual-Server Loadbalancign Mode for Team)
>>>
>>>
>>>
>>> Create new external Network in Hyper-V and use the new Team-Adapter.
>>>
>>> Now apply the new Network on the virtual-Clients und configure the V-LAN. While booting up, no errors should be written to the System-Log of your virutal-Host System.
>>>
>>>
>>>
>>> Hope this helps you.
>>>
>>> Manuel
>>> Submitted via EggHeadCafe
>>> Client-server autodiscovery in C# and UDP Sockets
>>> http://www.eggheadcafe.com/tutorials/aspnet/9da74d3d-7415-4dfe-984e-2a5db900bdb2/clientserver-autodiscovery-in-c-and-udp-sockets.aspx
Manuel Leonhardt
(From a Intel White-Paper: Those Nics dont support V-Lan Config. on virtualisation)
We changed the TEAM-Setting to "Switch Fault Tolerance"
And the Warnings in the System-Log are gone!
Greetiongs
Manuel
> On Thursday, June 17, 2010 12:38 PM Chris M wrote:
>> On Friday, July 30, 2010 4:07 AM Eduardo wrote:
>> I have the same problem and I have not been able to solve it. I am beginning
>> to have connectivity problems in the virtual machines. it is urgent to solve
>> this problem. Any help will be apreciated.
>>
>> I have a two node cluster with Hyper-V R2 and a team with 3 network
>> adapters.
>>
>> Thank you very much
>>
>> noticias:4666D025-B4FF-47F9...@microsoft.com...
>>> On Wednesday, November 24, 2010 5:51 AM Manuel Leonhardt wrote:
>>> In case you Problem is still there:
>>>
>>>
>>>
>>> We have solved this problem by deleting the external Network in Hyper-V. Deleteting the Team.Config on our Intel-Network-Cards (on your Virutal Host) (Pro/1000 PT Dualportadapters are not VLAN supportet) and Reboot your Server.
>>>
>>>
>>>
>>> Next, create a new Team (use Fault-Tolerance! and not Virtual-Server Loadbalancign Mode for Team)
>>>
>>>
>>>
>>> Create new external Network in Hyper-V and use the new Team-Adapter.
>>>
>>> Now apply the new Network on the virtual-Clients und configure the V-LAN. While booting up, no errors should be written to the System-Log of your virutal-Host System.
>>>
>>>
>>>
>>> Hope this helps you.
>>>
>>> Manuel
>>>> On Wednesday, November 24, 2010 6:55 AM Manuel Leonhardt wrote:
>>>> I hade the same Problem. As additional information: We are using Intel Pro/1000 PT Dualportadapters configured as a TEAM. Team-Setting = "Virtual Machine Loadbalancing"
>>>>
>>>>
>>>>
>>>> (From a Intel White-Paper: Those Nics dont support V-Lan Config. on virtualisation)
>>>>
>>>>
>>>>
>>>> We changed the TEAM-Setting to "Switch Fault Tolerance"
>>>>
>>>>
>>>>
>>>> And the Warnings in the System-Log are gone!
>>>>
>>>>
>>>>
>>>> Greetiongs
>>>>
>>>> Manuel
>>>> Submitted via EggHeadCafe
>>>> Update Configuration of a ClickOnce WPF Application Using Mage or MageUI
>>>> http://www.eggheadcafe.com/tutorials/aspnet/a8788ed5-c1b5-41d5-b49c-ea4760c3b820/update-configuration-of-a-clickonce-wpf-application-using-mage-or-mageui.aspx
Manuel Leonhardt
(From a Intel White-Paper: Those Nics dont support V-Lan Config. on virtualisation)
We changed the TEAM-Setting to "Switch Fault Tolerance"
And the Warnings in the System-Log are gone!
Greetiongs
Manuel
> On Thursday, June 17, 2010 12:38 PM Chris M wrote:
>> On Friday, July 30, 2010 4:07 AM Eduardo wrote:
>> I have the same problem and I have not been able to solve it. I am beginning
>> to have connectivity problems in the virtual machines. it is urgent to solve
>> this problem. Any help will be apreciated.
>>
>> I have a two node cluster with Hyper-V R2 and a team with 3 network
>> adapters.
>>
>> Thank you very much
>>
>> noticias:4666D025-B4FF-47F9...@microsoft.com...
>>> On Wednesday, November 24, 2010 5:51 AM Manuel Leonhardt wrote:
>>> In case you Problem is still there:
>>>
>>>
>>>
>>> We have solved this problem by deleting the external Network in Hyper-V. Deleteting the Team.Config on our Intel-Network-Cards (on your Virutal Host) (Pro/1000 PT Dualportadapters are not VLAN supportet) and Reboot your Server.
>>>
>>>
>>>
>>> Next, create a new Team (use Fault-Tolerance! and not Virtual-Server Loadbalancign Mode for Team)
>>>
>>>
>>>
>>> Create new external Network in Hyper-V and use the new Team-Adapter.
>>>
>>> Now apply the new Network on the virtual-Clients und configure the V-LAN. While booting up, no errors should be written to the System-Log of your virutal-Host System.
>>>
>>>
>>>
>>> Hope this helps you.
>>>
>>> Manuel
>>>> On Wednesday, November 24, 2010 6:55 AM Manuel Leonhardt wrote:
>>>> I hade the same Problem. As additional information: We are using Intel Pro/1000 PT Dualportadapters configured as a TEAM. Team-Setting = "Virtual Machine Loadbalancing"
>>>>
>>>>
>>>>
>>>> (From a Intel White-Paper: Those Nics dont support V-Lan Config. on virtualisation)
>>>>
>>>>
>>>>
>>>> We changed the TEAM-Setting to "Switch Fault Tolerance"
>>>>
>>>>
>>>>
>>>> And the Warnings in the System-Log are gone!
>>>>
>>>>
>>>>
>>>> Greetiongs
>>>>
>>>> Manuel
>>>>> On Wednesday, November 24, 2010 6:56 AM Manuel Leonhardt wrote:
>>>>> I hade the same Problem. As additional information: We are using Intel Pro/1000 PT Dualportadapters configured as a TEAM. Team-Setting = "Virtual Machine Loadbalancing"
>>>>>
>>>>>
>>>>>
>>>>> (From a Intel White-Paper: Those Nics dont support V-Lan Config. on virtualisation)
>>>>>
>>>>>
>>>>>
>>>>> We changed the TEAM-Setting to "Switch Fault Tolerance"
>>>>>
>>>>>
>>>>>
>>>>> And the Warnings in the System-Log are gone!
>>>>>
>>>>>
>>>>>
>>>>> Greetiongs
>>>>>
>>>>> Manuel
>>>>> Submitted via EggHeadCafe
>>>>> Office Open XML File Formats - Word 2007
>>>>> http://www.eggheadcafe.com/tutorials/aspnet/190e6d8f-3c4e-427b-ab86-1afbf94a1869/office-open-xml-file-formats--word-2007.aspx