Dépannage du problème de jonction de point d'accès Catalyst 9130
Table des matières
Introduction
Ce document décrit un cas d'utilisation spécifique où le point d'accès est bloqué lors de la mise à niveau du code pendant le processus de jonction du contrôleur.
Conditions préalables
Exigences
Cisco vous recommande de prendre connaissance des rubriques suivantes :
- Connaissances de base du contrôleur Cisco WLC 9800
- Connaissance de base des points d'accès Cisco Wave2 et/ou 11AX
- Bonne compréhension pour le processus de jonction AP avec le WLC Catalyst 9800.
Composants utilisés
Les informations contenues dans ce document sont basées sur les versions de matériel et de logiciel suivantes :
- WLC Catalyst 9800-L, Cisco IOS® XE Cupertino 17.9.3
- Point d'accès Catalyst C9130AXI-E
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. Si votre réseau est en ligne, assurez-vous de bien comprendre l’incidence possible des commandes.
Topologie
Ce flux de dépannage s'applique aux points d'accès connectés en mode local ou aux points d'accès connectés en mode de connexion flexible dans un site de filiale.
Dépannage de la topologie
Scénario
Ce document traite d'un cas d'utilisation spécifique dans lequel le point d'accès termine sa phase de découverte et de jointure, mais reste bloqué à la phase de vérification des données d'image. Ce problème survient en raison d'une poussée de mise à niveau du code entre le contrôleur LAN sans fil et le point d'accès, ce qui entraîne un message d'erreur indiquant « No space left on device » (Aucun espace restant sur le périphérique).
A. Phase de découverte du point d'accès terminée :
B. Journaux de configuration DTLS initiés et de processus de jointure terminés :
Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.0002] CAPWAP State: DTLS Setup Feb 13 11:11:31 kernel:
[*02/13/2024 11:11:31.6405] Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6405] CAPWAP State: Join Feb 13 11:11:31
kernel: [*02/13/2024 11:11:31.6422] Sending Join request to 10.228.104.4 through port 5248 Feb 13 11:11:31 kernel:
[*02/13/2024 11:11:31.6454] Join Response from 10.228.104.4 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6454]
AC accepted join request with result code: 0 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6489] Received wlcType 0,
timer 30 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6489] TLV ID 2216 not found Feb 13 11:11:31 kernel:
[*02/13/2024 11:11:31.6489] TLV-DEC-ERR-1: No proc for 2216
C. Une fois le processus de jointure terminé, le point d'accès entre dans la phase de données d'image. Au cours de cette phase, vous pouvez observer un transfert d'image du contrôleur vers le point d'accès, qui échoue, accompagné du message d'erreur « No space left on device ».
Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6709] CAPWAP State: Image Data Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6712] AP image version 8.10.112.0 backup 0.0.0.0, Controller 17.9.3.50 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.6712] Version does not match. Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.7111] do PRECHECK, part1 is active part Feb 13 11:11:31 upgrade: /tmp space: OK available 80268, required 40000 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.7322] upgrade.sh: /tmp space: OK available 80268, required 40000 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.7326] wtpImgFileReadRequest: request ap1g6a, local /tmp/part.tar Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.7337] Image Data Request sent to 10.228.104.4, fileName [ap1g6a], slaveStatus 0 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.7351] Image Data Response from 10.228.104.4 Feb 13 11:11:31 kernel: [*02/13/2024 11:11:31.7351] AC accepted join request with result code: 0 Feb 13 11:11:31 LED: State received is Dis_join_completed Feb 13 11:11:31 LED: State received is Sofware_upgrade_progress Feb 13 11:11:31 LED: LED state Changed from LED_CYCLIC_GRO_LED to LED_BLINKING_BLUE Feb 13 11:11:45 kernel: [*02/13/2024 11:11:31.7393] <.................................................. Feb 13 11:11:53 kernel: [*02/13/2024 11:11:45.3443] .................................................. Feb 13 11:12:07 kernel: [*02/13/2024 11:11:53.9200] .................................................. Feb 13 11:12:16 kernel: [*02/13/2024 11:12:07.5228] ..........................Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10). Feb 13 11:12:25 kernel: [*02/13/2024 11:12:18.7413] ........................ Feb 13 11:12:43 kernel: [*02/13/2024 11:12:25.5137] .................................................. Feb 13 11:13:06 kernel: [*02/13/2024 11:12:43.6235] ...................................Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10). Feb 13 11:13:07 kernel: [*02/13/2024 11:13:07.0982] ...Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10). Feb 13 11:13:07 kernel: [*02/13/2024 11:13:07.5458] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10). Feb 13 11:13:07 kernel: [*02/13/2024 11:13:07.5965] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10). Feb 13 11:13:09 kernel: [*02/13/2024 11:13:07.6044] ............ Feb 13 11:13:21 kernel: [*02/13/2024 11:13:09.9353] .............> 84387840 bytes, 62742 msgs, 1195 last Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.0817] Last block stored, IsPre 0, WriteTaskId 0 Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.0847] wtpProcessImageDataRequest(10): fileName ap1g6a, pre 0 Feb 13 11:13:21 upgrade: Start doing upgrade arg1=PREDOWNLOAD arg2= arg3= ... Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.1278] do PREDOWNLOAD, part1 is active part Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.1419] upgrade.sh: Start doing upgrade arg1=PREDOWNLOAD arg2= arg3= ... Feb 13 11:13:21 upgrade: Using image /tmp/part.tar on axel-qca ... Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.1945] upgrade.sh: Using image /tmp/part.tar on axel-qca ... Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.1947] sh: write error: No space left on device Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.1997] tar: write error: No space left on device Feb 13 11:13:21 upgrade: ERROR: Image type mismatch. Expected:ap1g6a Got: Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.2247] upgrade.sh: ERROR: Image type mismatch. Expected:ap1g6a Got: Feb 13 11:13:21 upgrade: Cleanup for do_upgrade... Feb 13 11:13:21 upgrade: /tmp/upgrade_in_progress cleaned Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.2411] upgrade.sh: Cleanup for do_upgrade... Feb 13 11:13:21 upgrade: Cleanup tmp files ... Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.2581] upgrade.sh: /tmp/upgrade_in_progress cleaned FebFeb 13 11:13:21 kernel: [*02/13/2024 11:13:21.3072] capwap-upgrade script returned failure when calling PREDOWNLOAD. Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.3073] Discarding msg CAPWAP_WTP_EVENT_REQUEST(type 9) in CAPWAP state: Image Data(10). Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.3074] CAPWAP SM handler: Failed to process message type 15 state 10. Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.3074] Failed to handle capwap control message from controller - status 2 Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.3074] Failed to process encrypted capwap packet 0x55aaaa2000 from 10.228.104.4 Feb 13 11:13:21 kernel: [*02/13/2024 11:13:21.3074] Failed to send capwap message 0 to the state machine. Packet already freed. Feb 13 11:13:22 LED: State received is Sofware_upgrade_fail Feb 13 11:13:22 LED: LED state Changed from LED_BLINKING_BLUE to LED_GREEN Feb 13 11:13:25 kernel: [*02/13/2024 11:13:25.6121] Invalid event 56 & state 10 combination. Feb 13 11:13:25 kernel: [*02/13/2024 11:13:25.6121] Failed to handle timer message. Feb 13 11:13:28 kernel: [*02/13/2024 11:13:28.4629] Re-Tx Count=1, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=1 Feb 13 11:13:28 kernel: [*02/13/2024 11:13:28.4629] Feb 13 11:13:31 kernel: [*02/13/2024 11:13:31.3139] Re-Tx Count=2, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=1 Feb 13 11:13:31 kernel: [*02/13/2024 11:13:31.3139] Feb 13 11:13:34 kernel: [*02/13/2024 11:13:34.1648] Re-Tx Count=3, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=1 Feb 13 11:13:34 kernel: [*02/13/2024 11:13:34.1648] Feb 13 11:13:37 kernel: [*02/13/2024 11:13:37.0157] Re-Tx Count=4, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=1 Feb 13 11:13:37 kernel: [*02/13/2024 11:13:37.0157] Feb 13 11:13:39 kernel: [*02/13/2024 11:13:39.8666] Re-Tx Count=5, Max Re-Tx Value=5, SendSeqNum=5, NumofPendingMsgs=1 Feb 13 11:13:39 kernel: [*02/13/2024 11:13:39.8666] Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.7175] Max retransmission count exceeded, going back to DISCOVER mode. Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.7175] Dropping msg CAPWAP_ECHO_REQUEST, type = 1, len = 0, eleLen = 8, sendSeqNum = 5 Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.7185] Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.7185] CAPWAP State: DTLS Teardown Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.7303] Aborting image download(0x0): Dtls cleanup, ap1g6a Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.7952] do ABORT, part1 is active part Feb 13 11:13:42 upgrade: Cleanup tmp files ... Feb 13 11:13:42 kernel: [*02/13/2024 11:13:42.8145] upgrade.sh: Cleanup tmp files ...
Solution
Il existe plusieurs solutions pour gérer ceci :
Option 1. Commencez par mettre à niveau vers une image intermédiaire contenant le correctif avant de passer à la version 17.7+. 1. Mise à niveau vers 17.3.5.2. Passez à la version 17.7+.
Option 2. Solution manuelle DE : mount -o remount, size=100M /tmp/ Ceci nécessite un accès dev.
L'une ou l'autre de ces options fonctionne et vous aurez peut-être besoin d'aide avec le TAC lorsque vous travaillerez avec l'option 2.
Historique de révision
| Révision | Date de publication | Commentaires |
|---|---|---|
1.0 |
22-May-2024 |
Première publication |
CommentairesContacter Cisco
- Ouvrir un dossier d’assistance
- (Un contrat de service de Cisco est requis)