Here is a good reference/place to start: http://www.netaxs.com/~freedman/multi.html - paul At 11:48 AM 11/6/97 +0800, Michael R. Poyaoan wrote:
The diagram below describes our current set-up:
* We have two default routes via BGP with MCI (L1 and L2) for outgoing traffic. * The two MCI links are configured to load share incoming traffic thru the use of MEDs.
AS701 +--------+ | UUNet | +--------+ | AS3561 | +-------+ +--------+ | MCI | | UNA | AS10275 +-------+ +--------+ | | | | | | | | | L1| |L2 L3| | | AS6648 | | | +----------+ | | +---| | | | | Sky |-----+ +------| | +----------+
Questions:
1. How can I use the third link for default routes? Is static routing the only solution?
2. Is it possible to load-share outgoing traffic between two different ASN's? How?
3. How can I unclude the third link for load-sharing incoming traffic?
Please reply privately.
Thanks, --------------------------------------------------------------------------- Michael R. Poyaoan email: mrp@skyinet.net Network Operations Center voice: +63 2 411-2005 Sky Internet, Inc. fax: +63 2 411-2003 ---------------------------------------------------------------------------
Here is a good reference/place to start:
http://www.netaxs.com/~freedman/multi.html
- paul
Thanks for the reference, Paul. I should have put a pointer at that location to the newer one: http://www.netaxs.com/~freedman/bgp/bgp.html - a rewritten one with more details... Thanks, Avi <who only reads NANOG every week or so at current volume>
Apropos of the multihoming discussions here in general, I've posted an I-D intended to help clarify some confusing alternatives. Discussions on NANOG, as well as my student questions, suggested to me there might be a need for a tutorial at a different level of abstraction than the specific technique discussions that are available. It's not intended to show how, for example, to do BGP multihoming. It's intended to help someone, especially an end user organization, decide what the problem is they are trying to solve. Once they know that, the next step will be selecting DNS-based methods, and/or routing-based methods using BGP or IGPs. Comments very welcome, especially in the DNS area. My plan is to submit this to the IDR WG at the IETF in December, but it's an individual contribution at this point. To Be Multihomed: Requirements & Definitions draft-berkowitz-multirqmt-00.txt 2. Abstract As organizations find their Internet connectivity increasingly critical to their mission, they seek ways of making that connectivity more robust. The term ''multi-homing'' often is used to describe means of fault-tolerant connection. Unfortunately, this term covers a variety of mechanisms, including naming/directory services, routing, and physical connectivity. This memorandum presents a systematic way to define the requirement for resilience, and a taxonomy for describing mechanisms to achieve it. Multiple mechanisms may be appropriate for specific situations, including DNS, BGP, etc.
participants (3)
-
Avi Freedman -
Howard C. Berkowitz -
Paul Ferguson