W.O.W. → new routing in Chicago Area.

Had an outage while working then saw this. Performance is still rock solid, so I assume this is just migration to new routing. WOW_Dan can you tell us whats going on if its not too much trouble? Also please turn up 100Mbps profile.... your power users will buy you a unicorn in return.

traceroute to www.indigo.nu (198.199.64.231), 30 hops max, 60 byte packets
1 router.blu.indigo.nu (10.0.0.1) 0.442 ms 0.268 ms 0.144 ms
2 * * *
3 dynamic-76-73-171-9.knology.net (76.73.171.9) 13.183 ms 13.946 ms 13.821 ms
4 76-73-170-112.knology.net (76.73.170.112) 14.326 ms 14.252 ms 14.115 ms
5 76-73-164-137.knology.net (76.73.164.137) 13.101 ms 12.915 ms 18.407 ms
6 76-73-164-125.knology.net (76.73.164.125) 19.079 ms 17.713 ms 17.488 ms
7 76-73-164-121.knology.net (76.73.164.121) 17.388 ms 14.028 ms 12.432 ms
8 76-73-164-109.knology.net (76.73.164.109) 12.909 ms 18.572 ms 19.234 ms
9 76-73-164-105.knology.net (76.73.164.105) 19.053 ms 18.902 ms 18.732 ms
10 76-73-164-65.knology.net (76.73.164.65) 14.359 ms 13.560 ms 13.398 ms
11 xe-11-2-1.edge1.Chicago2.Level3.net (4.71.248.245) 13.915 ms 20.572 ms 14.887 ms
12 vl-3512-ve-126.ebr1.Chicago2.Level3.net (4.69.158.222) 34.993 ms vl-3510-ve-124.ebr1.Chicago2.Level3.net (4.69.158.214) 41.293 ms vl-3509-ve-123.ebr1.Chicago2.Level3.net (4.69.158.210) 36.309 ms
13 ae-6-6.ebr1.Chicago1.Level3.net (4.69.140.189) 41.812 ms 41.899 ms 41.470 ms
14 ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66) 41.168 ms 41.069 ms 40.875 ms
15 ae-46-46.ebr2.NewYork1.Level3.net (4.69.201.29) 40.699 ms ae-45-45.ebr2.NewYork1.Level3.net (4.69.141.21) 39.682 ms ae-46-46.ebr2.NewYork1.Level3.net (4.69.201.29) 40.251 ms
16 ae-2-2.ebr1.Newark1.Level3.net (4.69.132.98) 39.198 ms 37.693 ms 38.131 ms
17 ae-1-51.edge3.Newark1.Level3.net (4.69.156.11) 36.452 ms 39.132 ms 37.526 ms
18 SERVERSTACK.edge3.Newark1.Level3.net (4.28.6.70) 47.960 ms 48.604 ms 48.405 ms
19 www.indigo.nu (198.199.64.231) 48.322 ms 48.135 ms 47.935 ms

This is part of our core network migration we're working on in all of the older WOW market (Michigan, Illinois, Indiana and Ohio).

Last night I moved Arlington Heights, Mount Prospect, Prospect Heights, Park Ridge and Des Plaines over to the new network.

Dan,
Can you speak to what this core network migration is (or what the purpose is)? I am in central Ohio. Is it to optimize routing within the network? Will it get rid of the hops using RFC1918 space getting out to the public Internet?

Matt

I can't really go into a huge amount of detail, but the upgrades are to design a more modern network, with much more capacity and equipment that can be used to offer more high end services down the line. This upgrade, once completed, will remove all RFC1918 hops you see currently while running traceroutes.

Thank you! Tired of seeing RFC1918 addresses in use for routing customer data. So this means 100meg this year right?
We have 8 downstream and 2 upstream channels here so you're well on your way.

Looks like the new network is running MPLS too. Keep up the good work Dan!

                                                               Packets               Pings
 Host                                                        Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. packet.pushing.robot (192.168.189.1)                      0.0%    76    0.2   0.3   0.2   0.8   0.0
 2. ???
 3. dynamic-76-73-171-13.knology.net (76.73.171.13)           0.0%    75   10.7  14.6   9.4  56.8   8.5
 4. 76-73-170-112.knology.net (76.73.170.112)                 0.0%    75   17.3  16.8   9.5  84.7  12.7
    [MPLS: Lbl 303040 Exp 0 S 1 TTL 1]
 5. 76-73-164-137.knology.net (76.73.164.137)                 0.0%    75   12.8  16.8   9.8  51.5  10.4
    [MPLS: Lbl 706477 Exp 0 S 1 TTL 1]
 6. 76-73-164-125.knology.net (76.73.164.125)                 0.0%    75    8.9  16.3   8.9  76.4  10.8
    [MPLS: Lbl 574648 Exp 0 S 1 TTL 1]
 7. 76-73-164-121.knology.net (76.73.164.121)                 0.0%    75   13.5  17.5   9.1  73.5  11.4
    [MPLS: Lbl 475148 Exp 0 S 1 TTL 1]
 8. 76-73-164-109.knology.net (76.73.164.109)                 0.0%    75   12.8  16.3   9.9  87.1  11.2
    [MPLS: Lbl 665561 Exp 0 S 1 TTL 1]
 9. 76-73-164-105.knology.net (76.73.164.105)                 0.0%    75   12.7  16.9  10.8  55.1   9.5
    [MPLS: Lbl 657104 Exp 0 S 1 TTL 1]
