Cisco AP down - shows as 'Ieee PD' on the PoE switch

[Andrew White]

Hello,

I noticed on our 5508 WLC that an access point on the roof of one of our buildings is down (roof terrance). On the PoE switch is now shows Ieee PD instead of AIR-CAP1532E-EK9

I have done a shut and no shut and I get the same.  Nothing shows within CDP.

I seems to of happened when we rebooted the PoE switch one eve.

The place is shut due to Covid19.

I did a cable test too

Any other things I can try?

[Leo Laohoo]

101 metres???  
Exactly what switch is this and what exact firmware is the switch running on?

[Andrew White]

It's on a roof, been working for about 4 years.  There are 8 floors in this office, comms is on the 7th.

Model - WS-C3650-48PQ

FM 03.06.05E cat3k_caa-universalk9

[marce1000]

       - Can  also happen when the ap does not complete start-up for some reason , you could try a longer shut-state of the port.

 M.

[Andrew White]

I suspect it is stuck on rommon, but I will try that too.

[Leo Laohoo]

Can you post the complete output to the following command: 

sh interface Gi2/0/1 controll

[Andrew White]

sh interface Gi2/0/1 controll
GigabitEthernet2/0/1 is down, line protocol is down (notconnect)
Hardware is Gigabit Ethernet, address is 00f2.8b18.2901 (bia 00f2.8b18.2901)
Description: AP Port
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Auto-duplex, Auto-speed, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output never, 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: Class-based queueing
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 0 multicast, 0 pause input
0 input packets with dribble condition detected
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 1 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 GigabitEthernet2/0/1 Receive
0 Total bytes 0 Total bytes
0 Unicast frames 0 Unicast frames
0 Unicast bytes 0 Unicast bytes
0 Multicast frames 0 Multicast frames
0 Multicast bytes 0 Multicast bytes
0 Broadcast frames 0 Broadcast frames
0 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
0 Minimum size frames 0 Minimum size frames
0 65 to 127 byte frames 0 65 to 127 byte frames
0 128 to 255 byte frames 0 128 to 255 byte frames
0 256 to 511 byte frames 0 256 to 511 byte frames
0 512 to 1023 byte frames 0 512 to 1023 byte frames
0 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 0 > 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 0 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 5333982740 msecs AGO

[Leo Laohoo]

Wait ... Something is off with this port. 

What is the uptime of the switch? 

According to the output there is "0" traffic since the uptime of the switch.  

[Andrew White]

Switch has been up 8 weeks and 6 days

[Leo Laohoo]

Console into the AP.  
I agree with what the rest have said & the AP has gone into ROMMON. 

When in ROMMON enter the command "dir" and post the complete output.

[Arshad Safrulla]

I would like to recommend to hardcode the speed to 100 and duplex full, there were instances where I was mandated to work with cables longer than 90M connecting to AP's or any other POE devices, I noticed that Gig negotiation fails some times. This could be due to attenuation as well.

Make sure that you shut and no shut the ports after the changes. But in the long run it always recommended to replace the cable with shielded cables and test the cable using Fluke or any other cable tester. As a best practice I always instruct my team to keep the cable length below 90M to any endpoints.

[rahulnile14]

##- Thanks for responding.
When I replaced the IEEE pde AP with new on same cable; new AP booted
successfully and visible on WLC,
So there is no possibility of cable fault ..Atleast in my case.

Just to mention, we are facing this on multiple APs and last option is
replacing it. -##

[Rich R]

Yes I'd agree - most likely stuck on ROMMON for one reason or another.

[Andrew White]

I'll have to get up there and get it down and put a console cable into it.  If it is in ROMMON mode what can I do to recover it?

[Scott Fella]

First off, bounce the port a few times. This will disable PoE and re-enable it. Wait like 20 seconds before powering it back on and see if the helps. If the device is in rommon, you can find a lot of blogs, videos and links to what you can do. Search the forum also for “Cisco AP rommon”.