cancelar
Mostrar resultados para 
Pesquisar em vez de 
Queria dizer: 
cancel
1512
Apresentações
0
Útil
23
Respostas

9800-CL Controller and AIR-AP3802

rdrigues
Level 1
Level 1

I'm trying to run AIR-AP3802-Z-K9(Version 9.0.5.5)  on the 9800-CL controller version 17.3.3 and it won't run:

Does anyone know what it could be?


CAPWAP State: Discovery
Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
IP DNS query for CISCO-CAPWAP-CONTROLLER
DNS resolved CISCO-CAPWAP-CONTROLLER
DNS discover IP addr: 10.141.0.250
Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
Discovery Response from 10.141.0.250
CAPWAP State: DTLS Setup
First connect to vWLC, accept vWLC by default
CAPWAP State: Join
Sending Join request to 10.141.0.250 through port 5264
Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).

23 RESPOSTAS 23

Hi @rdrigues 

Can you share the complete output 

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

CAPWAP State: Discovery
[*11/28/2023 14:21:46.7924] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
[*11/28/2023 14:21:46.7927] IP DNS query for CISCO-CAPWAP-CONTROLLER
[*11/28/2023 14:21:46.7933] DNS resolved CISCO-CAPWAP-CONTROLLER
[*11/28/2023 14:21:46.7933] DNS discover IP addr: 10.141.0.250
[*11/28/2023 14:21:46.7962] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
[*11/28/2023 14:21:46.7991] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/28/2023 14:21:46.8031] Discovery Response from 10.141.0.250
[*11/28/2023 14:21:46.8094] Discovery Response from 10.141.0.250
[*11/28/2023 14:21:56.0003]
[*11/28/2023 14:21:56.0003] CAPWAP State: DTLS Setup
[*11/28/2023 14:21:56.7372]
[*11/28/2023 14:21:56.7372] CAPWAP State: Join
[*11/28/2023 14:21:56.7404] Sending Join request to 10.141.0.250 through port 5272
[*11/28/2023 14:22:01.3170] Sending Join request to 10.141.0.250 through port 5272
[*11/28/2023 14:22:06.0685] Sending Join request to 10.141.0.250 through port 5272
[*11/28/2023 14:22:53.0320]
[*11/28/2023 14:22:53.0320] CAPWAP State: DTLS Teardown
[*11/28/2023 14:22:53.1168] upgrade.sh: Script called with args:[ABORT]
[*11/28/2023 14:22:53.1747] do ABORT, part1 is active part
[*11/28/2023 14:22:53.1895] upgrade.sh: Cleanup tmp files ...
[*11/28/2023 14:22:53.2207] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/28/2023 14:22:53.2208] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/28/2023 14:23:07.7841]
[*11/28/2023 14:23:07.7841] CAPWAP State: Discovery
[*11/28/2023 14:23:07.7874] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
[*11/28/2023 14:23:07.7876] IP DNS query for CISCO-CAPWAP-CONTROLLER
[*11/28/2023 14:23:07.7884] DNS resolved CISCO-CAPWAP-CONTROLLER
[*11/28/2023 14:23:07.7884] DNS discover IP addr: 10.141.0.250
[*11/28/2023 14:23:07.7911] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
[*11/28/2023 14:23:07.7940] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/28/2023 14:23:07.7962] Discovery Response from 10.141.0.250
[*11/28/2023 14:23:07.8001] Discovery Response from 10.141.0.250
[*11/28/2023 14:23:18.0003]
[*11/28/2023 14:23:18.0003] CAPWAP State: DTLS Setup
[*11/28/2023 14:23:18.7513]
[*11/28/2023 14:23:18.7513] CAPWAP State: Join
[*11/28/2023 14:23:18.7546] Sending Join request to 10.141.0.250 through port 5272
[*11/28/2023 14:23:23.5072] Sending Join request to 10.141.0.250 through port 5272
[*11/28/2023 14:23:28.2586] Sending Join request to 10.141.0.250 through port 5272
[*11/28/2023 14:24:06.6723] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
[*11/28/2023 14:24:06.6856] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
[*11/28/2023 14:24:07.7150] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Join(5).
[*11/28/2023 14:24:15.0309]
[*11/28/2023 14:24:15.0309] CAPWAP State: DTLS Teardown
[*11/28/2023 14:24:15.1008] upgrade.sh: Script called with args:[ABORT]
[*11/28/2023 14:24:15.1586] do ABORT, part1 is active part
[*11/28/2023 14:24:15.1735] upgrade.sh: Cleanup tmp files ...
[*11/28/2023 14:24:15.2042] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/28/2023 14:24:15.2043] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).
[*11/28/2023 14:24:29.7835]
[*11/28/2023 14:24:29.7835] CAPWAP State: Discovery
[*11/28/2023 14:24:29.7867] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
[*11/28/2023 14:24:29.7870] IP DNS query for CISCO-CAPWAP-CONTROLLER
[*11/28/2023 14:24:29.7876] DNS resolved CISCO-CAPWAP-CONTROLLER
[*11/28/2023 14:24:29.7877] DNS discover IP addr: 10.141.0.250
[*11/28/2023 14:24:29.7904] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)
[*11/28/2023 14:24:29.7934] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)
[*11/28/2023 14:24:29.7968] Discovery Response from 10.141.0.250
[*11/28/2023 14:24:29.8039] Discovery Response from 10.141.0.250

