<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>a very rudimentary diagram follows.<br><br>Essentially, any traffic that hits core-1 will go to the VG224:fa0/0 interface and any traffic that hits core-2 will go to the VG224:fa0/1 interface. That's because an interlink between the two cores (not pictured, sorry) increases the distance to the other side.<br><br>We are using intermediary switches because there are not enough ports on the core switches/routers.<br><br>The links are essentially layer three routed point-to-point links (through a layer two interface).<br><br>The default route is sent to the VG224 using eigrp summary command and they are equally weighted. So traffic outbound from the VG224 will be random across both links. I can change this by using a delay command easily to prefer one route over the other. But again, this will affect outbound traffic only.<br><br>I guess there's a difference between equal routes (which appear on the VG224) which means traffic to the same destination will traverse both links and with an asymetrical route which I understand as traffic to a device goes out one link and comes back on another. However, I can't guarantee that traffic from a device on the network will always choose core-1 or core-2, so it may be a case of inbound traffic coming in on either interface as well.<img src="cid:DWT148"><span><br><br><span name="x"></span>---<br>Lelio Fulgenzi, B.A.<br>Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><span name="x"></span><br></span><br><hr id="zwchr"><b>From: </b>"Wes Sisk" <wsisk@cisco.com><br><b>To: </b>"Lelio Fulgenzi" <lelio@uoguelph.ca><br><b>Cc: </b>"voyp list" <cisco-voip@puck.nether.net><br><b>Sent: </b>Wednesday, October 13, 2010 4:29:18 PM<br><b>Subject: </b>Re: [cisco-voip] asymetrical routing and voice - thoughts? requirements?<br><br>
We're missing a bit of information like how you got asymmetrical
routing to the router interfaces. Care to share?<br>
<br>
Otherwise, in theoretical discussion, my peers agree that router will
service traffic for any locally configured IP from any network
interface.<br>
<br>
There are the classic issues of binding VOIP protocols to interfaces
with routable IP addresses but that is a separate issue.<br>
<br>
/Wes<br>
<br>
Lelio Fulgenzi wrote:
<blockquote style="border: medium none ! important; padding-left: 0px ! important; padding-right: 0px ! important; margin-left: 0px ! important; margin-right: 0px ! important;" cite="mid:1395946369.442430.1286998822419.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">OK,
not sure if this has been discussed before, but I just tried to get all
my voice through one interface of my VG224 and in doing so, I lost the
route to the other interface. We did this by using the delay command.
Anything else I've been told, will take significant time to deploy.<br>
<br>
So the question is, in the case of end devices (mainly gateways) that
have two uplinks, how important is it to ensure that only one side is
always used? Is it a requirement or is it a nice to have? I'd rather
not be introducing delay statements if I don't have to.<br>
<br>
Or is it all just to make troubleshooting easier?<br>
<span><br>
<span></span>---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<span></span><br>
</span><br>
</div>
<pre><hr width="90%" size="4">
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</div></body></html>