Home

Forums

Stories

Knowledge Base

Home Network Community > Wi-Fi Routers > Ancher A7 suddenly restart

< Wi-Fi Routers

Ancher A7 suddenly restart

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Ancher A7 suddenly restart

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Davidmoran92

2020-06-14 18:39:53 - last edited 2020-08-31 07:09:36

Posts: 1

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-06-14

Ancher A7 suddenly restart

2020-06-14 18:39:53 - last edited 2020-08-31 07:09:36

Model: Archer A7

Hardware Version: V5

Firmware Version: 1.0.14

I have and ancher A7 with a R220 in a one mesh network. Everyday I'm losing signal and noticed that the A7 turns off and restart, I need to wait around 1 minute to have signal again

1 Accepted Solution

Kevin_Z

2020-08-31 07:09:28 - last edited 2020-08-31 07:09:36

Posts: 21542

Helpful: 5003

Solutions: 2536

Stories: 21

Registered: 2018-12-24

Re:Ancher A7 suddenly restart-Solution

2020-08-31 07:09:28 - last edited 2020-08-31 07:09:36

@SumitPune

Hi,

Please check this post directly as we need to verify more details:

https://community.tp-link.com/en/home/forum/topic/179006?page=4

Good days.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX55V2 Supports WireGuard VPN, EasyMesh Ethernet Backhaul, IoT Network, Speed Limit,and More If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.

Recommended Solution

4 Reply

Solla-topee

2020-06-15 09:59:59

Posts: 13141

Helpful: 2249

Solutions: 1829

Stories: 8

Registered: 2020-05-19

Re:Ancher A7 suddenly restart

2020-06-15 09:59:59

@Davidmoran92

Hello,

May I check some details?

1. When you mean the Archer A7 restarts, does it mean the LEDs on its front panel will be flashing off then on automatically? How often does this happen and how will it recover?

2. Is there any specific operation or behavior when it restarts?

3. Are both the A7 firmware and RE220's firmware the latest? If not, please update their firmware first and reconfigure it for a try.

>>Landscape Mode - Tapo App for Pad. >>Smart Action 2.0 Explore and meet the next level home automation. >>How to position my TP-Link camera for optimal performance.

SumitPune

LV1

2020-08-30 13:34:21

Posts: 5

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2020-08-30

Re:Ancher A7 suddenly restart

2020-08-30 13:34:21

@Solla-topee

Hi,

I am also facing the same problem with my Archer A7. It is also restarting multiple times in a day.

The Model details are as follows:

Hardware Version: Archer A7 v5.0

Firmware Version: 1.0.14 Build 20200220 rel.33197(4555)

There is a RE200 connected in Mesh configuration.

Whenever it restarts all the leds switch on and then all leds go off, the center of the body feels a bit warm. And it keeps restarting in loop. Sometimes I have to switch off the mains and wait for 5-10 min. I have also tried factory reset.

The log is erased once it restarts. This is how the log looks like after it restarts:

