Hyper-V cluster validation report "Found duplicate physical address" on nic team interfaces.

I recently built a Windows 2012 Hyper-V cluster with 5 nodes. The validation report shows “duplicate physical address” error (error text pasted below).
The hardware: HP BladeSystem – servers are BL460c blades, in a c7000 enclosure, connected to HP Virtual Connect switches.
Each server has 2 physcal nics, teamed in Windows. In the NIC Teaming console, I created the following Team Interfaces and assigned each a VLAN ID:
“Team1” (the default team)
“Team1 - VLAN 204 – Management”
“Team1 - VLAN 212 - 2012HB”
“Team1 - VLAN 211 -Exchange DAG Replication”
I also created 2 HV Virtual Switches. Neither one allows management interface to share. They are assigned to “Team1” and “Team1 - VLAN 211 -Exchange DAG Replication” respectively.
Therefore, in Network Connection, I see the 2 physical Ethernet nics, and 4 “virtual” nics. Only 2 of them have IP addresses assigned: Management and HB. These are the two that the validation wizard complains
about.
The MAC address is not configurable in the NIC Teaming console, so I don’t see a way to resolve this error, except to use separate physical nics. I don’t want to do that because a) I would lose the benefits of
the bandwidth aggregation that Virtual Connect provides, and b) When creating an Interface on a Team in Windows, it looks like it ALWAYS gives it the same MAC address, so that should be a supported configuration.
Everything works just fine, and there are no other errors or IP conflicts or anything else. But I really want to fix it because I don’t know what unknown problems this may be causing.
From the Cluster Validation report:
Found duplicate physical address 10-60-4B-A9-4A-30 on node Cluster201.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster201.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address F0-92-1C-13-3C-2C on node Cluster202.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster202.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C1-7E-9C on node Cluster210.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster210.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 3C-4A-92-DE-1E-74 on node Cluster211.OurDomain.local adapter VC-Team - VLAN 212 - 2012HB and node Cluster211.OurDomain.local adapter
VC-Team - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C0-3D-50 on node Cluster212.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster212.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Thanks!
Dan

Hi Dan,
"It turns out that both hosts had the same default MAC address ranges for their virtual switches. Since the host vNICs were attached to the virtual switch on each host they received the first couple of MAC addresses from the switches.
For details please refer to following link:
http://www.jefflafr.com/blog/4/19/2013/conflicting-mac-addresses-when-building-a-hyper-v-cluster-with-converged-networking
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Failover Cluster Validation Report with warnings

Hi,
I have 2 Node cluster on windows 2008 R2.I have run cluster validation report and found following warnings pls suggest and guide me health of cluster and how to fix and remove these warnigns. thx.
Validate All Drivers Signed
Validate that tested servers contain only signed drivers.
Validating that the servers contain only signed drivers...
The node 'cluster1.domain.com'has unsigned drivers.
Device Name Device Class Driver Version Driver Date Manufacturer Inf Name Driver Name Device ID Description Status Start Mode
Virtual CloneDrive SCSIADAPTER 5.4.4.3 1/15/2011 12:00:00 AM Elaborate Bytes AG oem1.inf Value Not Found ROOT\SCSIADAPTER\0000 Virtual CloneDrive Value Not Found Unknown
Unsigned drivers were found on one or more of the servers.

Hi,
you need to run iso files at your cluster nodes often?
Well i think you need to provide iso files to your VMs. This is possible without "Virtual CloneDrive"!
I have seen many errors with this kind of software up to bluescreens.
But ok if you really need this software just ignore the warning from cluster validation report.
The cluster will work correctly if this are the only warnings from cluster validation report.
Regards
Sebastian

Failover Cluster Validation Report Error with IBM USB Remote NDIS Network device

We are setting up Microsoft Windows Server 2008 R2 Failover Cluster on IBM X3850 X5 and get errors in the Failover cluster Validation Report due to the IBM USB Remote NDIS Network Device is using APIPA adresses and both servers are using same APIPA-adresse.
How should I configure the Server and OS for the Failover cluster to be MS approved?
IBM don't recommend that i disable the Network device, but it is a possible solution!?!

What I did was use ipconfig /all to see the settings it is using and then when and set the ip setting on the NDIS driver to be that except I increment the last value by 1 for each node so that they do not have the same IP address. I ran the
cluster validation again and it came up clean and I have not experienced any issues yet. It does give warnings about it being an Automatic Private IP Address and should not be used, which is ok because we are not going to use it anyways.
Rich Baumet

Schedule Cluster Validation Report

Is there a way to schedule a validation report to run once a day? We would also need to have Storage deselected in the test selection. Thanks.

Alexey provided you with references to use PowerShell. Here is where you go to learn about the task scheduler -
http://technet.microsoft.com/en-us/library/cc721871.aspx Or, if you want to use PowerShell for that part, too -
http://technet.microsoft.com/en-us/library/jj649816.aspx
Your question really is not related to Hyper-V, though. Is there some other reason you posted in the Hyper-V forum?
. : | : . : | : . tim

Access is denied messages in Win2012 R2 Failover Cluster validation report and CSV entering a paused state

Been having some issues with nodes basically dropping out of clusters config.
Error showing was
"Cluster Shared Volume 'Volume1' ('Data') has entered a paused state because of '(c000020c)'. All I/O will temporarily be queued until a path to the volume is reestablished."
All nodes (Poweredge 420) connected a Dell MD3200 shared SAS storage.
Nodes point to Virtual 2012 R2 DC's
Upon running validation with just two nodes, get the same errors over and over again.
Bemused!
List Software Updates
Description: List software updates that have been applied on each node.
An error occurred while executing the test.
An error occurred while getting information about the software updates installed on the nodes.
One or more errors occurred.
Creating an instance of the COM component with CLSID {4142DD5D-3472-4370-8641-DE7856431FB0} from the IClassFactory failed due to the following error: 80070005 Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)).
and
List Disks
Description: List all disks visible to one or more nodes. If a subset of disks is specified for validation, list only disks in the subset.
An error occurred while executing the test.
Storage cannot be validated at this time. Node 'zhyperv2.KISLNET.LOCAL' could not be initialized for validation testing. Possible causes for this are that another validation test is being run from another management client, or a previous validation test was
unexpectedly terminated. If a previous validation test was unexpectedly terminated, the best corrective action is to restart the node and try again.
Access is denied
The event viewer on one of the hosts shows
Cluster node 'zhyperv2' lost communication with cluster node 'zhyperv1'. Network communication was reestablished. This could be due to communication temporarily being blocked by a firewall or connection security policy update. If the problem persists
and network communication are not reestablished, the cluster service on one or more nodes will stop. If that happens, run the Validate a Configuration wizard to check your network configuration. Additionally, check for hardware or software errors related
to the network adapters on this node, and check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.
The Cluster service is shutting down because quorum was lost. This could be due to the loss of network connectivity between some or all nodes in the cluster, or a failover of the witness disk.
Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected
such as hubs, switches, or bridges.
Only other warning is because the 4 nic ports in each node server are teamed on one ip address split over two switches - I am not concernd about this and could if required split then pairs, I think this is a red herring????

