Issues with level3?

Mailman List Mirror (Read Only)
1

Anyone seeing any issues with level3? We can connect to every other IP in our Class C. When tracerouting to individual IP's, (x.x.x.50/51/52/53) we get a drop at ge-4-16.car2.Washington1.Level3.net [4.59.146.53] for 50, but 51 is fine, drop for 52, 53 is fine.

Thanks.

2

Sounds like a classic problem with a member of a bundle (like a link-agg
or ECMP) breaking. Level3 tends not to do anything in bundles of 2, so
you might want to look elsewhere, like with your own connections to
them, possibly on the reverse path. Now, please go find a blunt object
and hit yourself in the head as punishment for using the words "Class C"
in 2013 in a non-historic or ironic context. Hard. :slight_smile:

3

I still call a /24 a class c too.. :confused: lol

4

More efficient that way - "class c" uses fewer syllables than "slash
twenty four" :slight_smile:

5

It is not just you. We are seeing issue with that Level3 router/site as well.

I would report it to Level3, but I don't see any need to add to my already extensive collection of one line Level3 support responses saying "All is well. Nothing to see here. All is well."

My guess would be that your up/down for individual IPs is a result of your testing methodology. That Level3 router/site appears to be dropping some packets to all IPs that I tested before dropping my conn there.

Our response to the nearly constant Level3 issues of the past 12/18 months has been terminate them. The washington1.level3 site was unfortunately the last on my list of DCs.

6

I tend to enjoy being rebellious... Lol

7

You realize that class-c address space was only found within 192/8 e.g. if you print it in hex, C0000000. so not only is it historically irrelevant but you're using it wrong anyway.

8

i only call class-c's class-c's when they come from the space GE uses.

9

But, class B is not B0000000 and A is not A0000000, so is that actually true, or just a coincidence?

Class C was actually 192.0.0.0-223.255.255.255 (192.0.0.0/3)

-Randy

10

Not to mention that it's classier.

... JG

11

Randy beat me.. :confused:

Class C
192. 0. 0. 0 = 11000000.00000000.00000000.00000000
223.255.255.255 = 11011111.11111111.11111111.11111111
                  110nnnnn.nnnnnnnn.nnnnnnnn.HHHHHHHH

12

I still call a /24 a class c too.. :confused: lol

More efficient that way - "class c" uses fewer syllables than
"slash
twenty four" :slight_smile:

You realize that class-c address space was only found within 192/8
e.g.
if you print it in hex, C0000000. so not only is it historically
irrelevant but you're using it wrong anyway.

But, class B is not B0000000 and A is not A0000000, so is that actually true, or just a coincidence?

yeah /3 not /8

class-a is the first half of the address space
class-b is the next 1/4
...

13

Hi David,

I'm sorry you've had so many poor experiences with Level 3 recently, but I assure you that we have acknowledged the problem and are actively working on it at present.

Of general operations interest,

I just saw an event notification that matches the description of the problem and our NOC, engineering team and vendor are working together to solve the problem. If you are a customer and believe you are impacted, you can reference event case ID: 6237890 as potentially being the related case.

Dave

14

joel jaeggli wrote:

15

Your mistake there is trying to communicate with people who have been in
networking long enough to understand "class-c", but *still* haven't educated
themselves out of the slash-what stage. Such people deserve to be shunned.

16

The new guys dont know to shun these old folk. And then its too late.

Joe