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

Problem with AP30

Hello.
We have an ASG320 (9.205-12) and different AP30 in different vlans.

There's one AP30 which doesn't work correct. It gets an IP from our windows dhcp server, but the Power LED Display stays only on for a few seconds (during this time the AP is shown as active in the admin interface of the utm and the AP answers pings to the IP). Then the Power LED changes to off (AP to inactive and no response to ping). This goes on and on. Another AP at the same cables works without problems. So it looks like the AP is broken.

When I take this AP to my office, which is in another vlan but also not the same as the utm, it works without a problem. So it looks like the AP isn’t broken.

While searching in the forum, I found that it could be a problem with the vlans (although it shouldn’t be, because another AP at the same connection works without a problem). So I distributed DHCP Option 234 (Verbindung zwischen Sophos Accesspoints und Sophos UTM | ictschule – sorry in German), but still the same result.

Thanks for any help.

This thread was automatically locked due to age.

0 Scott_Klassen over 10 years ago

Could be a power issue. How is the AP powered? Power brick or PoE? If PoE, by switch or injector?

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel
0 ckruesi over 10 years ago

PoE over injector. The same injector at my office and for the test with the other AP. Also tried with a second injector.
Cancel
Vote Up 0 Vote Down

Cancel
0 GuyFawkes over 10 years ago

When I take this AP to my office, which is in another vlan but also not the same as the utm, it works without a problem. So it looks like the AP isn’t broken.

This is a normal, you must be in the same subnet (IP - 1.2.3.4 goes to the default GW).
The AP starts an try to connect to the UTM, then the AP gets the new firmware and the configuration. After these two steps, the AP is able to connect to the UTM in a different subnet/VLAN. After the configuration transfer you can change the VLAN Ports on the switch [;)]

Nice greetings
Cancel
Vote Up 0 Vote Down

Cancel
0 ckruesi over 10 years ago in reply to GuyFawkes

Thanks for your answer. My office isn’t in the same subnet as the umt. So that would not explain, why the AP works there. Furthermore the dhcp option 234 should take care of the problem with the different subnets (even this wasn’t a problem until now), shouldn’t it?

But meanwhile the AP doesn’t work even in the office. I tried to manually re-flash it (Sophos Accesspoint: Firmware manuell einspielen | ictschule - sorry, again in german, but with many pictures). It looked like it would work (7892 tftp pakets sent and acknowledged between 192.168.99.8 and 192.168.99.9). Then it tries to re-flash from utm (blinking Power LED) but that doesn’t work.

Thanks
Cancel
Vote Up 0 Vote Down

Cancel
0 GuyFawkes over 10 years ago

Please, for flashing the AP, use the original Sophos tool.
How to recover a Sophos RED device / Sophos Access Point

Oh, I've vergotten the IP... the AP tries to connect to 1.2.3.4 and this IP you must route to the Sophos UTM.

Here is a good article for you, have you tried that?:
How to troubleshoot registration issues for the Sophos Access Point

Nice greetings
Cancel
Vote Up 0 Vote Down

Cancel
0 ckruesi over 10 years ago in reply to GuyFawkes

Hello GuyFawkes

Thanks for your answer.

Oh, I've vergotten the IP... the AP tries to connect to 1.2.3.4 and this IP you must route to the Sophos UTM.

Here is a good article for you, have you tried that?:
How to troubleshoot registration issues for the Sophos Access Point

This article was the reason I deployed DHCP option 234.

Please, for flashing the AP, use the original Sophos tool.
How to recover a Sophos RED device / Sophos Access Point

Thanks for this link. I tried the one from this BB entry: https://www.astaro.org/other-products/wireless-security/40866-reflashing-bricked-aps-ap10-30-50-a-3.html#post223706. With the new one, the flashing worked (I've updated my documentation on Sophos Accesspoint: Firmware manuell einspielen | ictschule. So I hope it will work at the other place also. Thanks again.
Cancel
Vote Up 0 Vote Down

Cancel
0 ckruesi over 10 years ago in reply to ckruesi

It doesn't work at the other place. I reflashed it again and I tried it with dhcp option 234 and with a route of 1.2.3.4 to the utm. All the other APs work without a problem. So maybe it's time to replace this one...
Cancel
Vote Up 0 Vote Down

Cancel
0 ckruesi over 10 years ago in reply to ckruesi

Just for feedback. I tested it again today after a Firmware upgrade of the utm to Version 9.206-35 (UTM Up2Date 9.206 Released | Sophos Blog). Now it works. Thanks for your help!
Cancel
Vote Up 0 Vote Down

Cancel