On Mon, 30 Aug 1999, Arthur Darren Dunham wrote:
NFS, CIFS, and HTTP requests are stored with the incoming interface. Their response is sent via the same interface.
That means that if the switch is round-robining the requests, the responses will also be pretty well distributed.
What happens when a request is larger than one ethernet frame? What happens if the response is larger than one ethernet frame. What happens if you send another request in while the first request is being output?
I don't believe that the NetApp implementation rememebers the interface on which the request came in. I think that it simply remembers the last interface on which a packet came in from a certain host. A sort of "arp" table.
If the requests are bunched up, so will the responses.
But the requests are a lot smaller than the responses so the one interface will be flooded while others will be sitting idle, right?
Is there any way to force a Cisco switch to round-robin traffic to a netapp like this? The one time I played with this configuration, the traffic was not well balanced at all.
I thought you said that it was pretty well distributed.
Tom