This is the first AP that you want to join to your vWLC? 

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

No, we have C9120AX and CAP2702

Ok, and What country code are you using in your vWLC?, Australia ? Can you run this command in your AP and share them with us:

debug capwap client events
debug capwap client error

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

I'm using it in Brazil, but in the controller I've already added "Australia":

Here's the result:

APA023.9F66.0FC4#debug capwap client events

[*11/28/2023 18:10:54.7892]

[*11/28/2023 18:10:54.7892] CAPWAP State: Discovery

[*11/28/2023 18:10:54.7967] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:10:54.7968] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)

[*11/28/2023 18:10:54.7970] Did not get log server settings from DHCP.

[*11/28/2023 18:10:54.7970] IP DNS query for CISCO-CAPWAP-CONTROLLER

[*11/28/2023 18:10:54.7978] DNS resolved CISCO-CAPWAP-CONTROLLER

[*11/28/2023 18:10:54.7978] DNS discover IP addr: 10.141.0.250

[*11/28/2023 18:10:54.7979]

[*11/28/2023 18:10:54.7979] Send Discovery requests to dcb capwapCfg.mwarIpAddr[0]=10.141.0.250

[*11/28/2023 18:10:54.8010] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:10:54.8012] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)

[*11/28/2023 18:10:54.8012]

[*11/28/2023 18:10:54.8012] SENDING DISCOVERY REQUEST: WLC name JV36MSP, addr 10.141.0.250

[*11/28/2023 18:10:54.8012]

[*11/28/2023 18:10:54.8039] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:10:54.8040] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*11/28/2023 18:10:54.8096] Discovery Response from 10.141.0.250

[*11/28/2023 18:10:54.8097] AC IPv4 10.141.0.250, load 17, count 1

[*11/28/2023 18:10:54.8098] Latency: 0, AC: IP=10.141.0.250 name=JV36MSP, index=0

[*11/28/2023 18:10:54.8132] Discovery Response from 10.141.0.250

[*11/28/2023 18:10:54.8132] AC IPv4 10.141.0.250, load 17, count 1

[*11/28/2023 18:10:54.8133] Duplicate Discovery response from JV36MSP(10.141.0.250)

[*11/28/2023 18:10:54.8133] Ignoring the duplicate discovery response


APA023.9F66.0FC4#debug capwap client error

[*11/28/2023 18:11:04.1521] Calling wtpGetAcToJoin from timer expiry.

[*11/28/2023 18:11:04.1522] DiscRep[0]: addr 10.141.0.250, apMgrCount 1

[*11/28/2023 18:11:04.1522] Selected MWAR 'JV36MSP' (mwarIdx 0).

[*11/28/2023 18:11:04.1522] Selected MWAR 'JV36MSP' 10.141.0.250 (index 0).

[*11/28/2023 18:11:04.1526] apMgrCount 1, index 0

[*11/28/2023 18:11:04.1527] Adding Ipv4 AP manager 10.141.0.250 to least load

[*11/28/2023 18:11:04.1527] WLC: JV36MSP ApMgr count 1, ipTransportTried 0, prefer-mode 0, isIpv4OrIpv6Static 0

[*11/28/2023 18:11:04.1528] IPv4 Pref mode. Choosing AP Mgr with index 0, IP 10.141.0.250, load 17, AP ip: (10.129.27.232)

[*11/28/2023 18:11:04.1528] capwapSetTransportAddr returning: index 0, apMgrCount 0

[*11/28/2023 18:11:04.1528]

[*11/28/2023 18:11:04.0003]

[*11/28/2023 18:11:04.0003] CAPWAP State: DTLS Setup

[*11/28/2023 18:11:04.0184] DTLS connection created sucessfully local_ip: 10.129.27.232 local_port: 5272 peer_ip: 10.141.0.250 peer_port: 5246