10. 76-73-164-65.knology.net (76.73.164.65)                   0.0%    75   12.2  17.7  10.0  81.8  11.6
11. xe-11-2-1.edge1.Chicago2.Level3.net (4.71.248.245)        0.0%    75   13.2  18.4  11.7  68.5  10.0
12. vl-3512-ve-126.ebr1.Chicago2.Level3.net (4.69.158.222)    0.0%    75   34.6  40.9  33.6  67.8   9.1
    [MPLS: Lbl 1208 Exp 0 S 1 TTL 1]
13. ae-6-6.ebr1.Chicago1.Level3.net (4.69.140.189)            0.0%    75   33.6  37.0  32.8  74.6   6.9
    [MPLS: Lbl 2019 Exp 0 S 1 TTL 1]
14. ae-2-2.ebr2.NewYork2.Level3.net (4.69.132.66)             0.0%    75   34.4  38.1  33.0  70.1   8.4
    [MPLS: Lbl 1216 Exp 0 S 1 TTL 1]
15. ae-48-48.ebr2.NewYork1.Level3.net (4.69.201.37)           0.0%    75   33.5  39.0  31.9  82.5   9.0
    [MPLS: Lbl 2010 Exp 0 S 1 TTL 1]
    ae-45-45.ebr2.NewYork1.Level3.net (4.69.141.21)
    [MPLS: Lbl 2010 Exp 0 S 1 TTL 1]
16. ae-2-2.ebr1.Newark1.Level3.net (4.69.132.98)              0.0%    75   35.1  38.1  32.7  83.2   9.4
    [MPLS: Lbl 1462 Exp 0 S 1 TTL 1]
17. ae-1-51.edge3.Newark1.Level3.net (4.69.156.11)            0.0%    75   35.0  39.3  32.4  84.8  10.5
18. SERVERSTACK.edge3.Newark1.Level3.net (4.28.6.70)          0.0%    75   48.4  42.6  34.0  84.8   9.6
19. www.indigo.nu (198.199.64.231)                            0.0%    75   34.2  38.8  34.0  68.4   7.6
 

thanks dan for info i did reboot ultra modem to let it pick up the change thanks agen keep up the great work, and all way smile bring, out the best day

ryan3531,
What are you using to perform a trace and see the MPLS labels?

It looks like MTR with the -e option (»www.BitWizard.nl/mtr)

OK, will this migration you are working on clear up speed issues??

I am asking because for the last 5 days I have been getting slow speeds. on average, Speakeasy.net (the speed test that WOW instructed me to use) has been giving me results between 18-30 Mbps down. Problem is, I am paying for 50 Mbps down.

A technician came out and replaced some cables but not really anything more than that and seemed to had cleared up until about 5 days ago.

That's it! Thank you DennisD.
Now what argument can I use to get MTR to display both the rDNS name and IP address like in the MTR above?
Thanks!

Hi, Dan. Thanks for calling them RFC1918 addresses. I'd love to see that horribly inaccurate "non-routable" name banned...

Isn't this against the trend as IPv4 address space gets scarce? Anything you can add about IPv6?

I agree. Call it RFC1918 since they are routable addresses - just not on the global internet. No BGP advertisements of that space!
I'd also love to see native IPv6 deployed on WOWs network. But meanwhile I'm glad to see the RFC1918 hops going away. I would say it is acceptable for WOW to use global space for routing. I've never been with an ISP before that used RFC1918 space to route customers to the public Internet so I'm glad WOW is making the change. The resources may be scarce (relatively) but I consider this an appropriate use of global address space. Of course I'm not a good gauge since my employer uses all global address space on the network.

Not much I can add about IPv6 at this time. While we have run it in the lab, our current IPv4 address space is not quite in jeopardy yet. IPv6 will be worked on once we've fully finished building the new infrastructure. Even then, it will probably only be used internally and on cable modems, so I wouldn't expect to see IPv6 anytime in 2014 unless something changes.

Thanks, Dan. It's obvious the IPv6 excitement has died down in general.

Hi mdpterman. The old cable service known as @Home had a zillion 10.x.x.x routers across the country but peering points where they left the network were all 172.(16-31).x.x so you always had a solid reference. I kinda liked that simplicity.

Back in those days it should have been fairly easy for them to get IPv4 resources. Seems like they would have used global address space for everything on the network. Each company to their own I suppose.

Hello WOW-Dan have you done this recently too in the Detroit area? As my routing has been going through knology.net only in the last half a day.

Yes. Recently some of our sites in all markets have been getting moved. This will continue over the next couple months until all sites have been migrated.