Hi,
Such events happen because of the following reason:
1- Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks not enabled on all network interfaces. Check this KB article: http://support.microsoft.com/kb/2008795
. Please make sure these two protocols are enabled on all cluster networks
2- Network connectivity issue can cause this event as well. Please make sure the network cabling/Cards/Switches are correctly configured and working as expected
3- Connectivity issue with the storage can also cause this event. Please make sure all the nodes are connected to storage. Check HBA/Cabling connectivity to SAN. Make sure
that the SAN drivers are up-to-date.
4- Antivirus may interrupt network communication and cause this failure. Please exclude CSV volumes from being scanned by AV: http://social.technet.microsoft.com/wiki/contents/articles/953.microsoft-anti-virus-exclusion-list.aspx
5- Disable TCP Chimney related settings on all cluster nodes. http://support.microsoft.com/kb/951037
6- Please check the Network Binding Order (http://social.technet.microsoft.com/Forums/windowsserver/en-US/2535c73a-a347-4152-be7a-ea7b24159520/hyperv-r2-csv-cluster-recommended-binding-order?forum=windowsserver2008r2highavailability)
7- Firewall Rules For All Inbound and Outbound For Cluster and Hyper-V for all the Profiles
8- Update NIC Driver/Firmware.
9- Check Compatibility of the NIC with Windows Server 2012R2
10- Set-NetAdapterRss - Resources and Tools for IT Professionals | TechNet : http://technet.microsoft.com/en-us/library/jj130863.aspx
11- Check the Following Article http://social.technet.microsoft.com/Forums/windowsserver/en-US/e06fede9-931c-4dee-8379-4fd985e20f0a/hypervvmswitch-eventid-106
12- General Updates to be applied on the nodes :
Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013 : http://support.microsoft.com/kb/2887595
Windows 8.1 and Windows Server 2012 R2 General Availability Update Rollup :
http://support.microsoft.com/kb/2883200
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

No Systems relevant for Configuration-Validation Reporting found!

Hi,
When we access http://<host>:<port>/sap/bc/webdynpro/sap/diagcpl_virt_sys and want to create a target system, we don't see any source system, although we configured several systems in E2E RAC. Please can you asssist.
Br
Steven

Hi Steven,
Configuration Validation displays source systems that are available in the E2E Change Management.
You need a system to be registered in E2E Diagnostics and have at least one config store.
To check this start the Root Cause Workcenter and navigate to the "System Analysis".
Select a system and clic "Change Reporting".
You would see config stores available for this system.
If you see no stores or systems - you need to check E2E Diagnostics setup
Best regards
Andrey

Hyper-V Cluster Name offline

We have a 2012 Hyper-V cluster that isn't online and we can't migrate VMs to the other Hyper-V host. We see event errors in the Failover Cluster Manager:
The description for Event ID 1069 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Cluster Name
Cluster Group
Network Name
The description for Event ID 1254 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Cluster Group
The description for Event ID 1155 from source Microsoft-Windows-FailoverClustering cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component
on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ACMAIL
3604536
Any help or info is appreciated.
Thank you!

Here is the network validation. Any thoughts?
Failover Cluster Validation Report
Failover Cluster Validation Report
      Node: ACHV01.AshtaChemicals.localValidated
      Node: ACHV02.AshtaChemicals.localValidated
      Started8/6/2014 5:04:47 PM
      Completed8/6/2014 5:05:22 PM
The Validate a Configuration Wizard must be run after any change is made to the
configuration of the cluster or hardware. For more information, see
Results by Category
      NameResult SummaryDescription
      NetworkWarning
Network
      NameResultDescription
      List Network Binding OrderSuccess
      Validate Cluster Network ConfigurationSuccess
      Validate IP ConfigurationWarning
      Validate Multiple Subnet PropertiesSuccess
      Validate Network CommunicationSuccess
      Validate Windows Firewall ConfigurationSuccess
Overall Result
Testing has completed for the tests you selected. You should review the
warnings in the Report. A cluster solution is supported by Microsoft only if
it passes all cluster validation tests.
List Network Binding Order
Description: List the order in which networks are bound to the adapters on
each node.
ACHV01.AshtaChemicals.local
        Binding OrderAdapterSpeed
        iSCSI3Intel(R) PRO/1000 PT Quad Port LP Server Adapter #31000 Mbit/s
        Ethernet 3Intel(R) PRO/1000 PT Quad Port LP Server AdapterUnavailable
        Mgt - HeartbeatMicrosoft Network Adapter Multiplexor Driver #42000
Mbit/s
        Mgt - LiveMigrationMicrosoft Network Adapter Multiplexor Driver #32000
        Mbit/s
        MgtMicrosoft Network Adapter Multiplexor Driver2000 Mbit/s
        iSCSI2Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #371000
        Mbit/s
        3Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)Unavailable
ACHV02.AshtaChemicals.local
        Binding OrderAdapterSpeed
        Mgt - HeartbeatMicrosoft Network Adapter Multiplexor Driver #42000
Mbit/s
        Mgt - LiveMigrationMicrosoft Network Adapter Multiplexor Driver #32000
        Mbit/s
        MgtMicrosoft Network Adapter Multiplexor Driver #22000 Mbit/s
        iSCSI1Broadcom NetXtreme Gigabit Ethernet #71000 Mbit/s
        NIC2Broadcom NetXtreme Gigabit EthernetUnavailable
        SLOT 5 2Broadcom NetXtreme Gigabit EthernetUnavailable
        iSCSI2Broadcom NetXtreme Gigabit Ethernet1000 Mbit/s
Back to Summary
Back to Top
Validate Cluster Network Configuration
Description: Validate the cluster networks that would be created for these
servers.
Network: Cluster Network 1
DHCP Enabled: False
Network Role: Disabled
One or more interfaces on this network are connected to an iSCSI Target. This
network will not be used for cluster communication.
        PrefixPrefix Length
        192.168.131.024
        ItemValue
        Network InterfaceACHV01.AshtaChemicals.local - iSCSI3
        DHCP EnabledFalse
        Connected to iSCSI targetTrue
        IP Address192.168.131.113
        Prefix Length24
        ItemValue
        Network InterfaceACHV02.AshtaChemicals.local - iSCSI2
        DHCP EnabledFalse
        Connected to iSCSI targetTrue
        IP Address192.168.131.121
        Prefix Length24
