 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 3 edits | reply to koma3504
Re: [HSI] Charter Subs said by koma3504: i want the reboots stopped for 1 Ok, talk to local plant/tech managers. Obvously going round and round with phone support and random guys sent to your home isn't getting it done.
said by koma3504: Um yea right like anyone gets to talk to them. Quite often actually. Especially when the direct forum guys get involved in a difficult situation or you show up in there local tech office and ASK.
said by koma3504:ANd the techs here can not touch a CBN account. You said you also have a regular residential account. They can deal with that since it has the same issue.
said by koma3504:Current signal levels look fine exept the -11 and 12 but hten agin the upstream is hidden. Can you just write out ALL the signal levels shown, please? Downstrean level, SNR level, Upstream level? Those aren't hidden on the Motorola or Ambit modems you've said you had previously.
Here's mine:
 Home
 Away from home
|
|
 koma3504AdvocatePremium join:2004-06-22 North Richland Hills, TX 1 edit | Hows this ??? |
|
|
|
 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 4 edits | Looking at your signal levels.... a few things jump out.
1. Considering the difference between your downstream signal level being so low and your upstream signal level being so high, it would seem you modem is not connected to the first split after the demac or it's a 4-way or larger splitter. That started on the 26th. That's on the Motorola modem specifically.
2. A week ago today, something or someone corrected a low forward signal issue for you or your area. It also helped improve your forward SNR. Considering the return levels didn't change much, I'd guess it was water damage related...
3. Your signal levels vary way too much. They're bad, they're good, they're bad. It's not just one cause either. Sometimes it's the forward, sometimes it's the return, sometimes it's both.
4. Why is there a 5 dB difference in return levels between two modems in the same home? Especially when the forward signal levels are within 1 dB of each other?
5. That's entirely too much info to post about your account. It's got IPs, MAC addresses, etc. I just wanted current signal levels, I didn't need or ask for anything else. I'd suggest removing those screenshots. |
|
 koma3504AdvocatePremium join:2004-06-22 North Richland Hills, TX 2 edits | 1. thats when charter jacked everything up. replaced a couple ends in the house chargerd a 35 charge when there shold not have been.
4. not really sure.
unless it the fact the took the residential modem and put it on the other drop with the 3.5 leg which also has a 7.5 leg on it as well and a barrel roll.
Cause it was on the other drop with a ground block then off to a barrel roll in the attack then off to the wall plate where both modems was on splitter with 3.5 legs.
To me it does not make much since to put the modem on a drop that has 5 T.V's on it with a few going to be added.
Which look like this when changed back.
I was still told that the line tap was out of balence.
And im getting these kinds of speed test out of a 16/2 connection.





2010-03-28 18:00:54 6-Notice M571.1 Ethernet link up - ready to pass packets 2010-03-28 18:00:48 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-28 17:57:12 6-Notice M571.1 Ethernet link up - ready to pass packets 2010-03-28 17:57:08 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-28 17:48:40 6-Notice M571.1 Ethernet link up - ready to pass packets 2010-03-28 17:48:36 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:00:53 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:00:47 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:31 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 2010-03-28 11:35:28 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 2010-03-28 11:35:28 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2010-03-28 09:50:32 6-Notice M571.1 Ethernet link up - ready to pass packets 2010-03-28 09:50:28 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:00:50 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:00:44 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:33 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-27 22:09:58 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 2010-03-27 22:09:58 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:00:54 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:00:47 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:30 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-27 21:24:42 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 2010-03-27 21:24:42 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:00:48 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:00:44 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:29 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-27 18:48:15 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 2010-03-27 18:48:15 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2010-03-27 18:23:18 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response 1970-01-01 00:01:47 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:01:43 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:01:32 6-Notice M572.0 T1 No Ucd Timeout - Reinitialize MAC... 1970-01-01 00:01:32 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:01:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:01:12 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:01:12 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:57 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 1970-01-01 00:00:24 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:00:08 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-27 17:51:29 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 1970-01-01 00:01:37 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:01:33 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:01:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:01:13 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3) 1970-01-01 00:01:07 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2) 1970-01-01 00:01:01 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:59 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:58 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:57 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:56 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:19 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:18 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:17 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:11 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:00:11 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-27 17:45:58 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active
_____________________________________________
Oh here are some logs from the other day.
1970-01-01 00:01:34 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3) 1970-01-01 00:01:22 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:01:22 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:00:46 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:00:46 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:08:38 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:08:38 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2) 1970-01-01 00:07:59 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:07:56 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:07:56 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:07:53 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:07:52 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:07:14 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:07:14 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3) 1970-01-01 00:06:39 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:06:39 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:05:49 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:05:47 6-Notice M572.0 T1 No Ucd Timeout - Reinitialize MAC... 1970-01-01 00:05:47 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:05:37 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:05:33 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:05:33 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:05:31 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:05:31 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:05:29 6-Notice M572.0 T1 No Ucd Timeout - Reinitialize MAC... 1970-01-01 00:05:29 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:05:18 6-Notice M572.0 T1 No Ucd Timeout - Reinitialize MAC... 1970-01-01 00:05:18 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:05:08 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:05:07 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:05:07 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3) 1970-01-01 00:04:33 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:04:33 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2) 1970-01-01 00:03:56 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:03:56 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:03:16 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:03:16 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:02:40 6-Notice M572.0 T1 No Ucd Timeout - Reinitialize MAC... 1970-01-01 00:02:40 3-Critical U001.0 No UCD's Received - Timeout 1970-01-01 00:02:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:21 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:02:21 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:02:21 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:02:21 3-Critical R002.0 No Ranging Response received - T3 time-out (US 3) 1970-01-01 00:01:40 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:01:40 3-Critical R002.0 No Ranging Response received - T3 time-out (US 2) 1970-01-01 00:01:16 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:01:16 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:00:38 3-Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted 1970-01-01 00:00:38 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-24 13:45:02 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 2010-03-24 13:45:02 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2010-03-24 13:44:29 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out 1970-01-01 00:00:58 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:00:51 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:00:30 3-Critical R002.0 No Ranging Response received - T3 time-out (US 1) 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 2010-03-24 13:03:18 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 2010-03-24 13:03:18 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2010-03-23 23:52:58 6-Notice M571.1 Ethernet link up - ready to pass packets 2010-03-23 23:52:52 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:01:19 4-Error D004.3 ToD request sent- No Response received 1970-01-01 00:01:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response. 1970-01-01 00:01:04 3-Critical R002.0 No Ranging Response received - T3 time-out (US 4) 1970-01-01 00:00:58 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:55 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:54 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:53 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:52 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:18 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing 1970-01-01 00:00:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:03 6-Notice M571.1 Ethernet link up - ready to pass packets 1970-01-01 00:00:03 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:02 6-Notice M571.4 Ethernet link dormant - not currently active 1970-01-01 00:13:50 6-Notice M573.0 Modem Is Shutting Down and Rebooting... 1970-01-01 00:13:50 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 1970-01-01 00:00:02 6-Notice M571.1 Ethernet link up - ready to pass packets
-- Koma If YOu Don't Think It's Possable!! It's Acually A Reality!!The best way to predict the future is to invent it. Alan Kay!! Ya Don't Know The signal Till Ya Ride It!! Voice Break's There's Trouble!!!! |
|
 pbarrowPremium join:2003-09-16 Montgomery, AL kudos:1 | I can just about gaurantee you that with your signals looking good and you having T3 timeouts in your logs and dropping connection that you are having Upstream SNR problems.
