cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2616
Views
0
Helpful
10
Replies

Help with joining AP to WLC 5508 Getting error in LOG's

Eric Daoust
Level 1
Level 1

I am tryign to join my first AP to the 5508 and am gettign this error int he logs.

*Dec 07 10:42:31.067: %DTL-3-NPUARP_ADD_FAILED: dtl_arp.c:2280 Unable to add an ARP entry for 0:0.0.0 to the network processor. entry does not exist

The management Interface is on the the same vlan as the AP , both untagged ports. the AP gets an ip address from my dhcp server.

Any ideas?

Thanks

10 Replies 10

Stephen Rodriguez
Cisco Employee
Cisco Employee

can you run the following debugs concurrently?

debug mac addr < ap mac address >

debug capwap events enable

debug capwap errors enable

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

(Cisco Controller) >show debug

MAC address ................................ e0:2f:6d:17:d5:6b

Debug Flags Enabled:

  capwap error enabled.

  capwap critical enabled.

  capwap events enabled.

  capwap state enabled.

  lwapp events enabled.

  lwapp errors enabled.

(Cisco Controller) >*Dec 07 11:06:13.882: e0:2f:6d:17:d5:6b Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*Dec 07 11:06:13.882: e0:2f:6d:17:d5:6b Discarding discovery request in LWAPP from AP supporting CAPWAP

*Dec 07 11:06:13.883: e0:2f:6d:17:d5:6b Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*Dec 07 11:06:13.883: e0:2f:6d:17:d5:6b Discarding discovery request in LWAPP from AP supporting CAPWAP

*Dec 07 11:06:33.759: e0:2f:6d:17:d5:6b Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*Dec 07 11:06:33.760: e0:2f:6d:17:d5:6b Discarding discovery request in LWAPP from AP supporting CAPWAP

*Dec 07 11:06:33.760: e0:2f:6d:17:d5:6b Received LWAPP DISCOVERY REQUEST to ff:ff:ff:ff:ff:ff on port '1'

*Dec 07 11:06:33.760: e0:2f:6d:17:d5:6b Discarding discovery request in LWAPP from AP supporting CAPWAP

so far so good.  the request is getting there as a broadcast.

Let the debug run through two reboots of the AP.

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

How long shoudl that take? or should i manually reboot it

it just keep repeating over and over

Also which software shoud i be on?  i got 6.0.199.4

6.0.199.4 is kinda old...what type of AP do you have?

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

AIR-CAP3502I-A-K9

Also here's this if useful

Discovery phase statistics

- Discovery requests received.............................. 114

- Successful discovery responses sent...................... 0

- Unsuccessful discovery request processing................ 0

- Reason for last unsuccessful discovery attempt........... Not applicable

- Time at last successful discovery attempt................ Not applicable

- Time at last unsuccessful discovery attempt.............. Not applicable

Join phase statistics

- Join requests received................................... 0

- Successful join responses sent........................... 0

- Unsuccessful join request processing..................... 0

- Reason for last unsuccessful join attempt................ Not applicable

- Time at last successful join attempt..................... Not applicable

- Time at last unsuccessful join attempt................... Not applicable

Configuration phase statistics

- Configuration requests received.......................... 0

- Successful configuration responses sent.................. 0

- Unsuccessful configuration request processing............ 0

- Reason for last unsuccessful configuration attempt....... Not applicable

--More-- or (q)uit

- Time at last successful configuration attempt............ Not applicable

- Time at last unsuccessful configuration attempt.......... Not applicable

Last AP message decryption failure details

- Reason for last message decryption failure............... Not applicable

Last AP disconnect details

- Reason for last AP connection failure.................... Not applicable

Last join error summary

- Type of error that occurred last......................... None

- Reason for error that occurred last...................... Not applicable

- Time at which the last join error occurred............... Not applicable

Ethernet Mac : 00:00:00:00:00:00  Ip Address : 192.168.14.50

the 3502 requires that you run at least 7.0 code.  I'd probaly upgrade to the latest 7.2 though.

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

I agree with Steve, the 3500 requires a minimum of 7.2.X, however, I would recommend you upgrade to 7.3.102.0 instead.

Make sure you upgrade the FUS too! 

Whats the FUS?

Look at this doc as it shows what is bundled in the FUS (Field Upgrade Software) image

https://supportforums.cisco.com/docs/DOC-23757

Sent from Cisco Technical Support iPhone App

-Scott
*** Please rate helpful posts ***
Review Cisco Networking for a $25 gift card