proxmox 控制台无法连接_思科瘦AP无法加入WLC故障排除3

故障排除为何无线接入点无法加

无线控制器版本    4.2.61.0 开始， 无线控制器保持跟踪所有的无线接入点发送的发现请求和已 经对哪些无线接入点发送一个发现答复。    它还跟踪尝试加入无线控制器的无线接入点的成功 状态。无线控制器上有    2 个新的    CLI(通过控制台或    SSH)命令来帮助解决为什么无线接入 点无法加入无线控制器：

Show ap join stats summary [all | AP_Mac_Address] Show ap join stats detailed AP_Mac_Address

故障诊断算法

使用 show ap join stats summary all 命令来查看哪个无线接入点没有加入无线控制器。 一旦无 线控制器收到一个无线接入点的发现请求， 该无线接入点立即被插入到  show ap join stats 列 表中。

注：无线控制器不会将无线接入点从列表中删除，    直到无线控制器重新启动。    在某些情况下， 失败加入的无线接入点尝试时间超过一天或完全脱机。使用    show ap join stats detail        命令找 出从无线接入点发送出来的最后的发现请求和最后的加入请求，        以确定无线接入点是否失去 了连接或者可能转移到另一个无线控制器。

输出给出无线控制器已收到的所有发出发现请求的无线接入点总数，    然后列出这些无线接入 点当前是否加入到无线控制器。

(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

一旦你了解到未加入无线接入点使用的    MAC 地址，    使用 show  ap  join  stats  summary 显示最后加入和失败原因。

(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

如果你想了解发现请求、加入请求和配置要求的详细信息，使用    show  ap join        stats detail

命令。此命令还将显示无线控制器是否只看到从无线接入点发出了发现请求 而没有看到加入请求。

(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 appli