<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000000'>...it can be, but we're not using it as a layer three switch. we decided to do all the routing on the router to make it a simpler config. we'll end up saving money two since we don't have to buy the more expensive L3 switch and pay for ip services license for EIGRP.<br><br>we'll try that out. thanks for the pointers.<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 (JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking with unix is easy. You just sed it and forget it. <br> - LFJ (with apologies to Mr. Popeil)<br><br><br>----- Original Message -----<br>From: "Brantley Richbourg" <Brantley.Richbourg@MMICNC.COM><br>To: "Lelio Fulgenzi" <lelio@uoguelph.ca><br>Cc: "Nate VanMaren" <VanMarenNP@ldschurch.org>, "cisco-voip voyp list" <cisco-voip@puck.nether.net><br>Sent: Thursday, March 18, 2010 10:57:58 AM GMT -05:00 US/Canada Eastern<br>Subject: RE: [cisco-voip] weighted EIGRP routes<br><br>
<style>P {
MARGIN: 0px
}
</style>
<div dir="ltr" align="left"><span class="655505314-18032010"><font color="#000080" size="2" face="Trebuchet MS">It would need to be changed on the router's g2/0.201
interface where you are running EIGRP. I assume that your switch is
<em>not</em> a layer 3 switch, right?</font></span></div>
<div dir="ltr" align="left"><span class="655505314-18032010"><font color="#000080" size="2" face="Trebuchet MS"></font></span> </div>
<div dir="ltr" align="left">
<hr>
<font size="2" face="Tahoma"><b>From:</b> Lelio Fulgenzi [mailto:lelio@uoguelph.ca]
<br><b>Sent:</b> Thursday, March 18, 2010 10:43 AM<br><b>To:</b> Brantley
Richbourg<br><b>Cc:</b> Nate VanMaren; cisco-voip voyp list<br><b>Subject:</b>
Re: [cisco-voip] weighted EIGRP routes<br></font><br></div>
<div></div>
<div style="font-size: 10pt; color: rgb(0, 0, 0); font-family: Verdana;">OK. In this
case, the "interface" that connects the routers to the VG224 are not a physical
interface, but a logical VLAN (or sub) interface.<br><br>do I put the
bandwidth/delay command on the gi2/0.201 sub-interface or on the switch's
physical interface?<br><br>
<div style="margin-left: 40px;">
<hr style="width: 100%; height: 2px;">
on the router:<br><br>interface gi2/0<br> desc Service
Module<br>interface gi2/0.201<br> encap dot1q
201<br> ip address 192.168.201.1 /24<br><br>on the
internal switch:<br> <br>interface
gi0/1<br> vlan 201<br> desc
VG224<br>interface gi0/18<br> desc trunk to
router<br> allowed VLANs 201 (among others)<br><br>on
the vg224:<br><br>interface fast0/0<br> desc link to
router<br> ip address 192.168.201.2 /24<br>
<hr style="width: 100%; height: 2px;">
<br></div><br><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
(JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking
with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br><br><br>----- Original Message
-----<br>From: "Brantley Richbourg" <Brantley.Richbourg@MMICNC.COM><br>To:
"Nate VanMaren" <VanMarenNP@ldschurch.org>, "Lelio Fulgenzi"
<lelio@uoguelph.ca>, "cisco-voip voyp list"
<cisco-voip@puck.nether.net><br>Sent: Thursday, March 18, 2010 10:33:02 AM
GMT -05:00 US/Canada Eastern<br>Subject: RE: [cisco-voip] weighted EIGRP
routes<br><br>
<style>P {
MARGIN: 0px
}
</style>
<style title="owaParaStyle">P {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</style>
<div dir="ltr" align="left"><font face="Tahoma"><font size="2"><span class="893242214-18032010"><font color="#000080" face="Trebuchet MS"><strong><font color="#000000" face="Tahoma"> If you want to change the metric calculations
for an EIGRP route, you have to modify parameters that EIGRP uses to calculate
the feasible distance. The bandwidth and delay commands on the interface(s) in
question can accomplish this. You can verify by looking at the "show
ip route" and you should see the next hop as the one for your primary path.
"show ip eigrp topo" command will also show how feasible distance
was calculated for each upstream
router. </font></strong></font></span></font></font></div>
<div dir="ltr" align="left"><font face="Tahoma"><font size="2"><span class="893242214-18032010"><font color="#000080" face="Trebuchet MS"><strong><font color="#000000" face="Tahoma"></font></strong></font></span></font></font> </div>
<div dir="ltr" align="left"><font face="Tahoma"><font size="2"><span class="893242214-18032010"><font color="#000080" face="Trebuchet MS"><strong><font color="#000000" face="Tahoma">If you change the bandwidth or delay on the
interface that belongs to the upstream router, that will change
the "Reported Distance" sent to the downstream router, which will in
turn change the "weight" on that router to the upstream
router. </font></strong> </font></span></font></font></div>
<div dir="ltr" align="left">
<hr>
</div>
<div dir="ltr" align="left"><font size="2" face="Tahoma"><b>From:</b>
cisco-voip-bounces@puck.nether.net [cisco-voip-bounces@puck.nether.net] On
Behalf Of Lelio Fulgenzi [lelio@uoguelph.ca]<br><b>Sent:</b> Wednesday, March
17, 2010 9:30 PM<br><b>To:</b> cisco-voip voyp list<br><b>Subject:</b>
[cisco-voip] weighted EIGRP routes<br></font><br></div>
<div></div>
<div>
<div style="font-size: 10pt; color: rgb(0, 0, 0); font-family: Verdana;">Any
pointers on how to tell a downstream EIGRP neighbour to weigh one route better
than another? Do I put the weight on the downstream neighbour to say EIGRP
routes coming in on one interface should be weighted more heavily? Or on the
upstream router to push down the weights?<br><br>Basically, what I have is
this:<br><br>
<div style="margin-left: 40px;">
<hr style="width: 100%; height: 2px;">
<span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
+-----------------------+</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
V
V </span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">3945 ->
switch -> VG224 <- switch <- 3945, where switch = SM-ESx-16</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;"><span style="font-family: Courier New,courier,monaco,monospace,sans-serif;">(view with
fixed font)</span><br style="font-family: Courier New,courier,monaco,monospace,sans-serif;">
<hr style="width: 100%; font-family: Courier New,courier,monaco,monospace,sans-serif; height: 2px;">
<br></div>Two 3945s with service module ethernet switches which connects to the
two VG224 ports. All routing is done on the router and the switch provides layer
two connectivity. A port channel group between the two switches allow the
routers to communicate HSRP keepalives. The VG224 is an EIGRP stub, and the two
upstream routers send out only default routes to the VG224 (that's all I
want).<br><br>Everything is working great. Except for the fact that the two
upstream routers are equal weight. This means that when the VG224 is talking to
the active HSRP address, it's going back and forth. Since the layer two link is
up between the routers, it still works, but not ideal. Bad things happen if the
link between the routers goes down - split brain!<br><br>Any
pointers?<br><br><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
(JNHN)<br>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>Cooking
with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br><br></div></div>
<div>
<p class="MsoNormal"><span style="font-family: 'Helvetica','Tahoma','Arial','sans-serif';"><font color="#666666"><br><br>NOTICE: This email message is for the sole use of the
intended recipient(s) and may contain confidential and privileged information.
Any unauthorized review, use, disclosure or distribution is prohibited. If you
are not the intended recipient, please contact the sender by reply email and
destroy all copies of the original message.</font></span></p><font color="#666666"><br></font></div><font color="#666666"></font><pre></pre>
<p>Confidentiality: The information in this electronic mail may contain
confidential, sensitive and/or protected health information intended only for
the addressee(s). Any other person, including anyone who believes he/she might
have received it due to an addressing error, is requested to notify this sender
immediately by return e-mail, and shall delete it without further reading and
retention. The information shall not be forwarded or shared unless in compliance
with MMIC policies on confidentiality, and/or the written permission of this
sender. </p></div><pre></pre><p>Confidentiality: The information in this electronic mail may contain confidential, sensitive and/or protected health information intended only for the addressee(s). Any other person, including anyone who believes he/she might have received it due to an addressing error, is requested to notify this sender immediately by return e-mail, and shall delete it without further reading and retention. The information shall not be forwarded or shared unless in compliance with MMIC policies on confidentiality, and/or the written permission of this sender.
</p>
</div></body></html>