Hello all,
I'm a Comcast Business customer and have had great service over the past 4 years or so. Lately, we bought a new house -- so we moved across town and got the service moved in February. Fast forward to last week. My Surfboard 6121 started resetting with T3 ranging errors and T4 timeouts. My setup at the time was:
Setup:
1. 6121 Modem with a 10db pad on the coax connector of the modem (placed by tech that installed).
2. First device after the modem is my ASUS RTN-66u.
3. 24 port switch is last where my devices plug in.
Background:
Last Saturday, I got a tech scheduled to come out and check stuff over. REALLY nice guy who got up to the tap on the pole across the street and indicated that a couple of the connectors at the tap plate were loose and tightened them. (I was watching, so that seems reasonable from my perspective.) He then came down and found an old connector in the box on the side of the house and an older combination MOCA filter and ground block which he indicated was deprecated, so it was replaced with a new one.
He then visited the basement where my office and the coax enters our home. He replaced a barrel coupler and a couple of ends down there in addition to changing out my 10db attenuator on the modem with a 6db instead. He indicated that if I had trouble after he left, change the modem out. (I provide my own since I'm dynamic IP space.) At the time my 6121 was a few years old, so I thought that could be reasonable as my old 5100 died in much the same way -- high noise on the upstream and then just wouldn't sync, period.
So, I had resets again after provisioning and I went to the store and bought a 6141. I got it provisioned and I'm having the same sort of issue. I called Comcast Business today and told them the situation and immediately got an escalated ticket to see if the Line guys thought there was a problem. (So I'm told...) Anyway, they just said to send a second premises tech which is scheduled for Friday.
Problems:
1. Signals look good and then randomly creep up on the upstream side and cause a reboot/series of reboots until upstream signals drops back into range (under 54 in my experience thus far)
2. If I take the attenuator off, it lasts for a few hours and then either the downstream exceeds 10db and stuff goes weird and we get a reboot or the upstream goes crazy again. (upwards of 58)
Logs:
DownstreamBonding Channel ValueChannel ID2 3 4 5 6 7 9 10 Frequency681000000 Hz 687000000 Hz 693000000 Hz 699000000 Hz 705000000 Hz 711000000 Hz 723000000 Hz 729000000 Hz Signal to Noise Ratio38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB Downstream ModulationQAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 Power LevelThe Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading0 dBmV 0 dBmV 0 dBmV 0 dBmV 1 dBmV 1 dBmV 0 dBmV 0 dBmV UpstreamBonding Channel ValueChannel ID30 29 31 32 Frequency23800000 Hz 19000000 Hz 31700000 Hz 36500000 Hz Ranging Service ID9751 9751 9751 9751 Symbol Rate5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec 2.560 Msym/sec Power Level41 dBmV 40 dBmV 42 dBmV 42 dBmV Upstream Modulation[3] QPSK[3] 64QAM [3] QPSK[2] 16QAM [3] QPSK[3] 64QAM [3] QPSK[3] 64QAM Ranging StatusSuccess Success Success Success Signal Stats (Codewords)Bonding Channel ValueChannel ID2 3 4 5 6 7 9 10 Total Unerrored Codewords94413486 93559888 93568162 93577316 93550483 93552539 93553955 93554865 Total Correctable Codewords0 0 0 1 120 11 18 13 Total Uncorrectable Codewords561 590 570 509 1474 598 587 751
Apr 27 2015 17:55:275-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:55:153-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:54:445-WarningZ00.0MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Jan 01 1970 00:00:523-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Jan 01 1970 00:00:156-NoticeN/ACable Modem Reboot due to T4 timeout ;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:543-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:543-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:543-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:443-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:443-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:443-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:373-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:373-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:373-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:293-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:293-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 17:52:283-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 15:51:373-CriticalR06.0Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 15:51:373-CriticalR03.0Ranging Request Retries exhausted;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;Apr 27 2015 15:51:353-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=6c:ca:08:88:9a:6a;CMTS-MAC=00:01:5c:71:2e:61;CM-QOS=1.1;CM-VER=3.0;
Thoughts? I'm thinking it's a line-crew type issue, should I be concerned that a second premises tech is coming? If anyone else has had something similar -- what was your solution?
TIA,
ayoustic
↧