####################################################################
# Archer A7 System Log
# Time = 2020-08-30 18:34:15
# H-Ver = 5.0.0 ; S-Ver = 1.0.14 Build 20200220 rel.33197
# LAN: I = 192.168.0.1 ; M = 255.255.255.0 ; MAC = CC:32:E5:7C:55:90
# WAN: W = pppoe ; I = 123.201.12.171 ; M = 255.255.255.255 ; MAC = CC:32:E5:7C:55:91
# G = 123.201.12.1 ; D1 = 203.187.215.35 ; D2 = 203.187.215.66
# Clients connected: 5 ; WI-FI : 4
####################################################################
2020-08-30 18:26:45 dhcps[4086]: <6> 212054 send ack ip 192.168.0.207 and dns 192.168.0.1 to e4:a4:71:94:56:f6
2020-08-30 18:26:45 dhcps[4086]: <6> 212053 receive request ip 192.168.0.207 from e4:a4:71:94:56:f6
2020-08-30 18:17:52 dhcps[4086]: <6> 212054 send ack ip 192.168.0.246 and dns 192.168.0.1 to 40:9f:38:dd:17:33
2020-08-30 18:17:52 dhcps[4086]: <6> 212053 receive request ip 192.168.0.246 from 40:9f:38:dd:17:33
2020-08-30 18:17:52 dhcps[4086]: <6> 212052 send offer ip 192.168.0.246 and dns 192.168.0.1 to 40:9f:38:dd:17:33
2020-08-30 18:17:49 dhcps[4086]: <6> 212051 receive discover from 40:9f:38:dd:17:33
2020-08-30 18:06:14 dhcps[4086]: <6> 212054 send ack ip 192.168.0.207 and dns 192.168.0.1 to e4:a4:71:94:56:f6
2020-08-30 18:06:14 dhcps[4086]: <6> 212053 receive request ip 192.168.0.207 from e4:a4:71:94:56:f6
2020-08-30 18:06:14 dhcps[4086]: <6> 212052 send offer ip 192.168.0.207 and dns 192.168.0.1 to e4:a4:71:94:56:f6
2020-08-30 18:06:11 dhcps[4086]: <6> 212051 receive discover from e4:a4:71:94:56:f6
2020-08-30 17:59:52 dhcps[4086]: <6> 212054 send ack ip 192.168.0.111 and dns 192.168.0.1 to 4c:ef:c0:96:b5:b8
2020-08-30 17:59:52 dhcps[4086]: <6> 212053 receive request ip 192.168.0.111 from 4c:ef:c0:96:b5:b8
2020-08-30 17:59:51 dhcps[4086]: <6> 212054 send ack ip 192.168.0.111 and dns 192.168.0.1 to 4c:ef:c0:96:b5:b8
2020-08-30 17:59:51 dhcps[4086]: <6> 212053 receive request ip 192.168.0.111 from 4c:ef:c0:96:b5:b8
2020-08-30 17:59:51 dhcps[4086]: <6> 212052 send offer ip 192.168.0.111 and dns 192.168.0.1 to 4c:ef:c0:96:b5:b8
2020-08-30 17:59:48 dhcps[4086]: <6> 212051 receive discover from 4c:ef:c0:96:b5:b8
2020-08-30 17:59:38 dhcps[4086]: <6> 212054 send ack ip 192.168.0.129 and dns 192.168.0.1 to 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212053 receive request ip 192.168.0.129 from 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212052 send offer ip 192.168.0.129 and dns 192.168.0.1 to 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212051 receive discover from 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212054 send ack ip 192.168.0.123 and dns 192.168.0.1 to 7c:03:5e:06:fe:04
2020-08-30 17:59:38 dhcps[4086]: <6> 212053 receive request ip 192.168.0.123 from 7c:03:5e:06:fe:04
2020-08-30 17:59:38 dhcps[4086]: <6> 212054 send ack ip 192.168.0.123 and dns 192.168.0.1 to 7c:03:5e:06:fe:04
2020-08-30 17:59:38 dhcps[4086]: <6> 212053 receive request ip 192.168.0.123 from 7c:03:5e:06:fe:04
2020-08-30 17:59:38 dhcps[4086]: <6> 212052 send offer ip 192.168.0.129 and dns 192.168.0.1 to 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212052 send offer ip 192.168.0.129 and dns 192.168.0.1 to 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212051 receive discover from 7a:8a:25:eb:5d:06
2020-08-30 17:59:38 dhcps[4086]: <6> 212052 send offer ip 192.168.0.129 and dns 192.168.0.1 to 7a:8a:25:eb:5d:06
2020-08-30 17:59:35 dhcps[4086]: <6> 212051 receive discover from 7a:8a:25:eb:5d:06
2020-08-30 17:59:35 dhcps[4086]: <6> 212052 send offer ip 192.168.0.123 and dns 192.168.0.1 to 7c:03:5e:06:fe:04
2020-08-30 17:59:35 dhcps[4086]: <6> 212051 receive discover from 7c:03:5e:06:fe:04
2020-08-30 17:59:35 dhcps[4086]: <6> 212057 send nak to 4c:ef:c0:96:b5:b8 for wrong server-ID
2020-08-30 17:59:35 dhcps[4086]: <6> 212053 receive request ip 192.168.0.103 from 4c:ef:c0:96:b5:b8
2020-08-30 17:59:35 dhcps[4086]: <6> 212052 send offer ip 192.168.0.123 and dns 192.168.0.1 to 7c:03:5e:06:fe:04
2020-08-30 17:59:32 dhcps[4086]: <6> 212051 receive discover from 7c:03:5e:06:fe:04
2020-08-30 17:59:28 dhcps[4086]: <6> 212054 send ack ip 192.168.0.141 and dns 192.168.0.1 to 50:d4:f7:54:b4:d2
2020-08-30 17:59:28 dhcps[4086]: <6> 212053 receive request ip 192.168.0.141 from 50:d4:f7:54:b4:d2
2020-08-30 17:59:28 dhcps[4086]: <6> 212052 send offer ip 192.168.0.141 and dns 192.168.0.1 to 50:d4:f7:54:b4:d2
2020-08-30 17:59:25 dhcps[4086]: <6> 212051 receive discover from 50:d4:f7:54:b4:d2
2020-08-30 17:59:10 upnp[7898]: <6> 217504 Service start
2020-08-30 17:59:09 upnp[7898]: <6> 217505 Service stop
2020-08-30 17:59:04 nat[7095]: <6> 211501 Initialization succeeded
2020-08-30 17:59:02 nat[7095]: <6> 211501 Initialization succeeded
2020-08-30 17:58:56 dhcps[4086]: <6> 212054 send ack ip 192.168.0.103 and dns 192.168.0.1 to 00:06:78:1d:49:71
2020-08-30 17:58:56 dhcps[4086]: <6> 212053 receive request ip 192.168.0.103 from 00:06:78:1d:49:71
2020-08-30 17:58:56 dhcps[4086]: <6> 212052 send offer ip 192.168.0.103 and dns 192.168.0.1 to 00:06:78:1d:49:71
2020-08-30 17:58:54 dhcps[4086]: <6> 212051 receive discover from 00:06:78:1d:49:71
2020-08-30 17:58:51 qos[6892]: <6> 259504 Service start
2020-08-30 17:58:51 qos[6892]: <6> 259503 Function disabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 IPSEC ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 L2TP ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 PPTP ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 SIP ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 RTSP ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 H323 ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 TFTP ALG enabled
2020-08-30 17:58:44 nat[5554]: <6> 211021 FTP ALG enabled
2020-02-20 00:01:10 ppp[5593]: <6> 261091 ppp receive IPCP ACK
2020-02-20 00:01:10 ppp[5593]: <6> 261090 ppp send IPCP Req options(addr=123.201.12.171;dns1=203.187.215.35;dns2=203.187.215.66;)
2020-02-20 00:01:10 ppp[5593]: <6> 261093 ppp receive IPCP NAK options(addr=123.201.12.171;dns1=203.187.215.35;dns1=203.187.215.66;)
2020-02-20 00:01:10 ppp[5593]: <6> 261090 ppp send IPCP Req options(addr=0.0.0.0;dns1=0.0.0.0;dns2=0.0.0.0;)
2020-02-20 00:01:10 ppp[5593]: <6> 261075 ppp receive PAP AuthAck Authentication success,Welcome!
2020-02-20 00:01:10 ppp[5593]: <6> 261074 ppp send PAP AuthReq user=(sumit212)
2020-02-20 00:01:10 ppp[5593]: <6> 261060 ppp send LCP ACK
2020-02-20 00:01:10 ppp[5593]: <6> 261058 ppp receive LCP Request options(mru=1492;authtype=PPP_PAP;magic=0xec24b50b;)
2020-02-20 00:01:08 nat[5554]: <6> 211501 Initialization succeeded
2020-02-20 00:01:07 factory-reset[6089]: <6> 284504 Service start
2020-02-20 00:01:07 ppp[5593]: <6> 261064 ppp receive LCP ACK
2020-02-20 00:01:07 ppp[5593]: <6> 261061 ppp send LCP Request options(mru=1480;magic=0x8f2c030f;)
2020-02-20 00:01:07 ppp[5593]: <6> 261025 pppoe receive PADS sess-id(5531)
2020-02-20 00:01:07 ppp[5593]: <6> 261024 pppoe send PADR Host-Uniq(15d9)
2020-02-20 00:01:07 ppp[5593]: <6> 261022 pppoe receive PADO form AC-MAC(84:a9:c4:d2:b3:6b)
2020-02-20 00:01:07 ppp[5593]: <6> 261023 pppoe receive PADO AC-Name(PUN-HWI-X8-BRAS-YOUBB-01)
2020-02-20 00:01:07 ppp[5593]: <6> 261021 pppoe send PADI Host-Uniq(15d9)
2020-02-20 00:01:05 nat[5554]: <6> 211501 Initialization succeeded
2020-02-20 00:01:02 ppp[5593]: <6> 261021 pppoe send PADI Host-Uniq(15d9)
2020-02-20 00:01:02 dhcps[4086]: <6> 212054 send ack ip 192.168.0.107 and dns 192.168.0.1 to 0c:9d:92:c9:28:36
2020-02-20 00:01:02 dhcps[4086]: <6> 212053 receive request ip 192.168.0.107 from 0c:9d:92:c9:28:36
2020-02-20 00:00:44 parental-control[5047]: <6> 229504 Service start
2020-02-20 00:00:44 parental-control[5047]: <6> 229502 Function enabled
2020-02-20 00:00:41 nat[3824]: <7> 211001 Flush conntrack
2020-02-20 00:00:41 nat[3824]: <6> 211502 Function enabled
2020-02-20 00:00:41 nat[3824]: <5> 211051 Create NAT chain succeeded
2020-02-20 00:00:37 nat[3824]: <6> 211501 Initialization succeeded
2020-02-20 00:00:35 nat[3824]: <6> 211501 Initialization succeeded
2020-02-20 00:00:31 imb[3740]: <6> 218507 Daemon connection succeeded
2020-02-20 00:00:31 imb[3740]: <6> 218012 ARP Binding disabled
2020-02-20 00:00:31 imb[3740]: <6> 218506 Config interface initialization succeeded
2020-02-20 00:00:31 imb[3740]: <6> 218501 Initialization succeeded
2020-02-20 00:00:29 basic-security[2596]: <6> 219504 Service start
2020-02-20 00:00:29 basic-security[2596]: <5> 219606 Flush conntrack table succeeded
2020-02-20 00:00:29 upnp[3328]: <6> 217504 Service start
2020-02-20 00:00:27 upnp[3328]: <6> 217505 Service stop
2020-02-20 00:00:21 access-control[2565]: <6> 239504 Service start
2020-02-20 00:00:21 access-control[2565]: <6> 239503 Function disabled
2020-02-20 00:00:20 firewall[1049]: <6> 209504 Service start
2020-02-20 00:00:15 modem[1992]: <7> 292032 proto_init_config: proto=qmi
2020-02-20 00:00:10 modem[1478]: <7> 292032 proto_init_config: proto=ncm
2020-02-20 00:00:03 modem[1036]: <7> 292032 proto_init_config: proto=3g
2020-02-20 00:00:00 system[828]: <6> 293200 check num = 00110
2020-02-20 00:00:00 time-settings[806]: <6> 279504 Service start

Kevin_Z

2020-08-31 07:09:28 - last edited 2020-08-31 07:09:36

Posts: 21542

Helpful: 5003

Solutions: 2536

Stories: 21

Registered: 2018-12-24

Re:Ancher A7 suddenly restart-Solution

2020-08-31 07:09:28 - last edited 2020-08-31 07:09:36

@SumitPune

Hi,

Please check this post directly as we need to verify more details:

https://community.tp-link.com/en/home/forum/topic/179006?page=4

Good days.

Ancher A7 suddenly restart

Ancher A7 suddenly restart

Information

Voters 0

Tags