This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

AP30's not showing up as active

Greetings, 

I've got 4 AP30 devices. One is doing just fine.

The other 3 were disconnected for a construction project.

I'm guessing there was an update to the AP30's while they were disconnected, and now they don't react to the UTM.

These 3 AP30's will not show up as active in the UTM portal.

I've looked at the DHCP log, and what I see is endless DHCPDiscovers and offers (shown below). 192.168.1.52 is a correct IP for this device. This is a VLAN'd interface, but it will time out, and then try the non-VLAN'd interface ETH0, with the same result (different IP address. but appropriate, is offered to ETH0). Nothing ever shows up in the DHCP Lease table.

Ideas??? - Thanks, Mark

2018:06:04-18:55:23 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:23 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:26 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:26 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:29 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:29 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:32 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:32 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:35 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:35 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:38 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:38 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:41 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:41 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:44 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:44 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:47 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:47 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:50 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:50 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:53 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:53 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:56 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:56 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:59 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:55:59 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:02 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:02 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:05 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:05 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:08 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:08 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:11 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
2018:06:04-18:56:11 vpn dhcpd: DHCPOFFER on 192.168.1.52 to 00:1a:8c:07:f4:d8 (AP30-A40001F8E5C31D3) via eth2.1
 
2018:06:04-19:07:50 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:51 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:53 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:53 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:56 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:56 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:59 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:07:59 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:08:02 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:08:02 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:08:05 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:08:05 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:08:08 vpn dhcpd: DHCPDISCOVER from 00:1a:8c:07:f4:d8 via eth0
2018:06:04-19:08:08 vpn dhcpd: DHCPOFFER on 192.168.5.100 to 00:1a:8c:07:f4:d8 via eth0


This thread was automatically locked due to age.