<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>We ended up going the route of EIGRP routing on the VG224s and 3800s. <br><br>Unfortunately, we got some not so positive feedback regarding the supportedness of EIGRP on VG224s, but like you found out, no real direction on how to configure redundancy on these.<br><br>I'm far less concerned with a port going down than a switch, so having the VG224s uplinked to different switches is our choice.<br><br>Lelio<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 (ANNU)<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>"Jason Burns" <burns.jason@gmail.com><br><b>To: </b>"Bill Riley" <bill@hitechconnection.net><br><b>Cc: </b>"Cisco List VoIP" <cisco-voip@puck.nether.net><br><b>Sent: </b>Wednesday, January 25, 2012 3:12:26 PM<br><b>Subject: </b>Re: [cisco-voip] ISR/VG Ethernet redundancy<br><br>I second Etherchannel from the upstream device. I had a customer who insisted on binding to the PortChannel interface for the voice protocols, even though we recommended using the Loopback. It's up and running just fine and does handle failure of a single link as expected.<br>
<br>-Jason<br><br><div class="gmail_quote">On Wed, Jan 25, 2012 at 3:07 PM, Bill Riley <span dir="ltr"><<a href="mailto:bill@hitechconnection.net" target="_blank">bill@hitechconnection.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
You should use a loop back and bind everything to in instead of the physical<br>
interface.<br>
<br>
If you want Ethernet redundancy you should be able to create an ether<br>
channel down from the router if you are going into the same switch or have<br>
VSS on the 6500.<br>
<br>
If not I have also bridged it into two separate switches using a BVI like<br>
you are looking at.<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
-----Original Message-----<br>
From: <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Ovidiu Popa<br>
Sent: Wednesday, January 25, 2012 1:57 PM<br>
To: Cisco List VoIP<br>
Subject: [cisco-voip] ISR/VG Ethernet redundancy<br>
<br>
Hello everyone<br>
<br>
I have a few questions regarding bridge virtual interfaces and voice<br>
protocols:<br>
- is binding sccp and/or mgcp to a bvi interface supported by Cisco Tac?<br>
- any official configuration guides for this kind of connectivity?<br>
- anyone have this configuration in production and would care to share<br>
his/hers feedback?<br>
<br>
<br>
My main goal is to be able to use the spare ethernet interfaces on a<br>
router/vg for redundancy but I was surprised by the lack of official<br>
guidance on the subject.<br>
<br>
Thanks<br>
Ovidiu<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>
<br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></div></body></html>