[cisco-voip] ISR/VG Ethernet redundancy

[Jason Burns]

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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120125/2699bb83/attachment.html>