mikekozy
Level 1: Cadet

Cable Ultimate irregular dropouts

Hey guys, 

Please note I've tried looking around and googling but I can't seem to find the answers I'm looking for so I'd thought I'd post.

I got cable Ultimate not to long ago, and I've been experiencing irregular drop outs of a couple of seconds. For what I'm using the net for, I cannot afford any drop outs at all. I running a decent computer and am directly connected to the netgear CG3100D-2BPAUS modem via ethernet. Theres about an extra 4-5 devices that run wirelessly.


Event Log


TimePriorityDescription
 Fri Aug 02 04:40:49 2013   Error (4)  DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 30 08:17:44 2013   Warning (5)  MDD message timeout;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Notice (6)  Honoring MDD; IP provisioning mode = IPv4 
 Sat Jul 27 09:10:00 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jul 26 14:37:31 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 25 15:09:41 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Wed Jul 24 09:51:11 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 23 11:37:11 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Mon Jul 22 10:55:32 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 21 11:27:42 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jul 20 08:06:16 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jul 19 09:52:50 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 18 15:04:25 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 16 01:40:09 2013   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 16 01:39:58 2013   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 16 01:39:46 2013   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 16 01:33:49 2013   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 16 01:33:31 2013   Critical (3)  No UCDs Received - Timeout;;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 16 01:33:12 2013   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 16 01:32:39 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 16 00:31:14 2013   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:89;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 16 00:31:00 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; 
 Tue Jul 16 00:30:49 2013   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 16 00:30:23 2013   Critical (3)  SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Tue Jul 16 00:30:17 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jul 13 23:32:54 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Sun Jul 07 10:41:02 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Sat Jul 06 13:24:18 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Fri Jul 05 16:07:33 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Thu Jul 04 18:25:21 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 
 Wed Jul 03 15:33:33 2013   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0d:7f:f0:90:78;CMTS-MAC=00:21:a0:ce:3e:9d;CM-QOS=1.1;CM-VER=3.0; 

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel470000000 HzLocked
Connectivity StateOKOperational
Boot StateOKOperational
Configuration FileOK 
SecurityEnabledBPI+

Downstream Bonded Channels
Lock StatusModulationChannel IDSymbol rateFrequencyPowerSNRDOCSIS/EuroDOCSIS locked
LockedQAM642376952000 sym/sec470000000 Hz4.8 dBmV40.3 dBEuroDOCSIS
LockedQAM642336952000 sym/sec438000000 Hz5.2 dBmV40.4 dBEuroDOCSIS
LockedQAM642346952000 sym/sec446000000 Hz5.1 dBmV40.3 dBEuroDOCSIS
LockedQAM642356952000 sym/sec454000000 Hz4.8 dBmV39.8 dBEuroDOCSIS
LockedQAM642366952000 sym/sec462000000 Hz4.2 dBmV40.3 dBEuroDOCSIS
LockedQAM642386952000 sym/sec478000000 Hz5.5 dBmV40.3 dBEuroDOCSIS
LockedQAM642396952000 sym/sec486000000 Hz4.9 dBmV40.3 dBEuroDOCSIS
LockedQAM642286952000 sym/sec494000000 Hz5.4 dBmV39.8 dBEuroDOCSIS

Upstream Bonded Channels
Lock StatusModulationChannel IDSymbol RateFrequencyPower
LockedATDMA45120 Ksym/sec59800000 Hz38.8 dBmV
Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV
Not LockedUnknown00 Ksym/sec0 Hz0.0 dBmV

Besides these logs, is there anything else that I need to factor in?

Thanks in advance,
Mike

Was this helpful?

  • Yes it was, thank you
  • No, I still need help
4 REPLIES 4
mikekozy
Level 1: Cadet

Re: Cable Ultimate irregular dropouts

To add,
-I often do restart the modem by turning off power, taking out the coax/ethernet, taking out the power, replugging the coax/ethernet putting the power cord back in, turning power on.
-There shouldn't be a major in dust etc, as the line was made from stratch as of a couple of weeks ago.
Brodie_Telstra
Telstra (Retired)
Telstra (Retired)

Re: Cable Ultimate irregular dropouts

Hey Mike,

 

If you have completed all those troubleshooting steps then most likely the fault lies with the connection itself. This may require further testing on our end. Have you contacted our Technical support area to investigate this further?

 

Brodie

 

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

mikekozy
Level 1: Cadet

Re: Cable Ultimate irregular dropouts

Ya I got a technician come in and the connection from the power pole wasn't properly sealed, dirt and moisture was in, and so far so good at the moment.
Shellock
Telstra (Retired)
Telstra (Retired)

Re: Cable Ultimate irregular dropouts

Hi Mike,

 

It's great to hear that one of our techs was able to get this resolved for you. 

 

If you mark this post as resolved, this may help other customers with similar experiences.

 

Need help? Check out our Community Wiki or Support Portal || Looking for a new mobile? Order online today || Get help with any Tech at Home with Telstra Platinum || Don't forget to tag answers as Accepted Solutions and give a Like to the member(s) who helped you out.

All moderation actions are supported by the CrowdSupport Community Guidelines

Set it & forget it

With direct debit there’s no need to give paying your bill another thought.

Avoid queuing up and never worry about late fees again.

Setup direct debit