Hey Guys -
I've got an issue I've been working on for a couple of days now and need help with. Our company has a VDI cluster which has a total of 5 nodes. Recently, one went down and was rebuilt. I was told that all settings were configured as they should be and have verified for one that all of the NIC settings (static IPs, options enabled, etc) are correct or match the other hosts.
The problem is that in VMM (2008), the node is still listed as "Needs Attention." When I run a validation on the cluster, I get many network-related issues that appear. Below are examples of the two primary ones.
Note: Node C is the one which was rebuilt...
Error Type #1
Node C is reachable from Node B by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Node D is reachable from Node C by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Node C is reachable from Node D by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Node C is reachable from Node E by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Error Type #2
Network interfaces E - LiveMigration and C - LiveMigration are on the same cluster network, yet either address 10.50.7.23 is not reachable from 10.50.7.25 or the ping latency is greater than the maximum allowed 500 milliseconds.
Network interfaces E - LiveMigration and C - LiveMigration are on the same cluster network, yet either address 10.50.7.23 is not reachable from 10.50.7.25 or the ping latency is greater than the maximum allowed 500 milliseconds.
Network interfaces C - LiveMigration and E - LiveMigration are on the same cluster network, yet either address 10.50.7.25 is not reachable from 10.50.7.23 or the ping latency is greater than the maximum allowed 500 milliseconds.
Network interfaces C - LiveMigration and B - LiveMigration are on the same cluster network, yet either address 10.50.7.22 is not reachable from 10.50.7.23 or the ping latency is greater than the maximum allowed 500 milliseconds.
... and so on... there are a total of 12 of the above error....
If it helps any, I restarted two of the nodes (including the one which was rebuilt) and received an IP Address Conflict message. The error included the MAC of the NIC which was conflicting. I found out which node the MAC was on and looked at it's IPv4 address (IPv6 disabled on all NICs / all nodes) and it didn't match any of the ones from the server that threw it - weird!
Any suggestions as to where to look or what to do? Thanks!
I've got an issue I've been working on for a couple of days now and need help with. Our company has a VDI cluster which has a total of 5 nodes. Recently, one went down and was rebuilt. I was told that all settings were configured as they should be and have verified for one that all of the NIC settings (static IPs, options enabled, etc) are correct or match the other hosts.
The problem is that in VMM (2008), the node is still listed as "Needs Attention." When I run a validation on the cluster, I get many network-related issues that appear. Below are examples of the two primary ones.
Note: Node C is the one which was rebuilt...
Error Type #1
Node C is reachable from Node B by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Node D is reachable from Node C by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Node C is reachable from Node D by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Node C is reachable from Node E by only one pair of interfaces. It is possible
that this network path is a single point of failure for communication within the cluster. Please verify that
this single path is highly available or consider adding additional networks to the cluster.
Error Type #2
Network interfaces E - LiveMigration and C - LiveMigration are on the same cluster network, yet either address 10.50.7.23 is not reachable from 10.50.7.25 or the ping latency is greater than the maximum allowed 500 milliseconds.
Network interfaces E - LiveMigration and C - LiveMigration are on the same cluster network, yet either address 10.50.7.23 is not reachable from 10.50.7.25 or the ping latency is greater than the maximum allowed 500 milliseconds.
Network interfaces C - LiveMigration and E - LiveMigration are on the same cluster network, yet either address 10.50.7.25 is not reachable from 10.50.7.23 or the ping latency is greater than the maximum allowed 500 milliseconds.
Network interfaces C - LiveMigration and B - LiveMigration are on the same cluster network, yet either address 10.50.7.22 is not reachable from 10.50.7.23 or the ping latency is greater than the maximum allowed 500 milliseconds.
... and so on... there are a total of 12 of the above error....
If it helps any, I restarted two of the nodes (including the one which was rebuilt) and received an IP Address Conflict message. The error included the MAC of the NIC which was conflicting. I found out which node the MAC was on and looked at it's IPv4 address (IPv6 disabled on all NICs / all nodes) and it didn't match any of the ones from the server that threw it - weird!
Any suggestions as to where to look or what to do? Thanks!
Ben K.