Network: Cluster Network 2
DHCP Enabled: False
Network Role: Internal
        PrefixPrefix Length
        192.168.141.024
        ItemValue
        Network InterfaceACHV01.AshtaChemicals.local - Mgt - Heartbeat
        DHCP EnabledFalse
        Connected to iSCSI targetFalse
        IP Address192.168.141.10
        Prefix Length24
        ItemValue
        Network InterfaceACHV02.AshtaChemicals.local - Mgt - Heartbeat
        DHCP EnabledFalse
        Connected to iSCSI targetFalse
        IP Address192.168.141.12
        Prefix Length24
Network: Cluster Network 3
DHCP Enabled: False
Network Role: Internal
        PrefixPrefix Length
        192.168.140.024
        ItemValue
        Network InterfaceACHV01.AshtaChemicals.local - Mgt - LiveMigration
        DHCP EnabledFalse
        Connected to iSCSI targetFalse
        IP Address192.168.140.10
        Prefix Length24
        ItemValue
        Network InterfaceACHV02.AshtaChemicals.local - Mgt - LiveMigration
        DHCP EnabledFalse
        Connected to iSCSI targetFalse
        IP Address192.168.140.12
        Prefix Length24
Network: Cluster Network 4
DHCP Enabled: False
Network Role: Enabled
        PrefixPrefix Length
        10.1.1.024
        ItemValue
        Network InterfaceACHV01.AshtaChemicals.local - Mgt
        DHCP EnabledFalse
        Connected to iSCSI targetFalse
        IP Address10.1.1.4
        Prefix Length24
        ItemValue
        Network InterfaceACHV02.AshtaChemicals.local - Mgt
        DHCP EnabledFalse
        Connected to iSCSI targetFalse
        IP Address10.1.1.5
        Prefix Length24
Network: Cluster Network 5
DHCP Enabled: False
Network Role: Disabled
One or more interfaces on this network are connected to an iSCSI Target. This
network will not be used for cluster communication.
        PrefixPrefix Length
        192.168.130.024
        ItemValue
        Network InterfaceACHV01.AshtaChemicals.local - iSCSI2
        DHCP EnabledFalse
        Connected to iSCSI targetTrue
        IP Address192.168.130.112
        Prefix Length24
        ItemValue
        Network InterfaceACHV02.AshtaChemicals.local - iSCSI1
        DHCP EnabledFalse
        Connected to iSCSI targetTrue
        IP Address192.168.130.121
        Prefix Length24
Verifying that each cluster network interface within a cluster network is
configured with the same IP subnets.
Examining network Cluster Network 1.
Network interface ACHV01.AshtaChemicals.local - iSCSI3 has addresses on all
the subnet prefixes of network Cluster Network 1.
Network interface ACHV02.AshtaChemicals.local - iSCSI2 has addresses on all
the subnet prefixes of network Cluster Network 1.
Examining network Cluster Network 2.
Network interface ACHV01.AshtaChemicals.local - Mgt - Heartbeat has addresses
on all the subnet prefixes of network Cluster Network 2.
Network interface ACHV02.AshtaChemicals.local - Mgt - Heartbeat has addresses
on all the subnet prefixes of network Cluster Network 2.
Examining network Cluster Network 3.
Network interface ACHV01.AshtaChemicals.local - Mgt - LiveMigration has
addresses on all the subnet prefixes of network Cluster Network 3.
Network interface ACHV02.AshtaChemicals.local - Mgt - LiveMigration has
addresses on all the subnet prefixes of network Cluster Network 3.
Examining network Cluster Network 4.
Network interface ACHV01.AshtaChemicals.local - Mgt has addresses on all the
subnet prefixes of network Cluster Network 4.
Network interface ACHV02.AshtaChemicals.local - Mgt has addresses on all the
subnet prefixes of network Cluster Network 4.
Examining network Cluster Network 5.
Network interface ACHV01.AshtaChemicals.local - iSCSI2 has addresses on all
the subnet prefixes of network Cluster Network 5.
Network interface ACHV02.AshtaChemicals.local - iSCSI1 has addresses on all
the subnet prefixes of network Cluster Network 5.
Verifying that, for each cluster network, all adapters are consistently
configured with either DHCP or static IP addresses.
Checking DHCP consistency for network: Cluster Network 1. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local -
iSCSI3 matches network Cluster Network 1.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local -
iSCSI2 matches network Cluster Network 1.
Checking DHCP consistency for network: Cluster Network 2. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local - Mgt
- Heartbeat matches network Cluster Network 2.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local - Mgt
- Heartbeat matches network Cluster Network 2.
Checking DHCP consistency for network: Cluster Network 3. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local - Mgt
- LiveMigration matches network Cluster Network 3.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local - Mgt
- LiveMigration matches network Cluster Network 3.
Checking DHCP consistency for network: Cluster Network 4. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local - Mgt
matches network Cluster Network 4.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local - Mgt
matches network Cluster Network 4.
Checking DHCP consistency for network: Cluster Network 5. Network DHCP status
is disabled.
DHCP status (disabled) for network interface ACHV01.AshtaChemicals.local -
iSCSI2 matches network Cluster Network 5.
DHCP status (disabled) for network interface ACHV02.AshtaChemicals.local -
iSCSI1 matches network Cluster Network 5.
Back to Summary
Back to Top
Validate IP Configuration
Description: Validate that IP addresses are unique and subnets configured
correctly.
ACHV01.AshtaChemicals.local
        ItemName
        Adapter NameiSCSI3
        Adapter DescriptionIntel(R) PRO/1000 PT Quad Port LP Server Adapter #3
        Physical Address00-26-55-DB-CF-73
        StatusOperational
        DNS Servers
        IP Address192.168.131.113
        Prefix Length24
        ItemName
        Adapter NameMgt - Heartbeat
        Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #4
        Physical Address78-2B-CB-3C-DC-F5
        StatusOperational
        DNS Servers10.1.1.2, 10.1.1.8
        IP Address192.168.141.10
        Prefix Length24
        ItemName
        Adapter NameMgt - LiveMigration
        Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #3
        Physical Address78-2B-CB-3C-DC-F5
        StatusOperational
        DNS Servers10.1.1.2, 10.1.1.8
        IP Address192.168.140.10
        Prefix Length24
        ItemName
        Adapter NameMgt
        Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver
        Physical Address78-2B-CB-3C-DC-F5
        StatusOperational
        DNS Servers10.1.1.2, 10.1.1.8
        IP Address10.1.1.4
        Prefix Length24
        ItemName
        Adapter NameiSCSI2
        Adapter DescriptionBroadcom BCM5709C NetXtreme II GigE (NDIS VBD Client)
        #37
        Physical Address78-2B-CB-3C-DC-F7
        StatusOperational
        DNS Servers
        IP Address192.168.130.112
        Prefix Length24
        ItemName
        Adapter NameLocal Area Connection* 12
        Adapter DescriptionMicrosoft Failover Cluster Virtual Adapter
        Physical Address02-61-1E-49-32-8F
        StatusOperational
        DNS Servers
        IP Addressfe80::cc2f:d769:fe24:3d04%23
        Prefix Length64
        IP Address169.254.2.195
        Prefix Length16
        ItemName
        Adapter NameLoopback Pseudo-Interface 1
        Adapter DescriptionSoftware Loopback Interface 1
        Physical Address
        StatusOperational
        DNS Servers
        IP Address::1
        Prefix Length128
        IP Address127.0.0.1
        Prefix Length8
        ItemName
        Adapter Nameisatap.{96B6424D-DB32-480F-8B46-056A11A0A6A8}
        Adapter DescriptionMicrosoft ISATAP Adapter
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.131.113%16
        Prefix Length128
        ItemName
        Adapter Nameisatap.{A0353AF4-CE7F-4811-B4FC-35273C2F2C6E}
        Adapter DescriptionMicrosoft ISATAP Adapter #3
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.130.112%18
        Prefix Length128
        ItemName
        Adapter Nameisatap.{FAAF4D6A-5A41-4725-9E83-689D8E6682EE}
        Adapter DescriptionMicrosoft ISATAP Adapter #4
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.141.10%22
        Prefix Length128
        ItemName
        Adapter Nameisatap.{C66443C2-DC5F-4C2A-A674-2191F76E33E1}
        Adapter DescriptionMicrosoft ISATAP Adapter #5
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:10.1.1.4%27
        Prefix Length128
        ItemName
        Adapter Nameisatap.{B3A95E1D-CB95-4111-89E5-276497D7EF42}
        Adapter DescriptionMicrosoft ISATAP Adapter #6
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.140.10%29
        Prefix Length128
        ItemName
        Adapter Nameisatap.{7705D42A-1988-463E-9DA3-98D8BD74337E}
        Adapter DescriptionMicrosoft ISATAP Adapter #7
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:169.254.2.195%30
        Prefix Length128
