Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 6672

Hyper-V Cluster Network failed

$
0
0

Hello,

I need some help on this one.  I have a 2008 R2 Hyper-V cluster with 4 server nodes. 

On one of the nodes iSCSI network keeps failing, the error shows in the failover cluster manager:

Cluster network interface 'HV-2 - iSCSI_SAN_VLAN' for cluster node HV-2' on network 'iSCSI SAN VLAN' failed. 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.

It's happening about 20 times a day, yet any VM's on that server will sit happy and not failover.

The adapter is a dual port 10Gb SFP,  the other port is fine and doesn't complain.  I have tried different ports on the switch and I have swapped the cable,  last resort is the card but I don't want to have to do this if it's something else.

Any ideas?

Thanks

Here is the error on the node itself:

A network interface has failed. An Ethernet adapter's status changed from OK to Error, or an Ethernet team's status changed to Error from another state.

 User Action

Check the network cables, switches, and hubs for the cause of the failure.

WBEM Indication Properties

AlertingElementFormat: 2 0x2 (CIMObjectPath)

AlertingManagedElement: "\\HV-2\ROOT\HPQ:HP_WinEthernetPort.DeviceID="{82B9C395-AE5C-4B7E-850D-7401C125DD5A}",CreationClassName="HP_WinEthernetPort",SystemCreationClassName="HP_WinComputerSystem",SystemName="HV-2.domain.com""

AlertType: 2 0x2 (Communications Alert)

Description: "A network interface has failed. An Ethernet adapter's status changed from OK to Error, or an Ethernet team's status changed to Error from another state."

EventCategory: 9 0x9 (Network Device)

EventID: "2"

EventSubCategory: 11 0xb (Ethernet Port)

ImpactedDomain: 4 0x4 (System)

IndicationIdentifier: "{1FACF9E4-7BA8-4468-AA4F-0EC418B455AC}"

IndicationTime: "20130906055102.995000+060"

NetworkAddresses[0]: "fe80::b4a1:d55d:de4c:9945%30"

NetworkAddresses[1]: "172.16.32.173"

NetworkAddresses[2]: "fe80::1dfa:c267:135d:e172%21"

NetworkAddresses[3]: "172.16.20.173"

NetworkAddresses[4]: "fe80::b573:486f:166f:425a%10"

NetworkAddresses[5]: "10.0.0.173"

NetworkAddresses[6]: "fe80::9925:de29:de82:703c%15"

NetworkAddresses[7]: "169.254.2.58"

OSVersion: "6.1.7601"

PerceivedSeverity: 6 0x6 (Critical)

ProbableCause: 7 0x7 (Communications Subsystem Failure)

ProbableCauseDescription: "Network Interface Lost Connectivity"

ProviderName: "HP Ethernet"

ProviderVersion: "9.2.5.0"

RecommendedActions[0]: "Check the network cables, switches, and hubs for the cause of the failure."

Summary: "Network interface lost connectivity"

SystemCreationClassName: "HP_WinComputerSystem"

SystemFirmwareVersion[0]: "2010.03.30"

SystemFirmwareVersion[1]: "2010.03.30"

SystemGUID: "33313934-3531-5A43-3230-3231364A5635"

SystemModel: "ProLiant DL380 G6"

SystemName: "HV-2.domain.com"

SystemProductID: "491315-421"

SystemSerialNumber: "CZ20216JV5"

TIME_CREATED: 130229166675143661 0x1ceaabcb3112bed

For more information, please contact HP Support.


Viewing all articles
Browse latest Browse all 6672

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>