iBurst Peering on CINX?

[ginggs]

I've just noticed traffic between me and UCT is no longer going via Joburg!

 

[drs]

Not that I can see -- if iBurst is at CINX, they're not peering with TENET. Go http://lg.tenet.ac.za and select "bgp summary" and "Cape Town IPv4". That shows a list BGP peering sessions on TENET's Cape Town router, and I don't see AS 33762 there. On bgp summary for the Johannesburg 1 router, you can see the peering session with iBurst at JINX listed.

What does your traceroute show?

 

[r00igev@@r]

CINX is not yet active :-(

 

[ginggs]

Tracing route to srvslsweb001.uct.ac.za [137.158.158.44]
over a maximum of 30 hops:

1 121 ms 45 ms 274 ms wbs-41-208-224-1.wbs.co.za [41.208.224.1]
2 54 ms 39 ms 44 ms 192.168.2.3
3 148 ms 47 ms 45 ms 192.168.2.9
4 90 ms 156 ms 40 ms 66.8.22.205
5 178 ms 58 ms 156 ms srp5-0.br2.cpt1.za.mtnbusiness.net [196.31.249.65]
6 104 ms 104 ms 140 ms other-side.s3-2chan0.br2.cpt1.za.mtnbusiness.net [196.7.8.194]
7 98 ms 184 ms 116 ms ch1-ctn-gi0-2.ip.isnet.net [168.209.6.129]
8 130 ms 90 ms 106 ms 168.209.21.42
9 * 114 ms 110 ms uct-cpt1-t201-vl2744.net.tenet.ac.za [155.232.7.2]
10 204 ms 110 ms 208 ms inside-e2.uct.ac.za [137.158.253.10]

Previously, and last time I checked, on Sunday I think (unfortunately did not save a copy) it was something like:
wbs.co.za
mtnbusiness.net
isnet.net cape town
isnet.net joburg
wbs.co.za joburg
jinx
tenet joburg
tenet bloemfontain
tenet cape town
uct

 

[ginggs]

CINX is not yet active :-(

I think it is now.

Down to only 6 hops to get to inside-e2.uct.ac.za.

 

[ambo]

Down to only 6 hops to get to inside-e2.uct.ac.za.

And you latency?

 

[r00igev@@r]

Yep, we are active and CINX. It was like birthing an elephant.

BTW: If there is anyone from Telkom, Internet Solutions, MTN, Vodacom, etc reading this, this is an open invitation to peer with us at CINX.

 

[ambo]

BTW: If there is anyone from Telkom, Internet Solutions, MTN, Vodacom, etc reading this, this is an open invitation to peer with us at CINX.

If you succeed with that please let me know. All I get is the sounds of silence...

 

[r00igev@@r]

If you succeed with that please let me know. All I get is the sounds of silence...

We received the proverbial middle finger.

 

[ginggs]

And you latency?

rtt min/avg/max/mdev = 56.427/87.772/129.306/24.604 ms

 

[ginggs]

Why does the traffic to TENET no longer go via CINX?

$ traceroute www.uct.ac.za
traceroute to www.uct.ac.za (137.158.158.44), 30 hops max, 60 byte packets
1 mikrotik (192.168.88.1) 0.512 ms 0.658 ms 0.803 ms
2 lac4.cpt.wbs.co.za (41.56.199.1) 36.467 ms 41.415 ms 46.370 ms
3 vl75.cs2.cpt.wbs.co.za (41.56.254.3) 51.369 ms 56.344 ms 61.277 ms
4 vl75.cs3.cpt.wbs.co.za (41.56.254.22) 71.284 ms 76.276 ms 76.320 ms
5 iburst-41-56-254-195.iburst.co.za (41.56.254.195) 106.286 ms 111.193 ms 116.185 ms
6 192.168.0.113 (192.168.0.113) 116.273 ms 113.861 ms 118.618 ms
7 pgw05-jinx-ge03.jhb.wbs.co.za (41.213.126.22) 123.689 ms 94.321 ms 99.256 ms
8 tenet.jinx.net.za (196.223.14.33) 99.794 ms 94.387 ms 99.261 ms
9 unknown.uni.net.za (155.232.6.109) 99.865 ms 94.395 ms 99.287 ms
10 unknown.uni.net.za (155.232.6.66) 99.381 ms 69.528 ms 74.427 ms
11 inside-e2.uct.ac.za (137.158.253.10) 74.774 ms 95.349 ms 74.559 ms
12 137.158.248.18 (137.158.248.18) 94.521 ms 99.516 ms 99.444 ms

 

[ambo]

Why does the traffic to TENET no longer go via CINX?

Based on those latencies I would guess asynchronous routing. Packets going to TENET via JINX and returning to iBurst via CINX.

Rooi probably needs to ask his guys to check the metrics and local-pref on their routers.

 

[ginggs]

Better now, thanks.

$ traceroute www.uct.ac.za
traceroute to www.uct.ac.za (137.158.158.44), 30 hops max, 60 byte packets
1 mikrotik (192.168.88.1) 0.558 ms 0.718 ms 0.876 ms
2 lac1.cpt.wbs.co.za (41.56.212.1) 36.865 ms 41.795 ms 46.663 ms
3 vl75.cs2.cpt.wbs.co.za (41.56.254.3) 56.697 ms 56.784 ms 61.559 ms
4 ge0-1.75.cr2.cpt.wbs.co.za (41.56.254.31) 66.581 ms 76.583 ms 81.612 ms
5 vl75.cr3.cpt.wbs.co.za (41.56.254.36) 81.698 ms 86.529 ms 86.587 ms
6 tenet.cinx.net.za (196.223.22.33) 96.611 ms 100.511 ms 100.485 ms
7 unknown.uni.net.za (155.232.6.113) 105.537 ms 43.206 ms 40.720 ms
8 unknown.uni.net.za (155.232.6.66) 45.676 ms 50.648 ms 55.519 ms
9 inside-e2.uct.ac.za (137.158.253.10) 65.585 ms 70.476 ms 75.459 ms
10 137.158.248.18 (137.158.248.18) 80.492 ms 85.450 ms 90.394 ms