ACHV02.AshtaChemicals.local
        ItemName
        Adapter NameMgt - Heartbeat
        Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #4
        Physical Address74-86-7A-D4-C9-8B
        StatusOperational
        DNS Servers10.1.1.8, 10.1.1.2
        IP Address192.168.141.12
        Prefix Length24
        ItemName
        Adapter NameMgt - LiveMigration
        Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #3
        Physical Address74-86-7A-D4-C9-8B
        StatusOperational
        DNS Servers10.1.1.8, 10.1.1.2
        IP Address192.168.140.12
        Prefix Length24
        ItemName
        Adapter NameMgt
        Adapter DescriptionMicrosoft Network Adapter Multiplexor Driver #2
        Physical Address74-86-7A-D4-C9-8B
        StatusOperational
        DNS Servers10.1.1.8, 10.1.1.2
        IP Address10.1.1.5
        Prefix Length24
        IP Address10.1.1.248
        Prefix Length24
        ItemName
        Adapter NameiSCSI1
        Adapter DescriptionBroadcom NetXtreme Gigabit Ethernet #7
        Physical Address74-86-7A-D4-C9-8A
        StatusOperational
        DNS Servers
        IP Address192.168.130.121
        Prefix Length24
        ItemName
        Adapter NameiSCSI2
        Adapter DescriptionBroadcom NetXtreme Gigabit Ethernet
        Physical Address00-10-18-F5-08-9C
        StatusOperational
        DNS Servers
        IP Address192.168.131.121
        Prefix Length24
        ItemName
        Adapter NameLocal Area Connection* 11
        Adapter DescriptionMicrosoft Failover Cluster Virtual Adapter
        Physical Address02-8F-46-67-27-51
        StatusOperational
        DNS Servers
        IP Addressfe80::3471:c9bf:29ad:99db%25
        Prefix Length64
        IP Address169.254.1.193
        Prefix Length16
        ItemName
        Adapter NameLoopback Pseudo-Interface 1
        Adapter DescriptionSoftware Loopback Interface 1
        Physical Address
        StatusOperational
        DNS Servers
        IP Address::1
        Prefix Length128
        IP Address127.0.0.1
        Prefix Length8
        ItemName
        Adapter Nameisatap.{8D7DF16A-1D5F-43D9-B2D6-81143A7225D2}
        Adapter DescriptionMicrosoft ISATAP Adapter #2
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.131.121%21
        Prefix Length128
        ItemName
        Adapter Nameisatap.{82E35DBD-52BE-4BCF-BC74-E97BB10BF4B0}
        Adapter DescriptionMicrosoft ISATAP Adapter #3
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.130.121%22
        Prefix Length128
        ItemName
        Adapter Nameisatap.{5A315B7D-D94E-492B-8065-D760234BA42E}
        Adapter DescriptionMicrosoft ISATAP Adapter #4
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.141.12%23
        Prefix Length128
        ItemName
        Adapter Nameisatap.{2182B37C-B674-4E65-9F78-19D93E78FECB}
        Adapter DescriptionMicrosoft ISATAP Adapter #5
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:192.168.140.12%24
        Prefix Length128
        ItemName
        Adapter Nameisatap.{104DC629-D13A-4A36-8845-0726AC9AE25E}
        Adapter DescriptionMicrosoft ISATAP Adapter #6
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:10.1.1.5%33
        Prefix Length128
        ItemName
        Adapter Nameisatap.{483266DF-7620-4427-BE5D-3585C8D92A12}
        Adapter DescriptionMicrosoft ISATAP Adapter #7
        Physical Address00-00-00-00-00-00-00-E0
        StatusNot Operational
        DNS Servers
        IP Addressfe80::5efe:169.254.1.193%34
        Prefix Length128
