Sounds like the same thing I am experiencing here in High Park Bloor West Village area re: http://communityforums.rogers.com/t5/forums/forumtopicpage/board-id/Getting_connected/thread-id/2922...
I've been told by tech support on different days earlier this week and last weekend that there have been area outages. At times, my CGN3 router couldn't even get an I.P. address. I was also getting some black screens on a few TV channels and two way on-demand wouldn't work.
It certainly does look like Rogers nodes are taxed beyond the max... seems okay today though
So it is just like you said, good for a day, then yesterday un-usable. I have a tech comming out again today (i doubt it will yield anything). If he is unable to provide a fix then I dont have much choice, I will be cancelling and going over to a DSL provider, which is unfortunate because rogers speed trumps anything else available, however what does the speed mean to me if i cant use it. I will post an update after he is done here today.
He just replaced the line from the pole to the tap, my signal strength is actually flawless, im still seeing the T3 timeouts though, not sure where to go from here. The tech said talk to maintenence next, but how much longer do i really need to go through this for. Ill update again once i call into rogers.
Instead of calling, send a pm to @CommunityHelps asking for further assistance. I've already pm'd @RogersMoin to have a look at your previous post. The presence of T3 timeouts might not affect your service. Depending on what it is, it might merely mean that the Cable Modem Termination System is not responding to the Modem requests within its normal allotted time span, but that doesn't necessarily have an impact on your service.
I believe we pay for 250/20 ? we get 310/20 normally. The internet has been stable for 2 hours now, so i cant complain. Im just hoping it stays stable. both speed tests show me @ 310. I wonder if it is a cabling issue at all, if it just dissapeared. Attached are my new signal strenghts.
right now its working again, so if it causes issues again ill pm him. Thanks for checking up on it.
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||BandWidth|
|1||38596000||ATDMA - 64QAM||38.750||5||3200000|
|2||23700000||ATDMA - 64QAM||38.750||7||6400000|
|3||30596000||ATDMA - 64QAM||38.750||6||6400000|
|1||11/03/15 21:00:12||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:75:4f:90;CMTS-MAC=00:14:f1:eb:d5:4e;CM-QOS=1.1;CM-VER=3.0;|
Thats a request from the modem for a maintenance period, where the Cable Modem Termination System (CMTS) and the modem synchronize timing and a few other parameters and negotiate the modem signal levels back to the CMTS. The CMTS isn't answering on time and therefore the modem is timing out, waiting for the response. It then issues a T3 and will issue another request to the CMTS shortly thereafter. As long as this is an occasional occurrence, and not continuous, your modem should operate as expected. I see that occasionally in my modem logs and I don't give it a second thought. The modem operates as it should, so there's nothing to complain about from what I can see.
Disconnects starting again today, this is now flooding my docsis event log. Only posts to the log when i actually disconnect.
|1||11/05/15 14:52:17||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:75:4f:90;CMTS-MAC=00:14:f1:eb:d5:4e;CM-QOS=1.1;CM-VER=3.0;|
|2||11/06/15 19:02:02||68010300||error||DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=00:fc:8d:75:4f:90;CMTS-MAC=00:14:f1:eb:d5:4e;CM-QOS=1.1;CM-VER=3.0;|
|3||11/06/15 19:02:02||68010600||notice||DHCP Renew - lease parameters tftp file-bac10500010600fc8d754f90 modified;CM-MAC=00:fc:8d:75:4f:90;CMTS-MAC=00:14:f1:eb:d5:4e;CM-QOS=1.1;CM-VER=3.0;|
|4||11/07/15 14:20:07||82000200||critical||No Ranging Response received - T3 time-out;CM-MAC=00:fc:8d:75:4f:90;CMTS-MAC=00:14:f1:eb:d5:4e;CM-QOS=1.1;CM-VER=3.0;|
|5||11/07/15 21:06:37||90000000||warning||MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=00:fc:8d:75:4f:90;CMTS-MAC=00:14:f1:eb:d5:4e;CM-QOS=1.1;CM-VER=3.0;|
Now this one comes up, again when i get disconnected from the upstream channel.