1120 and 1231G ap's association with WiSM

Ma'moun Mohammad shanableh · ‎12-05-2011

Dear,

I am trying to associate a 1120 and 1231G AP's to cisco WiSM 1 ios version 5.

i have started with converting the AP's to lightweight image using TFTP. and then connecting them directly to the cire switch and configure the port as follows:

interface gig9/35

switchport

switchport mode access

switchport access vlan x (x=the wireless vlan )

and a DHCP is created for this vlan with option 43 hex ... is configured also.

but when i restart the AP after the port configuration, the access point keeps rebooting and does not associate with the WiSM, and nothing can be found in the logs about the new access points.

any idea

thanx in advance.

Scott Fella · ‎12-05-2011

You need to add the SSC to the WiSM. Take a look at this link.

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

Sent from my iPhone

-Scott
*** Please rate helpful posts ***

Ma'moun Mohammad shanableh · ‎12-06-2011

Dear Scott,

Thank you for your reply.

i have enabled the SSC on the WiSM, and it have discovered the AP and started to download the controller image, Operational status = Downloading, then it disapeared, first i thought that it was rebooting, but it didnt appear again on the controller.

this AP was a 1121G, i also have a 1120B that wasnt able to be converted using the tool, it keeps saying that the radio interface is not supported.

and the 1120B AP was unable to join the controller althoug i tried to issue the Debug pm pki enable on the WiSM but no results found from the command.

any idea

Thanks in advance.

George Stefanick · ‎12-06-2011

Specific to your 1120B, it is not supported unless you upgrade the radio to G. This is why its failing.

"Satisfaction does not come from knowing the solution, it comes from knowing why." - Rosalind Franklin
___________________________________________________________

Scott Fella · ‎12-06-2011

The tool sometimes doesn’t work… at least for me. Are you 100% sure it has been converted? If you console into the AP while you boot it up, can you post the output.

-Scott
*** Please rate helpful posts ***

Ma'moun Mohammad shanableh · ‎12-06-2011

The AP doesnt have a console port, and i guess that it is converted successfuly because i can see it on the controller before it disappears.

Scott Fella · ‎12-06-2011

Like George mentioned, the 1120B's will not work, now the 1231's should have a console port?

Please look at the linke to make sure the AP's you are trying to convert is possible:

http://www.cisco.com/en/US/docs/wireless/access_point/conversion/lwapp/upgrade/guide/lwapnote.html#wp157130

-Scott
*** Please rate helpful posts ***

Ma'moun Mohammad shanableh · ‎12-06-2011

I still have 3 AP's 1121G but i will convert the 1231 and see the result and get back to you.

Thank you very much scott and george

Have a nice day

Ma'moun Mohammad shanableh · ‎12-07-2011

Dear,

i have tried to add the AP's using SSC and MIC.

when using MIC the AP dont appear on the controller and it generates this error message on the Controller.

%LWAPP-3-RADIUS_ERR: spam_radius.c:108 could not send join reply

And when using SSC it appears on the controller and start downloading then reboots and issues the following message on the controller:

%CAPWAP-3-ECHO_ERR: capwap_ac_sm.c4636 did not recieve heartbeat reply.

also when using the SSC mode the captured logs are:

*Mar 1 00:00:06.980: soap_prepare_new_image_crash: mini ios flash:/c1200-rcvk9w8-mx/c1200-rcvk9w8-mx

*Mar 1 00:00:07.554: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed

*Mar 1 00:00:08.762: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0

*Mar 1 00:00:08.858: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 58 messages)

*Mar 1 00:00:11.038: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up

*M

User Access Verification

Username: ar 1 00:00:11.097: %SYS-5-RESTART: System restarted --

Cisco IOS Software, C1200 Software (C1200-K9W8-M), Version 12.4(18a)JA1, RELEASE SOFTWARE (fc1)

Technical Support: http://www.cisco.com/techsupport

Compiled Fri 23-Jan-09 19:41 by prod_rel_team

