Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, February 23, 2010 7:34 PM
We have a cluster of 3 Hosts (IBM HS-22 blade servers).
We are getting error and warning events at random times of the day. It doesn't seem to effect any of the functionality.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 23/02/2010 11:35:55 AM
Event ID: 1127
Task Category: Network Manager
Level: Error
Keywords:
User: SYSTEM
Computer: HV-ALPHA.xxx
Description:
Cluster network interface 'HV-BRAVO - Host' for cluster node 'HV-BRAVO' on network 'Cluster Network Corp' 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.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 23/02/2010 7:07:38 AM
Event ID: 1127
Task Category: Network Manager
Level: Error
Keywords:
User: SYSTEM
Computer: HV-ALPHA.xxx
Description:
Cluster network interface 'HV-ALPHA - Host' for cluster node 'HV-ALPHA' on network 'Cluster Network Corp' 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.
Log Name: System
Source: Microsoft-Windows-FailoverClustering
Date: 23/02/2010 5:56:24 AM
Event ID: 1126
Task Category: Network Manager
Level: Warning
Keywords:
User: SYSTEM
Computer: HV-ALPHA.xxx
Description:
Cluster network interface 'hv-charlie - Host' for cluster node 'hv-charlie' on network 'Cluster Network Corp' is unreachable by at least one other cluster node attached to the network. The failover cluster was not able to determine the location of the failure. 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.
I run the cluster validation and it passes all the tests.
There are 4 adapters on each blade and the first 3 are teamed together. Each host has a virtual adapter connected to the teamed network. The last one is dedicated for the private cluster network. There are no errors coming from the private cluster network.
Any ideas what may be casuing this?
All replies (2)
Thursday, February 25, 2010 6:59 AM ✅Answered
Hi,
Please refer to the following articles first:
http://technet.microsoft.com/en-us/library/dd354065(WS.10).aspx
http://technet.microsoft.com/en-us/library/dd353958(WS.10).aspx
Tim Quan - MSFT
Friday, February 26, 2010 8:16 PM ✅Answered
Does the same issue occur without teaming in place? Do you have the lastest NIC drivers applied?
This issue is going to be caused by either your teaming software or NIC driver/firmware.
Visit my blog about multi-site clustering - http://msmvps.com/blogs/jtoner