[Sysops-list] MOS-Vianet routing
Om Bikram Thapa
om at vianet.com.np
Wed Mar 8 15:54:45 NPT 2006
Whenever MOS npIX link goes down, it becomes unreachable from VSAT
path as well.
Here is the trace to www.mos.com.np from Vianet:
------------------------------------------------------------------
[om at dns1 om]$ /usr/sbin/traceroute www.mos.com.np
traceroute to mos.com.np (202.52.255.35), 30 hops max, 38 byte packets
1 int-ujeli (202.51.76.1) 0.208 ms 0.180 ms 0.151 ms
2 fa-0-0-iris (202.51.76.17) 0.619 ms 0.581 ms 0.639 ms
3 fa-0-1-cornea (202.51.76.238) 9.650 ms 14.821 ms 13.692 ms
4 202.51.95.241 (202.51.95.241) 10.871 ms 8.109 ms 16.224 ms
5 202.161.129.13 (202.161.129.13) 548.628 ms 577.884 ms 582.991 ms
6 202.161.130.1 (202.161.130.1) 562.909 ms 581.698 ms 570.579 ms
7 202.161.130.33 (202.161.130.33) 620.815 ms 825.923 ms *
8 fe5-5.cr01.sjo01.pccwbtn.net (63.218.7.121) 694.962 ms 682.436 ms
811.621 ms
9 corporateaccess.ge5-6.br01.hkg04.pccwbtn.net (63.218.115.2) 965.618
ms 925.112 ms 912.910 ms
10 203.91.129.142 (203.91.129.142) 925.011 ms 999.583 ms 927.750 ms
11 * * *
12 * * *
13 * * *
14 *
-----------------------------------------------------------------
Shekhar, could you please look into this issue?
Thanks,
Om.
On Wed, 8 Mar 2006, Ritesh Raj Joshi wrote:
> HI guys,
>
> Can't access some MOS customer sites via Vianet.
> Seems like some routing issue at npIX as the traffic is going via VSAT.
>
> Appreciate if the concerned ISPs can work together to resolve the matter
> at the earliest.
>
> Thanks,
>
> Ritesh
>
> C:\Documents and Settings\Ritesh>tracert www.nabilbank.com.np
>
> Tracing route to nabilbank.com.np [202.52.237.134]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms 192.168.111.1
> 2 11 ms 5 ms 7 ms 202.51.75.1
> 3 5 ms 4 ms 4 ms 192.168.233.1
> 4 4 ms 4 ms 4 ms int-dobhan.vianet.com.np [202.51.76.25]
> 5 6 ms 5 ms 5 ms fa-0-0-iris.vianet.com.np [202.51.76.17]
> 6 16 ms 29 ms 13 ms fa-0-1-cornea.vianet.com.np [202.51.76.238]
> 7 11 ms 8 ms 7 ms 202.51.95.241
> 8 579 ms 617 ms 574 ms 202.161.129.13
> 9 576 ms 628 ms 602 ms 202.161.130.1
> 10 648 ms 641 ms 629 ms 202.161.130.41
> 11 621 ms 707 ms 653 ms ge-0-1-0.405.ar1.SJC2.gblx.net
> [207.138.144.185]
>
> 12 634 ms 623 ms 652 ms so5-0-0-2488M.ar2.PAO2.gblx.net
> [67.17.93.109]
> 13 620 ms 621 ms 619 ms singtel-1.ar2.PAO2.gblx.net [208.50.13.166]
> 14 666 ms 851 ms 682 ms ge-3-0-0.plapx-cr3.ix.singtel.com
> [203.208.168.1
> 33]
> 15 852 ms 624 ms 868 ms p1-1.sngtp-cr3.ix.singtel.com
> [203.208.182.113]
>
> 16 873 ms 888 ms 876 ms p1-1.sngtp-cr3.ix.singtel.com
> [203.208.182.113]
>
> 17 833 ms 966 ms 831 ms p0-0-0.sngbt-ar2.ix.singtel.com
> [202.160.250.158
> ]
> 18 870 ms 892 ms 901 ms 203.208.145.38
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.
>
>
>
>
>
>
>
> _______________________________________________
> Sysops-list mailing list
> Sysops-list at npix.net.np
> http://lists.npix.net.np/mailman/listinfo/sysops-list
>
More information about the Sysops-list
mailing list