other routing anomalies

Mailman List Mirror (Read Only)
1

I don't know anything about how jvnc.net runs their business, but a few
weeks ago, they decided to start advertising some of my /19's, along with
a bunch of other AGIS routes, effectively taking me and a lot of AGIS
customers off-line for several hours. Maybe they're still having routing
problems...

Ugh, I replied privately to Gordon; didn't realize he sent it to nanog :slight_smile:

JVNC said to him in an earlier message that they were currently defaulting
into MCI and the reason that they were sending outgoing data to netaxs through
the CIX was because *any* route that showed up at the CIX would be taken
since they were just defaulting into MCI.

I don't know why they were doing it - perhaps they were hit too hard by MCI
backbone problems (which should??? be resolved shortly w/ OC3).

We almost had to shut off the backup connectivity we get by having
our routes announced @ the CIX because it's a poor route to choose when
MAE-East is functioning fine.

Anyway, I don't know what kind of routes JVNC uses or what kind of routing
they're doing, but I'm hoping they take full routes from MCI again shortly.

Avi

2

Avi wrote Ugh, I replied privately to Gordon; didn't realize he sent it
to nanog :slight_smile: JVNC said to him in an earlier message that they were
currently defaulting into MCI.......

COOK: let me clear up some uncomfortable ambiguity in avi's use of the
pronoun "it"...... my original post to which he replied was to
nanog..... I did NOT send his private reply to nanog.

In response to Randy: I *KNOW* nanog should be avoided for this sort of
thing and I have BELIEVE me I have been trying to get this worked out
through JVNC. I have called them everyday beginning a weekago today to
try to get a resolution to the problem. they have been courteous, but
the answer has alwsays been we are working on it it should be done by
the end of the day. unfortunately it doesn't get done. My post last
night has resulted in some fresh information that I hope will get the
problem fixed. So in that sense going public here could provide the
solution.. I will try to avoid any continuation of this thread. BTW
the problems as of right now is definitely NOT fixed. :frowning: