Strange. Now i have very bad broadband quality monitor charts - it seems my account has been restricted from uploading pictures...
@AnthonyW1 No, your account has not been restricted from uploading pictures. Images need to be approved before they are visible to everyone. Normally they should be visible to you as the uploader, but a bug in the current forum code prevents even you seeing them until they are approved. If you see yellow triangles in place of your images then they are fine and just awaiting approval. If any of them are showing a red circle with a diagonal line through it then that image has been rejected.
Your latest images contained your WAN IP address which is against the forum rules to protect your privacy, so they were rejected.
Creating multiple thread for the sames issue is also against the rules so I have merged your threads.
My setup: V6 TV box, M350 Fibre broadband with Hub 3 in modem mode connected to a Netgear R7000 router. Telewest/VM user since 2001.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
Re: drops at my end user level with 'No Ranging Response received - T3 time-out' in the Superhub 2 logs.
05-05-202018:46 - edited 05-05-202018:48
I suggest you read the DOCSIS 3.0 specification rather than some random interpretation of it if you want to truly understand the communication medium.
In a nutshell it seems from your posts that you have intermittent noise ingress in the upstream channels.
Unfortunately the modulation error ratio (effectively S/N ratio) and bit error rates for upstream signalling is only visible to the CMTS.
In your case, given that your problems occur during daylight hours, I would assume that the noise ingress is created by other CM on your segment or even some external source. You have to remember that the operating frequencies for upstream channels sit nicely in the radio spectrum.
If you connect to your SH3 during an outage you might get a better idea of what is going on.
Explanation:The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.
T3 timeouts result when a Cable Modem, that is locked into the downstream, transmits a Ranging Request(RNG-REQ) to the CMTS(Cable Modem Termination System) and 200 milliseconds passes without the CM receiving a Ranging Response(RNG-RSP) from the CMTS. Indeed, maintaining a PING(Packet InterNet Groper) less than 200ms is important to a healthy DOCSIS network. When 10 T3s occur in succession (a period of 20 seconds passes without the CM receiving a Ranging Response, the CM will cease attempting to communicate with the HFC(Hybrid Fiber Optic Coaxial) network and reset its DOCSIS interface. In this case the RESET statistic on the modem log will increment but not all T3s will cause a reset if communication is restored within 10 T3 periods or 20 seconds. When T3 timeouts occur, but not enough occur in succession to trigger a reset, slow speeds are often a symptom as these timeouts slow down the TCP/IP handshakes necessary to maintain internet connections.
T3 Timeouts are typically caused by Upstream Noise causing Ranging Requests to not be clearly received by the CMTS. T3 problems can often be intermittant in nature as they may be the result of noise originating in any part of the plant that shares the same line card at the CMTS with the subscriber impacted. In fact, T3s can even be caused by noise originating on other neighboring nodes if resources are shared at the headend. Speed issues and intermittant connectivity issues are some of the most common problems encounted on our Trouble Calls.
T3 Timeouts can also be encountered when the plant's noise floor is so severe that the CM cannot overtalk it (SNR is bad and Noise power level is higher than your modem's signal). This can affect a single leg of the plant or even entire nodes. When a high noise floor results in several modems resetting their DOCSIS interface because 10 T3 timeouts have occured in succession, as we covered above, this is referred to as a noise outage. Noise outages frequently occur node-wide and while some may self-clear, many continue until a Plant Maintenence Technician locates and repairs the offending source of noise. This is why we ALL must be vigilant about preventing noise from entering the plant.
Occurrence:Extremely common in the customer homes
Symptom:Will cause intermittent disconnections. If you see couple of them, it is fine. If you quite a few of them consecutively, then it will lead to disconnections.
Example: 2017-6-14, 00:05:06 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0