Hap AX2 Rebooting during fast transmission - power issues?

Hey there, I have been racking my brain over this for the past day, for the past few days me AX2 has been rebooting every 5 minutes to 4 hours. With the following in the log every time:

router rebooted without proper shutdown, probably power outage

I have spent the past day upgrading and downgrading firmware (have tried both the testing and the LTS branches, currently on stable). Have tried doing a full factory reset of the router then restoring from an rcs, didn't work. Have tried fiddling all day with my wifi configuration to no success, from changing max tx power, to availble encryption methods, to messing with the DHCP server. It's getting late and I'm about to crash it, so was hoping do you guys have any ideas for what I can try to further diagnose and fix the issue? It's not a CPU temp issue, and CPU usage stays low.

At this current stage I think it must be a PoE in issue, I'm using a PoE injector to power the router and it must be having issues but I don't have any other way to power it for the time being nor any way to test it without committing to buying new equipment.

I'm not a network admin by any means, just a hobbyist, and not a very good one at that. If you guys have any suggestions or ideas to look at in the morning, that would be great. Thank you :slight_smile:

supout (renamed from rif to txt to make it upload):
{ supout removed by mod }

Please remove supout file. It contains sensitive data. Use /export instead (remove serial before posting).

If you already came to this conclusion, why state it is related to fast transmission in the title of your post ?
And how IS it powered right now ? You didn't clarify that either.
You need from 12W up to 27W. What is provided now and how ?

PS supout link removed. As indicated by infabo, this is not something you post on a public place.

Another thing to check: power adapter which is powering the PoE injector.