*Mar 1 00:00:11.160: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Mar 1 00:00:11.216: SSC Load Current Size crypto_mykey 120, offset 9365, Saved Size soap_cert_crypto_mykey 124

*Mar 1 00:00:11.221: %SSH-5-ENABLED: SSH 2.0 has been enabled

*Mar 1 00:00:11.222: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar 1 00:00:11.693: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Mar 1 00:00:12.050: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up

*Mar 1 00:00:12.232: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up

*Mar 1 00:00:21.345: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.1.39.125, mask 255.255.255.0, hostname AP0013.191f.a6b6

Username: Cisco

Password:

*Mar 1 00:00:30.695: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!

*Mar 1 00:00:30.939: Logging LWAPP message to 255.255.255.255.

*Mar 1 00:00:31.006: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down

*Mar 1 00:00:31.016: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Mar 1 00:00:31.018: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated

AP0013.191f.a6b6>

*Mar 1 00:00:31.029: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upen

Password:

AP0013.191f.a6b6#

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

Translating "CISCO-LWAPP-CONTROLLER"...domain server (10.1.1.22)

*Mar 1 00:00:41.011: capwapHandleDiscoveryTimer Expired

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

*Mar 1 00:00:42.013: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER

*Mar 1 00:00:42.015: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLERwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Mar 1 00:00:52.018: capwapHandleDiscoveryTimer Expired

*Mar 1 00:00:52.018: %CAPWAP-3-ERRORLOG: Go join a capwap controller

RSSI IDB null

*Dec 7 14:37:12.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:13.793: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:13.795: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.4.133

*Dec 7 14:37:13.796: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Dec 7 14:37:13.799: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.4.133

*Dec 7 14:37:13.799: %DTLS-5-PEER_DISCONNECT: Peer 10.1.4.133 has closed connection.

*Dec 7 14:37:13.799: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.1.4.133

*Dec 7 14:37:14.045: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:37:14.050: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Dec 7 14:37:14.076: Power level 0 adjusted on slot 0 for chan 11

*Dec 7 14:37:14.083: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Dec 7 14:37:14.085: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:14.097: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:37:24.081: capwapHandleDiscoveryTimer Expired

*Dec 7 14:37:24.081: %CAPWAP-3-ERRORLOG: Go join a capwap controller

RSSI IDB null

*Dec 7 14:37:24.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:25.790: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:25.792: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.4.133

*Dec 7 14:37:25.793: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Dec 7 14:37:25.795: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.4.133

*Dec 7 14:37:25.795: %DTLS-5-PEER_DISCONNECT: Peer 10.1.4.133 has closed connection.

*Dec 7 14:37:25.795: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.1.4.133

*Dec 7 14:37:26.042: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:37:26.043: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:37:26.061: Power level 0 adjusted on slot 0 for chan 11

*Dec 7 14:37:26.062: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Dec 7 14:37:26.068: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Dec 7 14:37:26.070: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:26.082: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:37:26.088: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:26.101: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:37:36.067: capwapHandleDiscoveryTimer Expired

*Dec 7 14:37:36.067: %CAPWAP-3-ERRORLOG: Go join a capwap controller

RSSI IDB null

*Dec 7 14:37:37.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:38.795: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:38.797: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.4.133

*Dec 7 14:37:38.797: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Dec 7 14:37:38.799: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.4.133

*Dec 7 14:37:38.799: %DTLS-5-PEER_DISCONNECT: Peer 10.1.4.133 has closed connection.

*Dec 7 14:37:38.799: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.1.4.133

*Dec 7 14:37:39.049: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:37:39.067: Power level 0 adjusted on slot 0 for chan 11

*Dec 7 14:37:39.069: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Dec 7 14:37:39.074: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Dec 7 14:37:39.076: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:39.088: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:37:39.094: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:39.106: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:37:49.073: capwapHandleDiscoveryTimer Expired

