Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Finally got moved on to 8 downstream channels earlier on today, was previously on 6.

DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 299000000 Hz 267000000 Hz 275000000 Hz 283000000 Hz 291000000 Hz 307000000 Hz 315000000 Hz 323000000 Hz
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked Locked Locked
Channel ID 79 75 76 77 78 80 215 216
Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256
Symbol Rate (Msym/sec) 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17
Power Level (dBmV) 0.0 dBmV -1.8 dBmV -1.8 dBmV -1.5 dBmV -2.0 dBmV 0.2 dBmV -0.2 dBmV -0.3 dBmV
RxMER (dB) 36.3 dB 36.8 dB 36.5 dB 36.4 dB 35.9 dB 36.5 dB 36.2 dB 36.0 dB

http://www.thinkbroadband.com/ping/s...27-08-2014.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Had this when arrived home yesterday after a night away. Quickly fixed with a reboot. Any similar experiences recently?

http://www.thinkbroadband.com/ping/s...27-08-2014.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Anybody else see a speed bump last night

[img]Download Failed (1)[/img]

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Nope. Nothing like that here in Coventry.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

All fine here too.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Nothing like that here in RG41.

http://www.thinkbroadband.com/ping/s...08-09-2014.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Thanks gents, must be just me then, overdue for some node work this month that should hopefully iron this out.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I wish I hadn't upgraded to 152Mb so quickly. Poor performance now..

http://www.thinkbroadband.com/ping/s...14-09-2014.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

That's either a noise fault or a TBB glitch. What do your modem stats say?

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

No, it's neither.

It's a core network fault. Saw it on several core nodes yesterday and today.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

The later event certainly looks like load, it tailed off after peak time.

Not local load either, DOCSIS doesn't react like that to downstream overbooking.

The way the packet loss disappeared when the load abated makes me think the problem was/is deeper into VM's network.

Point to point Ethernet links congest like that when they have no advanced queuing running on them.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

At times when there's an issue, downstream channels switch between 6 and 7.

http://grab.by/An56
http://grab.by/An58

And this morning, things are obviously better at this time.

http://grab.by/AnV8
http://grab.by/AnVa

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Interesting. I may have to stand corrected unless there are 2 different issues going on.

Never seen such an extreme reaction from DOCSIS on the downstream before, shouldn't happen if the load balancing is working properly.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Before commenting on the downstream channels, please - copy & paste the stats rather than putting up images. From our end it makes extra work having to open other files .

Anyway, when you have the problem, you are losing DS-4 & DS-6. So I reckon there's a problem/fault in the circuit that VM will have to rectify.

---------- Post added at 08:29 ---------- Previous post was at 08:05 ----------

Knowing Igni as I do, he might have said: "I reckon you should have 8 downstream channels, not 7 or 6. One of the 6 will be a bit ugly too for erroring."

On that point, the pre & post RS errors on the downstream would be useful to see. They are present if you don't log into the GUI but instead use the ROUTER STATUS link at the top right of the login screen.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

https://www.cableforum.co.uk/images/local/2014/09/9.png

You were right earlier

And there are two issues - the massive ping spike is VM's core network, the packet loss is likely more local.