AP-650 as a sensor

M Michael Elin 3 years 7 months ago
1 2 0

Having problems while tring to configure AP-650 (AP-0650-66030-WW) as a sensor according to 72E-135967-0, Rev A http://support.symbol.com/support/search.do?cmd=displayKC&docType=kc&ex… Using document proposed point-to-point ethernet configuration with PoE injector in between, AP never gets an IP. Wireshark shows just CAPWAP L2 requests, which are counts incrementally and indefinitely and DHCP requests. With DHCP server in place, AP gets an ip and DNS than tried to resolve some addresses such as WISPE_ADDRESS to find the switch and make an adoption, fails with it, than releases IP and process restarts in a loop. Both scenarios IMHO are absolutely normal behaviour. Having IP temporary AP rejects any SSH session requests, as well as having permanent IP while L3 adopted to the switch. There are no option to convert AP-650 to the sensor using GUI. Can someone help me with this, cause our partner tries to propose AP-650 as a 11n sensors to airport, which already have ~40 AP-300 based sensors.

Please Register or Login to post a reply

2 Replies

N Nathan Rowe

Michael -- I think Jared hit on the problem.  The AP650 needs to be running WiNG 5.0 code before the steps in the document to convert it to a sensor can be attempted.  From what you describe not being able to SSH to it and the traffic you see in wireshark it sounds like it is running 4.x.  If the customer orders the sensor part numbers shown below they will be upgraded to 5.0 before being shipped.

AP-0650-6001S-WW

AP-0650-6603S-US

AP-0650-6603S-WW

AP-0650-66040S-US

AP-0650-66040S-WW

AP-0650-60010S-US

AP-0650-60020S-US

AP-0650-60020S-WW

Of course if the customer or you in the lab had a RFS4000 running WiNG 5.0 and adopted an AP650 running 4.x code it would automatically upgrade and then be converted to a sensor following to steps in the document Jared provided.

J Jared Ebel

What version of code are you running on the AP-650?  You should use 5.0.0.0-107R for sensor operation, even in a Wi-NG 4.X WLAN environment.  A Wi-NG 4.X AP-650 cannot be managed via SSH.  The easiest way to give the AP an IP address in the direct connect configuration is by running a DHCP server like tftpd32 on your PC. Use the attached How-To Guide for AP-650 sensor configuration.  The one provided at your link is a bit dated.  Be sure to execute the commands listed in the "Co-Existence with Wireless Controllers running WiNG 4.X" section.  This will ensure the AP-650 does not get downgraded when placed on the same L2 segment as a Wi-NG 4.X controller.

CONTACT
Can’t find what you’re looking for?