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, September 22, 2015 2:03 PM
Hello Experts,
I am looking for your suggestions on below described issues with Multi-Site MSFC on 2012 R2.
We have 2 Physical Fujitsu Primergy BX920 S4 servers with CNA cards located both at different sites.
We have created 4 x Virtual NIC on each Physical server using OneCommand Manager. further these NICs are teamed.
Now we have 2 x NICs for each server as below.
NIC1 (VLAN-A IP-X.X.12.24), NIC2 (VLAN-B IP-X.X.20.10) for Node1
NIC3 (VLAN-A IP-X.X.13.24), NIC4 (VLAN-B IP-X.X.111.10) for Node2
VLAN-A is configured for Cluster Heartbeat without default Gateway.
VLAN-B is configured for Production and both NICs have Default Gateway.
While looking at Cluster Manager console for Network Component, we observed NIC1 is showing DOWN. and getting event in Event Logs as below.
Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. 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.
We have verified the network communication from NIC1 to Switch is working fine. The HeartBeat Network between both node is going through Switch only, there is no firewall.
We have tried to create static routes however both nodes, however while performing tracert to IP-X.X.13.24 from node1, The traffic is going through NIC2 (VLAN-B IP-X.X.20.10), where as it should go through NIC1.
Please suggest how can we troubleshoot it further.
Cluster network 'Cluster Network 1' is down. None of the available nodes can communicate using this network. 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.
Thanks & Regards,
Amit Katkar (MCITP Windows 2008)
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
All replies (4)
Tuesday, September 22, 2015 2:49 PM
Further to our investigation, we executed below command from Node1
Find-NetRoute -RemoteIPAddress <<NIC3 IP>>
and observed, the IPInterfaceAlise is showing as NIC2 Name, however, it should go through NIC1 interface.
However, when I try same command for other IP in same segment like below command
Find-NetRoute -RemoteIPAddress X.X.13.22
Its going though NIC1 interface, which is fine.
is there misconfiguration in cluster ?
How to identify the root cause of this behavior ?
Thanks & Regards,
Amit Katkar (MCITP Windows 2008)
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
Sunday, September 27, 2015 10:24 AM
Well, Finally, I am able to narrow down this issues.
We have observed multiple issues like,
1. Heartbeat communication was block on switch level, this has been resolved now.
2. NIC Team was causing issues for routing heartbeat network. We have dissolved the NIC teaming and now assigned same IP address to one of the NIC from this group. This is working now.
We are working with vendor to see why NIC teaming software is not working.
Thanks & Regards,
Amit Katkar (MCITP Windows 2008)
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.
Tuesday, September 29, 2015 7:54 AM
Hi Tech Love,
Start Server 2012 the third party network adapter teaming is not supported you can use the Server built-in teaming solution, mote details please refer the following article:
NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Monday, October 5, 2015 3:30 PM
Hello Alex,
Thanks for your response..,
That's correct, and we are using Windows 2012 R2 inbuilt NIC teaming feature.
We are working with Microsoft Tech for further investigation on this.
Thanks & Regards,
Amit Katkar (MCITP Windows 2008)
This posting is provided "AS IS" with no warranties or guarantees and confers no rights.