GarciaJJ
New Contributor II
Joined 3 years ago
User Profile
User Widgets
Contributions
Random drops\disconnects
Where to start. I have called and we went though the whole thing. could not find anything really wrong, A tech was supposed to come out but never showed. At this point its my hardware SB6141 or the main trunk coming to my house. I'm trying my hardest not to be upset but at this point is really annoying when streaming or playing online games and everything just drops. So any insight into this would be amazing. Snap Shot of Log Thanks1.4KViews0likes3CommentsRe: Errors in modem log Critical? SB6180
Now that, it shouldn't be doing. And we are seeing a high number of power adjustments. That along with the receive level running high could indicate a problem with an amplifier somewhere along the line. Ive been playing with the splitter setup trying to make sure the hiccup wasn't something on my end. Still could be the only wire that isnt new is the one thatphysically runs in to the house..ive seen the downstream run as high as 13.4 and it work it way all the way down to 5 or 6 only to go back up by the end of the night. 13.4 was with a 2-way splitter that drops 3.4 db something like that and is how its still setup. The only other option is a 4 way that drops it 7db2Views0likes0CommentsRe: Errors in modem log Critical? SB6180
No major issue like a total restart going on but just every once a while it dose hiccup and things fail to load. A simple refresh and everything is back to working order till the next time.. The old sb5120 was like this too but i figured it was just getting old and tired..had it since the service went from Roadrunner to cox shortly after that anyways. Was really hoping to loose that small hiccup with the new modem and also try to take advantage of the higher speeds D3 can offer along with reliably as i understand it.2Views0likes0CommentsErrors in modem log Critical? SB6180
Was mowing today and some way some how over the years the line from the pole to the house got pulled out away from the house and the mower found it in the grass Any ways i had a connector lying around and put it on the end of the wire but now i get all these errors in the logs that where not there before. It always had a few like TOD and the DHCP Renew. Should i call and have a cox tech come out and put a new connector, Would that solve these issues? I think i have a decent signal but I'm not an expert so thought i would ask. Software Version: SB6180-3.5.8.4-GA-00-507-NOSH Hardware Version: 1 MIB Version: II GUI Version: 1.0 Time Priority Description 2013-05-11 06:25:15 4-Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=a4:7a:a4:fe:c5:5 2013-05-10 18:25:18 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:c5:50;CMTS-MAC=00:26:cb:d4:f1:89;CM 2013-05-10 18:25:17 4-Error Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=a4:7a:a4:fe:c5:50;CMTS-MA 2013-05-10 18:25:17 4-Error Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=a4:7a:a4:fe:c5:50;CMTS-MA 1970-01-01 00:00:28 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:c5:50; 2013-05-10 18:17:31 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-10 18:17:29 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-10 18:17:28 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-10 18:17:14 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-10 18:17:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-10 18:16:59 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-10 18:16:58 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-10 18:16:44 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-10 18:16:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-10 18:15:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-10 18:15:30 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 19:04:42 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 19:03:28 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 19:02:51 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:00:23 3-Critical No Ranging Response received - T3 time-out 2013-05-09 17:27:33 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 17:27:33 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 17:27:17 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 17:27:17 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 17:27:02 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 17:27:02 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 17:26:47 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 17:26:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 17:25:36 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 17:20:32 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 17:19:25 3-Critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti 2013-05-09 17:19:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 17:18:40 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 16:17:06 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 16:17:00 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 16:13:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:00:26 3-Critical No Ranging Response received - T3 time-out 2013-05-09 15:41:20 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:40:28 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:40:27 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:40:26 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:40:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:40:10 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:40:09 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:39:55 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:39:55 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:39:40 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:39:40 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:38:23 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:38:18 3-Critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti 2013-05-09 15:32:18 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:00:23 3-Critical No Ranging Response received - T3 time-out 2013-05-09 15:19:51 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:00:23 3-Critical No Ranging Response received - T3 time-out 2013-05-09 15:17:50 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:16:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:16:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:16:00 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:15:59 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:15:58 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:15:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:15:53 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:15:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:15:51 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:15:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:15:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:14:30 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:14:30 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2013-05-09 15:14:29 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:14:28 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:14:12 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:14:12 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:13:57 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:13:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:13:42 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-09 15:13:42 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:12:43 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-09 15:12:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2013-05-08 18:45:09 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2013-05-08 18:20:58 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:02:01 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; Downstream Value Frequency 849000000 Hz Signal To Noise Ratio 39.4 dB Power Level 9.9 dBmV 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 Upstream Value Channel ID 3 Frequency 28700000 Hz Power 37.7 dBmVSolved14KViews0likes6CommentsRe: Cable modem reboots every 5 minutes
Change out splitters. If you have say a 4 way that divides the signal out from the drop. I would suggest putting a good 2-way off the drop line then put the modem coax line on one side and then the 4 way splitter for the tv's on the other side. Ive done so much reading the last few day trying to get the most out of my modem and read some stuff that i would have never thought of. Say a 4 way splitter drops the signal down 7.83 db then if you split that again with say a 2 way splitter that a 3.28 db loss of signal so right there you have over a 10 db loss in signal2Views0likes0Comments