*Dec 7 14:37:49.073: %CAPWAP-3-ERRORLOG: Go join a capwap controller

RSSI IDB null

*Dec 7 14:37:49.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:50.794: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:37:50.796: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.4.133

*Dec 7 14:37:50.796: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Dec 7 14:37:50.798: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.4.133

*Dec 7 14:37:50.799: %DTLS-5-PEER_DISCONNECT: Peer 10.1.4.133 has closed connection.

*Dec 7 14:37:50.799: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.1.4.133

*Dec 7 14:37:51.052: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:37:51.053: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:37:51.071: Power level 0 adjusted on slot 0 for chan 11

*Dec 7 14:37:51.072: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Dec 7 14:37:51.078: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Dec 7 14:37:51.080: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:51.092: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:37:51.098: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:37:51.110: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:38:01.077: capwapHandleDiscoveryTimer Expired

*Dec 7 14:38:01.077: %CAPWAP-3-ERRORLOG: Go join a capwap controller

RSSI IDB null

*Dec 7 14:38:01.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:38:02.789: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:38:02.791: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.4.133

*Dec 7 14:38:02.791: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Dec 7 14:38:02.793: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.4.133

*Dec 7 14:38:02.793: %DTLS-5-PEER_DISCONNECT: Peer 10.1.4.133 has closed connection.

*Dec 7 14:38:02.794: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.1.4.133

*Dec 7 14:38:03.040: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:38:03.041: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:38:03.059: Power level 0 adjusted on slot 0 for chan 11

*Dec 7 14:38:03.060: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Dec 7 14:38:03.065: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

wtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Dec 7 14:38:03.067: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:38:03.079: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:38:03.085: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:38:03.097: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:38:13.064: capwapHandleDiscoveryTimer Expired

*Dec 7 14:38:13.064: %CAPWAP-3-ERRORLOG: Go join a capwap controller

RSSI IDB null

*Dec 7 14:38:13.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:38:14.785: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 10.1.4.133 peer_port: 5246

*Dec 7 14:38:14.787: %CAPWAP-5-SENDJOIN: sending Join Request to 10.1.4.133

*Dec 7 14:38:14.787: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN

*Dec 7 14:38:14.790: %DTLS-5-ALERT: Received WARNING : Close notify alert from 10.1.4.133

*Dec 7 14:38:14.791: %DTLS-5-PEER_DISCONNECT: Peer 10.1.4.133 has closed connection.

*Dec 7 14:38:14.791: %DTLS-5-SEND_ALERT: Send WARNING : Close notify Alert to 10.1.4.133

*Dec 7 14:38:15.039: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:38:15.040: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY

*Dec 7 14:38:15.058: Power level 0 adjusted on slot 0 for chan 11

*Dec 7 14:38:15.059: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down

*Dec 7 14:38:15.065: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to upwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 0

*Dec 7 14:38:15.066: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset

*Dec 7 14:38:15.078: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:38:15.084: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to resetwtpDecodeDiscovery Response numOfCapwapDiscoveryResp = 1

*Dec 7 14:38:15.096: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up

*Dec 7 14:38:25.064: capwapHandleDiscoveryTimer Expired

Please advice

Scott Fella · ‎12-07-2011

Okay... You have other AP's on this wlc correct? Put the AP in the same subnet as the wlc management Interface. Make sure you have dhcp on that subnet. Once it joins successfully, then move that ap back to the subnet you have it on.

Sent from my iPhone

-Scott
*** Please rate helpful posts ***

Ma'moun Mohammad shanableh · ‎12-24-2011

I have opened a TAC case and the solution was by adding a country code for the access point.

The AP is 1121G-A-K9 and the A is for america and canada and the AP's that i have and the controller is configured for is 1121G-E-K9 and E is used for europe and yes my controller was configured in the country code for UK, then we added the US and it worked in addition of enabling the SSC as you said scott.

Thanks alot for your cooperation guys and wish you all the best.