Keith,
We have struggled with this same problem. However, in our case, the "clients" are actually IIS systems in a Virtual IP site. We had tried to have 2 NICs in the IIS NT "clients", one connecting to the shared net that also had the PDC, WINS, DNS and other servers on one subnet, while we had the filer and our SQL server on another sunet. The second subnet I'll call a "backchannel", the idea being to have requests from the IIS "clients" routed to the filer or database through the "backchannel".
What we ran into was that even though we put this backchannel on its own switch, and even though we specifically called the filer by the IP address via UNC (ie, \filerIP\sharename), NT still treats this as a string, not an IP. Thus, NT would try to resolve this through WINS, which it routed through the other subnet!! (the one the WINS server could 'see'). We tried many tricks including using the NOWINS and NOBROADCAST settings on the second NIC in the filer. We still have not been able to get a second subnet going. Can you suggest what we may be missing?
Sam
-----Original Message----- From: Keith Brown [mailto:keith@netapp.com] Sent: Friday, February 12, 1999 2:53 PM To: Mike Ball; toasters@mathworks.com Subject: Re: Can Netapp F700 series do load balancing via NT without using a Virtual IP?
I am assuming [Windows NT] sees the filer as a multihomed server and sees
all four IP's
But does it load balance between the 4 ports on the quad card?
A commonly asked question. I think I used to have a pointer to a Microsoft document that described this, but apparently that has gone walk-about, so I'm afraid you're stuck with my from-memory verbage below for now...
The Windows NT client usually starts out with the filer's name. It uses this name to queery WINS and gets returned a list of IP addresses (assuming the filer is multihomed). It then goes through the list of returned addresses and compares them with the address on its own, usually single interface. First it looks for an address to use that is on the same IP subnet as it finds itself on. If it finds multiple of those, it picks one at random, which will tend to balance the load to a single filer that has multiple interfaces connected to that same subnet as the client. If it doesn't find a match, it will look for an interface in the same IP network as it finds itself on. Again, if it finds multiple of those it will pick one at random, tending to balance the load to the target's interfaces. Finally, if it finds none of the above, it will just pick an address to use at random and go for it.
Per our 5.1 releases of Data ONTAP and higher, you also have the ability to control which interfaces the filer will register with WINS. This gives you the ability to stop certain Windows clients from choosing interfaces on the filer which they might not be able to access for various topological and/or routing issues.
Keith