Looking to discuss a routing issue going through NTT's link to JP.
We are getting a huge amount of traffic loss while sending to JP. I am trying to figure out if the problem is with cogent or NTT. Thoughts? Here is a MTR trace: login02.bal (0.0.0.0) Thu Nov 27 01:58:22 2014 Keys: Help Display mode Restart statistics Order of fields quit Packets Pings Host Loss% Last Avg Best Wrst StDev 1. v122-router.bal 0.0% 0.2 0.3 0.2 3.7 0.5 2. netscaler3.bal 0.0% 0.1 0.1 0.1 0.2 0.0 3. gw1.bal.brightcove.com 0.0% 0.6 1.9 0.2 12.4 3.2 4. border1.te9-1.brightcoveinc-2.chg004.pnap.net 2.1% 0.9 2.1 0.4 36.5 6.5 5. core1.te2-2-bbnet2.chg.pnap.net 0.0% 2.1 2.1 1.8 3.5 0.4 6. te0-5-0-33.ccr21.ord03.atlas.cogentco.com 0.0% 1.9 2.5 1.8 16.2 2.5 7. be2003.ccr42.ord01.atlas.cogentco.com 0.0% 2.4 2.5 2.3 3.7 0.3 8. be2157.ccr22.mci01.atlas.cogentco.com 0.0% 14.4 14.3 14.1 17.4 0.5 9. be2133.ccr22.sfo01.atlas.cogentco.com 0.0% 52.0 52.1 51.7 54.0 0.4 10. be2165.ccr22.sjc01.atlas.cogentco.com 23.4% 52.7 52.8 52.6 53.3 0.2 11. be2047.ccr21.sjc03.atlas.cogentco.com 67.4% 53.5 53.5 53.4 53.8 0.1 12. verio.iad01.atlas.cogentco.com 29.8% 53.1 53.2 53.0 54.6 0.4 13. ae-6.r20.snjsca04.us.bb.gin.ntt.net 67.4% 53.3 59.3 53.0 82.3 10.1 14. ae-4.r20.tokyjp05.jp.bb.gin.ntt.net 29.8% 138.2 140.6 138.1 173.9 7.6 15. ae-1.ocn.tokyjp05.jp.bb.gin.ntt.net 69.6% 153.8 153.9 153.8 154.0 0.0 16. 60.37.27.92 97.8% 154.1 154.1 154.1 154.1 0.0 17. 114.147.63.70 36.2% 194.0 167.0 155.0 203.5 16.7 18. 118.23.13.2 63.0% 155.8 155.9 155.8 156.1 0.1 19. 118.23.14.66 100.0 0.0 0.0 0.0 0.0 0.0 20. p3044-ipngnfx01marunouchi.tokyo.ocn.ne.jp 97.8% 150.8 150.8 150.8 150.8 0.0 On Thu, Nov 27, 2014 at 4:56 AM, Job Snijders <job@instituut.net> wrote:
On Thu, Nov 27, 2014 at 04:51:59AM -0500, james jones wrote:
Looking to discuss a routing issue going through NTT's link to JP.
Feel free to contact me off-list with the details.
Kind regards,
Job
Seems your MTR sees loss within the Cogent (174) network prior to reaching the NTT network. I think you perhaps need cogent assistance? - Jared On Thu, Nov 27, 2014 at 04:58:59AM -0500, james jones wrote:
We are getting a huge amount of traffic loss while sending to JP. I am trying to figure out if the problem is with cogent or NTT. Thoughts? Here is a MTR trace:
login02.bal (0.0.0.0) Thu Nov 27 01:58:22 2014
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Last Avg Best Wrst StDev
1. v122-router.bal 0.0% 0.2 0.3 0.2 3.7 0.5
2. netscaler3.bal 0.0% 0.1 0.1 0.1 0.2 0.0
3. gw1.bal.brightcove.com 0.0% 0.6 1.9 0.2 12.4 3.2
4. border1.te9-1.brightcoveinc-2.chg004.pnap.net 2.1% 0.9 2.1 0.4 36.5 6.5
5. core1.te2-2-bbnet2.chg.pnap.net 0.0% 2.1 2.1 1.8 3.5 0.4
6. te0-5-0-33.ccr21.ord03.atlas.cogentco.com 0.0% 1.9 2.5 1.8 16.2 2.5
7. be2003.ccr42.ord01.atlas.cogentco.com 0.0% 2.4 2.5 2.3 3.7 0.3
8. be2157.ccr22.mci01.atlas.cogentco.com 0.0% 14.4 14.3 14.1 17.4 0.5
9. be2133.ccr22.sfo01.atlas.cogentco.com 0.0% 52.0 52.1 51.7 54.0 0.4
10. be2165.ccr22.sjc01.atlas.cogentco.com 23.4% 52.7 52.8 52.6 53.3 0.2
11. be2047.ccr21.sjc03.atlas.cogentco.com 67.4% 53.5 53.5 53.4 53.8 0.1
12. verio.iad01.atlas.cogentco.com 29.8% 53.1 53.2 53.0 54.6 0.4
13. ae-6.r20.snjsca04.us.bb.gin.ntt.net 67.4% 53.3 59.3 53.0 82.3 10.1
14. ae-4.r20.tokyjp05.jp.bb.gin.ntt.net 29.8% 138.2 140.6 138.1 173.9 7.6
15. ae-1.ocn.tokyjp05.jp.bb.gin.ntt.net 69.6% 153.8 153.9 153.8 154.0 0.0
16. 60.37.27.92 97.8% 154.1 154.1 154.1 154.1 0.0
17. 114.147.63.70 36.2% 194.0 167.0 155.0 203.5 16.7
18. 118.23.13.2 63.0% 155.8 155.9 155.8 156.1 0.1
19. 118.23.14.66 100.0 0.0 0.0 0.0 0.0 0.0
20. p3044-ipngnfx01marunouchi.tokyo.ocn.ne.jp 97.8% 150.8 150.8 150.8 150.8 0.0
On Thu, Nov 27, 2014 at 4:56 AM, Job Snijders <job@instituut.net> wrote:
On Thu, Nov 27, 2014 at 04:51:59AM -0500, james jones wrote:
Looking to discuss a routing issue going through NTT's link to JP.
Feel free to contact me off-list with the details.
Kind regards,
Job
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
On Thu, Nov 27, 2014 at 11:00:32AM -0500, Jared Mauch wrote:
Seems your MTR sees loss within the Cogent (174) network prior to reaching the NTT network.
I think you perhaps need cogent assistance?
This was resolved off-list. James is now engaging with his supplier. For future reference: When assistance is needed from NTT, please reach out directly to noc@ntt.net. That mailbox is guarded 24/7 by good people. Kind regards, Job
Never assume symetric routing (though Im almost old enough to remember the days of.) Wish there was some kinda bidirect traceroute protocol widely supported. Mostly we only have lg's via www if they happen to have been setup for such occasions :( I know there were a few small projects with this kinda idea, but I am not sure if any of them really got anywhere. /kc On Thu, Nov 27, 2014 at 11:00:32AM -0500, Jared Mauch said:
Seems your MTR sees loss within the Cogent (174) network prior to reaching the NTT network.
I think you perhaps need cogent assistance?
- Jared
On Thu, Nov 27, 2014 at 04:58:59AM -0500, james jones wrote:
We are getting a huge amount of traffic loss while sending to JP. I am trying to figure out if the problem is with cogent or NTT. Thoughts? Here is a MTR trace:
login02.bal (0.0.0.0) Thu Nov 27 01:58:22 2014
Keys: Help Display mode Restart statistics Order of fields quit
Packets Pings
Host Loss% Last Avg Best Wrst StDev
1. v122-router.bal 0.0% 0.2 0.3 0.2 3.7 0.5
2. netscaler3.bal 0.0% 0.1 0.1 0.1 0.2 0.0
3. gw1.bal.brightcove.com 0.0% 0.6 1.9 0.2 12.4 3.2
4. border1.te9-1.brightcoveinc-2.chg004.pnap.net 2.1% 0.9 2.1 0.4 36.5 6.5
5. core1.te2-2-bbnet2.chg.pnap.net 0.0% 2.1 2.1 1.8 3.5 0.4
6. te0-5-0-33.ccr21.ord03.atlas.cogentco.com 0.0% 1.9 2.5 1.8 16.2 2.5
7. be2003.ccr42.ord01.atlas.cogentco.com 0.0% 2.4 2.5 2.3 3.7 0.3
8. be2157.ccr22.mci01.atlas.cogentco.com 0.0% 14.4 14.3 14.1 17.4 0.5
9. be2133.ccr22.sfo01.atlas.cogentco.com 0.0% 52.0 52.1 51.7 54.0 0.4
10. be2165.ccr22.sjc01.atlas.cogentco.com 23.4% 52.7 52.8 52.6 53.3 0.2
11. be2047.ccr21.sjc03.atlas.cogentco.com 67.4% 53.5 53.5 53.4 53.8 0.1
12. verio.iad01.atlas.cogentco.com 29.8% 53.1 53.2 53.0 54.6 0.4
13. ae-6.r20.snjsca04.us.bb.gin.ntt.net 67.4% 53.3 59.3 53.0 82.3 10.1
14. ae-4.r20.tokyjp05.jp.bb.gin.ntt.net 29.8% 138.2 140.6 138.1 173.9 7.6
15. ae-1.ocn.tokyjp05.jp.bb.gin.ntt.net 69.6% 153.8 153.9 153.8 154.0 0.0
16. 60.37.27.92 97.8% 154.1 154.1 154.1 154.1 0.0
17. 114.147.63.70 36.2% 194.0 167.0 155.0 203.5 16.7
18. 118.23.13.2 63.0% 155.8 155.9 155.8 156.1 0.1
19. 118.23.14.66 100.0 0.0 0.0 0.0 0.0 0.0
20. p3044-ipngnfx01marunouchi.tokyo.ocn.ne.jp 97.8% 150.8 150.8 150.8 150.8 0.0
On Thu, Nov 27, 2014 at 4:56 AM, Job Snijders <job@instituut.net> wrote:
On Thu, Nov 27, 2014 at 04:51:59AM -0500, james jones wrote:
Looking to discuss a routing issue going through NTT's link to JP.
Feel free to contact me off-list with the details.
Kind regards,
Job
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
-- Ken Chase - math@sizone.org Toronto
participants (4)
-
james jones -
Jared Mauch -
Job Snijders -
Ken Chase