Failing to Access Web Interface of 2602i AP

[Kelvin Machakaire]

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

[wireparts]

por favor, poderia nos postar esse comando?

[Scott Fella]

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

Sent from Cisco Technical Support iPhone App

[Kelvin Machakaire]

Thanks Scott

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

[Abhishek Abhishek]

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.

[Kelvin Machakaire]

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

[Scott Fella]

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

[Scott Fella]

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

[Scott Fella]

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

[Kelvin Machakaire]

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

[Scott Fella]

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

[Kelvin Machakaire]

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)

[Scott Fella]

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

[Kelvin Machakaire]

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?

[Kelvin Machakaire]

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.

[Prakash Parvathala]

There should not be a default IP already set if this is new out of the box.  It should be set to DHCP by default so you will need a DHCP server to provide an address to the AP.  If this was repurposed, it's possible a static address is set which you could then discover through CDP or ARP entries then address a client accordingly to access the AP's GUI and set back to DHCP or a desirable static address.