WLC - AP 1252

Unanswered Question
Jan 9th, 2009

We have a strange issue.. AP 1252 came up with Autonomous IOS, and we had converted it to LWAPP usign 12.4(10) OS.. We have defined the dhcp configurations on the core 6500 switches, for it to return option 43 and 60 to the LAP. 6500 trunks to 3750-E switches, to which the AP's are connected.

Now, the AP boots up, gets an IP address, finds the WLC, ad tries to get associated with it.. nothing happens after that ! we get an error that there is no heartbeat back from the AP !

Jan 09 18:20:39.367 spam_tmr.c:585 LWAPP-3-ECHO_ERR: Did not receive heartbeat reply; AP: 00:21:a0:40:31:b4

Jan 09 18:17:27.363 dhcp_support.c:365 DHCP-3-BIND_SRPORT_ERR: Binding service port failed.

Jan 09 18:09:07.134 dhcp_support.c:365 DHCP-3-BIND_SRPORT_ERR: Binding service port failed.

Jan 09 18:00:46.946 dhcp_support.c:365 DHCP-3-BIND_SRPORT_ERR: Binding service port failed.

Anyone seen this error ? there arent much info about this, on CCO..



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 3 (1 ratings)
Scott Fella Fri, 01/09/2009 - 14:01

What controllers do you have and do you have any ap's up currently?

sachinraja Fri, 01/09/2009 - 14:10

4404 controllers with 5.0.x software.. 1252 LWAPP's.. we were just going through the release notes of 5.0.x IOS and did not see any mention on the 1252 AP's.. hence we are upgrading to 5.1-5.2 (WLC's).. hopefully that should solve the issue.. will let ya know..


Scott Fella Fri, 01/09/2009 - 14:11

4.2.176 is a stable code we use on any 1252 deployments. 5.X has just been to unstable.

sachinraja Mon, 01/12/2009 - 18:39

as thought, the problem solved after upgrading the IOS.. Looks like 5.0 isnt compatible with 1252, according to some release notes.. thank you..


This Discussion



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode