With this command, no more AP lost in the dark, far from its controller!

MwarName (these are the primary, secondary, tertiary controllers) Once the AP is configured, you can use the show lwapp family of commands to check what is going on, such as the show lwapp ip config to check your AP IP details, or the show lwapp client config to check controller config and friends:ĪP0023.0410.4aea#show lwapp client config A useful one is the AP IP address:ĭefault-gateway Configure Default-gateway IP addressĬonfigure both! The AP needs both to get out of the local network. You can also give some other information to your AP, such as AP hostname, or syslog IP address where to dump all issues that the AP might encounter while trying to get to your controller. You AP knows how to get to a controller (careful, if your AP is already connected to a controller, using this command does not make any sense anymore, and you get a nice 'ERROR!!! Command is disabled' when you issue it). Log-server Configure the syslog server where all LWAPP errors will be loggedĪs you can see, you can give your AP, in LWAPP mode, information about a controller:ĪP0023.0410.4aea#lwapp ap controller ip ?Īddress Configure primary Controller IP addressĪP0023.0410.4aea#lwapp ap controller ip addĪP0023.0410.4aea#lwapp ap controller ip address ?ĪP0023.0410.4aea#lwapp ap controller ip address 10.1.1.10ĭone. boot the AP, get yourself a console connection, and try: You can configure your AP directly from the CLI to provide information to it. My friend's network is small, so no option 43 or DNS that you can dream of. There is no other AP around, so forget about OTAP. The AP is new, so there is no controller IP address the AP could remember from a previous life (AP priming). Now my friend has an AP at home, and wants to use it to connect to its corporate network over his VPN link (my friend's router to the company VPN concentrator). you know that the AP, upon booting, will try hard to discover a controller, using broadcast, pre-configuration (AP priming as they say) DHCP option 43, DNS, OTAP, etc. I had this case a couple of times and thought it might be useful for all of us.

Cisco lwapp controller