Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
AP C9130AXI is not able to join a WLC after physical disconnection or shut/no shut on the port of a C9300-48H. In a working scenario the AP grabs 33.1 watts and recongnizes the AP over CDP. SFG-IS-TEST3#show power inline gigabitEthernet 1/0/5 Interface Admin Oper Power Device Class Max (Watts) --------- ------ ---------- ------- ------------------- ----- ---- Gi1/0/5 auto on 33.3 C9130AXI-B 5 90.0 In a failed scenario the switch still gives power but now the AP is not seen over CDP and the MAC is not learned, as well we can see now takes more power. SFG-IS-TEST3#show power inline gigabitEthernet 1/0/5 Interface Admin Oper Power Device Class Max (Watts) --------- ------ ---------- ------- ------------------- ----- ---- Gi1/0/5 auto on 45.0 Ieee PD 5 90.0
Issue only happens with AP C9130AXI connected on a CAT9300 switch after it has succesfully joined to a WLC for the fisrt time, after that the issue can be replicated bouncing the port.
the command "power inline four-pair forced" can restore the connectivity between the AP and the WLC.
++After physical disconnection or bounce of the port any AP C9130AXI is no longer able to joined a WLC. ++While it is on failing condition we see that the AP takes more watts than previously negotiated: SFG-IS-TEST3#show power inline gigabitEthernet 1/0/5 Interface Admin Oper Power Device Class Max (Watts) --------- ------ ---------- ------- ------------------- ----- ---- Gi1/0/5 auto on 45.0 Ieee PD 5 90.0 ++Durring the Problem the MAC of the AP is not learned on the port and CDP does not recognize the AP. ++Issue can be solved by configuring the command "power inline four-pair forced" on the port, but the AP takes more watts than required. SFG-IS-TEST3#show power inline gigabitEthernet 1/0/5 Interface Admin Oper Power Device Class Max (Watts) --------- ------ ---------- ------- ------------------- ----- ---- Gi1/0/5 auto on 45.0 C9130AXI-B 5 90.0 ++This has been tested on the following versions all showing the same results: 17.02.01, 17.03.02a, 17.03.03, 17.4.1 and 17.5.1