Re: what causes this?
 

There isn't anything in my network log since I cleared it over a month ago, so no log to post.

Which page are 'tick counters' on? I can't see what you are asking for.

Re: what causes this?
 

http://192.168.100.1/VmRouterStatus_upstream.asp
….or...
http://192.168.100.1/VmRgNetworkStatus.asp


but they do get reset every so often after (hopefully) being transmitted to CMTS. However if there's nothing in your Network log then they're probably all zero anyway…

Re: what causes this?
 

Here you go. Downstream is included just in case it helps.

US-1 US-2 US-3 US-4
Channel Type 2.0 2.0 N/A N/A
Channel ID 5 4 N/A N/A
Frequency (Hz) 35800000 Hz 45800000 Hz N/A N/A
Ranging Status Success Success N/A N/A
Modulation QAM16 QAM16 N/A N/A
Symbol Rate (Sym/sec) 5120000 5120000 N/A N/A
Mini-Slot Size 128 128 N/A N/A
Power Level (dBmV) 53.0 dBmV 54.3 dBmV N/A N/A
T1 Timeouts 0 0 N/A N/A
T2 Timeouts 0 0 N/A N/A
T3 Timeouts 0 0 N/A N/A
T4 Timeouts 1 1 N/A N/A

DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 323000000 Hz 283000000 Hz 291000000 Hz 299000000 Hz 307000000 Hz 315000000 Hz N/A N/A
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked N/A N/A
Channel ID 80 75 76 77 78 79 N/A N/A
Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 N/A N/A
Symbol Rate (Msym/sec) 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 N/A N/A
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 N/A N/A
Power Level (dBmV) 5.0 dBmV 3.8 dBmV 3.2 dBmV 3.7 dBmV 3.7 dBmV 5.0 dBmV N/A N/A
RxMER (dB) 41.4 dB 42.0 dB 41.8 dB 41.9 dB 41.9 dB 41.9 dB N/A N/A
.

Re: what causes this?
 

Upstream is too high seeing as you have 2 bonded

Re: what causes this?
 

Only if it isn't stable at those values.

Re: what causes this?
 

I thought >50dBmV was an issue with 2 or more upstreams?

Re: what causes this?
 

It's not ideal - but if it's stable and there is no upstream problem, then that's what it takes to push the data. If the upstream power is fluctuating (like stepping up through the values reaching 55 dBmv), then there's a problem.

Re: what causes this?
 

Fairy 'nuff - but im sure VM work to 50 now instead of 55 IIRC

Re: what causes this?
 

It depends on what you mean "work to". In the same way as the ideal downstream is 0 dBmv, upstream is 40 dBmv (for reasons I've explained in my sticky on the VM forum).

Of course, plant/infrastructure can't be guaranteed across the board to behave ideally, hence the range of acceptable upstream values. The SH maxes out at 58 dBmv and so anything below that which is stable and produces acceptable upstream performance can be tolerated, though far from ideal because there is no headroom after 55 dBmv.

As a rule, infrastructure is behaving well if upstream power is as much above 40 dBmv as downstream is below 0 dBmv and vice versa. You see this in the various stats posted by peops.

But you're right in the sense that the OP needs to keep an eye on the upstream in the way that I have suggested.

Re: what causes this?
 

By "work to" I meant in the same way as they used to arrange a tech visit if it was above 55, they now do for above 50 (i could be wrong there)

Re: what causes this?
 

I'm still getting the internet dropouts although not as badly.

I see that my channel IDs have swapped upstreams and the power levels are slightly higher.

US-1 US-2 US-3 US-4
Channel Type 2.0 2.0 N/A N/A
Channel ID 4 5 N/A N/A
Frequency (Hz) 45800000 Hz 35800000 Hz N/A N/A
Ranging Status Success Success N/A N/A
Modulation QAM16 QAM16 N/A N/A
Symbol Rate (Sym/sec) 5120000 5120000 N/A N/A
Mini-Slot Size 128 128 N/A N/A
Power Level (dBmV) 54.3 dBmV 54.0 dBmV N/A N/A
T1 Timeouts 0 0 N/A N/A
T2 Timeouts 0 0 N/A N/A
T3 Timeouts 0 0 N/A N/A
T4 Timeouts 1 1 N/A N/A