SuperNet9Go Ninja,Go Ninja Go..PremiumReviews:
Harwood Heights, IL
[Signals] T4 timeout in upstream. How to fix?
How can I fix this? How do my levels look?
Downstream Bonding Channel Value
Channel ID 3 4 5 6
Frequency 663000000 Hz 669000000 Hz 675000000 Hz 681000000 Hz
Signal to Noise Ratio 36 dB 36 dB 36 dB 36 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
-1 dBmV -1 dBmV -1 dBmV -1 dBmV
Upstream Bonding Channel Value
Channel ID 7 8 9
Frequency 36400000 Hz 29500000 Hz 24200000 Hz
Ranging Service ID 11386 11386 11386
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 2.560 Msym/sec
Power Level 47 dBmV 47 dBmV 45 dBmV
Upstream Modulation  QPSK
Ranging Status Success T4 TimeOut Success
The power levels look fine.. I believe a T4 error means there was a communication errror with the upstream. If it's just a single T4 error, or a few T3 errors, and you're not seeing any service issues, I wouldn't worry about. There are any number of things that could cause the odd occurance of a T3 / T4.
T3 and T4 errors can be a sign of an upstream noise issue that can't be seen in the modem diagnostics. If you're having issues and start seeing the T3/T4 errors on the modem logs, try to call into Comcast while the problem is occuring ans ask for your upstream signal to noise ratio. I think anything above 30 should be OK.
|reply to SuperNet9 |
Rebooting the modem usually gets rid of the T4s (for the time being...at least)
gar187erI do this for a living
yea cause it wipes the log....lol
I'm better than you!
|reply to SuperNet9 |
This is a known issue with the Motorola SB61xx models. They sometimes T4 Timeout on the middle channel. You'll also notice the main Status page may say 'offline', even though it's working.
As mentioned, you can try rebooting to see if it properly connects. I found doing a power off reboot seemed to work better than using the Restart button on the Configuration page. Others have seen the reverse. It's hit-or-miss. There seems to be no logic as to why it may or may not timeout.
Contrary to what somebody else posted, it will NOT wipe out your log.