Search:  

 
 
   All ForumsHot TopicsGallery






how-to block ads


 
Forums » US Cable Support » Inside Insight » [Connectivity] Insight
Search Topic:
Uniqs:
472
Share Topic:
RSS topic:
toggle:
flat / full
normal / watch
Posting:
Post a:
Post a:
InsightBB and Docsis 3.0? »
AuthorAll Replies


soooflusterated

@rr.com

[Connectivity] Insight



been getting constant loss of sync for half hour chunks over the weekend, drops and stays gone for half and hour then comes back, anybody else got issues or just me?

Thanks

Ed


lilhurricane
Mallomars
Premium,Mod
join:2003-01-11
Purple Zone
clubs:
What area (market) are you in?


soooflusterated

@rr.com
New Albany Ohio

Singular
Premium
join:2008-08-13
Shelbyville, KY

reply to soooflusterated
Humm... Louisville Head end seems fine. Have you logged into your modem to see what error its getting? Checked the SNR and other stats? What type of modem do you have, so that I can direct you on how to look up this information if you don't already know.


soooflusterated

@rr.com

heres what i got, any thoughts are appricated. Thanks

Frequency 555000000 Hz
Signal To Noise Ratio 34.4 dB

Power Level -1.5 dBmV
Upstream Value
Channel ID 9
Frequency 20400000 Hz
Power 50.3 dBmV

2009-05-11 02:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-11 02:00:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-11 01:59:36 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-11 01:59:06 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-11 01:57:44 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-11 01:57:27 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-11 01:56:18 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-11 01:56:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-11 00:30:49 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-11 00:30:29 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 16:13:15 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 16:12:56 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 16:11:44 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 16:11:21 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:55:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:55:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:55:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:54:52 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:52:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:52:15 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:52:07 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:52:07 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:51:55 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:51:40 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:49:10 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:48:40 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:46:04 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:45:28 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:42:59 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:42:51 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:42:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:42:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:42:41 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:42:38 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:42:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:42:31 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:41:00 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 15:40:38 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:39:25 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:39:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:39:21 3-Critical U001.0 No UCD's Received - Timeout
2009-05-10 15:38:39 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:38:37 3-Critical U001.0 No UCD's Received - Timeout
2009-05-10 15:36:17 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 10:23:35 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 15:22:57 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:22:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:22:55 3-Critical U001.0 No UCD's Received - Timeout
2009-05-10 15:18:23 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:15:41 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 15:15:13 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:12:45 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:12:35 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:10:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:10:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:10:02 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:09:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:09:54 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:09:28 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:05:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:05:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 15:05:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:05:01 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 15:02:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 15:02:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 14:56:46 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:56:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:56:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:56:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:56:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:56:40 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:56:34 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:56:33 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:56:22 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:56:16 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 14:40:34 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:40:23 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:40:06 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:40:06 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:39:51 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:38:52 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 14:37:26 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:37:07 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 14:35:46 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:35:13 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:34:23 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:34:04 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 14:32:35 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:30:55 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2009-05-10 14:29:36 3-Critical R002.0 No Ranging Response received - T3 time-out
2009-05-10 14:28:52 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:28:44 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:28:44 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:28:43 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:28:43 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:28:42 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:28:42 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:28:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2009-05-10 14:28:40 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2009-05-10 14:28:34 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing

Singular
Premium
join:2008-08-13
Shelbyville, KY

reply to soooflusterated
All of the errors look like the normal stuff that comes up. To be honest the log is almost a perfect match to my own. All of the numbers look to be in range as well. To be honest, I am not sure what the problem could be. Are you having any other problems with your services? The only thing I could think of is a bad modem, a problem at the head end or possibly a bad splitter, or some type of interference. Its just to hard to tell, so many variables. I think you should talk to InsighTech5 if he hasn't sent you a PM already and start a web chat and have them look over everything on their end.
-
Forums » US Cable Support » Inside InsightInsightBB and Docsis 3.0? »


Sunday, 08-Nov 22:18:43 Terms of Use | Privacy Policy | Hosting by www.nac.net - DSL,Hosting & Co-lo | feedback | contact
over 10 years online! © 1999-2009 dslreports.com.republican-creole
page compression OFF
Most commented news this week
· [156] Cable Uncapper Faces Criminal Charges
· [140] AT&T Sues Verizon Over 3G Ads
· [112] Why Run Fiber When You Can Run Ads That Pretend You Do?
· [108] Comcast Is Simply Getting Huge
· [93] Apple Cooking Up New $30 A Month TV Service?
· [83] Bits Of ACTA Agreement Leaking Out
· [80] Will 'Three Strikes' Come To The United States?
· [78] Verizon To Double Smartphone ETFs?
· [77] Verizon: Droid Tethering Will Cost $30 Extra
· [73] Comcast, NBC Deal Almost Complete
Most people now reading
· Hit and run [General Questions]
· [FS] Motherboard + CPU + Hard Drive + Servers + More! [For Sale/Wanted]
· My cat is reluctant to exercise. [General Questions]
· 3.x Feral Druid - Bear Tanking Guide [World of Warcraft]
· [WIN7] Which Services in Win 7 Have You Turned Off? [Microsoft Help]
· [NFL] Week 9 Games Thread [Sports Chat]
· Maximizing Rogue DPS for 3.1 [World of Warcraft]
· Voxox Unlimited US/Canada for $2.45 or World $12.95 a month [VOIP Tech Chat]
· no Globalive/Wind Mobile in Canada [TekSavvy]