[*11/28/2023 18:12:01.0139] Wait DTLS timer has expired

[*11/28/2023 18:12:01.0139] Dtls session establishment failed

[*11/28/2023 18:12:01.0339]

[*11/28/2023 18:12:01.0339] CAPWAP State: DTLS Teardown

[*11/28/2023 18:12:01.0513] CAPWAP data tunnel delete from forwarding succeeded

[*11/28/2023 18:12:01.1041] upgrade.sh: Script called with args:[ABORT]

[*11/28/2023 18:12:01.1624] do ABORT, part1 is active part

[*11/28/2023 18:12:01.1770] upgrade.sh: Cleanup tmp files ...

[*11/28/2023 18:12:01.2079] Setting gPreDownloadComplete=0

[*11/28/2023 18:12:01.2083] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).

[*11/28/2023 18:12:01.2084] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: DTLS Teardown(4).

[*11/28/2023 18:12:05.7654] DTLS session cleanup completed. Restarting capwap state machine.

[*11/28/2023 18:12:05.7846] Previous CAPWAP state was DTLS Setup, numOfCapwapDiscoveryResp = 1.

[*11/28/2023 18:12:05.7847] Attempting to join next controller

[*11/28/2023 18:12:05.7847] Go Join the next controller

[*11/28/2023 18:12:05.7847] Calling wtpGetAcToJoin from timer expiry.

[*11/28/2023 18:12:05.7847] DiscRep[0]: addr 10.141.0.250, apMgrCount 0

[*11/28/2023 18:12:05.7847] Selected MWAR 'JV36MSP' (mwarIdx 0).

[*11/28/2023 18:12:05.7847] Selected MWAR 'JV36MSP' 10.141.0.250 (index 0).

[*11/28/2023 18:12:05.7851] apMgrCount 0, index 0

[*11/28/2023 18:12:05.7852] No more AP manager addresses remain..

[*11/28/2023 18:12:05.7853] No valid AP manager found for controller 'JV36MSP' (ip: 10.141.0.250)

[*11/28/2023 18:12:05.7853] Failed to join controller JV36MSP.

[*11/28/2023 18:12:05.7853] Failed to join controller.

[*11/28/2023 18:12:05.7854] Go Join the next controller

[*11/28/2023 18:12:05.7854] Remove discovery response at index 0

[*11/28/2023 18:12:05.7854]

[*11/28/2023 18:12:05.7854] Could not discover any WLC. Count:[1]

[*11/28/2023 18:12:15.7868] Starting Discovery.

[*11/28/2023 18:12:25.7886]

[*11/28/2023 18:12:25.7887] CAPWAP State: Discovery

[*11/28/2023 18:12:25.8158] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:12:25.8159] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)

[*11/28/2023 18:12:25.8162] Did not get log server settings from DHCP.

[*11/28/2023 18:12:25.8162] IP DNS query for CISCO-CAPWAP-CONTROLLER

[*11/28/2023 18:12:25.8170] DNS resolved CISCO-CAPWAP-CONTROLLER

[*11/28/2023 18:12:25.8170] DNS discover IP addr: 10.141.0.250

[*11/28/2023 18:12:25.8171]

[*11/28/2023 18:12:25.8171] Send Discovery requests to dcb capwapCfg.mwarIpAddr[0]=10.141.0.250

[*11/28/2023 18:12:25.8202] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:12:25.8203] Discovery Request sent to 10.141.0.250, discovery type STATIC_CONFIG(1)

[*11/28/2023 18:12:25.8203]

[*11/28/2023 18:12:25.8203] SENDING DISCOVERY REQUEST: WLC name JV36MSP, addr 10.141.0.250

[*11/28/2023 18:12:25.8203]

[*11/28/2023 18:12:25.8230] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:12:25.8232] Discovery Request sent to 255.255.255.255, discovery type UNKNOWN(0)

[*11/28/2023 18:12:25.8274] Discovery Response from 10.141.0.250

[*11/28/2023 18:12:25.8275] AC IPv4 10.141.0.250, load 17, count 1

[*11/28/2023 18:12:25.8276] Latency: 0, AC: IP=10.141.0.250 name=JV36MSP, index=0

[*11/28/2023 18:12:25.8301] Discovery Response from 10.141.0.250

[*11/28/2023 18:12:25.8302] AC IPv4 10.141.0.250, load 17, count 1

[*11/28/2023 18:12:25.8302] Duplicate Discovery response from JV36MSP(10.141.0.250)

