Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[mark_newbs]

Hi,

I am looking for some help/Info.

I have a VMG8924 running the latest firmware (13C0).  My PC is hardwired to the GigE port.

Pinging the router *.254 is 100% reliable but pinging google.co.uk gets anything from 5% to 50% packet loss/Request Timed out.  is anyone else with this router experiencing the same issue?

Is there any advice on solving this issue/tutorials I should read?

Thanks in advance.

DSL stats:
               
============================================================================
    VDSL Training Status:   Showtime
                    Mode:   VDSL2 Annex B
            VDSL Profile:   Profile 17a
                G.Vector:   Disable
            Traffic Type:   PTM Mode
             Link Uptime:   1 day: 22 hours: 6 minutes
============================================================================
       VDSL Port Details       Upstream         Downstream
               Line Rate:     20.063 Mbps       79.998 Mbps
    Actual Net Data Rate:     19.999 Mbps       79.999 Mbps
          Trellis Coding:         ON                ON
              SNR Margin:       15.1 dB            9.2 dB
            Actual Delay:          0 ms              0 ms
          Transmit Power:        6.2 dBm          14.4 dBm
           Receive Power:      -12.2 dBm           2.2 dBm
              Actual INP:        0.0 symbols      48.0 symbols
       Total Attenuation:       18.2 dB           12.1 dB
Attainable Net Data Rate:     32.540 Mbps       94.693 Mbps
============================================================================
      VDSL Band Status    U0      U1      U2      U3      D1      D2      D3
  Line Attenuation(dB):  4.0    17.6    26.2     N/A    10.0    23.0    36.0   
Signal Attenuation(dB):  4.0    17.3    25.9     N/A    10.1    22.8    36.0   
        SNR Margin(dB): 14.9    15.1    15.1     N/A     9.2     9.2     9.2   
   Transmit Power(dBm):- 9.0   -25.5     5.9     N/A    12.3     7.8     6.9   
============================================================================

            VDSL Counters

           Downstream        Upstream
Since Link time = 6 min 11 sec
FEC:      171746      15032
CRC:      708      453
ES:      73      389
SES:      9      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 15 minutes time = 12 min 33 sec
FEC:      21      25
CRC:      0      7
ES:      0      6
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 15 minutes time = 15 min 0 sec
FEC:      9      13
CRC:      0      1
ES:      0      1
SES:      0      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Latest 1 day time = 22 hours 57 min 33 sec
FEC:      32900      13015
CRC:      83      254
ES:      10      211
SES:      2      0
UAS:      0      0
LOS:      0      0
LOF:      0      0
LOM:      0      0
Previous 1 day time = 24 hours 0 sec
FEC:      368561      2258
CRC:      1906      211
ES:      92      190
SES:      30      0
UAS:      51      28
LOS:      1      0
LOF:      5      0
LOM:      0      0
Total time = 1 days 22 hours 57 min 33 sec
FEC:      556566      34511
CRC:      2693      1041
ES:      213      915
SES:      36      0
UAS:      86      63
LOS:      1      0
LOF:      5      0
LOM:      0      0
============================================================================

                 

Mark

[William Grimsley]

Hi mark_newbs,

Your line is dropping out frequently with a lot of ES occuring, so you'll need to sort out the line fault before trying to investigate the packet loss issue.

[mark_newbs]

Thanks William,

The ES is about 200 per 24 hour period.  I thought this was pretty normal for VDSL lines (I would prefer 0 but I think the old copper I am on has been the issue).  is 200 a high number for ES?

Thanks

Mark

[William Grimsley]

Thanks William,

The ES is about 200 per 24 hour period.  I thought this was pretty normal for VDSL lines (I would prefer 0 but I think the old copper I am on has been the issue).  is 200 a high number for ES?

Hmm, really?

Since Link time = 6 min 11 sec
FEC:      171746      15032
CRC:      708      453
ES:      73      389

[mark_newbs]

HI William, the link time is misreported under the total link time - there are days and hours missing.

If you look at the last 24 hours and previous 24 hours:

Latest 1 day time = 22 hours 57 min 33 sec
FEC:      32900      13015
CRC:      83      254
ES:      10      211

Previous 1 day time = 24 hours 0 sec
FEC:      368561      2258
CRC:      1906      211
ES:      92      190

Thanks

Mark

[Starman]

My upstream ES are generally ~250 per day which isn't enough for DLM to take action. Although I generally only get <5 ES on my downstream - personally I'd be more worried about Serious Error Seconds etc.

I have the same router but I don't use the modem and my pings to Google are fine.

Could you run a tracert and perhaps a pingpath? Who's your ISP?

[mark_newbs]

