We're seeing some really weird issues with connections that go through / to
Level3 IP space. Basically, certain pairs of IPs (particular L3 IPs
coupled with particular IPs of ours) have dodgy/nonexistent connectivity,
but if you change the IP at either end everything's hunky dory.
I've sniffed
1) I've seen this behavior before; you are not alone in the universe.
2) Most likely there is a balanced channel on the path, either L3 or
L2, and one of the links in the bundle is dead but has not been
detected as such.
Rubens
On Sun, Jun 15, 2008 at 11:01 AM, Matt Palmer [EMAIL PROTECTED]
Palmer [EMAIL PROTECTED]
To: nanog@nanog.org
Sent: Sunday, June 15, 2008 10:39:56 AM GMT -05:00 US/Canada Eastern
Subject: Re: Single IP routing problems through Level3
On Sun, Jun 15, 2008 at 11:12:25AM -0300, Rubens Kuhl Jr. wrote:
1) I've seen this behavior before; you are not alone
Matt Palmer wrote:
We're seeing some really weird issues with connections that go through / to
Level3 IP space. Basically, certain pairs of IPs (particular L3 IPs
coupled with particular IPs of ours) have dodgy/nonexistent connectivity,
but if you change the IP at either end everything's hunky
Matt Palmer wrote:
A multiple-link bundle which is load balanced by source/destination pair
with an undetected dud link? I hadn't thought of that, but it does make an
*awful* lot of sense
I've also seen interesting OSPF misconfigurations that resulted in a
router doing path-wise load
5 matches
Mail list logo
