I get the same behavior regardless of if I try to mount with udp or tcp.<br><br><div class="gmail_quote">On Thu, Apr 1, 2010 at 11:53 PM, Steve Francis <span dir="ltr">&lt;<a href="mailto:sfrancis@logicmonitor.com">sfrancis@logicmonitor.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">You could also switch to TCP mounts, instead of UDP (which I&#39;m just<br>
assuming you are currently using.)<br>
Fastpath should be the answer, but with fastpath off, UDP packets that<br>
were sent to VIF1, that are replied to by VIF2 (due to the filers<br>
route table), will have a source address of VIF2 (and hence be dropped<br>
by the mounting system.)  TCP packets will be source with the IP<br>
address of the destination interface on the filer, regardless of the<br>
egress interface.<br>
<br>
So switching to TCP mounts will make your current config work rapidly,<br>
but not necessarily with the transit paths as you want.<br>
<br>
(The above is characteristic of UDP - not just NetApps.)<br></blockquote></div>