<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>They are. What I have seen is that the stub routing issue is ran into and the internal staff will just download the IPSERVICES image and run full eigrp routing. That works for most of the devices but will not work moving forward. If you did that on the 3750-x switch it would allow you to enable IPSERVICES but only for a few days as a trial. The cost is almost double to get the IPSERVICES image.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Lelio Fulgenzi [mailto:lelio@uoguelph.ca] <br><b>Sent:</b> Thursday, January 26, 2012 9:11 AM<br><b>To:</b> Bill Riley<br><b>Cc:</b> Cisco List VoIP; Ed Leatherman<br><b>Subject:</b> Re: [cisco-voip] ISR/VG Ethernet redundancy<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>I believe our core switches are advanced, not sure. Not my group. Here is the show version:<br><br>core1#show version<br>Cisco IOS Software, C3750 Software (C3750-IPSERVICES-M), Version 12.2(25)SEE3, RELEASE SOFTWARE (fc2)<br>Copyright (c) 1986-2007 by Cisco Systems, Inc.<br><br><br>---<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><br><o:p></o:p></span></p><div class=MsoNormal align=center style='text-align:center'><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'><hr size=2 width="100%" align=center id=zwchr></span></div><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>From: </span></b><span style='font-size:10.0pt;font-family:"Verdana","sans-serif";color:black'>"Bill Riley" <bill@hitechconnection.net><br><b>To: </b>"Ed Leatherman" <ealeatherman@gmail.com><br><b>Cc: </b>"Cisco List VoIP" <cisco-voip@puck.nether.net><br><b>Sent: </b>Thursday, January 26, 2012 10:05:17 AM<br><b>Subject: </b>Re: [cisco-voip] ISR/VG Ethernet redundancy<br><br>So then are you purchasing the advanced image for those switches? In that design I have always ran into the issue that the switches only support stub routing so they will not advertise the loopback adaptor of the VG because it is not directly connected. Then I have to get into static routes on the switch and redistributing them. Or purchase the image which makes the price too high.<br><br><br>-----Original Message-----<br>From: Ed Leatherman [mailto:ealeatherman@gmail.com] <br>Sent: Thursday, January 26, 2012 8:59 AM<br>To: Bill Riley<br>Cc: Cisco List VoIP<br>Subject: Re: [cisco-voip] ISR/VG Ethernet redundancy<br><br>Yes, in most cases it's L3 interfaces on whatever distribution hardware we happen to be using at the location. Usually 3750G or X pair or stack.<br><br>On Thu, Jan 26, 2012 at 9:54 AM, Bill Riley <<a href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>> wrote:<br>> So you are doing a layer 3 interface on the switchport the VG's are connected to? Are they the same switch or different switches?<br>><br>> I am doing the same thing just wondering how others are doing it.<br>><br>> -----Original Message-----<br>> From: Ed Leatherman <a href="mailto:[mailto:ealeatherman@gmail.com]">[mailto:ealeatherman@gmail.com]</a><br>> Sent: Thursday, January 26, 2012 8:53 AM<br>> To: Bill Riley<br>> Cc: Eric Pedersen; Lelio Fulgenzi; Jason Burns; Cisco List VoIP<br>> Subject: Re: [cisco-voip] ISR/VG Ethernet redundancy<br>><br>> I'm doing a /30 on each interface. Also have the VG224's configured as EIGRP stub and i'm filtering routes down to them so they don't get our full table. Seems to work well.<br>><br>><br>> On Thu, Jan 26, 2012 at 8:23 AM, Bill Riley <<a href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>> wrote:<br>>> For those that are running a routing protocol on your VG224 or ISR <br>>> used as a voice gateway do you have them dual uplinked? It’s great <br>>> that you have a routing protocol running in the event the L3 path <br>>> changes but what about the physical uplink from the VG to the <br>>> switches? Do you have that dual connected? Are you using either <br>>> channel or are your running multiple L3 subnets on each interface?<br>>><br>>><br>>><br>>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>>> <a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">[mailto:cisco-voip-bounces@puck.nether.net]</a> On Behalf Of Eric <br>>> Pedersen<br>>> Sent: Wednesday, January 25, 2012 4:04 PM<br>>> To: Lelio Fulgenzi; Jason Burns<br>>><br>>><br>>> Cc: Cisco List VoIP<br>>> Subject: Re: [cisco-voip] ISR/VG Ethernet redundancy<br>>><br>>><br>>><br>>> We're running OSPF on our VG224s and ISR PRI gateways for uplink <br>>> redundancy with no issues so far. It's nice to have the routing <br>>> protocol intelligence to handle upstream failures.<br>>><br>>><br>>><br>>> Eric<br>>><br>>><br>>><br>>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>>> <a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">[mailto:cisco-voip-bounces@puck.nether.net]</a> On Behalf Of Lelio <br>>> Fulgenzi<br>>> Sent: 25 January 2012 1:19 PM<br>>> To: Jason Burns<br>>> Cc: Cisco List VoIP<br>>> Subject: Re: [cisco-voip] ISR/VG Ethernet redundancy<br>>><br>>><br>>><br>>> 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 <br>>> supportedness of EIGRP on VG224s, but like you found out, no real <br>>> direction on how to configure redundancy on these.<br>>><br>>> I'm far less concerned with a port going down than a switch, so <br>>> having the VG224s uplinked to different switches is our choice.<br>>><br>>> Lelio<br>>><br>>><br>>> ---<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>>><br>>> ________________________________<br>>><br>>> From: "Jason Burns" <<a href="mailto:burns.jason@gmail.com">burns.jason@gmail.com</a>><br>>> To: "Bill Riley" <<a href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>><br>>> Cc: "Cisco List VoIP" <<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>><br>>> Sent: Wednesday, January 25, 2012 3:12:26 PM<br>>> Subject: Re: [cisco-voip] ISR/VG Ethernet redundancy<br>>><br>>> I second Etherchannel from the upstream device. I had a customer who <br>>> insisted on binding to the PortChannel interface for the voice <br>>> protocols, even though we recommended using the Loopback. It's up and <br>>> running just fine and does handle failure of a single link as expected.<br>>><br>>> -Jason<br>>><br>>> On Wed, Jan 25, 2012 at 3:07 PM, Bill Riley <br>>> <<a href="mailto:bill@hitechconnection.net">bill@hitechconnection.net</a>><br>>> wrote:<br>>><br>>> You should use a loop back and bind everything to in instead of the <br>>> physical 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 <br>>> have VSS on the 6500.<br>>><br>>> If not I have also bridged it into two separate switches using a BVI <br>>> like you are looking at.<br>>><br>>><br>>><br>>> -----Original Message-----<br>>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>>> <a href="mailto:[mailto:cisco-voip-bounces@puck.nether.net]">[mailto: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 <br>>> share 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">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">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">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>><br>>><br>>><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>><br>>> The contents of this message may contain confidential and/or <br>>> privileged<br>>><br>>> subject matter. If this message has been received in error, please <br>>> contact<br>>><br>>> the sender and delete all copies. Like other forms of communication,<br>>><br>>> e-mail communications may be vulnerable to interception by <br>>> unauthorized<br>>><br>>> parties. If you do not wish us to communicate with you by e-mail, <br>>> please<br>>><br>>> notify us at your earliest convenience. In the absence of such<br>>><br>>> notification, your consent is assumed. Should you choose to allow us <br>>> to<br>>><br>>> communicate by e-mail, we will not take any additional security <br>>> measures<br>>><br>>> (such as encryption) unless specifically requested.<br>>><br>>><br>>><br>>><br>>> _______________________________________________<br>>> cisco-voip mailing list<br>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>>><br>><br>><br>><br>> --<br>> Ed Leatherman<br>><br><br><br><br>--<br>Ed Leatherman<br><br><br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></p></div></div></body></html>