Searching for something?
Reply
Fresh as a Daisy
Benjami
Posts: 3
Registered: ‎10-12-2011

DHCP FAILED - Request sent, No response

Hi

 

I posted earlier but thought I would start my own topic as the problem still persists.

 

This problem has been on/off for the last few years and numerous visits from Technicians failed to fix the problem in the long run. I would switch providers but it is so much hassle so I would prefer if it could be fixed :smileyhappy:

 

Here are my logs:

 

TimePriorityDescription
 Sat Dec 10 22:41:00 2011   Critical (3)  DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Sat Dec 10 22:40:54 2011   Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Sat Dec 10 20:48:09 2011   Critical (3)  DHCP FAILED - Requested Info not supported.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 Sat Dec 10 20:21:59 2011   Critical (3)  Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 Sat Dec 10 20:16:19 2011   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Sat Dec 10 20:12:39 2011   Critical (3)  DHCP FAILED - Request sent, No response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Sat Dec 10 20:00:52 2011   Critical (3)  SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Sat Dec 10 19:44:20 2011   Critical (3)  Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 Sat Dec 10 19:28:08 2011   Critical (3)  REG RSP not received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 
 Time Not Established  Critical (3)  DHCP FAILED - Requested Info not supported.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Critical (3)  No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Warning (5)  Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Warning (5)  MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Critical (3)  SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 
 Time Not Established  Critical (3)  DHCP FAILED - Requested Info not supported.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.0;CM-VER=3.0; 

 

 

Startup Procedure
ProcedureStatusComment
Acquire Downstream Channel450250000 HzLocked
Connectivity StateIn progressAccess Denied
Boot StateOKOperational
Configuration FileOK 
SecurityIn progressDisabled

Downstream Channels
Lock StatusModulationChannel IDMax Raw Bit RateFrequencyPowerSNRDocsis/EuroDocsis locked
LockedQAM643541712000 Kbits/sec450250000 Hz8.6 dBmV37.3 dBHybrid
LockedQAM643341712000 Kbits/sec434250000 Hz8.5 dBmV37.1 dBHybrid
LockedQAM643441712000 Kbits/sec442250000 Hz8.9 dBmV37.2 dBHybrid
LockedQAM643641712000 Kbits/sec458250000 Hz8.3 dBmV36.9 dBHybrid
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV0.0 dBUnknown
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV0.0 dBUnknown
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV0.0 dBUnknown
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV0.0 dBUnknown

Upstream Channels
Lock StatusModulationChannel IDMax Raw Bit RateFrequencyPower
LockedATDMA120480 Kbits/sec45800000 Hz42.3 dBmV
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV
UnlockedUnknown00 Ksym/sec0 Hz0.0 dBmV
 

Primary Downstream Service Flow
Downstream(0)
SFID13424
Max Traffic Rate33330000 bps
Max Traffic Burst3044 bytes
Mix Traffic Rate0 bps

Primary Upstream Service Flow
Upstream(0)
SFID13423
Max Traffic Rate3333000 bps
Max Traffic Burst8160 bytes
Mix Traffic Rate0 bps
Max Concatenated Burst8160 bytes
Scheduling TypeBest Effort

 

Cheers for any help and please message me if you need any more information.

 

Thanks

 

Ben

Please use plain text.
Brainbox
michelle190
Posts: 166
Registered: ‎30-11-2011

Re: DHCP FAILED - Request sent, No response

Power levels dont look right on the downstream, too high.

 

The max traffic rates dont look right either, there both the same?

 

The downstream and upstream should have different max traffic rates.

 

 

 

 

Please use plain text.
Fresh as a Daisy
Benjami
Posts: 3
Registered: ‎10-12-2011

Re: DHCP FAILED - Request sent, No response

Problem still exists this morning which is unusual, normally it fixes itself.

Is there anyway I can adjust the power levels etc myself? I do have a Technician coming out on Tuesday, but I might as well do anything I can till then :smileytongue:
Please use plain text.
Captain Clued-Up
Mark_Wilco
Posts: 2,088
Registered: ‎19-10-2011

Re: DHCP FAILED - Request sent, No response

Hi Benjami

 

Power levels need to be adjusted by a tech,can you let us know if the visit had resolved this?

Mark_Wilco
Help & Support Forum Team

If someone's helped you out say thanks by clicking on the Kudos Star. If someone's solved your problem, why not mark their message as a Helpful Answer? You can also help other users find useful posts by Tagging them with keywords.
Got a problem? Check for faults online with our new service status and fault checker


If you are new to the forum, please remember to search the forum before posting your question. Please don't send private messages directly to the forum team unless they ask you to, post your issue to the forum first.
Please use plain text.