Anyone anyalize this?

megatexel

Senior member
Jan 13, 2000
624
0
0
I try doing a traceroute to hatchet.badaxe.k12.mi.us and get this...

-----------------------------------------------------------------------------

C:\>tracert hatchet.badaxe.k12.mi.us

Tracing route to hatchet.badaxe.k12.mi.us [199.177.186.5]
over a maximum of 30 hops:

1 * * * Request timed out.
2 140 ms 140 ms 141 ms 4.18.150.7
3 140 ms 130 ms 140 ms router.iresa-net.com [4.18.150.1]
4 171 ms 150 ms 150 ms s11-0-0-13-2.detroit1-cr1.bbnplanet.net [4.0.244
.45]
5 160 ms 171 ms 160 ms h3-0.cleveland1-br1.bbnplanet.net [4.0.2.1]
6 220 ms 181 ms 170 ms h11-0-0.nyc4-br2.bbnplanet.net [4.0.3.22]
7 160 ms 181 ms 170 ms p3-0.nyc4-nbr2.bbnplanet.net [4.0.5.29]
8 170 ms 171 ms 170 ms p4-0.nycmny1-nbr1.bbnplanet.net [4.0.5.97]
9 220 ms 181 ms 170 ms p1-0.nycmny1-br1.bbnplanet.net [4.24.10.82]
10 210 ms 171 ms 170 ms p1-0.nycmny1-ba1.bbnplanet.net [4.24.6.230]
11 220 ms 181 ms 170 ms p1-0.xnyc1-mci.bbnplanet.net [4.24.7.70]
12 220 ms 181 ms 180 ms corerouter2.WestOrange.cw.net [204.70.9.139]
13 220 ms 181 ms 180 ms corerouter2.NorthRoyalton.cw.net [204.70.9.137]

14 190 ms 191 ms 180 ms bordercore2.NorthRoyalton.cw.net [166.48.224.1]

15 271 ms 210 ms 230 ms merit-its.NorthRoyalton.cw.net [166.48.225.250]

16 351 ms 320 ms 541 ms 198.108.22.126
17 220 ms 230 ms 221 ms 198.108.23.9
18 230 ms 220 ms 221 ms h2-0.saginaw.mich.net [198.108.23.54]
19 280 ms 230 ms 231 ms 198.111.194.6
20 360 ms 251 ms * 199.177.128.4
21 * 270 ms * 199.177.187.5
22 2033 ms * * router.badaxe.k12.mi.us [199.177.186.1]
23 * 771 ms * hatchet.badaxe.k12.mi.us [199.177.186.5]
24 * 2444 ms 1252 ms hatchet.badaxe.k12.mi.us [199.177.186.5]

Trace complete.

-----------------------------------------------------------------------------

Can anyone tell me which router is down? OR what the problem is?

please help... thx

 

jmcoreymv

Diamond Member
Oct 9, 1999
4,264
0
0
Yes, it means your isps network engineers suck, and they dont know how to properly configure BGP.
 

Xanathar

Golden Member
Oct 14, 1999
1,435
0
0
It means your problem lies with 199.177.187.5 or the link between that router and 199.177.186.1 or the 199.177.186.1 router itself. It is most likely an overloaded router at 187.5
 

jmcoreymv

Diamond Member
Oct 9, 1999
4,264
0
0
Oops didnt notice that, but also you have way to many hops on the bbnplanet backbone which leads me to believe that BGP is misconfigured.