[cisco-voip] weighted EIGRP routes
Peter Slow
peter.slow at gmail.com
Sun Mar 21 21:52:18 EDT 2010
that is totally overkill. It's SRST. You would be better off putting
the money into a properly architecture. Im imagining two smaller
routers connected to two switches, to which each of the vg224s is
connected. Also, If you're intent on this design and on using HSRP,
which i still think is completely wrong, you can get around your split
brain thing by disposing of EIGRP on the VG224 and linking its two FE
interfaces into a bridge group and usinng ONE IP address on it, on a
BVI interface. if the link between the routers goes down, the HSRP
traffic can still traverse the BVI interface on the VG224s. You dont
really need EIGRP here, thogh the failover tiem is ideal... You
definitely dont need multipath unless you're planning on sourcing more
than 100 mbps of traffic form the VG.
Realistically, the link between the two router's ESW modules shoudlnt
go down unless one of the routers goes down, and tehn you dont have to
worry about the split brain thing. I still think you're making this
more complicated than it needs to be. If this site is that important
that you cant risk it not having phone service, put a callmanager
there. Additionally, if the link between the two routers is
imperative, and you think theres a chance of losing it, add another
link between the etherswitch modules and either use etherchannel to
bond them, or just have an extra one staiding by and let STP take care
of shutting it down.
-Peter
On Fri, Mar 19, 2010 at 6:35 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
> The HSRP config provides a virtual SRST address that the VG224s can connect
> to. If one router goes down, they register to the other.
>
>
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
> - LFJ (with apologies to Mr. Popeil)
>
>
> ----- Original Message -----
> From: "Peter Slow" <peter.slow at gmail.com>
> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
> Cc: "Brantley Richbourg" <Brantley.Richbourg at mmicnc.com>, "cisco-voip voyp
> list" <cisco-voip at puck.nether.net>
> Sent: Friday, March 19, 2010 12:25:14 AM GMT -05:00 US/Canada Eastern
> Subject: Re: [cisco-voip] weighted EIGRP routes
>
> Lelio,
> multipath and voice mix rather poorly. also, you shoudlnt be using
> HSRP in this scenario.
> What need do you have for L2 connectivity between the two
> etherswitch modules? This really seems like bad design. What is it
> that you're trying to accomplish?
>
>
> -Peter
> (R&S / V #9048 ;)
>
> On Thu, Mar 18, 2010 at 11:00 AM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>> ...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.
>>
>> we'll try that out. thanks for the pointers.
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Cooking with unix is easy. You just sed it and forget it.
>> - LFJ (with apologies to Mr. Popeil)
>>
>>
>> ----- Original Message -----
>> From: "Brantley Richbourg" <Brantley.Richbourg at MMICNC.COM>
>> To: "Lelio Fulgenzi" <lelio at uoguelph.ca>
>> Cc: "Nate VanMaren" <VanMarenNP at ldschurch.org>, "cisco-voip voyp list"
>> <cisco-voip at puck.nether.net>
>> Sent: Thursday, March 18, 2010 10:57:58 AM GMT -05:00 US/Canada Eastern
>> Subject: RE: [cisco-voip] weighted EIGRP routes
>>
>> 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 not a layer 3 switch, right?
>>
>> ________________________________
>> From: Lelio Fulgenzi [mailto:lelio at uoguelph.ca]
>> Sent: Thursday, March 18, 2010 10:43 AM
>> To: Brantley Richbourg
>> Cc: Nate VanMaren; cisco-voip voyp list
>> Subject: Re: [cisco-voip] weighted EIGRP routes
>>
>> 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.
>>
>> do I put the bandwidth/delay command on the gi2/0.201 sub-interface or on
>> the switch's physical interface?
>>
>> ________________________________
>> on the router:
>>
>> interface gi2/0
>> desc Service Module
>> interface gi2/0.201
>> encap dot1q 201
>> ip address 192.168.201.1 /24
>>
>> on the internal switch:
>>
>> interface gi0/1
>> vlan 201
>> desc VG224
>> interface gi0/18
>> desc trunk to router
>> allowed VLANs 201 (among others)
>>
>> on the vg224:
>>
>> interface fast0/0
>> desc link to router
>> ip address 192.168.201.2 /24
>> ________________________________
>>
>>
>>
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Cooking with unix is easy. You just sed it and forget it.
>> - LFJ (with apologies to Mr. Popeil)
>>
>>
>> ----- Original Message -----
>> From: "Brantley Richbourg" <Brantley.Richbourg at MMICNC.COM>
>> To: "Nate VanMaren" <VanMarenNP at ldschurch.org>, "Lelio Fulgenzi"
>> <lelio at uoguelph.ca>, "cisco-voip voyp list" <cisco-voip at puck.nether.net>
>> Sent: Thursday, March 18, 2010 10:33:02 AM GMT -05:00 US/Canada Eastern
>> Subject: RE: [cisco-voip] weighted EIGRP routes
>>
>> 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.
>>
>> 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.
>> ________________________________
>> From: cisco-voip-bounces at puck.nether.net
>> [cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
>> [lelio at uoguelph.ca]
>> Sent: Wednesday, March 17, 2010 9:30 PM
>> To: cisco-voip voyp list
>> Subject: [cisco-voip] weighted EIGRP routes
>>
>> 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?
>>
>> Basically, what I have is this:
>>
>> ________________________________
>> +-----------------------+
>> V V
>> 3945 -> switch -> VG224 <- switch <- 3945, where switch = SM-ESx-16
>>
>> (view with fixed font)
>> ________________________________
>> 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).
>>
>> 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!
>>
>> Any pointers?
>>
>>
>>
>>
>> ---
>> Lelio Fulgenzi, B.A.
>> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
>> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> Cooking with unix is easy. You just sed it and forget it.
>> - LFJ (with apologies to Mr. Popeil)
>>
>>
>>
>> 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.
>>
>> 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.
>>
>> 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.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
More information about the cisco-voip
mailing list