Problem Observations
It is observed that a total of six nodes (Pakistani nodes) are pingable from some regions (in particular Pakistan) and not pingable from other regions (see below), in particular they are not pingable from SLAC. It is also observed that we are unable to gather data from these nodes while accessing from SLAC however, we are able to gather data at SEECS. These nodes are
- pinger.pern.edu.pk (Islamabad HEC POP node)
- pingerisl-fjwu.pern.edu.pk (Islamabad Fatima Jinnah Women University POP node)
- pingerisl-qau.pern.edu.pk (Islamabad Quaid-e-Azam University POP node)
- pingermtn.pern.edu.pk (Multan POP node)*
- nuisb.seecs.edu.pk (FAST NU Islamabad Campus node)
- nukhimain.seecs.edu.pk (FAST NU Karachi Campus node)
* This host was pingable from SLAC and a Menlo Park home at 9:00pm 1/5/2012, so we will ignore
The other hosts are not pingable from SLAC but are pingable from homes near SLAC and from SLAC all are reached by a route going via transpac (Tokyo), apan and tein3 (Singapore)
1 rtr-servcore1-serv01-webserv.slac.stanford.edu (134.79.197.130) 0.612 ms 0.672 ms 0.765 ms 2 rtr-core1-p2p-servcore1.slac.stanford.edu (134.79.252.166) 0.391 ms 0.398 ms 0.449 ms 3 rtr-border2-p2p-core1.slac.stanford.edu (134.79.252.141) 0.566 ms 0.692 ms 0.775 ms 4 slac-mr2-p2p-rtr-border2.slac.stanford.edu (192.68.191.249) 0.264 ms 0.287 ms 0.275 ms 5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.653 ms 0.665 ms 0.685 ms 6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.738 ms 0.748 ms 0.737 ms 7 * * * 8 tokyo-losa-tp2.transpac2.net (192.203.116.146) 122.953 ms 122.985 ms 123.023 ms 9 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 126.046 ms 126.036 ms 126.021 ms 10 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 191.860 ms 191.850 ms 191.839 ms 11 pk-pr-v4.bb.tein3.net (202.179.249.46) 274.290 ms 274.364 ms 274.443 ms
Looking (via pingtable.pl) at the Pakistani hosts pinged by PingER from SLAC the above hosts have not been pingable for many days. Most hosts that are pingable appear to have a a route that goes via SJ, NY, Washington, Paris, Marseilles and KHI:
1 rtr-servcore1-serv01-webserv.slac.stanford.edu (134.79.197.130) 0.419 ms 0.527 ms 0.615 ms 2 rtr-core2-p2p-servcore1.slac.stanford.edu (134.79.252.162) 0.366 ms 0.405 ms 0.469 ms 3 rtr-border1-p2p-core2.slac.stanford.edu (134.79.252.137) 0.504 ms 0.600 ms 0.698 ms 4 slac-mr2-p2p-rtr-border1.slac.stanford.edu (192.68.191.245) 1.024 ms 1.014 ms 1.016 ms 5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.633 ms 0.627 ms 0.621 ms 6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.696 ms 0.697 ms 0.680 ms 7 paixpart1-sunncr1.es.net (134.55.218.133) 1.499 ms 1.553 ms 1.631 ms 8 ge-7-15.car1.SanJose2.level3.net (4.68.62.5) 1.362 ms 1.410 ms 1.474 ms 9 vlan80.csw3.SanJose1.Level3.net (4.69.152.190) 1.137 ms 1.165 ms 1.112 ms 10 ae-81-81.ebr1.SanJose1.Level3.net (4.69.153.9) 1.131 ms 1.137 ms 1.149 ms 11 ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186) 69.500 ms 69.350 ms 69.400 ms 12 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 69.277 ms 69.708 ms 69.543 ms 13 ae-1-100.ebr1.NewYork2.Level3.net (4.69.135.253) 69.929 ms 69.686 ms 69.604 ms 14 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 74.923 ms 74.776 ms 74.783 ms 15 ae-44-44.ebr2.Paris1.Level3.net (4.69.137.61) 154.104 ms ae-41-41.ebr2.Paris1.Level3.net (4.69.137.49) 154.599 ms ae-42-42.ebr2.Paris1.Level3.net (4.69.137.53) 164.308 ms 16 ae-24-24.ebr1.Paris1.Level3.net (4.69.143.129) 160.952 ms ae-22-22.ebr1.Paris1.Level3.net (4.69.143.121) 155.105 ms ae-23-23.ebr1.Paris1.Level3.net (4.69.143.125) 155.453 ms 17 ae-1-7.bar1.Marseille1.Level3.net (4.69.143.237) 166.513 ms 164.878 ms 165.227 ms 18 ae-2-3.edge2.Marseille1.Level3.net (4.69.143.250) 165.271 ms 164.625 ms 164.561 ms 19 213.242.115.6 (213.242.115.6) 278.961 ms 280.921 ms 278.227 ms 20 static-10GE-KHI275-P01-SwA.pie.net.pk (202.125.128.173) 281.109 ms 280.776 ms 280.474 ms 21 rwp44.pie.net.pk (221.120.251.158) 293.483 ms 293.701 ms 295.425 ms 22 221.120.197.114 (221.120.197.114) 304.808 ms 306.005 ms 305.021 ms 23 lcwu.edu.pk (111.68.103.135) 316.562 ms !X 315.079 ms !X 311.138 ms !X
Of the above 5 Pakistani hosts that are not pingable from SLAC, they all respond to telnet host 80 from SLAC or a home in Menlo Park near SLAC.
Beacons pingable from these 5 hosts
From PingER pingtable.pl looking from monitoring hosts in Pakistan and excluding Pakistani remote hosts (see for example from nukhimain.seecs.edu.pk):
- pinger.pern.edu.pk is not able to monitor Beacons in Australia and New Zealand (6), Canada (2), Europe (10 countries), China (2), Israel (1), Japan (2), South America (6 countries), South Asia (5 excluding Pakistan), SE Asia (6), US (2)
- It can monitor Beacons in about 20 countries in Africa (13 countries, but not South Africa), Byelorussia (1), Africa, Russia, Taiwan (1, Ukraine (1)
- pingerisl-fjwu.pern.edu.pk, pingerisl-qau.pern.edu.pk, nuisb.seecs.edu.pk have similar results
- On the other hand nukhimain.seecs.edu.pk appears to be in this mode since Jan 2, 2012, however previous to this it was able to ping most Beacons including pinger.slac.stanford.edu.
When did these hosts start being non pingable from SLAC
- pinger.pern.edu.pk and was pingable from SLAC until Dec 15, 2011,
- pingerisl-fjwu.pern.edu.pk, pingerisl-qau.per.edu.pk and nuisn.seecs.edu.pk were pingable until Dec 8 2011,
- nukhimain.seecs.edu.pk were pingable until Jan 2, 2012, this corresponds to what was seen pinging SLAC from this host
Is there a correlation with routes
- Prior to Dec 15, 2011 pinger.pern.edu.pk was routed to SLAC via the SJ, NY, Washington, Paris, Marseilles and KHI route seen above, after Dec15, 2011 it was routed via the transpac (Tokyo), apan and tein3 (Singapore) route also seen above.
- Prior to Dec 8, 2011 pingerisl.fjwu.pern.edu.pk, pingerisl-qau.pern.edu.pk and nuisb.seecs.edu.pk were routed to SLAC via PAIX (in Palo Alto), and Singtel, after Dec 8, 2011 they were routed via the transpac (Tokyo), apan and tein3 (Singapore) route seen above,
- Prior to Jan 1, 2012 nukhimain.seecs.edu.pk was routed via the transpac (Tokyo), apan and tein3 (Singapore) route
After Jan 2, 2011 it was routed apparently by the same route:
www-wanmon.slac.stanford.edu_to_nukhimain.seecs.edu.pk_2012_01_01 1 rtr-servcore1-serv01-webserv.slac.stanford.edu (134.79.197.130) 0.572 ms 0.614 ms 0.713 ms 2 rtr-core2-p2p-servcore1.slac.stanford.edu (134.79.252.162) 0.424 ms 0.425 ms 0.452 ms 3 rtr-border1-p2p-core2.slac.stanford.edu (134.79.252.137) 0.573 ms 0.743 ms 0.820 ms 4 slac-mr2-p2p-rtr-border1.slac.stanford.edu (192.68.191.245) 0.321 ms 0.316 ms 0.306 ms 5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.655 ms 0.648 ms 0.636 ms 6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.700 ms 0.687 ms 0.676 ms 7 * * * 8 tokyo-losa-tp2.transpac2.net (192.203.116.146) 122.961 ms 122.971 ms 123.022 ms 9 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 123.002 ms 122.985 ms 122.974 ms 10 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 191.983 ms 191.967 ms 191.955 ms 11 pk-pr-v4.bb.tein3.net (202.179.249.46) 273.936 ms 274.185 ms 274.226 ms 12 khi-nu.edu.pk (111.68.108.109) 274.874 ms !X 274.742 ms !X 274.730 ms !X
www-wanmon.slac.stanford.edu_to_nukhimain.seecs.edu.pk_2012_01_07 1 rtr-servcore1-serv01-webserv.slac.stanford.edu (134.79.197.130) 0.461 ms 0.526 ms 0.628 ms 2 rtr-core2-p2p-servcore1.slac.stanford.edu (134.79.252.162) 0.451 ms 0.502 ms 0.566 ms 3 rtr-border1-p2p-core2.slac.stanford.edu (134.79.252.137) 0.666 ms 0.775 ms 0.854 ms 4 slac-mr2-p2p-rtr-border1.slac.stanford.edu (192.68.191.245) 0.303 ms 0.290 ms 0.278 ms 5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.614 ms 0.670 ms 0.655 ms 6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.696 ms 0.695 ms 10.713 ms 7 * * * 8 tokyo-losa-tp2.transpac2.net (192.203.116.146) 122.962 ms 122.988 ms 123.073 ms 9 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 123.048 ms 123.046 ms 123.033 ms 10 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 191.881 ms 191.873 ms 191.839 ms 11 pk-pr-v4.bb.tein3.net (202.179.249.46) 274.194 ms 274.395 ms 274.468 ms
Can we identify where the blockage starts
Using mtr we can traceroute and then ping each of the routers along the route to see which routers respond. It is possible a router will pass pings but not respond to pings (or vice versa) so the results as to where a blockage may occur are not definitive. Mtr results from SLAC to pingerisl-fjwu.pern.edu indicate that all routers up through that at hop 11 respond to pings except for the one at hop 7 which was not pinged since it was not identifiable from the traceroute. Thus all routers up to that at hop 10 are passing pings through. We cannot tell if the router at hop 11 is passing pings since there is no information from the traceroute concerning the router at hop 12 and thus mtr cannot try and ping it.
Looking at the route from the pinger.pern.edu.pk to SLAC:
Executing exec(traceroute, -m 30 -q 3 -f 3, 134.79.104.80, 140) traceroute to 134.79.104.80 (134.79.104.80), 30 hops max, 140 byte packets 4 203.208.131.145 (203.208.131.145) 225.266 ms 227.588 ms 225.212 ms 5 203.208.152.205 (203.208.152.205) 231.704 ms 203.208.152.209 (203.208.152.209) 237.483 ms ge-4-0-6-0.sngc3-cr2.ix.singtel.com (203.208.182.153) 230.425 ms 6 203.208.171.186 (203.208.171.186) 295.895 ms 203.208.153.162 (203.208.153.162) 296.555 ms so-3-0-1-0.plapx-cr2.ix.singtel.com (203.208.151.246) 309.029 ms 7 203.208.171.154 (203.208.171.154) 315.002 ms ge-0-0-0-0.plapx-dr1.ix.singtel.com (203.208.149.1) 298.491 ms 203.208.171.154 (203.208.171.154) 316.112 ms 8 * * *
Looking at the route from the nukhimain.seecs.edu.pk to SLAC:
traceroute to 134.79.104.80 (134.79.104.80), 30 hops max, 140 byte packets 4 khi77.pie.net.pk (221.120.205.97) 5.244 ms 5.102 ms 5.057 ms 5 rwp44.pie.net.pk (221.120.251.21) 6.730 ms 7.252 ms rwp44.pie.net.pk (221.120.251.169) 4.934 ms 6 static-khidr-ni01-sw.pie.net.pk (202.125.128.161) 4.883 ms 4.842 ms 4.801 ms 7 * * * 8 te0-1-0-7.ccr21.mrs01.atlas.cogentco.com (154.54.39.129) 127.617 ms te0-2-0-7.ccr21.mrs01.atlas.cogentco.com (154.54.39.133) 127.971 ms te0-2-0-7.ccr22.mrs01.atlas.cogentco.com (154.54.39.201) 127.890 ms 9 te0-6-0-3.mpd22.par01.atlas.cogentco.com (154.54.59.241) 128.776 ms te0-0-0-3.mpd22.par01.atlas.cogentco.com (130.117.50.94) 128.720 ms te0-1-0-3.mpd22.par01.atlas.cogentco.com (130.117.50.98) 128.677 ms 10 * * te0-6-0-2.mpd21.jfk02.atlas.cogentco.com (154.54.46.109) 204.220 ms 11 te0-1-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.31.6) 211.972 ms * te0-0-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.6.50) 205.633 ms 12 gblx.jfk05.atlas.cogentco.com (154.54.11.138) 342.780 ms * gblx.jfk05.atlas.cogentco.com (154.54.11.138) 400.690 ms 13 HURRICANE-ELECTRIC-LLC-Ashburn.TenGigabitEthernet4-4.ar3.DCA3.gblx.net (64.214.121.170) 212.088 ms 213.845 ms 211.972 ms
Reverse traceroutes
It might be possible to learn more by comparing the forward and reverse traceroutes, The forward and reverse traceroutes betwen SLAC and pinger.pern.edu.pk are shown below. Comparing the router names and addresses for the forward and reverse paths between teh two pairs of hosts below it appears the forward and reverse routes in both cases are asymmetric.
The route from pinger.pern.edu.pk to pinger.slac.stanford.edu is shown below:
Executing exec(traceroute, -m 30 -q 3 -f 3, 134.79.104.80, 140) traceroute to 134.79.104.80 (134.79.104.80), 30 hops max, 140 byte packets 4 203.208.131.145 (203.208.131.145) 225.266 ms 227.588 ms 225.212 ms 5 203.208.152.205 (203.208.152.205) 231.704 ms 203.208.152.209 (203.208.152.209) 237.483 ms ge-4-0-6-0.sngc3-cr2.ix.singtel.com (203.208.182.153) 230.425 ms 6 203.208.171.186 (203.208.171.186) 295.895 ms 203.208.153.162 (203.208.153.162) 296.555 ms so-3-0-1-0.plapx-cr2.ix.singtel.com (203.208.151.246) 309.029 ms 7 203.208.171.154 (203.208.171.154) 315.002 ms ge-0-0-0-0.plapx-dr1.ix.singtel.com (203.208.149.1) 298.491 ms 203.208.171.154 (203.208.171.154) 316.112 ms 8 * * *
The route from pinger.slac.stanford.edu to pinger.pern.edu.pk is shown below:
26cottrell@pinger:~>traceroute pinger.pern.edu.pk traceroute to pinger.pern.edu.pk (111.68.96.158), 30 hops max, 38 byte packets 1 rtr-servcore1-serv01-iepm (134.79.104.66) 0.395 ms 0.243 ms 0.225 ms 2 rtr-core1-p2p-servcore1 (134.79.252.166) 0.536 ms 0.262 ms 0.241 ms 3 rtr-border2-p2p-core1 (134.79.252.141) 0.391 ms 0.310 ms 0.301 ms 4 slac-mr2-p2p-rtr-border2 (192.68.191.249) 0.232 ms 0.205 ms 0.217 ms 5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.671 ms 2.000 ms 0.620 ms 6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.773 ms 0.820 ms 0.717 ms 7 * * * 8 tokyo-losa-tp2.transpac2.net (192.203.116.146) 123.101 ms 123.010 ms 123.020 ms 9 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 123.151 ms 123.191 ms 123.157 ms 10 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 192.035 ms 192.054 ms 192.032 ms 11 pk-pr-v4.bb.tein3.net (202.179.249.46) 277.563 ms 276.972 ms 274.588 ms 12 * * *
The route from nukhimain.seecs.edu.pk to pinger.slac.stanford.edu is shown below:
traceroute to 134.79.104.80 (134.79.104.80), 30 hops max, 140 byte packets 4 khi77.pie.net.pk (221.120.205.97) 5.244 ms 5.102 ms 5.057 ms 5 rwp44.pie.net.pk (221.120.251.21) 6.730 ms 7.252 ms rwp44.pie.net.pk (221.120.251.169) 4.934 ms 6 static-khidr-ni01-sw.pie.net.pk (202.125.128.161) 4.883 ms 4.842 ms 4.801 ms 7 * * * 8 te0-1-0-7.ccr21.mrs01.atlas.cogentco.com (154.54.39.129) 127.617 ms te0-2-0-7.ccr21.mrs01.atlas.cogentco.com (154.54.39.133) 127.971 ms te0-2-0-7.ccr22.mrs01.atlas.cogentco.com (154.54.39.201) 127.890 ms 9 te0-6-0-3.mpd22.par01.atlas.cogentco.com (154.54.59.241) 128.776 ms te0-0-0-3.mpd22.par01.atlas.cogentco.com (130.117.50.94) 128.720 ms te0-1-0-3.mpd22.par01.atlas.cogentco.com (130.117.50.98) 128.677 ms 10 * * te0-6-0-2.mpd21.jfk02.atlas.cogentco.com (154.54.46.109) 204.220 ms 11 te0-1-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.31.6) 211.972 ms * te0-0-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.6.50) 205.633 ms 12 gblx.jfk05.atlas.cogentco.com (154.54.11.138) 342.780 ms * gblx.jfk05.atlas.cogentco.com (154.54.11.138) 400.690 ms 13 HURRICANE-ELECTRIC-LLC-Ashburn.TenGigabitEthernet4-4.ar3.DCA3.gblx.net (64.214.121.170) 212.088 ms 213.845 ms 211.972 ms
and the route from pinger.slac.stanford.edu to nukhimain.seecs.edu.pk is shown below
27cottrell@pinger:~>traceroute nukhimain.seecs.edu.pk traceroute to nukhimain.seecs.edu.pk (111.68.108.109), 30 hops max, 38 byte packets 1 rtr-servcore1-serv01-iepm (134.79.104.66) 0.647 ms 0.478 ms 1.330 ms 2 rtr-core1-p2p-servcore1 (134.79.252.166) 0.329 ms 0.251 ms 0.242 ms 3 rtr-border2-p2p-core1 (134.79.252.141) 0.390 ms 0.321 ms 0.299 ms 4 slac-mr2-p2p-rtr-border2 (192.68.191.249) 0.334 ms 3.347 ms 0.227 ms 5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.643 ms 0.617 ms 0.651 ms 6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.715 ms 0.698 ms 0.702 ms 7 * * * 8 tokyo-losa-tp2.transpac2.net (192.203.116.146) 122.851 ms 122.835 ms 122.814 ms 9 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 122.916 ms 122.895 ms 122.906 ms 10 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 191.802 ms 191.761 ms 191.762 ms 11 pk-pr-v4.bb.tein3.net (202.179.249.46) 274.450 ms 274.364 ms 274.304 ms 12 * * *
Detailed View for pingerisl-fjwu.pern.edu.pk
It is also observed that we are unable to telnet port 80, for these nodes, from SLAC, ES.net, SLAC visitor subnet and from a host at pinger2. However, we can gather data from home (Amber, Yee, Les and Antonio tried it).
The traceroute and pinging of nodes along the route using mtr are seen here. This is the same route seen by pinger.pern.edu.pk, pingerisl-qau.pern.edu.pk, nuisb.seecs.edu.pk, and nukhimain.seecs.edu.pk. It is seen the traceroute goes on transpac and apan via Tokyo and Singapore to get to Pakistan. On the other hand the route from SLAC to pingermtn.pern.edu.pk (which is pingable) is very different going on Level3 via New York, Washington, Paris, Marseilles to Karachi . When we compare the route(from mtr) from SLAC with the route from Antonio's or Yee's home below, they are very different.
---Original Message---
From: Antonio Ceseracciu [mailto:antony@slac.stanford.edu]
Sent: Thursday, January 05, 2012 2:10 PM
To: Cottrell, Les
Subject: traceroute pakistan
From Sonic in Bay Area
antony@toshi:~$ traceroute pingerisl-fjwu.pern.edu.pk traceroute to pingerisl-fjwu.pern.edu.pk (111.68.96.154),
30 hops max,
60 byte packets
1 192.168.11.2 (192.168.11.2) 10.077 ms 11.570 ms 12.018 ms
2 173-228-59-1.dsl.static.sonic.net (173.228.59.1) 48.164 ms 48.559 ms 48.955 ms
3 gig1-28.cr1.lsatca11.sonic.net (70.36.243.69) 49.432 ms 49.830 ms
50.213 ms
4 0.xe-7-1-0.gw.pao1.sonic.net (69.12.211.5) 113.319 ms 113.717 ms
114.113 ms
5 0.xe-6-1-0.gw2.200p-sf.sonic.net (64.142.0.109) 114.498 ms 115.353 ms 115.781 ms
6 as0.gw.200p-sf.sonic.net (208.106.96.249) 117.470 ms 35.588 ms
35.887 ms
7 xe-10-1-0.bar2.SanFrancisco1.Level3.net (4.53.134.9) 37.707 ms
39.211 ms 40.061 ms
8 ae-6-6.ebr2.SanJose1.Level3.net (4.69.140.154) 40.751 ms 54.165 ms
54.555 ms
9 ae-72-72.csw2.SanJose1.Level3.net (4.69.153.22) 54.954 ms ae-82-82.csw3.SanJose1.Level3.net
(4.69.153.26) 55.353 ms ae-92-92.csw4.SanJose1.Level3.net (4.69.153.30) 55.753 ms
10 ae-61-61.ebr1.SanJose1.Level3.net (4.69.153.1) 56.151 ms ae-81-81.ebr1.SanJose1.Level3.net
(4.69.153.9) 56.541 ms ae-91-91.ebr1.SanJose1.Level3.net (4.69.153.13) 56.943 ms
11 ae-2-2.ebr2.NewYork1.Level3.net (4.69.135.186) 117.103 ms 117.531 ms 117.926 ms
12 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 105.207 ms 113.022 ms 103.902 ms
13 ae-1-100.ebr1.NewYork2.Level3.net (4.69.135.253) 106.794 ms
107.641 ms 108.051 ms
14 ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 120.353 ms
120.750 ms 121.147 ms
15 ae-42-42.ebr2.Paris1.Level3.net (4.69.137.53) 195.417 ms
198.707 ms ae-41-41.ebr2.Paris1.Level3.net (4.69.137.49) 199.098 ms
16 ae-23-23.ebr1.Paris1.Level3.net (4.69.143.125) 199.512 ms ae-24-24.ebr1.Paris1.Level3.net (4.69.143.129) 188.451 ms 202.645 ms
17 ae-1-7.bar1.Marseille1.Level3.net (4.69.143.237) 203.516 ms
204.369 ms 204.770 ms
18 ae-2-3.edge2.Marseille1.Level3.net (4.69.143.250) 199.907 ms
203.548 ms 203.940 ms
19 213.242.115.2 (213.242.115.2) 313.558 ms 213.242.115.6
(213.242.115.6) 314.310 ms 213.242.115.2 (213.242.115.2) 314.652 ms
20 static-10GE-KHI494-P01-KHI494-SWA.pie.net.pk (202.125.128.174)
316.083 ms 314.656 ms 314.982 ms
21 rwp44.pie.net.pk (221.120.251.22) 311.968 ms 314.144 ms 312.754 ms
22 rwp44.pie.net.pk (221.120.236.190) 341.530 ms 343.480 ms 343.844 ms
23 * * *
24 pingerisl-fjwu.pern.edu.pk (111.68.96.154) 347.039 ms !X 343.632 ms !X 341.324 ms !X
antony@toshi:~$ lynx pingerisl-fjwu.pern.edu.pk Looking up 'pingerisl-fjwu.pern.edu.pk' first
~Antonio
---Original Message---
From: Li, Yee Ting
Sent: Thursday, January 05, 2012 2:17 PM
To: Cottrell, Les
Cc: Ceseracciu, Antonio
Subject: host at PK
from comast in the bay area
$ traceroute pingerisl-fjwu.pern.edu.pk
traceroute to pingerisl-fjwu.pern.edu.pk (111.68.96.154), 30 hops max, 60 byte packets
1 <redacted>
2 <redacted>
3 te-7-6-ur01.sanmateo.ca.sfba.comcast.net (68.87.197.225) 23.138 ms 23.362 ms 23.509 ms
4 te-0-6-0-0-ar01.sfsutro.ca.sfba.comcast.net (68.87.192.222) 24.748 ms 25.071 ms 25.211 ms
5 pos-3-0-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.93) 26.077 ms 26.239 ms 27.023 ms
6 pos-0-1-0-0-pe01.529bryant.ca.ibone.comcast.net (68.86.87.2) 27.278 ms 20.610 ms 20.714 ms
7 te7-7.mpd01.sjc04.atlas.cogentco.com (154.54.11.109) 29.169 ms 21.322 ms 21.654 ms
8 te0-1-0-7.mpd22.sfo01.atlas.cogentco.com (154.54.5.57) 21.860 ms 20.825 ms 20.672 ms
9 te0-2-0-2.mpd21.mci01.atlas.cogentco.com (154.54.6.166) 63.381 ms
te0-1-0-3.mpd22.mci01.atlas.cogentco.com (154.54.24.106) 62.167 ms
te0-1-0-3.mpd21.mci01.atlas.cogentco.com (154.54.2.209) 62.760 ms
10 te0-2-0-3.mpd22.ord01.atlas.cogentco.com (154.54.6.254) 84.217 ms
te0-0-0-3.mpd22.ord01.atlas.cogentco.com (154.54.25.78) 83.626 ms
te0-4-0-3.mpd22.ord01.atlas.cogentco.com (154.54.30.177) 84.090 ms
11 te0-1-0-6.ccr21.bos01.atlas.cogentco.com (154.54.43.190) 177.467 ms
te0-1-0-1.ccr21.bos01.atlas.cogentco.com (154.54.24.53) 181.052 ms
te0-0-0-5.ccr21.bos01.atlas.cogentco.com (154.54.28.114) 167.555 ms
12 te0-1-0-2.mpd21.lon13.atlas.cogentco.com (154.54.30.130) 172.178 ms 172.408 ms 172.871 ms
13 te0-2-0-0.mpd21.par01.atlas.cogentco.com (130.117.0.110) 171.294 ms
te0-5-0-3.ccr21.par01.atlas.cogentco.com (154.54.37.178) 172.633 ms
te0-0-0-0.ccr21.par01.atlas.cogentco.com (130.117.2.161) 173.066 ms
14 te0-3-0-5.ccr21.mrs01.atlas.cogentco.com (154.54.59.238) 185.572 ms
te0-4-0-5.ccr21.mrs01.atlas.cogentco.com (130.117.2.213) 181.096 ms
te0-3-0-5.ccr21.mrs01.atlas.cogentco.com (154.54.59.238) 182.664 ms
15 te0-0-0-3.mag21.mrs01.atlas.cogentco.com (154.54.39.130) 183.391 ms 183.144 ms 183.550 ms
16 149.6.154.238 (149.6.154.238) 295.202 ms 294.621 ms 294.817 ms
17 static-10GE-KHI494-P01-KHI494-SWA.pie.net.pk (202.125.128.174) 293.536 ms 299.366 ms 299.756 ms
18 rwp44.pie.net.pk (221.120.251.170) 300.469 ms 300.039 ms 300.255 ms
19 rwp44.pie.net.pk (221.120.236.190) 329.049 ms 316.954 ms 321.649 ms
20 172.31.240.14 (172.31.240.14) 321.954 ms 322.592 ms 322.302 ms
21 111.68.96.154.pern.pk (111.68.96.154) 322.132 ms !X 324.087 ms !X 323.848 ms !X
from SLAC internal (134.79/16):
traceroute pingerisl-fjwu.pern.edu.pk
traceroute to pingerisl-fjwu.pern.edu.pk (111.68.96.154), 30 hops max, 38 byte packets
1 rtr-servcore1-serv01-iepm (134.79.104.66) 0.626 ms 0.572 ms 0.223 ms
2 rtr-core1-p2p-servcore1 (134.79.252.166) 0.351 ms 0.251 ms 0.247 ms
3 rtr-border1-p2p-core1 (134.79.252.133) 0.593 ms 0.323 ms 0.304 ms
4 slac-mr2-p2p-rtr-border1 (192.68.191.245) 12.633 ms 0.233 ms 0.210 ms
5 sunnsdn2-ip-slacmr2.es.net (134.55.217.2) 0.657 ms 0.629 ms 0.617 ms
6 sunncr1-sunnsdn2.es.net (134.55.209.98) 0.761 ms 0.720 ms 0.708 ms
7 * * *
8 tokyo-losa-tp2.transpac2.net (192.203.116.146) 123.055 ms 123.034 ms 123.029 ms
9 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 123.142 ms 123.342 ms 123.127 ms
10 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 191.994 ms 192.005 ms 192.021 ms
11 pk-pr-v4.bb.tein3.net (202.179.249.46) 274.132 ms 274.268 ms 274.115 ms
12 * * *
13 * * *
...
from Internet2:
$ telnet pingerisl-fjwu.pern.edu.pk 8080 Trying 111.68.96.154...
telnet: connect to address 111.68.96.154: Connection timed out
telnet: Unable to connect to remote host:
Connection timed out
[ytl@packrat ~]$ traceroute pingerisl-fjwu.pern.edu.pk traceroute to
pingerisl-fjwu.pern.edu.pk (111.68.96.154), 30 hops max, 38 byte packets
1 prodserv-non-rtr.mgmt.internet2.edu (10.165.5.1) 61.406 ms 0.308 ms 0.291 ms
2 192.122.200.73 (192.122.200.73) 0.601 ms 3.688 ms 0.467 ms
3 xe-0-1-0x56.aa3.mich.net (198.108.22.137) 0.205 ms 0.201 ms 0.172 ms
4 xe-0-0-0x76.wsu5.mich.net (198.108.23.9) 1.809 ms 1.799 ms 1.785 ms
5 v0x1004.rtr.wash.net.internet2.edu (192.122.183.10) 13.674 ms 26.468 ms 13.714 ms
6 ae-8.10.rtr.atla.net.internet2.edu (64.57.28.6) 27.121 ms 27.195 ms 27.148 ms
7 xe-1-0-0.0.rtr.hous.net.internet2.edu (64.57.28.112) 50.569 ms 50.502 ms 50.514 ms
8 * ge-6-1-0.0.rtr.losa.net.internet2.edu (64.57.28.96) 583.960 ms 588.745 ms
9 transpac-1-lo-jmb-702.lsanca.pacificwave.net (207.231.240.136) 82.635 ms 82.665 ms 103.029 ms
10 tokyo-losa-tp2.transpac2.net (192.203.116.146) 196.544 ms 196.579 ms 196.611 ms
11 kote-dc-gm1-xe2-2-1-4005.jp.apan.net (203.181.248.249) 196.779 ms 196.681 ms 196.641 ms
12 sg-xe-01-v4.bb.tein3.net (202.179.249.77) 265.546 ms 265.526 ms 265.563 ms
13 pk-pr-v4.bb.tein3.net (202.179.249.46) 347.915 ms 347.886 ms 347.685 ms
14 * * *
Notes:
- access from SLAC's visitor network is blocked (from ES.net, same path as that from SLAC internal)
-- infer ACL/Firewall in path allowing SLAC
- access from COMCAST and SONIC and SLAC internal open for port 80 and 8080.
-- infer restrictive ACL for SLAC and possibly others?
- web access to port 80 from COMCAST and SONIC result in 503 forbidden
- web access from SLAC to port 80 times out
-- infer path from INTERNET2, ESNET and SLAC is restricted
~Yee.
Pinging pingerisl-fjwu.pern.edu.pk from around the world
Using reflector.cgi we pinged pingerisl-fjwu.pern.edu.pk from PingER landmarks (hosts that can be requested via the web to ping a target) around the world, we found 32 landmarks were able to ping pingerisl-fjwu.pern.edu.pk. Of these 19 were Pakistani landmarks. The remainder were:
Jordan Landmark(2)=http://pinger.sesame.org.jo/cgi-bin/traceroute.pl?target=111.68.96.154&function=ping,
Client=134.79.18.134, ability=1, 5 packets transmitted, received, 0% packet loss,
rtt min/avg/max = 266.404/266.579/267.031<br>
Brazil Landmark(2)=http://pinger.acmesecurity.org/cgi-bin/traceroute.pl?target=111.68.96.154&function=ping,
Client=134.79.18.134, ability=1, 5 packets transmitted, 5 received, 0% packet loss, rtt min/avg/max
=391.204/392.214/393.374<br>
Brazil Landmark(2)=http://pinger.acmesecurity.org/cgi-bin/traceroute.pl?target=111.68.96.154&function=ping,
Client=134.79.18.134, ability=1, 5 packets transmitted, 5 received, 0% packet loss, rtt min/avg/max =
391.204/392.214/393.374<br>
Texas, USA Landmark(2)=[https://192.124.228.118/gui/reverse_traceroute.cgi?target=111.68.96.154&function=ping],
Client=134.79.18.134, ability=1, 5 packets transmitted, 5 received, 0% packet loss, rtt min/avg/max =
265.746/266.008/266.624<br>
Texas, USA Landmark(2)=https://192.124.227.150/gui/reverse_traceroute.cgi?target=111.68.96.154&function=ping,
Client=134.79.18.134, ability=1, 5 packets transmitted, 5 received, 0% packet loss, rtt min/avg/max =
259.381/259.576/259.768<br>
Washington, USA Landmark(2)=http://138.238.250.157:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10
packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 239.755/239.8941/240.079<br>
California, USA Landmark(2)=http://198.175.112.105:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10
packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 296.599/300.0357/306.247<br>
Taiwan Landmark(2)=http://140.112.42.159:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10 packets transmitted, 10
received, 0% packet loss, rtt min/avg/max = 154.369/154.6627/155.060<br>
Washington, USA Landmark(2)=http://134.121.64.4:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10
packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 307.007/307.6455/309.486<br>
Washington, USA Landmark(2)=http://134.121.64.7:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10
packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 306.854/307.1627/308.064<br>
Palo Alto, CA, USA Landmark(2)=http://204.123.28.55:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10
packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 291.785/292.1598/292.783<br>
Taiwan Landmark(2)=http://140.112.107.82:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10 packets transmitted, 10
received, 0% packet loss, rtt min/avg/max = 153.097/157.6547/167.727<br>
Brazil Landmark(2)=http://200.19.159.34:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10 packets transmitted, 10
received, 0% packet loss, rtt min/avg/max = 379.993/380.1396/380.758<br>
New South Wales, Australia Landmark(2)=http://220.245.140.197:3355, Client=134.79.18.134, target=111.68.96.154, ability=1, 10
packets transmitted, 10 received, 0% packet loss, rtt min/avg/max = 515.532/516.4197/517.379<br>
Conclusion :
Some network provider between SLAC and pingerisl-fjwu.pern.edu.pk is blocking the access to few Pakistani nodes.
Reflector.cgi to pinger.pern.edu.pk
=======================================================
Further review by using reflector.cgi to ping pingerisl-fjwu.pern.edu.pk shows it is only pingable from 19 .pk (Pakistani) and 1 .jo (Jordan) hosts.
SOMEONE needs to work with the admins for pingerisl-qau.pern.edu.pk and pinger.pern.edu.pk or their network connections to see if they really are blocking pings from some IP addresses or regions.
In addition from previous emails:
SOMEONE needs to look at why http://pingermtn.pern.edu.pk/cgi-bin/traceroute.pl?function=ping&target=www-wanmon.slac.stanford.edu is not responding, it appears the web server or CGI script may be down.
=====================================================
----Original Message----
From: Cottrell, Les
Sent: Friday, December 30, 2011 12:48 PM
To: Amber Zeb (amber.zeb@gmail.com)
Cc: 'joun.muhammad@seecs.edu.pk'; anjum.naveed@seecs.edu.pk; 'kashif.sattar@seecs.edu.pk'
Subject: RE: Latest Update and Progress of Monitoring Status 29 December-2011 ( 16:40 PM ) (49/55)
Looking at further, even though pingerisl-fjwu.pern.edu.pk is not pingable from SLAC, I am now able to gather data using [http://pingerisl-fjwu.pern.edu.pk/cgi-bin/ping_data.pl?in_form=1&begin_hour=00&begin_min=00&begin_sec=00&begin_day=30&begin_month=12
&begin_year=2011&begin_offset=&begin_point=y
&end_hour=23&end_min=59&end_sec=00&end_day=31&end_month=12&end_year=2011&end_offset=&end_point=y]
However, using http://pingermtn.pern.edu.pk/cgi-bin/ping_data.pl? I get Chrome could not connect to pingermtn.pern.edu.pk so it looks as if the web server is down. Pinging it via http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pingermtn.pern.edu.pk&function=ping I get Executing exec(ping, -c 5 -s 56, 121.52.158.210) PING 121.52.158.210 (121.52.158.210) 56(84) bytes of data.
From 202.125.139.65 icmp_seq=1 Time to live exceeded From 202.125.139.65 icmp_seq=2 Time to live exceeded From 202.125.139.65 icmp_seq=3 Time to live exceeded From 202.125.139.65 icmp_seq=4 Time to live exceeded From 202.125.139.65 icmp_seq=5 Time to live exceeded
Also using http://pingerisl-qau.pern.edu.pk/cgi-bin/ping_data.pl? I get Google Chrome could not connect to pingerisl-qau.pern.edu.pk and am unable to ping it using http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pingerisl-fjwu.pern.edu.pk&function=ping
==================================================
----Original Message----
From: Cottrell, Les
Sent: Friday, December 30, 2011 12:31 PM
To: Amber Zeb (amber.zeb@gmail.com)
Cc: 'joun.muhammad@seecs.edu.pk'; anjum.naveed@seecs.edu.pk; 'kashif.sattar@seecs.edu.pk'
Subject: FW: Latest Update and Progress of Monitoring Status 29 December-2011 ( 16:40 PM ) (49/55)
Umar, Anjum and I met this morning via Skype. Anjum forwarded me a progress report from Joun for December 29, 2011 concerning the Pakistani monitoring hosts.
It identified
19. pingerqta.pern.edu.pk <http://pingerqta.pern.edu.pk/> (Partially down power issue will be up soon)
I looked at http://www-iepm.slac.stanford.edu/monitoring/checkdata/ after modifying checkdata_gif.pl (this is the script that reports on our success in gathering data from the monitoring hosts each day) to identify PERN hosts with problems and came up with:
Pakistani monitors: good=33, partial_data=7, no_data=15, total=55, problems=22, PERN monitors: good=9, partial_data=1, no_data=4, total=14, problems=5, no_data=pingerisl-fjwu.pern.edu.pk, no_data=pinger.pern.edu.pk, partial_data=pingerqta.pern.edu.pk, no_data=pingermtn.pern.edu.pk, no_data=pingerisl-qau.pern.edu.pk,
So we agree about pingerqta.pern.edu.pk
However we differ on pingerisl-fjwu.pern.edu.pk (node 32 in Joun's list), pingermtn.pern.edu.pk (43 in Joun's list), pingerisl-qau.pern.edu.pk (33 in Joun's list), pinger.pern.edu.pk (22 in Joun's list).
Looking in more detail:
pingermtn.pern.edu.pk is pingable, however http://pingermtn.pern.edu.pk/cgi-bin/traceroute.pl?function=ping&target=www-wanmon.slac.stanford.edu fails, it looks like the web server or cgi-script is down. SOMEONE SHOULD LOOK AT THIS
I am unable to ping the following from SLAC pingerisl-fjwu.pern.edu.pk (using http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pingerisl-fjwu.pern.edu.pk&function=ping) or pingerisl-qau.pern.edu.pk (using http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pingerisl-qau.pern.edu.pk&function=ping) or pinger.pern.edu.pk (http://www-wanmon.slac.stanford.edu/cgi-bin/nph-traceroute.pl?target=pinger.pern.edu.pk&function=ping) from SLAC at 12:11pm PST 12/30/2011.
However I am able to ping (using http://maggie1.seecs.edu.pk/cgi-bin/traceroute.pl?target=pinger.pern.edu.pk+&function=ping) pinger.pern.edu.pk, pingerisl-fjwu.pern.edu.pk from SEECS, SOMEONE SHOULD LOOK AT THIS
I can't ping pingerisl-qau.pern.edu.pk from SEECS
==================================================================
----Original Message----
From: Anjum Naveed anjum.naveed@seecs.edu.pk
Sent: Friday, December 30, 2011 9:55 AM
To: Kashif sattar; Cottrell, Les
Cc: Amber Ze
Subject: Re: Latest Update and Progress of Monitoring Status 29 December-2011 ( 16:40 PM ) (49/55)
Kashif,
Please add Les in this email. his email address is cottrell@slac.stanford.edu
regards,
Anjum
On 29-Dec-11, at 4:36 PM, Kashif sattar wrote:
======================================================================
------ Forwarded message --------
From: Joun Muhammad <joun.muhammad@seecs.edu.pk>
Date: Thu, Dec 29, 2011 at 4:31 PM
Subject: Latest Update and Progress of Monitoring Status 29 December-2011 ( 16:40 PM ) (49/55)
To: muhammad zeeshan <muhammad.zeeshan@seecs.edu.pk>, Kashif sattar <kashif.sattar@seecs.edu.pk>
Progress Report ( 29 December 2011)
Continuous Monitoring
When we first checked in morning 06 nodes were faulty.
- pinger.ustb.edu.pk <http://pinger.ustb.edu.pk/> (Pinging by other IP nd not showing data , Called Network issue,Troubleshooting in progress will be up soon )
- pinger.giki.edu.pk <http://pinger.giki.edu.pk/> ( Down ,Due to Network issues it is off, Will be up soon)
- kinnaird.seecs.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.KINNAIRD.SEECS.EDU&monalias=EDU.SLAC.STANFORD.N3> (Down,Called Due to Hollidsya, will be up soon)
- pinger.uaar.edu.pk <http://pinger.uaar.edu.pk/> (Down,Called network issue, will be up soon)
- airuniversity.seecs.edu.pk <http://airuniversity.seecs.edu.pk/> (Down,System problem, will be up soon)
#hu.seecs.edu.pk <http://hu.seecs.edu.pk/> (Down,Called system issue , will be up soon)
Monitoring Status 29 December- 2011 ( 16:40 PM )
--------------------------------------------------
Working Nodes: 49 out of 55 Nodes
A: Nodes which are up and working fine :- (49)
1. maggie1.seecs.edu.pk <http://maggie1.seecs.edu.pk/>
2. pinger-itc.pu.edu.pk <http://pinger-itc.pu.edu.pk/>
3. pinger-ncp.ncp.edu.pk <http://pinger-ncp.ncp.edu.pk/>
4. pinger.aiou.edu.pk <http://pinger.aiou.edu.pk/>
5. pinger.cemb.edu.pk <http://pinger.cemb.edu.pk/>
6. pinger.comsats.edu.pk <http://pinger.comsats.edu.pk/>
7. pinger.uet.edu.pk <http://pinger.uet.edu.pk/>
8. pinger.lcwu.edu.pk <http://pinger.lcwu.edu.pk/>
9. pingerjms.pern.edu.pk <http://pingerjms.pern.edu.pk/>
10 pingerkhi.pern.edu.pk <http://pingerkhi.pern.edu.pk/>
11. pinger.isra.edu.pk <http://pinger.isra.edu.pk/>
12. pinger.kohat.edu.pk <http://pinger.kohat.edu.pk/>
13. pingerlhr.pern.edu.pk <http://goog_910545261/>
14. pingerfsbd.pern.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.PERNFSBDPOP.EDU.N1&monalias=EDU.SLAC.STANFORD.N3>
15.www.upesh.edu.pk <http://www.upesh.edu.pk/>
16. maggie2.seecs.edu.pk <http://maggie2.seecs.edu.pk/>
17. pinger.nwfpuet.edu.pk <http://pinger.nwfpuet.edu.pk/> NEW IP 121.52.147.71 <http://121.52.147.71/>
18. npm.neduet.edu.pk <http://npm.neduet.edu.pk/>
19. pingerqta.pern.edu.pk <http://pingerqta.pern.edu.pk/> (Partially down power issue will be up soon)
20. pinger.nca.edu.pk <http://pinger.nca.edu.pk/>
21. pinger.vu.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.VU.EDU&monalias=EDU.SLAC.STANFORD.N3>
22. pinger.pern.edu.pk <http://pinger.pern.edu.pk/> NEW IP 111.68.96.158 <http://111.68.96.158/>
23. sbkwu.seecs.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.SBKWU.SEECS.EDU&monalias=EDU.SLAC.STANFORD.N3> NEW IP 121.52.157.25 <http://121.52.157.25/> (Partially down will be up soon)
24. nuisb.seecs.edu.pk <http://nuisb.seecs.edu.pk/>
25. vle.iiu.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.IIU.EDU.N2&monalias=EDU.SLAC.STANFORD.N3>
26.pingerpwr.pern.edu.pk <http://pingerpwr.pern.edu.pk/> (Partially down power issue will be up soon)
27. pinger.iba-suk.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.PINGER.IBA-SUK.EDU&monalias=EDU.SLAC.STANFORD.N3> NEW IP 121.52.155.11 <http://121.52.155.11/>
28. duhs.seecs.edu.pk <http://duhs.seecs.edu.pk/>
29.quest.seecs.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.QUEST.SEECS.EDU&monalias=EDU.SLAC.STANFORD.N3> NEW IP 121.52.155.122
30.ns1.pieas.edu.pk <http://ns1.pieas.edu.pk/>
31.pinger.numl.edu.pk <http://pinger.numl.edu.pk/>
32. pingerisl-fjwu.pern.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.PINGERISL-FJWU.PERN.EDU&monalias=EDU.SLAC.STANFORD.N3>
33. pingerisl-qau.pern.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.PINGERISL-QAU.PERN.EDU&monalias=EDU.SLAC.STANFORD.N3>
34.cae.seecs.edu.pk <http://cae.seecs.edu.pk/>
35.pingerkhi-cpsp.pern.edu.pk <http://pingerkhi-cpsp.pern.edu.pk/>
36.pingerkhi-uok.pern.edu <http://goog_742015447/> .pk <http://.pk/>
37.pinger.uob.edu.pk <http://pinger.uob.edu.pk/> NEW IP 121.52.157.112 <http://121.52.157.112/>
38. nukhimain.seecs.edu.pk <http://nukhimain.seecs.edu.pk/> (Partially down power issue will be up soon)
39.monitor.seecs.edu.pk <http://monitor.niit.edu.pk/>
40.pingerlhr-pu.pern.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.PINGERLHR-PU.PERN.EDU&monalias=EDU.SLAC.STANFORD.N3>
41.sau.seecs.edu.pk <http://sau.seecs.edu.pk/>
42.pinger.usindh.edu.pk <http://pinger.usindh.edu.pk/>
43.pingermtn.pern.edu.pk <http://pingermtn.pern.edu.pk/>
44.pinger.uettaxila.edu.pk <http://pinger.uettaxila.edu.pk/>
45.aup.seecs.edu.pk <http://aup.seecs.edu.pk/> NEW IP 121.52.146.67 <http://121.52.146.67/>
46.pingerlhr-gcu.pern.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.PINGERLHR-GCU.PERN.EDU&monalias=EDU.SLAC.STANFORD.N3>
47.buitms.seecs.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.BUITMS.SEECS.EDU&monalias=EDU.SLAC.STANFORD.N3> NEW IP 121.52.157.190 <http://121.52.157.190/>
48.lse.seecs.edu.pk <http://lse.seecs.edu.pk/>
49.pinger.lhr.nu.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.NU.EDU.N2&monalias=EDU.SLAC.STANFORD.N3>
Nodes Up but Under Trouble Shooting :- (1)
1)pinger.ustb.edu.pk <http://pinger.ustb.edu.pk/>
01-August-2011 Pinging by another IP but data not shown, Network Issue, Again Called today but call was not attended.
03-August-2011 Same status
08-August-2011 Same status
10-August-2011 Called Network
issue,Troubleshooting in progress
11-August-2011 Same status
16-August-2011 Same status
05-Octuber-2011 issue will be resolve in a week
15-NOv-2011 still trouble shooting in progress
Nodes Down :- (5)
- pinger.giki.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.GIKI.EDU.N1&monalias=EDU.SLAC.STANFORD.N3>
- pinger.uaar.edu.pk <http://pinger.uaar.edu.pk/>
- kinnaird.seecs.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.KINNAIRD.SEECS.EDU&monalias=EDU.SLAC.STANFORD.N3>
- hu.seecs.edu.pk <http://www.slac.stanford.edu/cgi-wrap/dbprac.pl?alias=PK.HU.EDU.N2&monalias=EDU.SLAC.STANFORD.N3>
5)airuniversity.seecs.edu.pk <http://airuniversity.seecs.edu.pk/>
08-August-2011 Down
16-August-2011 Down
08-September-2011 Down will be up soon
31-oct-2011 Down network issue will be resolve soon
27-Oct-2011 Pinging but not fetching data will be up soon
15-Nov-2011 Pinging but not fetching data will be up soon 26-Dec2011Down Due to Hollidays
14-Dec-2011Down system issue trouble shooting in progress will be up soon 26Dec2011Down Network issue
19Dec-2011 pinging but not fetching data trouble shooting in progress
26Dec2011 Down system issue will be up soon
Regards
JOUN MUHAMMAD
Response March/April 2012
Three nodes had IP address fixed. HEC Islamabad, Multan, Fatima Jenna university in Rawalpindi (near old NIIT).
FSBD POP have high unreachability values, which is not acceptable. They are looking into it. Backhaul network is currently leased from PTCL however in 3-4 months they will replace it with their own network. There would be no commercial traffic on it. As a result it is expected that RTT and losses will improve drastically. So next 6 months are important for observing the network performance.
Status May 2012
- Les looked at which Pakistani monitoring hosts SLAC is unable to gather data from since the start of May. They are as follows:
- hu.seecs.edu.pk aka PK.HU.EDU.N2 does not appear as a monitoring host in SEECS pingtable.pl. Also SEECS pingtable.pl has no data this month from AIOU to hu.seecs
- lse.seecs.edu.pk aka PK.LSE.EDU.N3 does not appear as a monitoring host in SEECS pingtable.pl. Also SEECS pingtable.pl has no data this month from AIOU to lse
- pinger-itc.pu.edu.pk aka PK.PU.EDU.N2 does not appear in the SEECS pingtable.pl as a monitoring host
- pinger.giki.edu.pk aka PK.GIKI.EDU.N1 does not appear as a monitoring host in SEECS pingtable.pl
- pinger.uaar.edu.pk aka PK.UAAR.EDU.N1 does not appear as a monitoring host in SEECS pingtable.pl
- pinger.ustb.edu.pk aka PK.USTB.EDU.N2 does not appear as a monitoring host in SEECS pingtable.pl
- sbkwu.seecs.edu.pk aka PK.SBKWU.SEECS.EDU does not appear as a monitoring host in SEECS pingtable.pl
- Should they be designated as Monitoring hosts?
- Amber reports: Looking at this weeks status report on wiki, the list of the nodes which are not monitoring nodes in SEECS pingtable but are monitoring nodes at SLAC can be due to the fact that these nodes are the usual problematic nodes since months. It might be possible that SEECS team (who manage SEECS pingtable) have made these nodes as remote nodes to avoid hassle. However, I shall confirm this from Kashif tomorrow and will update you on this. If this turns out to be true, I shall change these nodes to remote nodes in SLAC pingtable as well.