topic Great to hear that.You can in Wireless

New Air-Cap3502e Access Point

ivadministrator — Mon, 05 Jul 2021 10:23:35 GMT

Hello!

I am trying to add a new Access Point to an existing 5508 Wi-Fi controller. The instructions in the Cisco materials say just to have the controller set to "Master," which I did, then plug the AP into the network switch - and of course the switch must be able to access the controller, etc. All of that is done. It then says that the LED will eventually turn solid green, and the AP can then be configured from the WLC. I plugged this new AP into the same switch port as an existing AP, however the LED continues to flash Blue-Green-Red-Off.

I cannot find any documentation on how to connect via the Console, or anything else to do at this point.

I would really appreciate some assistance!

Thank you!

Hi

Rasika Nayanajith — Fri, 12 Jun 2015 01:20:29 GMT

You have to configure one of WLC discovery methods (DHCP option 43, DNS, Broadcast forwarding, static) unless AP management & WLC management are on two different vlans.

If you have AP console access & AP gets IP properly, you can try below.

LWAP-01#debug capwap console cli

LWAP-01#capwap ap primary-base [WLC name] [WLC_Mgt_IP_Add]

Refer below for more details

http://mrncciew.com/2013/03/17/ap-registration/

http://www.cisco.com/c/en/us/support/docs/wireless/4400-series-wireless-lan-controllers/99948-lap-notjoin-wlc-tshoot.html

If no luck, please attache full AP console output when it trying to register

HTH

Rasika

*** Pls rate all useful responses ***

Thank you. That info is

ivadministrator — Fri, 12 Jun 2015 16:00:35 GMT

Thank you. That info is useful. As I mentioned in the first post, I don't know how to connect to the AP via the console. Do I just do a network cable between the AP Console port and a laptop? If so, then use Putty or??? Putty needs the device to have an IP address.

So I am at the more basic problem level.

Thank you.

Here is a good doc to follow

Scott Fella — Fri, 12 Jun 2015 16:05:28 GMT

Here is a good doc to follow regarding the console:

https://supportforums.cisco.com/document/12341/how-console-cisco-aironet-access-points-and-bridges

-Scott

The disconnect here is that

ivadministrator — Fri, 12 Jun 2015 16:13:42 GMT

The disconnect here is that the Air-Cap3502 doesn't have an RS-232 port. It only has an RJ-45 port for the Console, and a separate RJ-45 port for the Ethernet connection.

What can I use for this type of AP?

You need a console cable and

Scott Fella — Fri, 12 Jun 2015 16:25:13 GMT

You need a console cable and a USB to serial adapter.

-Scott

Here is another link you can

Scott Fella — Fri, 12 Jun 2015 16:34:15 GMT

Here is another link you can use to reference. If you don't have a Cisco console cable, you will need to buy one or make one. You don't have to use a Cisco brand cable, but the pinout needs to be the same.

http://www.cisco.com/c/en/us/td/docs/wireless/access_point/12-4-25d-JA/Configuration/guide/cg_12_4_25d_JA/scg12-4-25d-JA-chap4-first.html#wp1103336

-Scott

Thank you. I now have my PC

ivadministrator — Fri, 12 Jun 2015 17:39:35 GMT

Thank you. I now have my PC connected by a "DB-15 to DB-9" cable, to a Cisco Console cable into the AP's RJ045 port (Cisco Air-Cap3502).

I use Putty set to "Serial, Com1 (also tried Com2), 9600, 8 data bits, 1 stop bit, no Parity (also tried Odd and Even), Flow Control (tried both XON/XOFF, and None).

All I get is "Unable to open connection to COM1. Unable to open serial port."

Any suggestions?

I have tried the instructions provided for resetting to factory defaults, however those instructions are for a different series of models, and do not match what happens on this device.

Can you provide a link to the "new config for a 3500" manual?

Thanks again.

All I get is "Unable to open

Leo Laohoo — Sat, 13 Jun 2015 05:43:47 GMT

All I get is "Unable to open connection to COM1.  Unable to open serial port."

Try different COM ports.

I now have my PC connected by a "DB-15 to DB-9" cable

This "cable" could be another issue. Can you try a different PC with a serial port?

you do need the right cable

Scott Fella — Sat, 13 Jun 2015 14:15:07 GMT

you do need the right cable and the right USB to serial adapter. If you don't see the USB to serial in the device manager, then that USB to serial isn't compatible with your OS. If you see the USB to serial adapter and you can't open the port, then like Leo stated, your cable it wrong or it's something with your laptop. You can just buy this and be done with it:

http://www.get-console.com/shop/en/18-usb-to-serial-cables

-Scott

The cable from here did the

ivadministrator — Tue, 16 Jun 2015 23:01:55 GMT

The cable from here did the trick!

So I am the console now, and

ivadministrator — Tue, 16 Jun 2015 23:09:57 GMT

So I am the console now, and am interacting. I have entered the following trying to go the static IP approach:

capwap ap ip address 192.168.201.21 255.255.255.224

capwap ap ip default-gateway 192.168.201.1

capwap ap controller ip address 192.168.201.2

I still just get, "*Jun 16 15:32:58.361: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)"

I then did:

Debug capwap console cli

capwap ap primary-base iv-wlc 192.168.201.2

(which IS the correct WLC name and Mgmt IP address) and I still just get the same error message.

You then noted, "If no luck, please attach full AP console output when it trying to register."

Please excuse the novice questions: How can I tell it to try to re-register? What is the command to save what I have already entered in?

Thank you.

You simply need to copy the

Rasika Nayanajith — Tue, 16 Jun 2015 23:19:59 GMT

You simply need to copy the console output messages to text file and attach it to here. Ie there should be more messages than below lines.

*Jun 16 15:32:58.361: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)"

Rasika

Well, good news. I found I

ivadministrator — Tue, 16 Jun 2015 23:28:55 GMT

Well, good news. I found I had a typo in the IP address, and once I fixed it, I can now see it in the controller.

Thank you!

Great to hear that.You can

Rasika Nayanajith — Wed, 17 Jun 2015 00:18:26 GMT

Great to hear that.

You can rate our responses if that helps you.