Access point crashing Sagemcom F@st 3284 cable modem /router

[eross1]

My setup:
Sagemcom F@st 3284 is my cable modem /router (which I got from the cable company) . Phone modem disabled. DHCP and wireless enabled.
I have a TP-Link router model TL-WDR4300 configured as Access Point only, connected with CAT5 cable to the F@st 3284. The DHCP on the TP-LINK is disabled. WAN is configured as fake static IP 192.168.111.111 subnet 255.255.255.0 and gateway 192.168.111.1
Before the F@st 3284 I had a Sagemcom F@st 3184 connected to the same access point without any problems.
Since I changed to F@st 3284 , 3 times a day at different intervals, the F@st 3284 loses the internet connection and has to re-sync. The power light is still on, but all other light go off. This typically take 85-90 seconds.
The intervals between the disconnections vary from 5-12 hours, but always 3 times a day.
I disabled everything I could on the access point, other than the wireless - but nothing changes. I also tried an older TP-Link router, configured the same way - same disconnections.
Any ideas what can cause this? (needles to say the cable company and Sagemcom are clueless).

 

[Ralston18]

ISP cable ------>F@st3284[LAN port] -----CAT5 Ethernet cable------->[LAN Port]TP-LINK(AccessPoint) ----->wired/wireless devices. Correct?

F@st3284 IP is 192.168.111.1, TP-LINK is 192.168.111.111 (static, reserved, outside the allocated DHCP range established on the F@st3284).

As I understand your post everything (IP's, devices, etc.) is the same with the exception of the F@st3284 cable modem/router itself. And you tried the older TP-Link Router as a replacement for the Access Point using the original configuration.

Are there any errors or warnings in the logs for the F@st3284 and the TP-LINK(s) Access Point?

Try disabling the wireless on the access point. Just as a matter of elimination.

If the logs and disabling AP wireless do not provide any additional information then the F@st3284 is suspect.

Ask Sagemcom for a replacement F@st3284. That seems to be the only variable between no disconnects and disconnects.

Cannot explain the random disconnections of 5 - 12 hours,would think maybe overheating. But the consistent 3 times a day is interesting and negates overheating I think.

 

[eross1]

Thanks for the reply.
The cable modem/router F@st3284 was replaced with a new one - no change.
The log of the last disconnection on the F@st3284 is this:
Tue Mar 22 12:16:10 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Tue Mar 22 12:15:23 2016 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=7c:b7:...
Tue Mar 22 12:15:22 2016 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=7c:b7:...

Other times it's just:
Tue Mar 22 01:32:45 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Mar 21 18:45:58 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Mar 21 09:56:56 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Mar 21 00:32:07 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Mar 20 18:54:30 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Mar 20 13:06:19 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sun Mar 20 05:37:33 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 19 22:21:57 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 19 16:34:57 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Sat Mar 19 12:28:34 2016 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...

As you can see the error messages are clipped.

 

[Ralston18]

Google this:

"Received Response to Broadcast Maintenance Request, But no Un... "

You will find quite a number of related links/problems/solutions.....

Here is a bit of an explanation from another website:

"T3 Timeout ( Ranging Request Retries Exhausted )

Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request."

Not the final answer/solution per se but the log entries and the links I found point to an ISP related problem. However, the problem could also be physical with respect to degraded signal strength via faulty cable and connections or splitters.

You may be able to access the F@st3284 admin pages and see the various upstream and downstream signal statistics, SNR, etc. If you can capture that information screen and post it here, someone may be able to tell if your results are out of spec.

Again, not at an end answer per se but the logs and tools you have can narrow it down.

And if you peruse a few other links you may note something of further interest and applicability as you know your own system better than anyone.

Then you can go back to Sagemcom and see if you can get a tech out to fix things.

 

[eross1]

A few techs from the cable company have been here and checked and replaced all connectors. They checked the box outside the house as well. My power levels are good:

At first, I was sure it was an ISP network problem. But now I have narrowed it down to whether or not an Access point is connected to my network. I just don't understand why it would cause this.

 

[Ralston18]

Channel 5: 33 "Correctables", 36 "Uncorrectables".

Way out of line with the other channels.

To be honest I will need to look at that a bit more later as time is short at the moment.

Felt it best to at least point out the discrepency until I can look at the manual and a couple of other things.

Can you see the logs in the TP-Link/Access Point?

 

[eross1]

TP link system log not very helpful:
####################################################################
# TL-WDR4300 System Log
# Time = 2013-01-06 10:13:00 468781s
# H-Ver = WDR4300 v1 00000000 : S-Ver = 3.15.33 Build 131016 Rel.53333n
# L = 192.168.1.2 : M = 255.255.255.0
# W1 = STATIC IP : W = 192.168.111.111 : M = 255.255.255.0 : G = 192.168.111.1
####################################################################

1st day 00:00:07 [global]
workgroup = WORKGROUP
netbios name = SOHO router
server string =
log file = /tmp/samba/var/%m.log
max log size = 5
log leINFO
1st day 00:00:12 SECURITY INFO PPTP Passthrough diabled
1st day 00:00:12 SECURITY INFO L2TP Passthrough diabled
1st day 00:00:12 SECURITY INFO IPSEC Passthrough diabled
1st day 00:00:12 SECURITY INFO FTP ALG disabled
1st day 00:00:12 SECURITY INFO TFTP ALG disabled
1st day 00:00:12 SECURITY INFO H323 ALG disabled
1st day 00:00:12 SECURITY INFO RTSP ALG disabled

 

[Ralston18]

Is your network name really "WORKGROUP" or is that just hardwired into the router? (As my Linksys is.....)

The TP Link date-time stamp is incorrect. That can throw things off also. Reset the date and time.

IPs look okay as I understand your network so far.

Need to find an opportunity to look through the User Manual/Guide for your TP Link. Not sure about all those disabled Security settings. May need one of them (or something else) configured so the TP Link and the F@st3284 can communicate properly. In all honesty I am not seeing it yet....

Hopefully some other reader will spot something and post accordingly.

 

[eross1]

I fixed the time settings - still disconnects. The WORKGROUP is not a setting I can change. It's probably as you stated "hardwired into the router".