Verifying that a node does not have multiple adapters connected to the same
subnet.
Verifying that each node has at least one adapter with a defined default
gateway.
Verifying that there are no node adapters with the same MAC physical address.
Found duplicate physical address 78-2B-CB-3C-DC-F5 on node
ACHV01.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV01.AshtaChemicals.local adapter Mgt - LiveMigration.
Found duplicate physical address 78-2B-CB-3C-DC-F5 on node
ACHV01.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV01.AshtaChemicals.local adapter Mgt.
Found duplicate physical address 78-2B-CB-3C-DC-F5 on node
ACHV01.AshtaChemicals.local adapter Mgt - LiveMigration and node
ACHV01.AshtaChemicals.local adapter Mgt.
Found duplicate physical address 74-86-7A-D4-C9-8B on node
ACHV02.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV02.AshtaChemicals.local adapter Mgt - LiveMigration.
Found duplicate physical address 74-86-7A-D4-C9-8B on node
ACHV02.AshtaChemicals.local adapter Mgt - Heartbeat and node
ACHV02.AshtaChemicals.local adapter Mgt.
Found duplicate physical address 74-86-7A-D4-C9-8B on node
ACHV02.AshtaChemicals.local adapter Mgt - LiveMigration and node
ACHV02.AshtaChemicals.local adapter Mgt.
Verifying that there are no duplicate IP addresses between any pair of nodes.
Checking that nodes are consistently configured with IPv4 and/or IPv6
addresses.
Verifying that all nodes IPv4 networks are not configured using Automatic
Private IP Addresses (APIPA).
Back to Summary
Back to Top
Validate Multiple Subnet Properties
Description: For clusters using multiple subnets, validate the network
properties.
Testing that the HostRecordTTL property for network name Name: Cluster1 is set
to the optimal value for the current cluster configuration.
HostRecordTTL property for network name Name: Cluster1 has a value of 1200.
Testing that the RegisterAllProvidersIP property for network name Name:
Cluster1 is set to the optimal value for the current cluster configuration.
RegisterAllProvidersIP property for network name Name: Cluster1 has a value of
0.
Testing that the PublishPTRRecords property for network name Name: Cluster1 is
set to the optimal value for the current cluster configuration.
The PublishPTRRecords property forces the network name to register a PTR in
DNS reverse lookup record IP address to name mapping.
Back to Summary
Back to Top
Validate Network Communication
Description: Validate that servers can communicate, with acceptable latency,
on all networks.
Analyzing connectivity results ...
Multiple communication paths were detected between each pair of nodes.
Back to Summary
Back to Top
Validate Windows Firewall Configuration
Description: Validate that the Windows Firewall is properly configured to
allow failover cluster network communication.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - Mgt - LiveMigration'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - iSCSI3'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - Mgt - Heartbeat'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - Mgt'.
The Windows Firewall on node 'ACHV01.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV01.AshtaChemicals.local - iSCSI2'.
The Windows Firewall on node ACHV01.AshtaChemicals.local is configured to
allow network communication between cluster nodes.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - Mgt'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - iSCSI2'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - Mgt - LiveMigration'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - Mgt - Heartbeat'.
The Windows Firewall on node 'ACHV02.AshtaChemicals.local' is configured to
allow network communication between cluster nodes over adapter
'ACHV02.AshtaChemicals.local - iSCSI1'.
The Windows Firewall on node ACHV02.AshtaChemicals.local is configured to
allow network communication between cluster nodes.
Back to Summary
Back to Top

Windows server 2012 Datacenter Hyper-V Cluster -- Failed to validate Operating System Installation Option?

Hi I have a 4 node Windows server 2012 Hyper-V cluster. When I try to run a cluster validation report, everything else is fine but it fails at validate the Operating System Installation Option step. I did some research but couldn't really find any solution.
Anyone knows how to pass this test? Thanks.
Here's the error I get when run the test:
An error occurred while executing the test.
The operation has failed. An error occurred while getting the operating system installation option for node "server1"

Hi JasonLiu2002,
Please post the original error information, the current information is so wide that difficult to determine where may have issue and please offer more information about your
server configuration, you can refer the following article to prepare your cluster environment first.
Windows Server 2012 Hyper-V Best Practices (In Easy Checklist Form)
http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx
When you preparing the new cluster on Server 2012 please install the Recommended hotfixes and updates for Windows Server 2012-based failover clusters updates.
http://support.microsoft.com/kb/2784261
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Validation Report warnings

In my application, I have 3 processes, and a PDF form,
the 3 processes reference the PDF form,
so each time I make a change to the PDF form, I got 3 warnings in the Validation Report tab, saying that the PDF that these processes depend on has been changed.
I can get rid of those warnings manually by doing the "Validate" on those processes.
my question is, why it doesn't do the Validate automatically? and stop displaying those warnings all the time?
is there a way to let it do the Validate automatically?
thanks

Hi,
you need to run iso files at your cluster nodes often?
Well i think you need to provide iso files to your VMs. This is possible without "Virtual CloneDrive"!
I have seen many errors with this kind of software up to bluescreens.
But ok if you really need this software just ignore the warning from cluster validation report.
The cluster will work correctly if this are the only warnings from cluster validation report.
Regards
Sebastian

Cluster Validation error.

I have 2012 R2 Failover cluster with two nodes.
When I try to add third node and run Validation test, I've got error in Validation Report:
"Two disks have been found on node Hyperv01.local.com with duplicate disk signatures or disk GUIDs. The disks involved are physical disk 2 and physical disk 12. There may be a Multipath I/O (MPIO) problem such as the software is not installed or is not
working properly. If MPIO is not involved, or MPIO has been verified as working, you must either mask one of these disks off at this node, or run validation and specify a disk list that includes only one of these disks, for example by using the Test-Cluster
cmdlet in Windows PowerShell."
But disk signature and disk GUIDs are different.
All disks connected via ISCSI.
Can anyone please help?
Thank you.

Hi oxyGEN_ua,
Please confirm your storage compatible with server 2012r2 and your do not use the disk which marked as active and please confirm all your node have the same update and hotfix,
please install the following update.
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
https://support.microsoft.com/kb/2920151/en-us?wa=wsignin1.0
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Hyper-V cluster: Unable to fail VM over to secondary host

