<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>someone else has mentioned the backup interface command. it didn't click until you put it in the config below, however.<br><br>so essentially, on the VG224, i use the backup interface command and one of the interfaces will more than likely "go down" ? <br><br>this should keep the upstream router from using that second interface correcT?<br><br><br><span><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>"James Brown" <James.Brown@barclayswealth.com><br><b>To: </b>lelio@uoguelph.ca<br><b>Cc: </b>cisco-voip@puck.nether.net<br><b>Sent: </b>Thursday, October 14, 2010 12:25:57 PM<br><b>Subject: </b>RE: [cisco-voip] asymetrical routing and voice - thoughts? requirements?<br><br>
<style>P {
MARGIN: 0px
}
</style>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2">Have you
considered the backup interface command?</font></div>
<div><font color="#0000ff" face="Arial" size="2"></font> </div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2">!<br>int
fa0/0<br> backup interface Fast Ethernet 1/0<br>!</font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"></font> </div>
<div dir="ltr" align="left"><font face="Arial"><font color="#0000ff"><font size="2"><span class="841102416-14102010">The only alternative I can think of
</span>might <span class="841102416-14102010">involve attaching a route-map,
but then you have to consider changing the metric of both inbound and outbound
routes on a per-interface basis.</span></font></font></font></div>
<div dir="ltr" align="left"><font face="Arial"><font color="#0000ff"><font size="2"><span class="841102416-14102010"></span></font></font></font> </div>
<div dir="ltr" align="left"><font face="Arial"><font color="#0000ff"><font size="2"><span class="841102416-14102010">Regards</span></font></font></font></div>
<div dir="ltr" align="left"><font face="Arial"><font color="#0000ff"><font size="2"><span class="841102416-14102010"></span></font></font></font> </div>
<div dir="ltr" align="left"><font face="Arial"><font color="#0000ff"><font size="2"><span class="841102416-14102010">James.</span></font></font></font></div><br>
<div class="OutlookMessageHeader" dir="ltr" align="left" lang="en-us">
<hr>
<font face="Tahoma" size="2"><b>From:</b> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b>On Behalf Of </b>Lelio
Fulgenzi<br><b>Sent:</b> 13 October 2010 21:48<br><b>To:</b> Wes
Sisk<br><b>Cc:</b> voyp list<br><b>Subject:</b> Re: [cisco-voip] asymetrical
routing and voice - thoughts? requirements?<br></font><br></div>
<div></div>
<div style="font-size: 10pt; color: rgb(0, 0, 0); font-family: Verdana;">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:841102416@14102010-13EF"><span><br><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>
<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; padding-right: 0px ! important; padding-left: 0px ! important; margin-left: 0px ! important; margin-right: 0px ! important;" cite="mid:1395946369.442430.1286998822419.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>P {
MARGIN: 0px
}
</style>
<div style="font-size: 10pt; color: rgb(0, 0, 0); font-family: Verdana;">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>
<p>
</p><hr>
<font face="Arial" size="1">Barclays Wealth is the wealth management division of
Barclays Bank PLC. This email may relate to or be sent from other members of the
Barclays Group.</font><p></p>
<p><font face="Arial" size="1">The availability of products and services may be
limited by the applicable laws and regulations in certain jurisdictions. The
Barclays Group does not normally accept or offer business instructions via
internet email. Any action that you might take upon this message might be at
your own risk.</font></p>
<p><font face="Arial" size="1">This email and any attachments are confidential and
intended solely for the addressee and may also be privileged or exempt from
disclosure under applicable law. If you are not the addressee, or have received
this email in error, please notify the sender immediately, delete it from your
system and do not copy, disclose or otherwise act upon any part of this email or
its attachments.</font></p>
<p><font face="Arial" size="1">Internet communications are not guaranteed to be
secure or without viruses. The Barclays Group does not accept responsibility for
any loss arising from unauthorised access to, or interference with, any Internet
communications by any third party, or from the transmission of any viruses.
Replies to this email may be monitored by the Barclays Group for operational or
business reasons.</font></p>
<p><font face="Arial" size="1">Any opinion or other information in this email or its
attachments that does not relate to the business of the Barclays Group is
personal to the sender and is not given or endorsed by the Barclays
Group.</font></p>
<p><font face="Arial" size="1">Barclays Bank PLC. Registered in England and Wales
(registered no. 1026167).<br>Registered Office: 1 Churchill Place, London, E14
5HP, United Kingdom.</font></p>
<p><font face="Arial" size="1">Barclays Bank PLC is authorised and regulated by the
Financial Services Authority.</font></p>
</div></body></html>