dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2048

UHF
All static, all day, Forever
MVM
join:2002-05-24

UHF

MVM

[IA] What does this mean?

I see a lot of this sort of thing in my modem event log. At the moment, the connection is bouncing up and down. What does it mean?

Fri Sep 12 14:14:19 2014   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=00:26:24:ac:63:26;CMTS-MAC=6... 
 Fri Sep 12 14:14:19 2014   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Fri Sep 12 14:14:11 2014   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:26:24:ac... 
 Fri Sep 12 14:14:02 2014   Critical (3)  DCC aborted unable to communicate on new upstream channel;CM-... 
 Fri Sep 12 14:14:02 2014   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Fri Sep 12 14:13:50 2014   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:26:24:ac... 
 Fri Sep 12 14:13:22 2014   Critical (3)  Started Unicast Maintenance Ranging - No Response received - ... 
 Fri Sep 12 14:13:19 2014   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=00:26:24:ac:63:26;CMTS-MAC=6... 
 Fri Sep 12 14:13:19 2014   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Fri Sep 12 14:13:09 2014   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:26:24:ac... 
 Fri Sep 12 14:12:26 2014   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Fri Sep 12 14:09:56 2014   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=00:26:24:ac:63:26;CMTS-MAC=6... 
 Fri Sep 12 14:09:55 2014   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Fri Sep 12 14:09:47 2014   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:26:24:ac... 
 Fri Sep 12 14:09:37 2014   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Fri Sep 12 14:09:34 2014   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:26:24:ac... 
 Fri Sep 12 14:09:16 2014   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 Fri Sep 12 14:08:44 2014   Notice (6)  TLV-11 - unrecognized OID;CM-MAC=00:26:24:ac:63:26;CMTS-MAC=6... 
 Fri Sep 12 14:08:44 2014   Warning (5)  DHCP WARNING - Non-critical field invalid in response ;CM-MAC... 
 Fri Sep 12 14:08:35 2014   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=00:26:24:ac... 
 Fri Sep 12 14:08:06 2014   Critical (3)  Unicast Ranging Received Abort Response - Re-initializing MAC... 
 

MediacomChad
Mediacom Social Media Relations Team
Premium Member
join:2010-01-20
Gulf Breeze, FL

MediacomChad

Premium Member

Hello UHF See Profile,

These errors are normally generated by signal related problems. Could you IM me the MAC ID of the modem you're currently using? I'll look into this and see what I can find out.

thedragonmas
Premium Member
join:2007-12-28
Albany, GA
Netgear R6300 v2
ARRIS SB6180

thedragonmas to UHF

Premium Member

to UHF
some one with more detailed knowledge can answer better, but id post your signal levels.

keep in mind these are in reverse, so they are actually..

Critical (3) Started Unicast Maintenance Ranging - No Response received connection lost modem will now try to reconnect

Critical (3) No Ranging Response received - T3 time-out modem tried to range on known channel, but mediacoms equipment did not reply in time

Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC mediacoms equipment has sent an abort request, modem will now try to reconnect and reprovision

Critical (3) DCC aborted unable to communicate on new upstream channel mediacom told modem to use a different upstream channel, but modem cant talk to mediacom on this channel, it will now abort trying on this channel and try a different channel

Critical (3) No Ranging Response received - T3 time-out connection still lost, modem modem is still trying to reconnect

Warning (5) DHCP WARNING - Non-critical field invalid in response mediacom sent some weird info with the DHCP header, its not standard thus its invalid, modem will ignore

Notice (6) TLV-11 - unrecognized OID this one i have no idea about, but its only a notice so not connection criticle

these are my best guesses and may be completely wrong, but its what i gather is going on based on years of troubleshooting my own connection before reaching out to mediacom, otheres may have more accurate information.

edit: and chad got in before i was done typing

dsm9
@97.125.179.x

dsm9 to UHF

Anon

to UHF
Just started having the same errors and issue in des moines this afternoon using a motorola sb6121. Signal levels are good and haven't changed.

MediacomChad
Mediacom Social Media Relations Team
Premium Member
join:2010-01-20
Gulf Breeze, FL

MediacomChad

Premium Member

Hey dsm9, can you send me an IM with your phone, account number, or address so I can look into the issue you're having?

dsm9
@97.125.179.x

dsm9

Anon

When people on Mediacom's support forum create a new topic about this specific issue after apparently seeing the pattern, then Mediacom certainly should see it as well and be more forward about the issue:
»forums.mediacomcable.com ··· =23177.0
said by MediacomChad:

Hey dsm9, can you send me an IM with your phone, account number, or address so I can look into the issue you're having?


kwbelt1
join:2006-06-03
Harrisburg, IL

kwbelt1

Member

I've been getting T3, T4 time outs and reboots for a couple months .

UHF
All static, all day, Forever
MVM
join:2002-05-24

UHF

MVM

Mediacom was JUST HERE to fix the "signal level issues". I can't remember if it was last Friday or the one before that. But other say they are having the same issues at the same time, so I'll assume it's not an issue on this end.

dsm9
@97.125.179.x

dsm9 to kwbelt1

Anon

to kwbelt1
Some T3 and T4 errors, especially spread out, are normal. What many Mediacom customers are reporting as of late is not normal when they occur every few minutes or so and cause modem resets.

Your issue may be due to a signal issue if it has been occurring for months.

Based on reports here and on Mediacom's website it is appearing that there is some sort of issue, possibly related to specific hardware, that is showing up on the upstream and may be the result of upstream channel bonding work and is something fairly recent within the past few weeks.
said by kwbelt1:

I've been getting T3, T4 time outs and reboots for a couple months .