I am working on a Server 2012 Hyper-V Cluster. I am unable to fail my VMs from one node to the other using either LIVE or Quick migration.
A force shutdown of VMHost01 will force a migration to VMHost02. And once we are on VMHost02 we can migrate back to VMHost01, but once that is done we can't move the VMs back to VMHost02 without a force shutdown.
The following error pops up:
Event ID: 21502 The Virtual Machine Management Service failed to establish a connection for a Virtual machine migration with host.... The connection attempt failed because the connected party did not properly respond after a period of time, or the established
connection failed because connected host has failed to respond (0X8007274C)
Here's what I noticed:
VMMS.exe is running on VMHost02 however it is not listening on Port 6600. Confirmed this after a reboot by running netstat -a. We have tried setting this service to a delayed start.
I have checked Firewall rules and Anti-Virus exclusions, and they are correct. I have not run the cluster validation test yet, because I'll need to schedule a period of downtime to do so.
We can start/stop the VMMS.exe service just fine and without errors, but I am puzzled as to why it will not listen on Port 6600 anywhere. Anyone have any suggestions on how to troubleshoot this particular issue?
Thanks,
Tho H. Le

Just ran into the same issue in a 16-node cluster being managed by VMM. When trying to live migrate VMs using the VMM console the migration would fail with the following: Error 10698. Failover Cluster manager would report the following error code: Error
(0x8007274C).
+ Validated Live Migration and Cluster networks. Everything checked out.
+ Looking in Hyper-V manager and migrations are enabled and correct networks displayed.
+ Found this particular Blog that mentions that the Virtual Machine Management service is not listening to port 6600
http://blogs.technet.com/b/roplatforms/archive/2012/10/16/shared-nothing-migration-fails-0x8007274c.aspx
Ran the following from an elivated command line:
Netstat -ano | findstr 6600
Node 2 did not return anything
Node 1 returned correct output:
TCP
10.xxx.251.xxx:6600
0.0.0.0:0
LISTENING
4540
TCP
10.xxx.252.xxx:6600
0.0.0.0:0
LISTENING
4560
Set Hyper-V Virtual Machine Service to delayed start.
Restarted the service; no change.
Checked the Event Logs for Hyper-V VMMS and noted the following events - VMMS Listener started
for Live Migration networks, and then shortly after listener stopped.
Removed the system from the cluster and restarted - No change
Checked this host by running gpedit.msc - could not open console: Permission Error
Tried to run a GPO refresh (gpupdate /force), but error returned that LocalGPO could not apply registry settings. Group Policy
processing would not continue until this was resolved.
Checked the local group policy folder on node 2 and it was corrupt:
C:\Windows\System32\GroupPolicy\Machine\reg.pol showed 0K for the size.
Copied local policy folders from Node 1 to 2, and then was able to refresh the GPOs.
Restarting the VMMS service did not change the status of the ports.
Restarted Server, added Live Migration networks back into Hyper-V manager and now netstat output reports that VMMS service
is listening on 6600.

Hyper-V cluster Backup causes virtual machine reboots for common Cluster Shared Volumes members.

I am having a problem where my VMs are rebooting while other VMs that share the same CSV are being backed up. I have provided all the information that I have gather to this point below. If I have missed anything, please let me know.
My HyperV Cluster configuration:
5 Node Cluster running 2008R2 Core DataCenter w/SP1. All updates as released by WSUS that will install on a Core installation
Each Node has 8 NICs configured as follows:
NIC1 - Management/Campus access (26.x VLAN)
NIC2 - iSCSI dedicated (22.x VLAN)
NIC3 - Live Migration (28.x VLAN)
NIC4 - Heartbeat (20.x VLAN)
NIC5 - VSwitch (26.x VLAN)
NIC6 - VSwitch (18.x VLAN)
NIC7 - VSwitch (27.x VLAN)
NIC8 - VSwitch (22.x VLAN)
Following hotfixes additional installed by MS guidance (either while build or when troubleshooting stability issue in Jan 2013)
KB2531907 - Was installed during original building of cluster
KB2705759 - Installed during troubleshooting in early Jan2013
KB2684681 - Installed during troubleshooting in early Jan2013
KB2685891 - Installed during troubleshooting in early Jan2013
KB2639032 - Installed during troubleshooting in early Jan2013
Original cluster build was two hosts with quorum drive. Initial two hosts were HST1 and HST5
Next host added was HST3, then HST6 and finally HST2.
NOTE: HST4 hardware was used in different project and HST6 will eventually become HST4
Validation of cluster comes with warning for following things:
Updates inconsistent across hosts
  I have tried to manually install "missing" updates and they were not applicable
  Most likely cause is different build times for each machine in cluster
   HST1 and HST5 are both the same level because they were built at same time
   HST3 was not rebuilt from scratch due to time constraints and it actually goes back to Pre-SP1 and has a larger list of updates that others are lacking and hence the inconsistency
   HST6 was built from scratch but has more updates missing than 1 or 5 (10 missing instead of 7)
   HST2 was most recently built and it has the most missing updates (15)
Storage - List Potential Cluster Disks
  It says there are Persistent Reservations on all 14 of my CSV volumes and thinks they are from another cluster.
  They are removed from the validation set for this reason. These iSCSI volumes/disks were all created new for
  this cluster and have never been a part of any other cluster.
When I run the Cluster Validation wizard, I get a slew of Event ID 5120 from FailoverClustering. Wording of error:
  Cluster Shared Volume 'Volume12' ('Cluster Disk 13') is no longer available on this node because of
  'STATUS_MEDIA_WRITE_PROTECTED(c00000a2)'. All I/O will temporarily be queued until a path to the
  volume is reestablished.
Under Storage and Cluster Shared VOlumes in Failover Cluster Manager, all disks show online and there is no negative effect of the errors.
Cluster Shared Volumes
We have 14 CSVs that are all iSCSI attached to all 5 hosts. They are housed on an HP P4500G2 (LeftHand) SAN.
I have limited the number of VMs to no more than 7 per CSV as per best practices documentation from HP/Lefthand
VMs in each CSV are spread out amonst all 5 hosts (as you would expect)
Backup software we use is BackupChain from BackupChain.com.
Problem we are having:
When backup kicks off for a VM, all VMs on same CSV reboot without warning. This normally happens within seconds of the backup starting
What have to done to troubleshoot this:
We have tried rebalancing our backups
  Originally, I had backup jobs scheduled to kick off on Friday or Saturday evening after 9pm
  2 or 3 hosts would be backing up VMs (Serially; one VM per host at a time) each night.
  I changed my backup scheduled so that of my 90 VMs, only one per CSV is backing up at the same time
   I mapped out my Hosts and CSVs and scheduled my backups to run on week nights where each night, there
   is only one VM backed up per CSV. All VMs can be backed up over 5 nights (there are some VMs that don't
   get backed up). I also staggered the start times for each Host so that only one Host would be starting
   in the same timeframe. There was some overlap for Hosts that had backups that ran longer than 1 hour.
  Testing this new schedule did not fix my problem. It only made it more clear. As each backup timeframe
  started, whichever CSV the first VM to start was on would have all of their VMs reboot and come back up.
