Hello All,
Recently we noticed that our ERP application on MS2K8 FC (failover cluster) at startup taking the network adapter for communication which has the numerically smallest Index number.
The Interface selected by the application is unfortunately is the Microsoft Failover Cluster Internal communication with the APIPA, Cost: we are having a delay of 15-30 seconds per connection from the application to the DB. App in NodeA and DB in NodeB.
We tried to change the network binding order to correct this situation without a success as the Microsoft Failover Cluster Internal communication is a non manageable adapter.
Ipconfig /all shows this adapter in the end of the IP List.
Do we have a supported solution to change the InterfaceIndex of a network adapter to a different value, so that we can avoid a complete cluster build ?
Screenshot from application with the wrong subnet:
The problem with the interfaceIndex numbering:
The aim is to change the Idx of the local area connection* 9 which is the virtual adapter for Microsoft Failover Cluster Internal communication from 12 to say 19.
FYI: Node A and B are VMs.
Thanks in advance for your help.
Sujin JOHNY