North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Q on what IGP routing protocol to use for supplying only gateway address

  • From: Howard Berkowitz
  • Date: Thu Sep 14 15:20:52 2006



From: "william(at)elan.net" <[email protected]>
To: Roland Dobbins <[email protected]>
CC: [email protected]
Subject: Re: Q on what IGP routing protocol to use for supplying only gateway address
Date: Thu, 14 Sep 2006 10:55:28 -0700 (PDT)



On Thu, 14 Sep 2006, Roland Dobbins wrote:

On Sep 14, 2006, at 10:35 AM, william(at)elan.net wrote:

Any suggestion as to what IGP protocol is best for this scenario?
This is more of a cisco-nsp question, but probably OSPF, as it's supported
by the routing daemons on most *NIXes out of the box. I don't know about Windows.
If this was 5+ years ago, I'd have said RIP as it works great for supplying only gateway address, but I want RIP to go RIP and will
not use it again. So yes OSPF seems like best choice, but I was
hoping something simple for gateway-only is available. I've no idea
yet how to deal with Windows (all win2000 and win2003), anybody?
At least a few years ago, Windows OSPF was a port of Bay RS, which was really Wellfleet code. So far, whenever I've needed to look at Windows and figure out how it did something, knowing RS usually gave me the answer.

Are you doing anycasting or something?
Yes, anycasting will be involved but only for very small number of
servers (all linux) - that is kind-of separate issue. The equipment
itself however will only see local gateway addresses (obviously), so
it should not care or know about it.

If simple redundancy in the default gateway is the goal, another (and probably simpler) method is to implement HSRP or GLBP between your routers which are serving the hosts in question.
Can't use HSRP in this case (or IVRP or whatever else its called with non-cisco options) - too long to explain why.
VRRP for the non-Cisco. I've recently had to deal with some situations, in VoIP, where the critical Call Agents have to stay in communication even if physically distant. 802.1w seves nicely to share a subnet between two geographically separate sites. Admittedly, one can reasonably count on dual OC-192s, diversely routed, and each connected to two switches at either end.

_________________________________________________________________
Windows Live Spaces is here! It�s easy to create your own personal Web site. http://spaces.live.com/signup.aspx