[cisco-voip] ISR/VG Ethernet redundancy

[Lelio Fulgenzi]

We ended up going the route of EIGRP routing on the VG224s and 3800s. 

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. 

I'm far less concerned with a port going down than a switch, so having the VG224s uplinked to different switches is our choice. 

Lelio 


--- 
Lelio Fulgenzi, B.A. 
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1 
(519) 824-4120 x56354 (519) 767-1060 FAX (ANNU) 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
Cooking with unix is easy. You just sed it and forget it. 
- LFJ (with apologies to Mr. Popeil) 


----- Original Message -----
From: "Jason Burns" <burns.jason at gmail.com> 
To: "Bill Riley" <bill at hitechconnection.net> 
Cc: "Cisco List VoIP" <cisco-voip at puck.nether.net> 
Sent: Wednesday, January 25, 2012 3:12:26 PM 
Subject: Re: [cisco-voip] ISR/VG Ethernet redundancy 

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. 

-Jason 


On Wed, Jan 25, 2012 at 3:07 PM, Bill Riley < bill at hitechconnection.net > wrote: 


You should use a loop back and bind everything to in instead of the physical 
interface. 

If you want Ethernet redundancy you should be able to create an ether 
channel down from the router if you are going into the same switch or have 
VSS on the 6500. 

If not I have also bridged it into two separate switches using a BVI like 
you are looking at. 




-----Original Message----- 
From: cisco-voip-bounces at puck.nether.net 
[mailto: cisco-voip-bounces at puck.nether.net ] On Behalf Of Ovidiu Popa 
Sent: Wednesday, January 25, 2012 1:57 PM 
To: Cisco List VoIP 
Subject: [cisco-voip] ISR/VG Ethernet redundancy 

Hello everyone 

I have a few questions regarding bridge virtual interfaces and voice 
protocols: 
- is binding sccp and/or mgcp to a bvi interface supported by Cisco Tac? 
- any official configuration guides for this kind of connectivity? 
- anyone have this configuration in production and would care to share 
his/hers feedback? 


My main goal is to be able to use the spare ethernet interfaces on a 
router/vg for redundancy but I was surprised by the lack of official 
guidance on the subject. 

Thanks 
Ovidiu 




_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 

_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 


_______________________________________________ 
cisco-voip mailing list 
cisco-voip at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-voip 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120125/a0b84e39/attachment.html>