topic Warrior28,You can try to see in Wireless

Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Sun, 04 Jul 2021 07:40:53 GMT

Straight from the box I have connected the 2602i wireless access point to the cable LAN and I can ping its default IP 192.168.1.1. When I try to access the AP using web-browser it fails I guess because web access is disabled by default. I'm unfamiliar with the commands on the system.

Can somebody help with the commands.

Thanks in advance

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Tue, 20 Aug 2013 11:39:30 GMT

Console into the ap and issue a show version or let us know the model number of the AP. if the model starts with a AIR-CAP then it's a lightweight and you can't web into those. You need a wlc for that model ap. if the model starts with AIR-SAP, then it's a standalone and you should be able to GUI into that.

When you console into the ap, the default username is cisco and the password is cisco. If the ap is a standalone, you should be able to enter enable at the ap prompt ">" and then enter cisco for that enable password. Then you issues a config t and then ip http server.

That command allows GUI access.

Sent from Cisco Technical Support iPhone App

Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Tue, 20 Aug 2013 17:15:21 GMT

Thanks for the reply.

The model is AIR-CAP2601i. I have got a 2504 wlc. What's the procedure? How do I let the AP find the controller? I couldn't even find the command to set the AP's IP address.

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Tue, 20 Aug 2013 17:29:01 GMT

Put the ap on the same subnet as the wlc. It will discover the wlc via layer 2 broadcast and will join. Once joined you can move the ap into any other vlan.

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Tue, 20 Aug 2013 17:30:00 GMT

Here is a doc you can reference also. This explains the ap registration process.

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Tue, 20 Aug 2013 18:00:36 GMT

Thanks Scott

I think you forgot to insert the link to the document.

Re: Failing to Access Web Interface of 2602i AP

Abhishek Abhishek — Tue, 20 Aug 2013 18:59:07 GMT

Hello,

As per your query i can suggest you the following solution -

Make sure that the Cisco wireless LAN controller DS port is connected to the network. Use

the CLI, web-browser interface, or Cisco WCS procedures as described in the appropriate

Cisco wireless LAN controller guide.

Hope this will help you.

Re: Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Tue, 27 Aug 2013 09:39:58 GMT

I have put the AP within the same subnet as the controller. On the controller I can now see that the AP has joined and has acquired IP address but am still not geting any wireless signal from the AP itself. (See picture below from web interface of the controller.)

The AP console is outputting the following errors:

Translating "CISCO-CAPWAP-CONTROLLER.zw.batgen.com"...domain server (10.131.201.5)

*Mar 1 00:18:58.047: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.

*Mar 1 00:19:01.047: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.zw.batgen.com

Not in Bound state.

*Mar 1 00:19:46.547: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar 1 00:19:52.051: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.

*Mar 1 00:19:52.179: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.131.201.111, mask 255.255.255.0, hostname AP4403.a7a1.0b59

Please help

/Kelvin

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Tue, 27 Aug 2013 11:00:10 GMT

Well as long as the AP has joined the WLC your at a good starting point. Make sure you setup a WLAN to broadcast and also make sure that the ap model (country code) is configured on your WLC also. If both are US for example then your fine.

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Tue, 27 Aug 2013 11:02:16 GMT

The screen shot shows the ap not joined? Make sure the time is also set correctly on the WLC. That is very important or else the ap will fail to join.

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Tue, 27 Aug 2013 11:04:26 GMT

Here is a good link to review also

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Wed, 28 Aug 2013 10:07:24 GMT

Thanks for the link to the trobleshooting guide.

I realize I need to fix the issue with time before I go further. I have found the command to set the time without any problem. However the time defaults when I reboot the LAP device.

May you assist with the command that I should use to save configs before rebooting the LAP. Also if you could link me to a page where I can the commands for the LAP device itself. I have looked around to no luck.

/Kelvin

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Wed, 28 Aug 2013 11:46:38 GMT

The time will default until it joins the WLC. The time on the WLC needs to be correct. The easiest way to have an ap join is to place it on the same subnet as the management of the WLC. If it doesn't join, then you have something not configured right and that link I posted explains what you need to do to troubleshoot.

If you console into the AP and issue a

capwap controller IP address

Or

test capwap erase
test capwap controller ip

These commands tell the ap the WLC ip.

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Thu, 29 Aug 2013 09:40:07 GMT

My setup is as shown in the figure below.

From the results below would you be able to tell where the problem is?

I have run 3 debugs which are given below:

(1). debug capwap event enable

Aug 29 10:38:23.205: 44:03:a7:a0:f6:80 Discovery Request from 10.131.201.115:3946

Aug 29 10:38:23.205: 44:03:a7:a0:f6:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 5, joined Aps =0

Aug 29 10:38:23.205: 44:03:a7:a0:f6:80 Discovery Response sent to 10.131.201.115:3946

