Solved: Re: Rejecting discovery request from unsupported AP

mendicus · ‎08-30-2019

Hi there,

I am trying to connect a Cisco Aironet 1562E to a WS-C3850-24U without success.

I have followed so far this documents:

https://www.cisco.com/c/en/us/td/docs/wireless/access_point/1560/installation/guide/1560hig/1560_ch3.html#62182

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3850/software/release/16-1/converged_access_deployement_guide/m_conAccess_deploy_guide/converged_access_enabling_wireless.html#concept_38BBC97EFB8E40F989EC1B96E6B0B130

But the AP does not join the Controller.

The 3850 shows log:

Aug 30 16:59:19: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 16:59:29: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 16:59:39: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 16:59:48: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 16:59:58: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 17:00:08: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 17:00:17: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 17:00:27: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]   
Aug 30 17:00:37: *%CAPWAP-3-DISC_UNSUPPORTED_AP:Switch 1 R0/0: wcm:  Rejecting discovery request from unsupported AP dc8c.37f9.xxxx [...It occurred 3 times/sec!.]

Here some further information:

SWITCH3850#sh ver
Switch Ports Model              SW Version        SW Image              Mode   
------ ----- -----              ----------        ----------            ----   
*    1 32    WS-C3850-24U       16.3.3            CAT3K_CAA-UNIVERSALK9 BUNDLE

SWITCH3850#sh wireless mobility summary 

Mobility Controller Summary:

Mobility Role                                   : Mobility Controller
Wireless Management VLAN                        : 11
Wireless Management IP Address                  : 10.11.0.100
Mobility Group Name                             : default
Guest-Only Mode                                 : Disabled
DTLS Mode                                       : Enabled
Mobility Keepalive Interval/Count               : 10/3
Mobility Control Message DSCP Value             : 48
Mobility Domain Member Limit/Count              : 8/1

Link Status is Control Link Status : Data Link Status

Controllers configured in the Mobility Domain:

HostName                IP               Public IP        Group Name       Multicast IP     Link Status
-------------------------------------------------------------------------------------------------------
SWITCH3850             10.11.0.100            N/A              default           0.0.0.0          N/A

SWITCH3850#sh ap mac-address dc8c.37f9.xxxx join stats detailed 
Discovery phase statistics
  Discovery requests received                             : 199
  Successful discovery responses sent                     : 0
  Unsuccessful discovery request processing               : 199
  Reason for last unsuccessful discovery attempt          : Discovery request received from an unsupported AP
  Time at last successful discovery attempt               : Not applicable
  Time at last unsuccessful discovery attempt             : Aug 30 17:03:41.254

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
  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                        : Lwapp discovery request rejected
  Reason for error that occurred last                     : Discovery request received from an unsupported AP
  Time at which the last join error occurred              : Aug 30 17:03:41.254

Some information from the 1562

cisco AIR-AP1562E-E-K9 ARMv7 Processor rev 1 (v7l) with 1028584/682180K bytes of memory.
Processor board ID FCZ2318Z0AP
AP Running Image     : 8.5.140.0
Primary Boot Image   : 8.5.140.0
Backup Boot Image    : 0.0.0.0
1 Gigabit Ethernet interfaces
2 802.11 Radios
Radio Driver version : 9.0.5.5-W8964
Radio FW version : 9.1.8.1
NSS FW version : 2.4.25

Base ethernet MAC Address            : 74:88:BB:1D:88:7A
Part Number                          : 73-100839-06
PCA Assembly Number                  : 000-00000-00
PCA Revision Number                  :
PCB Serial Number                    : FOC2312ATGR
Top Assembly Part Number             : 068-100610-02
Top Assembly Serial Number           : FCZ2318Z0AP
Top Revision Number                  : A0
Product/Model Number                 : AIR-AP1562E-E-K9

And this is what I see in the log from the AP connected to the CLI:

[*04/18/2019 01:19:59.6419] CAPWAP State: Discovery
[*04/18/2019 01:19:59.6440] Discovery Request sent to 10.11.0.100, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:19:59.6457] Discovery Request sent to 10.11.0.1, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:19:59.6478] Discovery Request sent to 10.11.0.100, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:19:59.6537] Discovery Request sent to 10.11.0.1, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:19:59.6549] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/18/2019 01:20:09.3346]
[*04/18/2019 01:20:09.3346] CAPWAP State: Discovery
[*04/18/2019 01:20:09.3370] Discovery Request sent to 10.11.0.100, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:09.3389] Discovery Request sent to 10.11.0.1, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:09.3407] Discovery Request sent to 10.11.0.100, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:09.3418] Discovery Request sent to 10.11.0.1, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:09.3429] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*04/18/2019 01:20:19.0276]
[*04/18/2019 01:20:19.0276] CAPWAP State: Discovery
[*04/18/2019 01:20:19.0306] Discovery Request sent to 10.11.0.100, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:19.0322] Discovery Request sent to 10.11.0.1, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:19.0377] Discovery Request sent to 10.11.0.100, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:19.0389] Discovery Request sent to 10.11.0.1, discovery type STATIC_CONFIG(1)
[*04/18/2019 01:20:19.0400] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

So the AP is trying to discover the controller via L2 and L3 but failes and then reboots. This continues for ever.

10.11.0.1 is wireless mobility controller 1

10.11.0.100 is wireless mobility controller 2

Any help much appreciated!

Leo Laohoo · ‎08-30-2019

1560 can only be supported with AireOS 8.3.111.0 and later.
3650/3850 running Converged Access (CA) will not support 1560.

NOTE: Final firmware support for CA on 3650/3850, Sup8 is 16.3.X. (CA is not supported on 16.4.X and later.)
Your only option is to get a WLC that can support 8.3.111.0 (and later) firmware or get an AP that will support Mobility Express.

View solution in original post

marce1000 · ‎08-30-2019

- Google on 'cisco wireless compatibility matrix' then find out whether this ap-model is supported by the used controller and software version being used on this controller.

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

mendicus · ‎08-30-2019

Thanks for your hint.

Have checked this document https://www.cisco.com/c/en/us/td/docs/wireless/compatibility/matrix/compatibility-matrix.html

and found:

But I do not understand this completey. As far as I know is Denali 16.3 the last IOS which supports the wireless mobility feature.

Very confusing....

Leo Laohoo · ‎08-30-2019

1560 can only be supported with AireOS 8.3.111.0 and later.
3650/3850 running Converged Access (CA) will not support 1560.

NOTE: Final firmware support for CA on 3650/3850, Sup8 is 16.3.X. (CA is not supported on 16.4.X and later.)
Your only option is to get a WLC that can support 8.3.111.0 (and later) firmware or get an AP that will support Mobility Express.

mendicus · ‎08-30-2019

Hi Leo,

thanks for clarification.

Then I will go for the Mobility Express option and convert the AP from CAPWAP.

Only downsite: I need a valid service contract to download the conversion software.

Thanks again!

Leo Laohoo · ‎08-31-2019

Mobility Express does not require a valid Service Contract because it is a free software.

mendicus · ‎08-31-2019

Ok....

So why can't I download the software then? Even when I login with my Cisco account, i still get the information, that I need a valid service contract to download the .tar file.