Fehlerbehebung bei APs, die nicht zu einem Controller gehören
Einleitung
Dieses Dokument beschreibt die neuen Befehle show ap join stats in Controller Version 4.2.61.0 und zeigt, wie sie effektiv verwendet werden.
Voraussetzungen
Anforderungen
Es gibt keine spezifischen Anforderungen für dieses Dokument.
Verwendete Komponenten
Dieses Dokument ist nicht auf bestimmte Software- und Hardware-Versionen beschränkt.
Die Informationen in diesem Dokument beziehen sich auf Geräte in einer speziell eingerichteten Testumgebung. Alle Geräte, die in diesem Dokument benutzt wurden, begannen mit einer gelöschten (Nichterfüllungs) Konfiguration. Wenn Ihr Netzwerk in Betrieb ist, stellen Sie sicher, dass Sie die möglichen Auswirkungen aller Befehle kennen.
Konventionen
Weitere Informationen zu Dokumentkonventionen finden Sie unter Cisco Technical Tips Conventions (Technische Tipps von Cisco zu Konventionen).
Hintergrundinformationen
Dieses Dokument enthält Informationen über die neuen Befehle show ap join stats in Controller Version 4.2.61.0 und veranschaulicht deren effektive Verwendung. Weitere Informationen finden Sie unter Problembehandlung bei einem Lightweight Access Point, der einem Wireless LAN-Controller nicht beitritt, um herauszufinden, warum ein Access Point (AP) nicht mit einem Controller verbunden wird. Wenn der WAP keine Join-Nachricht an den Controller sendet, müssen Sie die Fehlerbehebung am WAP durchführen.
Dieses Dokument gilt für alle Controller-Versionen (WLC) von 4.2.61 bis zur aktuellen Version 7.2.103.
Mehrere Beispielausgaben verschiedener Fehler, die auf dem Controller auftreten, finden Sie nach den Abschnitten Hintergrundinformationen und Fehlerbehebung bei Algorithmen.
In der Controller-Version 4.2.61.0 verfolgt der Controller nun alle APs, die ihm eine Erkennungsanforderung senden und an die er eine Erkennungsantwort sendet. Es verfolgt auch APs, die dem Controller beitreten möchten, und ob sie erfolgreich sind. Der Controller verfügt über zwei neue CLI-Befehle (Konsole oder SSH), die bei der Fehlerbehebung helfen, warum ein Access Point dem Controller nicht beitreten kann:
show ap join stats summary [all | AP_Mac_Address]
show ap join stats detail
Algorithmus zur Fehlerbehebung
Mit dem Befehl show ap join stats summary all können Sie sehen, welche APs nicht zum Controller gehören. Der Access Point wird in die Liste mit Show-AP-Join-Statistiken eingefügt, sobald der Controller eine Erkennungsanforderung erhält.
Hinweis: Der Controller entfernt den Access Point erst nach einem Neustart des Controllers aus der Liste "Show ap join statistics". In einigen Fällen haben die ausgefallenen Access Points versucht, sich länger als einen Tag einzuwählen, oder sind vollständig offline. Mit dem Befehl show ap join stats detail können Sie feststellen, wann die letzte Erkennungsanforderung und die letzte Verbindungsanforderung vom Access Point gesendet wurden, um festzustellen, ob der Access Point die Verbindung zum Controller verloren hat oder möglicherweise auf einen anderen Controller umgestellt wurde.
Die Ausgabe gibt die Gesamtzahl der APs an, von denen der Controller Ermittlungsanforderungen empfangen hat, und listet dann auf, ob diese APs derzeit mit dem Controller verbunden sind.
(Cisco Controller) > show ap join stats summary all Number of APs................................. 3 00:0b:85:1b:7c:b0............................. Joined 00:12:44:bb:25:d0............................. Joined 00:13:19:31:9c:e0............................. Not joined
Wenn die MAC-Adresse des Access Points nicht beigetreten ist, können Sie mithilfe von show ap join statistics summary <mac addr> den letzten Join und den Grund für den Fehler ermitteln.
(Cisco Controller) >show ap join stats summary 00:14:f2:63:12:50 Is the AP currently connected to controller............. Yes Time at which the AP joined this controller last time... Jan 24 12:21:32.414 Type of error that occurred last........................ AP got or has been disconnected Reason for error that occurred last..................... Timed out while waiting for ECHO response from the AP Time at which the last join error occurred.............. Jan 24 12:21:14.751
Wenn Sie detaillierte Informationen zu Discovery-Anfragen, Join-Anfragen und Konfigurationsanfragen benötigen, verwenden Sie den Befehl show ap join statistics detail <MAC-Adresse> . Dieser Befehl gibt auch an, ob der Controller nur eine Erkennungsanforderung vom Access Point, aber keine Beitrittsanfrage sieht.
(Cisco Controller) >show ap join stats detail 00:14:f2:63:12:50 Discovery phase statistics - Discovery requests received........................... 2 - Successful discovery responses sent................... 2 - Unsuccessful discovery request processing............. 0 - Reason for last unsuccessful discovery attempt........ Not applicable - Time at last successful discovery attempt............. Jan 24 12:21:20.547 - Time at last unsuccessful discovery attempt........... Not applicable Join phase statistics - Join requests received................................ 2 - Successful join responses sent........................ 2 - Unsuccessful join request processing.................. 0 - Reason for last unsuccessful join attempt............. Not applicable - Time at last successful join attempt.................. Jan 24 12:21:30.669 - Time at last unsuccessful join attempt................ Not applicable Configuration phase statistics - Configuration requests received....................... 2 - Successful configuration responses sent............... 2 - Unsuccessful configuration request processing......... 0 - Reason for last unsuccessful configuration attempt.... Not applicable - Successful configuration attempt...................... Jan 24 12:21:32.414 - 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................. Timed out while waiting for ECHO response from the AP Last join error summary - Type of error that occurred last...................... AP got or has been disconnected - Reason for error that occurred last................... Timed out while waiting for ECHO response from the AP - Time at which the last join error occurred............ Jan 24 12:21:14.751
Beispiel 1
In diesem Fall ist die Zeit auf dem Controller falsch. Der Fehler zeigt an, dass die Zertifikatsnutzlast der APs ungültig ist. Dieser Fehler ist aufgetreten, weil die Zeit auf dem Controller außerhalb des Zertifikatsgültigkeitszeitintervalls lag. Stellen Sie sicher, dass der Befehl show time (Uhrzeit anzeigen) die richtige Uhrzeit anzeigt. Beachten Sie die Zeitwerte vom 6. März 1993 in der unten stehenden Ausgabe. An dieser Stelle wird die Uhr für den Controller gestartet, ohne dass das NTP konfiguriert ist.
Die drei Phasen der AP-Join-Berichtsstatistik mit Zeitstempeln sind die Erkennungs-, Join- und Konfigurationsphase. Lesen Sie in der Zusammenfassung der letzten Fehler nach, warum der Access Point nicht beitreten oder die Verbindung trennen konnte.
(Cisco Controller) >show ap join stats detailed 00:14:1b:5a:40:10 Discovery phase statistics - Discovery requests received........................... 2 - Successful discovery responses sent................... 1 - Unsuccessful discovery request processing............. 2113123 - Reason for last unsuccessful discovery attempt........ Discovery request received on unsupported VLAN - Time at last successful discovery attempt............. Mar 06 19:03:50.779 - Time at last unsuccessful discovery attempt........... Mar 06 19:03:50.782 Join phase statistics - Join requests received................................ 1 - Successful join responses sent........................ 0 - Unsuccessful join request processing.................. 1 - Reason for last unsuccessful join attempt............. Certificate payload in join request contains invalid certificate - Time at last successful join attempt.................. Not applicable - Time at last unsuccessful join attempt................ Mar 06 19:04:00.810 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 join request rejected - Reason for error that occurred last................... Certificate payload in join request contains invalid certificate - Time at which the last join error occurred............ Mar 06 19:04:00.810
Beispiel 2
In diesem Fall sendet der WAP die Erkennungsanforderung an ein anderes VLAN als das Management-IP-Adressen-VLAN. Der Controller lehnt alle Erkennungsanforderungen ab, die nicht im Subnetz der Management-Schnittstelle empfangen werden.
(Cisco Controller) >show ap join stats detailed 00:14:1b:5a:40:10 Discovery phase statistics - Discovery requests received........................... 10 - Successful discovery responses sent................... 5 - Unsuccessful discovery request processing............. 2113123 - Reason for last unsuccessful discovery attempt........ Discovery request received on unsupported VLAN - Time at last successful discovery attempt............. Jan 30 14:30:12.284 - Time at last unsuccessful discovery attempt........... Jan 30 14:30:12.288 Join phase statistics - Join requests received................................ 4 - Successful join responses sent........................ 0 - Unsuccessful join request processing.................. 4 - Reason for last unsuccessful join attempt............. Certificate payload in join request contains invalid certificate - Time at last successful join attempt.................. Not applicable - Time at last unsuccessful join attempt................ Mar 06 19:19:03.345 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...................... Failed to send Lwapp discovery response - Reason for error that occurred last................... Discovery request received on unsupported VLAN - Time at which the last join error occurred............ Jan 30 14:30:12.288 (Cisco Controller) >
Beispiel 3
In diesem Fall wechselte der Access Point von diesem Controller zu seinem primären Controller.
Hinweis: Der Fehler kann aus mehreren Gründen generiert werden, von denen einer eine Netzwerkunterbrechung ist.
(Cisco Controller) >show ap join stats detailed 00:14:1b:5a:40:10
Discovery phase statistics
- Discovery requests received........................... 23
- Successful discovery responses sent................... 23
- Unsuccessful discovery request processing............. 0
- Reason for last unsuccessful discovery attempt........
Not applicable
- Time at last successful discovery attempt.............
Jan 30 14:39:38.526
- Time at last unsuccessful discovery attempt...........
Not applicable
Join phase statistics
- Join requests received................................ 21
- Successful join responses sent........................ 21
- Unsuccessful join request processing.................. 0
- Reason for last unsuccessful join attempt.............
Not applicable
- Time at last successful join attempt..................
Jan 30 14:39:07.085
- Time at last unsuccessful join attempt................
Not applicable
Configuration phase statistics
- Configuration requests received....................... 21
- Successful configuration responses sent............... 21
- Unsuccessful configuration request processing......... 0
- Reason for last unsuccessful configuration attempt....
Not applicable
- Time at last successful configuration attempt.........
Jan 30 14:39:09.481
- 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.................
Timed out while waiting for ECHO response from the AP
Last join error summary
- Type of error that occurred last......................
AP got or has been disconnected
- Reason for error that occurred last...................
Timed out while waiting for ECHO response from the AP
- Time at which the last join error occurred............
Jan 30 14:40:15.451
Beispiel 4
In diesem Fall war das selbstsignierte Zertifikat (SSC) des AP auf dem Controller nicht korrekt. Der Controller überprüft immer seine lokale Datenbank, bevor er die Anfrage an einen definierten Radius-Server weiterleitet. Als Ergebnis wird die RADIUS-Autorisierung für AP-Fehler angehalten angezeigt, wenn der Controller die SSC nicht lokal findet.
(Cisco Controller) >show ap join stats detailed 00:13:5f:fa:88:50 Discovery phase statistics - Discovery requests received........................... 2 - Successful discovery responses sent................... 1 - Unsuccessful discovery request processing............. 2113123 - Reason for last unsuccessful discovery attempt........ Discovery request received on unsupported VLAN - Time at last successful discovery attempt............. Jan 30 14:58:58.070 - Time at last unsuccessful discovery attempt........... Jan 30 14:58:58.071 Join phase statistics - Join requests received................................ 1 - Successful join responses sent........................ 0 - Unsuccessful join request processing.................. 1 - Reason for last unsuccessful join attempt............. RADIUS authorization is pending for the AP - Time at last successful join attempt.................. Not applicable - Time at last unsuccessful join attempt................ Jan 30 14:59:13.111 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................. Radius authorization of the AP has failed Last join error summary - Type of error that occurred last...................... AP got or has been disconnected - Reason for error that occurred last................... Radius authorization of the AP has failed - Time at which the last join error occurred............ Jan 30 14:59:13.117 (Cisco Controller) >
Beispiel 5
(Cisco Controller) >show ap join stats detailed 0026cb8168c0 Discovery phase statistics - Discovery requests received.............................. 202 - 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................................... 122 - 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.......................... 115 - 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.................... Image data request received from an unsupported AP Last join error summary - Type of error that occurred last......................... AP got or has been disconnected - Reason for error that occurred last...................... Image data request received from an unsupported AP - Time at which the last join error occurred............... Feb 16 00:50:16.841
Discovery phase statistics - Discovery requests received.............................. 44 - Successful discovery responses sent...................... 44 - Unsuccessful discovery request processing................ 0 - Reason for last unsuccessful discovery attempt........... Not applicable - Time at last successful discovery attempt................ Feb 26 18:36:24.098 - Time at last unsuccessful discovery attempt.............. Not applicable Join phase statistics - Join requests received................................... 44 - Successful join responses sent........................... 0 - Unsuccessful join request processing..................... 44 - Reason for last unsuccessful join attempt................ Join request receive d from an unsupported AP - Time at last successful join attempt..................... Not applicable - Time at last unsuccessful join attempt................... Feb 26 18:36:39.497 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 attemp--More-- or (q)uit t............ Not applicable - Time at last unsuccessful configuration attempt.......... Not applicable Last AP message decrytion 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 join request r ejected - Reason for error that occurred last...................... Join request receive d from an unsupported AP - Time at which the last join error occurred............... Feb 26 18:36:39.497
Zugehörige Informationen
Revisionsverlauf
| Überarbeitung | Veröffentlichungsdatum | Kommentare |
|---|---|---|
3.0 |
11-Apr-2023 |
Formatierung aktualisieren. Technische Informationen überprüft. Rezertifizierung. |
1.0 |
26-Feb-2008 |
Erstveröffentlichung |
FeedbackCisco kontaktieren
- Eine Supportanfrage öffnen
- (Erfordert einen Cisco Servicevertrag)