InVision's profile

InVision

New Contributor

 • 

15 Messages

Closed

Cable modem errors

I have been getting the following errors from my SB6183 Cable Modem.  Anyone have a clue what it means?

Thanks,

M

Fri Feb 06 07:01:13 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;
Fri Feb 06 07:00:32 2015 Notice (6) TLV-11 - unrecognized OID;

Discussions

 • 

Updated 

3K

3

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Long answer: The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting the registration process. Typically, this indicates an occasional, temporary loss of service, but if the problem persists, check for possible service outages or maintenance activity on this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request.

Short answer: It can be caused by several things, but mostly if the signal coming into the modem drops or can't be detected for 30-40 seconds. What are your signal levels? 

0

0

I

InVision

New Contributor

 • 

15 Messages

Well I have not seen these messages again unless I reboot modem.  Solution, don't reboot modem.

But I get this message a bunch " DHCP RENEW WARNING - Field invalid in response v4 option.  Solution, not a clue.

I am also getting some bonded channel corrected errors.  What is the norm on this.


Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables
1 Locked QAM256 30 843000000 Hz 3.0 dBmV 40.6 dB    2 0
2 Locked QAM256 29 837000000 Hz 3.1 dBmV 41.2 dB    2 0
3 Locked QAM256 31 849000000 Hz 3.1 dBmV 41.3 dB    0 0
4 Locked QAM256 32 855000000 Hz 3.0 dBmV 41.3 dB    1 0
5 Locked QAM256 33 861000000 Hz 2.6 dBmV 41.2 dB    0 0
6 Locked QAM256 34 867000000 Hz 2.6 dBmV 41.1 dB    1 0
7 Locked QAM256 35 873000000 Hz 2.2 dBmV 40.9 dB    2 0
8 Locked QAM256 36 879000000 Hz 2.3 dBmV 40.2 dB    0 0



Thanks,

M


0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Both of those things are completely normal. DHCP errors are just inherent in the DHCP process. The DHCP server gets busy sometimes so the first few DHCP requests get rejected, but it usually gets it within a second or two, and since DHCP IP's don't have to change for days, or sometimes even months, it's not a big deal. The correctables are a normal part of the TCP process, which if a packet is dropped or unreadable, then it asks to repeat the packet. If you were getting 10-100K a day, then that might cause some lag, but otherwise its normal. Don't worry about it until you start to see uncorrectables, and even then only if alot over a short time.

0

0

Recent Discussions