Re: New AP Connected to Existing Network Not Found

Johnny Dash · ‎10-25-2023

Hello! I haven't been able to find a clear answer on this online.

This is the scenario:

We have a Controller already set-up with many APs, but they kept disconnecting and one AP never reconnected. The local team switched the faulty AP with the new one and sent us the new AP MAC and asked us to reconfigure it.
The main problem is that I can't seem to find the new AP on the Controller in order to configure it and also we don't have access to the respective AP CLI. What should be the approach in this situation?

Thanks!

marce1000 · ‎10-25-2023

- What is the controller model and software version running on it ? What is the AP model ?
Also : check or post the AP boot process ; check the controller logs when the AP tries to join.

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

Johnny Dash · ‎10-25-2023

Controller model Cisco 5520 and software version v8.5.182.0.

Unfortunately I don't have access to the AP, I should have to ask the local team for those information. Though, the Access Switch to which the AP is connected to is a cisco C9300-48UXM (v17.3.5).

These are the logs that I believe we got on the Access Switch when the AP was first connected to it:
*Oct 24 06:03:53.873 CST: %ILPOWER-5-DETECT: Interface Te1/0/40: Power Device detected: IEEE PD
*Oct 24 06:05:11.897 CST: %ILPOWER-5-IEEE_DISCONNECT: Interface Te1/0/40: PD removed
*Oct 24 06:05:11.897 CST: %ILPOWER-3-CONTROLLER_PORT_ERR: Controller port error, Interface Te1/0/40: Power given, but Power Controller does not report Power Good
*Oct 24 06:05:21.898 CST: %ILPOWER-5-IEEE_DISCONNECT: Interface Te1/0/40: PD removed

marce1000 · ‎10-25-2023

>....Power Device detected: IEEE PD
- That is not good , it means that the Cisco AP is not recognized as such and or will not get correct power to start with. Configure LLDP on the port. Use show cdp neighbors detail on the switch further on.

M.

-- Each morning when I wake up and look into the mirror I always say ' Why am I so brilliant ? '
When the mirror will then always repond to me with ' The only thing that exceeds your brilliance is your beauty! '

ammahend · ‎10-25-2023

Also perform a TDR test on the port, see if all pins are normal.

Step 1	test cable-diagnostics tdr {interface { `interface-number` }}	Starts the TDR test.
Step 2	show cable-diagnostics tdr {interface `interface-number`}	Displays the TDR test counter information.

-hope this helps-

Johnny Dash · ‎10-26-2023

ACCESS-SWITCH01#show cable-diagnostics tdr interface Te1/0/40
TDR test last run on: October 26 15:37:22

Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Te1/0/40 100M Pair A 23 +/- 10 meters N/A Normal
Pair B 21 +/- 10 meters N/A Normal
Pair C 26 +/- 10 meters N/A Short
Pair D 28 +/- 10 meters N/A Short

ammahend · ‎10-26-2023

seems to be a short-circuit fault in the cable around 26-28 meter from testing point (switch), have your cabling guys involved or use another jack.

-hope this helps-

Leo Laohoo · ‎10-26-2023

Turn OFF PoE on that port and re-run the TDR.

Johnny Dash · ‎10-26-2023

Ok, this is what I got:

TDR test last run on: October 27 01:24:41

Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Te1/0/40 100M Pair A N/A N/A Not Completed
Pair B N/A N/A Not Completed
Pair C N/A N/A Not Completed
Pair D N/A N/A Not Completed

Leo Laohoo · ‎10-26-2023

The result says "Not Completed". Keep punching in the command "sh cable tdr interface Te1/0/40" several times and the result will come up.

Be aware of CSCvw97924 & CSCwd97177.

Leo Laohoo · ‎10-25-2023

Post the complete output to the following commands:

sh power inline Te1/0/40
sh cable tdr interface Te1/0/40
sh interface Ten1/0/40 controll

Johnny Dash · ‎10-26-2023

Hello, this is the output from the Access Switch:

ACCESS-SWITCH01#sh power inline Te1/0/40
Interface Admin Oper Power Device Class Max
(Watts)
--------- ------ ---------- ------- ------------------- ----- ----
Te1/0/40 auto off 0.0 n/a n/a 60.0