You can't see Upstream SNR from your end - only Charter can see it from the Headend. Most of the Phone tech support people don't know jack about Upstream SNR or even how to check it. You need to insist that they put your modem on a Watch for several days and check the CMTS history for your Upstream SNR. The min is 22db and if it drops to 22db and below you will have speed and performance issues and at worst dropped connections.
Regardless of what Any of them try to tell you - frequent T3 timeouts = cable plant noise problems. It can be intermittent noise and will still cause you problems and it make take a lot of effort on their part to track it down and find it. |
|
 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 4 edits | said by pbarrow:I Most of the Phone tech support people don't know jack about Upstream SNR or even how to check it. You need to insist that they put your modem on a Watch for several days and check the CMTS history for your Upstream SNR. The min is 22db and if it drops to 22db and below you will have speed and performance issues and at worst dropped connections. The screenshots he had posted previously showed an upstream SNR of 29-32 dB. The reading were taken every 2 hours for several days.
Of course that doesn't show upstream BER, which directly impacts the likelyhood of T3s.
Things like CPD kill upstream SNR, while something like impulse noise will impact BER with little effect on upstream SNR. Either one will cause problems for upstream modem traffic.
Meanwhile something like upstream signal reflections, hum modulation, or ground loops on his home wiring can cause upstream signal problems and T3s for him and no one else. It wouldn't even register on the CMTS since those are aggregate upstream readings from all the modems on the port.
But you're right most phone tects and service techs sent to your home know nothing about those things and rarely have the tools to find them. |
|
 koma3504AdvocatePremium join:2004-06-22 North Richland Hills, TX | Meanwhile something like upstream signal reflections, hum modulation, or ground loops on his home wiring can cause upstream signal problems and T3s for him and no one else. It wouldn't even register on the CMTS since those are aggregate upstream readings from all the modems on the port.
Could you explian this a a little more??
So that I might check for such. -- Koma If YOu Don't Think It's Possable!! It's Acually A Reality!!The best way to predict the future is to invent it. Alan Kay!! Ya Don't Know The signal Till Ya Ride It!! Voice Break's There's Trouble!!!! |
|
 j_r0kk join:2009-03-31 Manhattan, KS kudos:2 | pbarrow,
don't be too quick to jump the gun on an upstream SNR issue. You're shooting darts in the dark without seeing any actual numbers. I'm not disagreeing, but you shouldn't throw stuff out there like that without factual information.
koma3504,
If I were in N. Richland Hills I'd come over there and fix your problem for you. However, I'm not so I can't. With that being said, you will unfortunately need to call in. Ask to speak to a supervisor this time. There is obviously an issue that needs attention at your residence. There is nothing anybody on this forum will be able to do for you unless you just want them to throw out possibilities and waste everyone's time. This issue has got to be taken care of in your neighborhood. |
|
 DrDrewSo that others may surf. join:2009-01-28 SoCal kudos:8 1 edit | reply to koma3504 said by koma3504:Meanwhile something like upstream signal reflections, hum modulation, or ground loops on his home wiring can cause upstream signal problems and T3s for him and no one else. It wouldn't even register on the CMTS since those are aggregate upstream readings from all the modems on the port. Could you explian this a a little more?? So that I might check for such. These sorts of things are rather rare, but not unheard of.
To measure them, you need the right meter and experience. Otherwise many of these problems are just fixed through swapping suspect parts.
Damaged cable, bad cable termination, and bad passive equipment in the home and system can cause signal reflections.
Hum modulation is caused by splitters and taps passing power. Most cable installed equipment has power blocking capacitors to stop this to a certain degree. Power can be put on the cable through hot chassis conditions, defective equipment, and hot/neutral swaps on some equipment such as TVs, computers modems, and other devices hooked to the cable system.
Ground loops occur when there are multiple paths to ground. Limiting grounding to one path usually eliminates this.
Phone techs and most service techs won't have a clue on what these things are. Most tech meters won't even pick these things up either. |
|