Closed Bug 568192 Opened 14 years ago Closed 14 years ago

40% packet loss at MOZILLA-2.GigabitEthernet4-15.ar2.SNV2.gblx.net

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
All
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: nthomas, Assigned: dmoore)

Details

This is from mtr between my laptop and the MPT VPN jumphost:
Host                                                 Loss%   Snt Drop    Avg
 1. 192.168.1.1                                        0.2%   894    2    1.3
 2. lo0.internet.ivpn.pe14.telstraclear.net            1.3%   894   12   57.0
 3. ???
 4. ie1-g-0-0-0.telstraclear.net                       1.7%   894   15   61.6
 5. ge-0-2-0-1.xcore1.acld.telstraclear.net            1.6%   894   14   61.5
 6. 203.167.233.10                                     1.5%   893   13   74.6
 7. i-14-1-0.wil-core02.bx.reach.com                   1.7%   893   15  208.0
 8. i-1-1.eqla01.bi.reach.com                          1.8%   893   16  209.1
 9. gblx-peer.eqla01.pr.reach.com                      1.7%   893   15  221.8
10. MOZILLA-2.GigabitEthernet4-15.ar2.SNV2.gblx.net   40.8%   893  364  209.2
11. v9.core2.sj.mozilla.com                           44.1%   893  394  198.1
12. ???

There's a big loss of packets between reach and MOZILLA-2.GigabitEthernet4-15.ar2.SNV2.gblx.net, which shows up as a very laggy shell on the jumphost. Load is very low on that box.
our path to both ISC and Beijing are through gblx, and I've been getting paged frequently tonight about both of those locations being offline, however, I've not managed to catch an mtr trace that actually shows it yet.
Reverse appears to go through level3...
i've turned down globalcrossing peers.
WFM, I'm routed via mzima.net now.
This specific issue is resolved.  We'll work on troubleshooting GBLX elsewhere.
Assignee: server-ops → dmoore
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.