I then thought maybe I was overloading the network still so I decided to disable all of the scheduled backup
and run it manually. Kicking off a backup on a single VM, in most cases, will cause the reboot of common
CSV members.
Ok, maybe there is something wrong with my backup software.
  Downloaded a Demo of Veeam and installed it onto my cluster.
  Did a test backup of one VM and I had not problems.
  Did a test backup of a second VM and I had the same problem. All VMs on same CSV rebooted
Ok, it is not my backup software. Apparently it is VSS. I have looked through various websites. The best troubleshooting
site I have found for VSS in one place it on BackupChain.com (http://backupchain.com/hyper-v-backup/Troubleshooting.html)
I have tested almost every process on there list and I will lay out results below:
  1. I have rebooted HST6 and problems still persist
  2. When I run VSSADMIN delete shadows /all, I have no shadows to delete on any of my 5 nodes
   When I run VSSADMIN list writers, I have no error messages on any writers on any node...
  3. When I check the listed registry key, I only have the build in MS VSS writer listed (I am using software VSS)
  4. When I run VSSADMIN Resize ShadowStorge command, there is no shadow storage on any node
  5. I have completed the registration and service cycling on HST6 as laid out here and most of the stuff "errors"
   Only a few of the DLL's actually register.
  6. HyperV Integration Services were reconciled when I worked with MS in early January and I have no indication of
   further issue here.
  7. I did not complete the step to delete the Subscriptions because, again, I have no error messages when I list writers
  8. I removed the Veeam software that I had installed to test (it hadn't added any VSS Writer anyway though)
  9. I can't realistically uninstall my HyperV and test VSS
  10. Already have latest SPs and Updates
  11. This is part of step 5 so I already did this. This seems to be a rehash of various other stratgies
I have used the VSS Troubleshooter that is part of BackupChain (Ctrl-T) and I get the following error:
  ERROR: Selected writer 'Microsoft Hyper-V VSS Writer' is in failed state!
  - Status: 8 (VSS_WS_FAILED_AT_PREPARE_SNAPSHOT)
  - Writer Failure code: 0x800423f0 (<Unknown error code>)
  - Writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
  - Instance ID: {d55b6934-1c8d-46ab-a43f-4f997f18dc71}
  VSS snapshot creation failed with result: 8000FFFF
VSS errors in event viewer. Below are representative errors I have received from various Nodes of my cluster:
I have various of the below spread out over all hosts except for HST6
Source: VolSnap, Event ID 10, The shadow copy of volume took too long to install
Source: VolSnap, Event ID 16, The shadow copies of volume x were aborted because volume y, which contains shadow copy storage for this shadow copy, wa force dismounted.
Source: VolSnap, Event ID 27, The shadow copies of volume x were aborted during detection because a critical control file could not be opened.
I only have one instance of each of these and both of the below are from HST3
Source: VSS, Event ID 12293, Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details RevertToSnashot [hr = 0x80042302, A Volume Shadow Copy Service component encountered an
unexpected error.
Source: VSS, Event ID 8193, Volume Shadow Copy Service error: Unexpected error calling routine GetOverlappedResult. hr = 0x80070057, The parameter is incorrect.
So, basically, everything I have tried has resulted in no success towards solving this problem.
I would appreciate anything assistance that can be provided.
Thanks,
Charles J. Palmer
Wright Flood

Tim,
Thanks for the reply. I ran the first two commands and got this:
Name
Role Metric
Cluster Network 1
3  10000
Cluster Network 2 - HeartBeat                              1   1300
Cluster Network 3 - iSCSI                                    0  10100
Cluster Network 4 - LiveMigration                         1   1200
When you look at the properties of each network, this is how I have it configured:
Cluster Network 1 - Allow cluster network communications on this network and Allow clients to connect through this network (26.x subnet)
Cluster Network 2 - Allow cluster network communications on this network. New network added while working with Microsoft support last month. (28.x subnet)
Cluster Network 3 - Do not allow cluster network communications on this network. (22.x subnet)
Cluster Network 4 - Allow cluster network communications on this network. Existing but not configured to be used by VMs for Live Migration until MS corrected. (20.x subnet)
Should I modify my metrics further or are the current values sufficient.
I worked with an MS support rep because my cluster (once I added the 5th host) stopped being able to live migrate VMs and I had VMs host jumping on startup. It was a mess for a couple of days. They had me add the Heartbeat network as part of the solution
to my problem. There doesn't seem to be anywhere to configure a network specifically for CSV so I would assume it would use (based on my metrics above) Cluster Network 4 and then Cluster Network 2 for CSV communications and would fail back to the Cluster Network
1 if both 2 and 4 were down/inaccessible.
As to the iSCSI getting a second NIC, I would love to but management wants separation of our VMs by subnet and role and hence why I need the 4 VSwitch NICs. I would have to look at adding an additional quad port NIC to my servers and I would be having to
use half height cards for 2 of my 5 servers for that to work.
But, on that note, it doesn't appear to actually be a bandwidth issue. I can run a backup for a single VM and get nothing on the network card (It caused the reboots before any real data has even started to pass apparently) and still the problem occurs.
As to Backup Chain, I have been working with the vendor and they are telling my the issue is with VSS. They also say they support CSV as well. If you go to this page (http://backupchain.com/Hyper-V-Backup-Software.html)
they say they support CSVs. Their tech support has been very helpful but unfortunately, nothing has fixed the problem.
What is annoying is that every backup doesn't cause a problem. I have a daily backup of one of our machines that runs fine without initiating any additional reboots. But most every other backup job will trigger the VMs on the common CSV to reboot.
I understood about the updates but I had to "prove" it to the MS tech I was on the phone with and hence I brought it up. I understand on the storage as well. Why give a warning for something that is working though... I think that is just a poor indicator
that it doesn't explain that in the report.
At a loss for what else I can do,
Charles J. Palmer

Server 2012 R2 Hyper-V Cluster - Losing connectivity to vLANs

Hi Everybody,
I am experiencing a strange issue with a Server 2012 R2 Hypervisor. There are two physical NICs teamed (one from on-board and one from expansion board), this team is assigned to a hyper-v virtual switch, there are four virtual network adapters
assigned to the switch (Backend, Heartbeat, Management & CSV/Live Migration).
The server has been running without issue for months but, all of a sudden has started to lose connectivity to the Backend and Heartbeat. The loss of connection only occurs once VMs are hosted on the server and it doesn't happen immediately, it can take
anywhere from 12 hours to several days.
There are no errors on the NICs or vNICs themselves and the configuration is intact. Once connectivity is lost to the Backend and Heartbeat, it remains that way and it seems the only solution so far is to reboot the server. Hardware diagnostics have been
run and revealed no issues. There are no useful events in event viewer, the alerts relate to the loss of connection to the cluster as a result of connectivity being lost on the Backend and Heartbeat.
I have 6 other hypervisors with the same network configuration that are performing without issue so, I don't believe the problem is the configuration. The only difference is the hypervisor that has the problems is a Dell Poweredge R620 and the other 6 are
Dell PowerEdge R610s.
Can anyone advise what might be the cause of these issues or, any event logging to enable that might help isolate where the issue lies.

Sorry Tim, is that all 50 blue screen if live migrated?
Are they all on the latest integration services? Does a cluster validation complete successfully? Are the hosts patched to the same level?
The fact that if you power them off then migrate them and they boot fine, does point to a processor incompatibility and the memory BIN file is not accepted on the new host.
Bit of a long shot but the only other thing I can think of off the top of my head if the compatibility option is checked, is checking the location of the BIN file when the VM is running to make sure its in the same place as the VHD\VHDX in the
CSV storage where the VM is located and not on the local host somewhere like C:\program data\.... that is stopping it being migrated to the new host when the VM is live migrated.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Network Questions on 2012 R2 Hyper-V Cluster

I am going through the setup and configuration of a clustered Windows Server 2012 R2 Hyper-V host.
I’ve followed as much documentation as I can find, and the Cluster Validation is passing with flying colors, but I have three questions about the networking setup.
Here’s an overview as well as a diagram of our configuration:
We are running two Server 2012 R2 nodes on a Dell VRTX Blade Chassis.
We have 4-dual port 10 GBe Intel NICS installed in the VRTX Chassis.
We have two Netgear 12-Port 10 GBe switches, both uplinked to our network backbone switch.
Here’s what I’ve done on each 2012 R2 node:
-Created a NIC team using two 10GBe ports from separate physical cards in the blade chassis.
-Created a Virtual Switch using this team called “Cluster Switch” with “ManagementOS” specified.
-Created 3 virtual Nics that connect to this “Cluster Switch”:
Mangement (10.1.10.x), Cluster (172.16.1.x), Live Migration (172.16.2.x)
-Set up VLAN ID 200 on the Cluster NIC using Powershell.
-Set Bandwidth Weight on each of the 3 NICS. Mangement has 5, Cluster has 40, Live Migration has 20.
-Set a Default Minimum Bandwidth for the switch at 35 (for the VM traffic.)
-Created two virtual switches for iSCSI both with
“-AllowManagementOS $false” specified.
-Each of these switches is using a 10GBe port from separate physical cards in the blade chassis.
-Created a virtual NIC for each of the virtual switches:
ISCSI1 (172.16.3.x) and ISCSI2 (172.16.4.x)
Here’s what I’ve done on the Netgear 10GB switches:
-Created a LAG using two ports on each switch to connect them together.
-Currently, I have no traffic going across the LAG as I’m not sure how I should configure it.
-Spread out the network connections over each Netgear switch so traffic from the virtual switch “Cluster Switch” on each node is connected to both Netgear 10 GB switches.
-Connected each virtual iSCSI switch from each node to its own port on each Netgear switch.
First Question: As I mentioned, the cluster validation wizard thinks everything is great.
But what about the traffic the Host and Guest VMs use to communicate with the rest of the corporate network?
That traffic is on the same subnet as the Management NIC.
Should the Management traffic be on that same corporate subnet, or should it be on its own subnet?
If Management is on its own subnet, then how do I manage the cluster from the corporate network?
I feel like I’m missing something simple here.
Second Question: Do I even need to implement VLANS in this configuration?
Since everything is on its own subnet, I don’t see the need.
Third Question: I’m confused how the LAG will work between the two 10 Gbe switches when both have separate uplinks to the backbone switch.
I see diagrams that show this setup, but I’m not sure how to achieve it without causing a loop.
Thanks!

"First Question: As I mentioned, the cluster validation wizard thinks everything is great.
But what about the traffic the Host and Guest VMs use to communicate with the rest of the corporate network?
That traffic is on the same subnet as the Management NIC.
Should the Management traffic be on that same corporate subnet, or should it be on its own subnet?
If Management is on its own subnet, then how do I manage the cluster from the corporate network?
I feel like I’m missing something simple here."
This is an operational question, not a technical question. You can have all VM and management traffic on the same network if you want. If you want to isolate the two, you can do that, too. Generally, recommended
practice is to create separate networks for host management and VM access, but it is not a strict requirement.
"Second Question: Do I even need to implement VLANS in this configuration?
Since everything is on its own subnet, I don’t see the need."
No, you don't need VLANs if separation by IP subnet is sufficient. VLANs provide a level of security against snooping that simple subnet isolation provides. Again, up to you as to how you want to configure things.
I've done it both ways, and it works both ways.
"Third Question: I’m confused how the LAG will work between the two 10 Gbe switches when both have separate uplinks to the backbone switch.
I see diagrams that show this setup, but I’m not sure how to achieve it without causing a loop."
This is pretty much outside the bounds of a clustering question. You might want to take network configuration questions to a networking forum. Or, you may want to talk with Netgear specialist. Different networking
vendors can accomplish this in different ways.
.:|:.:|:. tim

Server 2012 R2 Hyper-V Cluster, VM blue screens after migration between nodes.

I currently have a two node Server 2012 R2 Hyper-v Cluster (fully patched) with a Windows Server 2012 R2 Iscsi target.
The VMs run fine all day long, but when I try to do a live/quick migration the VM blue screens after about 20 minutes. The blue reports back about a “Critical_Structure_Corruption”.
I’m being to think it might be down to CPU, as one system has an E-2640v2 and the other one has an E5-2670v3. Should I be able to migrate between these two systems with these type of CPU?
Tim

Sorry Tim, is that all 50 blue screen if live migrated?
Are they all on the latest integration services? Does a cluster validation complete successfully? Are the hosts patched to the same level?
The fact that if you power them off then migrate them and they boot fine, does point to a processor incompatibility and the memory BIN file is not accepted on the new host.
Bit of a long shot but the only other thing I can think of off the top of my head if the compatibility option is checked, is checking the location of the BIN file when the VM is running to make sure its in the same place as the VHD\VHDX in the
CSV storage where the VM is located and not on the local host somewhere like C:\program data\.... that is stopping it being migrated to the new host when the VM is live migrated.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Hyper-V cluster validation report "Found duplicate physical address" on nic team interfaces.

Similar Messages

Maybe you are looking for