We are running a Hyper-V-Failover-Cluster with two Nodes. Starting mid-May I see the following error pop up in my event log on both Nodes (Switch-ID is different though)exactly once after a restart:
Fehler 18.05.2016 04:13:12 Hyper-V-VmSwitch 15 (1010)
Protokollname: System
Source: Microsoft-Windows-Hyper-V-VmSwitch
Date: 18.05.2016 04:13:12
Event-ID: 15
Aufgabenkategorie:(1010)
Ebene: Error
Schlüsselwörter:
Benutzer: SYSTEM
Computer: HUGSNODE01.xxxxx.xxx
Beschreibung:
Failed to restore configuration for port Properties (Friendly Name: ) on switch 505595D4-6D1E-4533-BE0E-338B30360C8F (Friendly Name: ), status = Der Objektname wurde nicht gefunden..
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Hyper-V-VmSwitch" Guid="{67DC0D66-3695-47C0-9642-33F76F7BD7AD}" />
<EventID>15</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>1010</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2016-05-18T02:13:12.084821000Z" />
<EventRecordID>216769</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="240" />
<Channel>System</Channel>
<Computer>HUGSNODE01.xxxxxxxxx.xx</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Status">3221225524</Data>
<Data Name="PortNameLen">10</Data>
<Data Name="PortName">Properties</Data>
<Data Name="PortFNameLen">1</Data>
<Data Name="PortFName">
</Data>
<Data Name="SwitchNameLen">36</Data>
<Data Name="SwitchName">505595D4-6D1E-4533-BE0E-338B30360C8F</Data>
<Data Name="SwitchFNameLen">1</Data>
<Data Name="SwitchFName">
</Data>
<Data Name="UniqueEvent">9</Data>
</EventData>
</Event>
There may be two incidents linked to the issue, although I am not sure about it.
Cluster-Aware-Updating was installing updates automatically. I remember that CAU was causing us major trouble once this year when an update one Node failed that also killed some Network settings. Major pain in the behind! I got it working again by reinstalling some network card drivers, but I honestly did not understand how. I followed some blog advice on the internet.
We also restructured the network connectivity at one point, deleting the NIC-Team and reconfiguring it. I don't think I made a mistake here, but just to be sure I'll say it.
I don't know what other Information you need, so I just copy-paste some I believe help
Once both Nodes are up and running, the cluster shows no errors and has full connectivity. But immediately after boot I see some weird errors regarding AD/DC/DNS/GPO issues and I believe this could be the underlying issue.
Please advise.
PS C:\Users\Administrator.AD> Get-VMSwitch | fl *
ComputerName : HUGSNODE01
Name : ClusterSwitch
Id : 505595d4-6d1e-4533-be0e-338b30360c8f
Notes :
SwitchType : External
AllowManagementOS : True
NetAdapterInterfaceDescription : Microsoft Network Adapter Multiplexor Driver
AvailableVMQueues : 0
NumberVmqAllocated : 0
IovEnabled : False
IovVirtualFunctionCount : 0
IovVirtualFunctionsInUse : 0
IovQueuePairCount : 0
IovQueuePairsInUse : 0
AvailableIPSecSA : 0
NumberIPSecSAAllocated : 0
BandwidthPercentage : 1
BandwidthReservationMode : Weight
DefaultFlowMinimumBandwidthAbsolute : 0
DefaultFlowMinimumBandwidthWeight : 1
Extensions : {Microsoft NDIS-Aufzeichnung, Microsoft Windows Filtering Platform}
IovSupport : False
IovSupportReasons : {SR-IOV wird von diesem Netzwerkadapter nicht unterstützt.}
IsDeleted : False
Key :PS C:\Users\Administrator.AD> Get-VMNetworkAdapter -ManagementOS
Name IsManagementOs VMName SwitchName MacAddress Status IPAddresses
---- -------------- ------ ---------- ---------- ------ -----------
LiveMigration True ClusterSwitch 00155D0A0142 {Ok}
Cluster True ClusterSwitch 00155D0A0141 {Ok}
Management and Client True ClusterSwitch 00155D0A0140 {Ok}