ACCESS-SWITCH01#sh cable tdr interface Te1/0/40
% TDR test was never run on Te1/0/40

ACCESS-SWITCH01#sh interface Te1/0/40 controller
TenGigabitEthernet1/0/40 is up, line protocol is up (connected)
Hardware is Ten Gigabit Ethernet, address is 7035.0983.58a8 (bia 7035.0983.58a8)
Description: ** BLD-ENERGY **
MTU 9198 bytes, BW 100000 Kbit/sec, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 100/1000/2.5G/5G/10GBaseTX
input flow-control is on, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:34:08, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 2000 bits/sec, 1 packets/sec
2064264 packets input, 486627339 bytes, 0 no buffer
Received 1296472 broadcasts (1296472 multicasts)
0 runts, 0 giants, 0 throttles
1 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1296472 multicast, 0 pause input
0 input packets with dribble condition detected
63838237 packets output, 12022706221 bytes, 0 underruns
Output 10725509 broadcasts (0 multicasts)
0 output errors, 0 collisions, 2 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
Transmit TenGigabitEthernet1/0/40 Receive
12022706221 Total bytes 486627339 Total bytes
4710133 Unicast frames 767792 Unicast frames
304012119 Unicast bytes 56199415 Unicast bytes
48402595 Multicast frames 1296472 Multicast frames
11021766681 Multicast bytes 430427924 Multicast bytes
10725509 Broadcast frames 0 Broadcast frames
696927421 Broadcast bytes 0 Broadcast bytes
0 System FCS error frames 0 IpgViolation frames
0 MacUnderrun frames 0 MacOverrun frames
0 Pause frames 0 Pause frames
0 Cos 0 Pause frames 0 Cos 0 Pause frames
0 Cos 1 Pause frames 0 Cos 1 Pause frames
0 Cos 2 Pause frames 0 Cos 2 Pause frames
0 Cos 3 Pause frames 0 Cos 3 Pause frames
0 Cos 4 Pause frames 0 Cos 4 Pause frames
0 Cos 5 Pause frames 0 Cos 5 Pause frames
0 Cos 6 Pause frames 0 Cos 6 Pause frames
0 Cos 7 Pause frames 0 Cos 7 Pause frames
0 Oam frames 0 OamProcessed frames
0 Oam frames 0 OamDropped frames
33653878 Minimum size frames 488967 Minimum size frames
535132 65 to 127 byte frames 278827 65 to 127 byte frames
986299 128 to 255 byte frames 2 128 to 255 byte frames
28662916 256 to 511 byte frames 1296468 256 to 511 byte frames
8 512 to 1023 byte frames 0 512 to 1023 byte frames
4 1024 to 1518 byte frames 0 1024 to 1518 byte frames
0 1519 to 2047 byte frames 0 1519 to 2047 byte frames
0 2048 to 4095 byte frames 0 2048 to 4095 byte frames
0 4096 to 8191 byte frames 0 4096 to 8191 byte frames
0 8192 to 16383 byte frames 0 8192 to 16383 byte frames
0 16384 to 32767 byte frame 0 16384 to 32767 byte frame
0 > 32768 byte frames 1 > 32768 byte frames
0 Late collision frames 0 SymbolErr frames
0 Excess Defer frames 0 Collision fragments
0 Good (1 coll) frames 0 ValidUnderSize frames
0 Good (>1 coll) frames 1 InvalidOverSize frames
0 Deferred frames 0 ValidOverSize frames
0 Gold frames dropped 0 FcsErr frames
0 Gold frames truncated
0 Gold frames successful
0 1 collision frames
0 2 collision frames
0 3 collision frames
0 4 collision frames
0 5 collision frames
0 6 collision frames
0 7 collision frames
0 8 collision frames
0 9 collision frames
0 10 collision frames
0 11 collision frames
0 12 collision frames
0 13 collision frames
0 14 collision frames
0 15 collision frames
0 Excess collision frames

LAST UPDATE 3567 msecs AGO