PAs are not very reliable in sense that they can "age" quite quickly and when they reach their limit, they still provide voltage (at specified level or very close to it so voltage measurements of idle PA won't show significant deviation) but they fail to provide specified current. When powered device tries to draw higher power, voltage drops ... and that in turn might cause device to reboot.

So try to find a replacement power adapter, preferably specified at same voltage and same or higher current as the one you're using now (the original). Jack plug is standard 5.5/2.1 mm (outer/inner diameter).

Thank you, here's the updated file, I read elsewhere that supout already came with sensitive info (as far as I can tell) removed.

# 2026-05-20 19:05:25 by RouterOS 7.22.3
# software id = KJNY-I7NI
#
# model = C52iG-5HaxD2HaxD
/interface bridge
add admin-mac=48:A9:8A:B8:EC:83 auto-mac=no comment=defconf name=bridge
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wifi channel
add band=2ghz-n frequency=2412,2432,2472 name=ch-2ghz width=20mhz
add band=5ghz-ax frequency=5180,5260,5500 name=ch-5ghz width=20/40/80mhz
/interface wifi security
add authentication-types=wpa2-psk disabled=no encryption=ccmp,gcmp management-protection=disabled name=common-auth wps=disable
/interface wifi configuration
add country=Australia disabled=no mode=ap name=common-conf security=common-auth ssid="MikTik AX" station-roaming=no
/interface wifi
# DFS channel availability check (1 min)
set [ find default-name=wifi1 ] channel=ch-5ghz configuration=common-conf configuration.mode=ap disabled=no mtu=1500 \
    security.authentication-types=wpa2-psk .encryption=ccmp,gcmp
set [ find default-name=wifi2 ] channel=ch-2ghz configuration=common-conf configuration.mode=ap disabled=no mtu=1500 \
    security.authentication-types=wpa2-psk .encryption=ccmp,gcmp
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/ip dhcp-server
add address-pool=default-dhcp interface=bridge lease-time=1d name=defconf
/interface bridge port
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge interface=wifi1
add bridge=bridge interface=wifi2
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=bridge list=LAN
add comment=defconf interface=ether1 list=WAN
/ip address
add address=192.168.88.1/24 comment=defconf interface=bridge network=192.168.88.0
/ip dhcp-client
add comment=defconf interface=ether1 name=ether1
/ip dhcp-server lease
add address=192.168.88.254 mac-address=00:1C:27:21:A2:8E server=defconf
add address=192.168.88.30 client-id=1:c:9d:92:86:cf:cd mac-address=0C:9D:92:86:CF:CD server=defconf
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan type=A
/ip firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment="defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat connection-state=new \
    in-interface-list=WAN
add action=fasttrack-connection chain=forward connection-state=established,related
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" dst-port=33434-33534 protocol=udp
add action=accept chain=input comment="defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=udp src-address=\
    fe80::/10
add action=accept chain=input comment="defconf: accept IKE" dst-port=500,4500 protocol=udp
add action=accept chain=input comment="defconf: accept ipsec AH" protocol=ipsec-ah
add action=accept chain=input comment="defconf: accept ipsec ESP" protocol=ipsec-esp
add action=accept chain=input comment="defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=input comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
add action=fasttrack-connection chain=forward comment="defconf: fasttrack6" connection-state=established,related
add action=accept chain=forward comment="defconf: accept established,related,untracked" connection-state=established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf: drop packets with bad src ipv6" src-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: drop packets with bad dst ipv6" dst-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: rfc4890 drop hop-limit=1" hop-limit=equal:1 protocol=icmpv6
add action=accept chain=forward comment="defconf: accept ICMPv6" protocol=icmpv6
add action=accept chain=forward comment="defconf: accept HIP" protocol=139
add action=accept chain=forward comment="defconf: accept IKE" dst-port=500,4500 protocol=udp
add action=accept chain=forward comment="defconf: accept ipsec AH" protocol=ipsec-ah
add action=accept chain=forward comment="defconf: accept ipsec ESP" protocol=ipsec-esp
add action=accept chain=forward comment="defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=forward comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
/ipv6 nd
set [ find default=yes ] advertise-dns=yes
/system clock
set time-zone-name=Australia/Sydney
/system logging
set 3 action=disk
/tool e-mail
set certificate-verification=no
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

If you already came to this conclusion, why state it is related to fast transmission in the title of your post ?

I'm really not totally certain that it is power related, as the logs say. I'm skeptical that after about a year that the power supply is failing. I have confirmed it's not the wiring of my house so if it is something directly power related, it would need to be an issue with the PSU. What I *do* know is that the problem seems to coincide with fast wireless transmission.

Even though I'm skeptical, the only untested thing is the powersupply as I don't have a replacement on hand. If it is a power issue, it'd be the transmission causing a spike in power usage. But before I spend $50+ to test that, I'm just checking to make sure I haven't missed any other potential causes for it.

And how IS it powered right now ? You didn't clarify that either.

It's powered by a PoE injector plugged into a wall outlet. 24v 3a here.

Indeed. But contains a lot of unneeded information for forum users.

If you are using Mikrotik RBGPOE, that can cause problems, I have seen quite a few misbehaving and I fixed APs just by replacing with another (new) RBGPOE.

This sounds very much like some sort of hardware failure.

Mikrotik's devices, that they do some of the quality control for, are surprisingly well made for their price point. My guess would be something around the power supply and injector as well. If you have another suitable power supply, attach that directly to the device temporarily, and then start reintroducing the other components.

You are right that the log message shouldn't be taken at face value, but power supply failure is far more common than failures of the devices themselves. There is no set-in-stone time limit for these to occur, and as is probably the case here, PSU failure is often not instantaneous and total, but soft and insidious.

Did you test it without the POE, (normal plug-in) would have been my first troubleshooting step???

Hey guys, thought I'd update here, I bit the bullet and bought a new power supply for the router, it's been plugged in for two days now and I have yet to see a reboot. This time it's just a regular power supply not a PoE injector. I would have originally tested with the power supply that came with the router but I had lost access to it but the new power supply seems to be working fine.

Thank you guys for the suggestions and help :slight_smile: