Cable Forum - View Single Post - 125M Exposed VM coax cable in junction box

RB2004 · 12-08-2012, 15:59

All looks fine on that cable,

Upstream is within tolerance,
Downstream is perfect as its close to 0, SNR slightly on low side but above 32 which would suggest a higher level of noise on the network...which is why loose connections and unterminated connections dont help.

Sephiroth states,

SNR (RxMER) - DOWNSTREAM

64QAM 29 dB minimum; 32 dB or above desired
256QAM 32 dB minimum; 35 dB or above is desired

See here for full details,

http://community.virginmedia.com/t5/...ER/td-p/148068

Was SNR any higher on the new cable? if not then i'd just leave it on the current cable and terminate the spare one if all works fine, will reduce noise introduction, and reduce vm network signal leak.. As well as protect the inside of the cable from dampness should it be needed in future.

Those T3s are probably a vm network problem.

I was T3 free until they gave Me 6 channels, now I'm getting up to 12 a day, but because my services aren't broke they won't fix it or acknowledge it as a problem.

So it's a case of. "when networks find or notice it as being a problem" it will be fixed but until them nothing will be done.

I was also told T3s can be caused by upstream congestion at the CMTS which is on VM headend.

Heres mine,

Upstream

nice 42 T3 errors since last reboot, lol but I tried to get VM to fix it but they wont...so its a problem on their network, like yours probably.

Downstream

12-08-2012, 15:59	#12
RB2004 Inactive Join Date: Jun 2009 Services: Services: 200 Mbit Gamer on Hub 3, 3x Arris V6 Boxes, CISCO V HD, VIP Package Posts: 689	All looks fine on that cable, Upstream is within tolerance, Downstream is perfect as its close to 0, SNR slightly on low side but above 32 which would suggest a higher level of noise on the network...which is why loose connections and unterminated connections dont help. Sephiroth states, SNR (RxMER) - DOWNSTREAM 64QAM 29 dB minimum; 32 dB or above desired 256QAM 32 dB minimum; 35 dB or above is desired See here for full details, http://community.virginmedia.com/t5/...ER/td-p/148068 Was SNR any higher on the new cable? if not then i'd just leave it on the current cable and terminate the spare one if all works fine, will reduce noise introduction, and reduce vm network signal leak.. As well as protect the inside of the cable from dampness should it be needed in future. Those T3s are probably a vm network problem. I was T3 free until they gave Me 6 channels, now I'm getting up to 12 a day, but because my services aren't broke they won't fix it or acknowledge it as a problem. So it's a case of. "when networks find or notice it as being a problem" it will be fixed but until them nothing will be done. I was also told T3s can be caused by upstream congestion at the CMTS which is on VM headend. Heres mine, Upstream nice 42 T3 errors since last reboot, lol but I tried to get VM to fix it but they wont...so its a problem on their network, like yours probably. Downstream