Hyper-V Cluster Name offline

Question

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!

Answer 1

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