Hi Starman,

I'm with plusnet.  Test results are below.  I'll be honest I didn't know about pathping which seems like the tool I have been looking for.  so the loss is between router and plusnets infrastructure?

Thanks

Mark

Tracing route to google.co.uk [216.58.198.195]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  ZyXEL.Home [192.168.1.254]
  2    11 ms     *        *     lo0.14.central14.ptw-bng01.plus.net [195.166.128
.174]
  3    11 ms    14 ms    11 ms  irb.14.ptw-cr02.plus.net [84.93.249.66]
  4    11 ms    11 ms    11 ms  72.14.223.32
  5    12 ms    11 ms    12 ms  216.239.56.67
  6    11 ms    12 ms    12 ms  216.58.215.193
  7    12 ms    11 ms    11 ms  lhr26s03-in-f3.1e100.net [216.58.198.195]

Trace complete.

Tracing route to google.co.uk [216.58.198.195]
over a maximum of 30 hops:
  0  LAP132.net.angliac.com [192.168.1.108]
  1  ZyXEL.Home [192.168.1.254]
  2  lo0.14.central14.ptw-bng01.plus.net [195.166.128.174]
  3  irb.14.ptw-cr02.plus.net [84.93.249.66]
  4  72.14.223.32
  5  216.239.56.67
  6  216.58.215.193
  7  lhr26s03-in-f3.1e100.net [216.58.198.195]

Computing statistics for 175 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           LAP132.net.angliac.com [192.168.1.108]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  ZyXEL.Home [192.168.1.254]
                                0/ 100 =  0%   |
  2   11ms    45/ 100 = 45%    45/ 100 = 45%  lo0.14.central14.ptw-bng01.plus.net [195.166.128.174]
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  irb.14.ptw-cr02.plus.net [84.93.249.66]
                                0/ 100 =  0%   |
  4   11ms    76/ 100 = 76%    76/ 100 = 76%  72.14.223.32
                                0/ 100 =  0%   |
  5  ---     100/ 100 =100%   100/ 100 =100%  216.239.56.67
                                0/ 100 =  0%   |
  6  ---     100/ 100 =100%   100/ 100 =100%  216.58.215.193
                                0/ 100 =  0%   |
  7   12ms     0/ 100 =  0%     0/ 100 =  0%  lhr26s03-in-f3.1e100.net [216.58.198.195]

Trace complete.

[npr]

Running a VMG8924 with firmware (13C0), ISP Plusnet.
Not seeing any problem with ping packet loss to google.co.uk here.

C:\Users\npr>ping google.co.uk -t

Pinging google.co.uk [216.58.213.99] with 32 bytes of data:
Reply from 216.58.213.99: bytes=32 time=23ms TTL=57
snip
Reply from 216.58.213.99: bytes=32 time=23ms TTL=57

Ping statistics for 216.58.213.99:
    Packets: Sent = 171, Received = 171, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 267ms, Average = 25ms

Have you tried running a TBB ping graph to see if there's any general packet loss?
http://www.thinkbroadband.com/ping
here's mine:

[mark_newbs]

I will sign up and give it a go.

Thank you for the heads up and confirmation that the 13C0 firmware is OK at your end.

I'm out of the office for a few days so will pick back up tuesday next week.

[Starman]

I'm also on PN - so here is my pathping to example.

Code: [Select]

Tracing route to google.co.uk [212.56.71.99]
over a maximum of 30 hops:
  0  *.Home [192.168.1.2]
  1  gateway [192.168.1.254]
  2  195.166.130.216
  3  link2-central10.pcl-gw02.plus.net [84.93.249.194]
  4  ae1.pcl-cr02.plus.net [195.166.129.3]
  5  plusnet-lcy4.plus.net [212.56.71.99]

Computing statistics for 125 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           *.Home [192.168.1.2]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  gateway [192.168.1.254]
                                0/ 100 =  0%   |
  2    9ms     0/ 100 =  0%     0/ 100 =  0%  195.166.130.216
                                0/ 100 =  0%   |
  3  ---     100/ 100 =100%   100/ 100 =100%  link2-central10.pcl-gw02.plus.net [84.93.249.194]
                                0/ 100 =  0%   |
  4   10ms     0/ 100 =  0%     0/ 100 =  0%  ae1.pcl-cr02.plus.net [195.166.129.3]
                                8/ 100 =  8%   |
  5    9ms     8/ 100 =  8%     0/ 100 =  0%  plusnet-lcy4.plus.net [212.56.71.99]

Trace complete.

Personally I'd suggest a simple gateway swap - if you disconnect the PPP session on the router rather than restart the whole thing this way it will not affect your DSL sync.