[*11/28/2023 18:12:25.8302] Ignoring the duplicate discovery response

[*11/28/2023 18:12:35.2249] Calling wtpGetAcToJoin from timer expiry.

[*11/28/2023 18:12:35.2249] DiscRep[0]: addr 10.141.0.250, apMgrCount 1

[*11/28/2023 18:12:35.2249] Selected MWAR 'JV36MSP' (mwarIdx 0).

[*11/28/2023 18:12:35.2250] Selected MWAR 'JV36MSP' 10.141.0.250 (index 0).

[*11/28/2023 18:12:35.2254] apMgrCount 1, index 0

[*11/28/2023 18:12:35.2255] Adding Ipv4 AP manager 10.141.0.250 to least load

[*11/28/2023 18:12:35.2255] WLC: JV36MSP ApMgr count 1, ipTransportTried 0, prefer-mode 0, isIpv4OrIpv6Static 0

[*11/28/2023 18:12:35.2255] IPv4 Pref mode. Choosing AP Mgr with index 0, IP 10.141.0.250, load 17, AP ip: (10.129.27.232)

[*11/28/2023 18:12:35.2256] capwapSetTransportAddr returning: index 0, apMgrCount 0

[*11/28/2023 18:12:35.2256]

[*11/28/2023 18:12:35.0003]

[*11/28/2023 18:12:35.0003] CAPWAP State: DTLS Setup

[*11/28/2023 18:12:35.0012] DTLS connection created sucessfully local_ip: 10.129.27.232 local_port: 5272 peer_ip: 10.141.0.250 peer_port: 5246

[*11/28/2023 18:12:35.7139] First connect to vWLC, accept vWLC by default

[*11/28/2023 18:12:35.7139]

[*11/28/2023 18:12:35.7358] Dtls Session Established with the AC 10.141.0.250, port 5246

[*11/28/2023 18:12:35.7361]

[*11/28/2023 18:12:35.7361] CAPWAP State: Join

[*11/28/2023 18:12:35.7426] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:12:35.7427] Sending Join request to 10.141.0.250 through port 5272

[*11/28/2023 18:12:40.3381] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:12:40.3382] Sending Join request to 10.141.0.250 through port 5272

[*11/28/2023 18:12:45.0719] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

[*11/28/2023 18:12:45.0720] Sending Join request to 10.141.0.250 through port 5272

[*11/28/2023 18:12:49.8269] Dropping TLV_AP_EWLC_TAGS_PAYLOAD. No info available

Ok Two Questions.

How many APs do you already have registered in your 9800-CL be sure you're license can support the new AP

Did you configure the certificate trust point, ?

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

I have 17 aps registered.

Did you configure the certificate trust point, ?  Not

show wireless management trustpoint 

this AP 3800 is coming form AirOS controller?

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

I can't tell if it came from any AirOS.

rdrigues_0-1701267381438.png

 



Well obviously you have the certificate, and if don't, then no AP will be registered in you WLC and already you have 2700 and 9100.

I strongly believe that the AP is coming from WLC AirOS and they were using SSC certificates. For that reason the AP can join to 9800-CL.

You can find information and the solutionin this post: https://gblogs.cisco.com/ch-tech/setup-your-lab-with-catalyst-9800-cl/

In the logs that you share I saw this: [*11/28/2023 18:12:05.7853] No valid AP manager found for controller 'JV36MSP' (ip: 10.141.0.250)

Now, if you can't back to the WLC AirOS then you can use this commands on the WLC 9800

WLC# wireless config vwlc-ssc key-size 2048 signature-algo sha256 password [password]

Make sure your password is sufficiently long and complex or this will fail. Unfortunately, you don’t get much of a warning or failure message when it fails, but you do get some lovely output when it succeeds which is enough to know it worked.

 

Next I clear the private-config on the access point. This is what I would normally do first when troubleshooting a previously used access point not joining a new controller.

This is often enough to fix many issues when moving APs from one WLC to another, so keep the command in the back of your mind for future tshooting.  SSH/Console into the access point (default creds are Cisco/Cisco if you haven’t changed them) and issue the following command: 

AccessPoint# clear lwapp private-config

Please check and let us know 

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

does not have this command:

AccessPoint# clear lwapp private-config

rdrigues_0-1701800736438.png

 

did you create the ssc certificate?

Espero que la información haya sido útil y si no tienes más preguntas recuerda cerrar el topic, seleccionando la respuesta como "Respuesta correcta"
**Please rate the answer if this information was useful***
**Por favor si la información fue util marca esta respuesta como correcta**

on the controller?
No!