[j-nsp] network engineering
Keegan.Holley at sungard.com
Keegan.Holley at sungard.com
Fri Feb 6 09:52:46 EST 2009
I'm sure someone will correct me if I'm wrong but if you plan to multihome
and actually use more than one connection you cannot completely prevent
this from happening. You can of course manipulate the attributes to make
certain flows use the same link. This should be on a case by case basis
and is not very scalable (like to the whole table). Asymmetric routing is
not a bad thing by and large just make sure your links are roughly the
same speed.
Keegan Holley ? Network Engineer I ? SunGard Availability Services ?
401 North Broad St. Philadelphia, PA 19108 ? (215) 446-1242 ?
keegan.holley at sungard.com Keeping People and Information Connected® ?
http://www.availability.sungard.com/
P Think before you print
CONFIDENTIALITY: This e-mail (including any attachments) may contain
confidential, proprietary and privileged information, and unauthorized
disclosure or use is prohibited. If you received this e-mail in error,
please notify the sender and delete this e-mail from your system.
From:
Matthias Gelbhardt <matthias at commy.de>
To:
juniper-nsp <juniper-nsp at puck.nether.net>
Date:
02/06/2009 04:12 AM
Subject:
[j-nsp] network engineering
Sent by:
juniper-nsp-bounces at puck.nether.net
Hi!
I have a little network engineering question and I would like to know
the best practice for that.
We have asymmetric routing in several cases. I would like to know, how
you would deal against that? Is there a simple way to send the packets
out of the same interface, they are received? But on the other hand,
many packets are send out by us, and we do not know, where the other
side is sending their packets into our network.
Is there a way to get an information, on which interface, better on
which BGP session the reverse path is coming in? Yes, there are
traceroute sites and looking glasses, but not for every network we
deal with.
The way I see it, the only way is to get the information, on which
interface the packets coming in (either by using a tool on the box or
by asking the network operator itself) ans then setting a local
prefernce to send the packet out of the same interface.
Any better ideas?
Regards,
Matthias
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list