Aug 29 10:38:39.202: 44:03:a7:a0:f6:80 Discovery Request from 10.131.201.115:3946

Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 5, joined Aps =0

Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Discovery Response sent to 10.131.201.115:3946

Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Discovery Request from 10.131.201.115:3946

Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 5, joined Aps =0

Aug 29 10:38:39.203: 44:03:a7:a0:f6:80 Discovery Response sent to 10.131.201.115:3946

Aug 29 10:38:39.203: 44:03:a7:a0:f6:83 Received LWAPP DISCOVERY REQUEST to f0:29:29:89:99:e0 on port '1'

Aug 29 10:38:39.203: 44:03:a7:a0:f6:83 Discarding discovery request in LWAPP from AP supporting CAPWAP

(2). debug pm pki enable

(Cisco Controller) >debug pm pki enable

(Cisco Controller) >*sshpmLscTask: Aug 28 11:20:09.116: sshpmLscTask: LSC Task received a message 4

*sshpmLscTask: Aug 28 11:22:09.116: sshpmLscTask: LSC Task received a message 4

*** IDLE TIMEOUT ***

(3). test capwap controller ip 10.131.201.162

AP4403.a7a0.f683#test capwap controller ip 10.131.201.162

AP4403.a7a0.f683#

Not in Bound state.

*Mar 1 00:25:25.103: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar 1 00:25:30.223: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.131.201.20, mask 255.255.255.0, hostname AP4403.a7a0.f683

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

Not in Bound state.

*Mar 1 00:26:56.603: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.

*Mar 1 00:27:01.723: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.131.201.21, mask 255.255.255.0, hostname AP4403.a7a0.f683

Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)

Re: Failing to Access Web Interface of 2602i AP

Scott Fella — Thu, 29 Aug 2013 11:57:20 GMT

They debug from the WLC doesn't show the IP address of the AP. If you connect a laptop to the switchport the AP is connected to, can you get an IP address and access the WLC either from the GUI or SSH? Is there a FIrewall or ACL between the AP and the WLC?

Sent from Cisco Technical Support iPhone App

Re: Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Thu, 29 Aug 2013 13:39:22 GMT

At the time of the debug the ip address of the AP was 10.131.201.115. However this keeps changing not to sure why (thinking it keeps getting new addresses from the DHCP). My setup is simple as shown in network diagram in my previous reply. WLC and LAP connected to the same switch and there are no vlans configured. Router being used as a DHCP server. No firewall or ACLs configured.

Any more debugs I need to run?

From the debugs I can see that the AP is sending 'discovery requests' to the WLC and the WLC is responding with the 'discovery response'. Instead of going back to the next level the the process recycles with the AP sending another 'discovery request' again.

Any reason why we wont go past this stage?

Re: Failing to Access Web Interface of 2602i AP

Kelvin Machakaire — Thu, 05 Sep 2013 18:21:37 GMT

Hi Scott,

I figured out what the real course of my problems where? My WLC was running software version 7.0.x.x which doesn't support the newer 2600 LAPs. On upgrading to 7.4 the problem was fixed. Now my LAPs can easily join the WLC.

Scott, I have a similar issue

warrior28 — Tue, 04 Aug 2015 02:27:07 GMT

Scott, I have a similar issue but i think mine is not as easy to solve. I have a brand new out of the box AIR-CAP2602i-A-K9. ...and thats all I have! lol i do not have controllers nor any other cisco equipment. I was told i was able to use these without needing to spend a gazillion $$$ on a controller. I have tried to connect directly through web but by reading your post above now I know after 2 years that it is not possible. When I connect to my network it blinks blue and green and then stays steady green. I have not been able to access it nor configure it in any way shape or form. I am pretty tech savvy but when it comes to cisco stuff I am not too familiar. Is there any way I can get these going without a controller? I have 2 of them. I am also running FIOS 300mb internet which I would like to connect these devices to. Would love some help/advice! Thank you! you can email me directly as well at Kris@murdockconnect.com

Warrior28,AIR-CAP2602i-A-K9

Scott Fella — Tue, 04 Aug 2015 02:58:45 GMT

Warrior28,

AIR-CAP2602i-A-K9 is a capwap access point

AIR-AP2602i-A-K9 is a standalone access point

The later is what you need. Since you have the CAP, you need to convert that with an autonomous code. The issue you will have is if you cannot download the software.

https://software.cisco.com/download/release.html?mdfid=284362257&flowid=34153&softwareid=284180979&release=15.3.3-JBB1&relind=AVAILABLE&rellifecycle=ED&reltype=latest

See if you can download the file or not.

Here are directions for the conversion:

http://mrncciew.com/2012/10/20/lightweight-to-autonomous-conversion/

-Scott

I tried downloading but it

warrior28 — Tue, 04 Aug 2015 14:42:05 GMT

I tried downloading but it says I need a contract or service license or whatever... so yeah, wasnt able to download. Is there another way to get this software? Also is there a way to keep it lightweight or would that require actually having a controller? My goal would be to broadcast my wifi (the same wifi connection) through out instead of having different AP and have to log on to each one separately. Do I make sense?