Solved: LAP unable to register with WLC 4402

mangesh-bhende · ‎01-05-2012

Hi All,

I have cisco WLC (AIR-WLC4402-12-K9) with two LAP (AIR-LAP1131AG-A-K9) connected to switch and one of the LAP is able to register with WLC while other one was standalone AP which has been converted to LAP which is unable to register with WLC. I can see that the AP is able to grab the Ip address and even joins the WLC but is unable to register. Kindly help us to troubleshoot this issue. I have attached all relevant logs with this case. Awaiting for your reply.

FYI i have refered to below URL but couldnt able to figureout the actual reason.

http://www.cisco.com/en/US/products/ps6366/products_tech_note09186a00808f8599.shtml

Leo Laohoo · ‎01-05-2012

I don't understand. You have TWO (2) 1131AG. One has joined for the last two days and another just recently joined. Are saying that the second one keeps "bouncing"?

Did you check if the WAP is going down due to power?

View solution in original post

Leo Laohoo · ‎01-05-2012

I don't understand. You have TWO (2) 1131AG. One has joined for the last two days and another just recently joined. Are saying that the second one keeps "bouncing"?

Did you check if the WAP is going down due to power?

mangesh-bhende · ‎01-05-2012

Hi WAP is powered on by POE and is ok but only thing is its keep on bouncing.

Leo Laohoo · ‎01-06-2012

Hi WAP is powered on by POE and is ok but only thing is its keep on bouncing.

Bouncing as in it keeps rebooting right? And it's powered using PoE? Cool. We're getting somewhere.

Can you please elaborate what exact PoE switch it is?

If its a Cisco switch, then chances are you can test if you have a cable issue using TDR.

Stephen Rodriguez · ‎01-06-2012

Run the following debuts for two boot cycles of the AP and post the results here

Debug mac address

Debug capwap events enable

Debug capwap errors enable

Sent from Cisco Technical Support iPhone App

HTH,
Steve

------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered

mangesh-bhende · ‎01-08-2012

Hi Stephen,

I was unable to capture debug mac address but have captured rest all.

(Cisco Controller) >debug caw pwap events enable

(Cisco Controller) >*spamReceiveTask: Jan 09 02:56:49.920: 00:18:18:1e:a4:ae Discovery Request from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:56:49.920: 00:18:18:1e:a4:ae Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =0

*spamReceiveTask: Jan 09 02:56:49.920: 00:18:18:1e:a4:ae Discovery Response sent to 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:56:49.920: 00:18:18:1e:a4:ae Received LWAPP DISCOVERY REQUEST to 00:1e:13:2a:42:20 on port '1'

*spamReceiveTask: Jan 09 02:56:49.920: 00:18:18:1e:a4:ae Discarding discovery request in LWAPP from AP supporting CAPWAP

*spamReceiveTask: Jan 09 02:56:59.917: 00:18:18:1e:a4:ae DTLS connection not found, creating new connection for 10:10:3:24 (59979) 10:10:2:3 (5246)

*spamReceiveTask: Jan 09 02:57:01.308: 00:18:18:1e:a4:ae DTLS Session established server (10.10.2.3:5246), client (10.10.3.24:59979)

*spamReceiveTask: Jan 09 02:57:01.308: 00:18:18:1e:a4:ae Starting wait join timer for AP: 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:57:01.312: 00:18:18:1e:a4:ae Join Request from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:57:01.313: 00:18:18:1e:a4:ae Join Version: = 117465600

*spamReceiveTask: Jan 09 02:57:01.315: 00:18:18:1e:a4:ae Join resp: CAPWAP Maximum Msg element len = 93

*spamReceiveTask: Jan 09 02:57:01.315: 00:18:18:1e:a4:ae Join Response sent to 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:57:01.315: 00:18:18:1e:a4:ae CAPWAP State: Join

*spamReceiveTask: Jan 09 02:57:01.315: 00:18:18:1e:a4:ae capwap_ac_platform.c:1216 - Operation State 0 ===> 4

*apfReceiveTask: Jan 09 02:57:01.316: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:57:01.316: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*spamReceiveTask: Jan 09 02:57:19.448: 00:18:18:1e:a4:ae DTLS connection closed event receivedserver (10:10:2:3/5246) client (10:10:3:24/59979)

*spamReceiveTask: Jan 09 02:57:19.448: 00:18:18:1e:a4:ae Entry exists for AP (10:10:3:24/59979)

*spamReceiveTask: Jan 09 02:57:19.448: 00:18:18:1e:a4:ae apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*spamReceiveTask: Jan 09 02:57:19.448: 00:18:18:1e:a4:ae apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*apfReceiveTask: Jan 09 02:57:19.448: 00:18:18:1e:a4:ae Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:57:19.448: 00:18:18:1e:a4:ae Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*spamReceiveTask: Jan 09 02:57:19.561: 00:18:18:1e:a4:ae Discovery Request from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:57:19.561: 00:18:18:1e:a4:ae Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =0

*spamReceiveTask: Jan 09 02:57:19.561: 00:18:18:1e:a4:ae Discovery Response sent to 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:57:19.561: 00:18:18:1e:a4:ae Received LWAPP DISCOVERY REQUEST to 00:1e:13:2a:42:20 on port '1'

*spamReceiveTask: Jan 09 02:57:19.561: 00:18:18:1e:a4:ae Discarding discovery request in LWAPP from AP supporting CAPWAP

*spamReceiveTask: Jan 09 02:57:29.559: 00:18:18:1e:a4:ae DTLS connection not found, creating new connection for 10:10:3:24 (59980) 10:10:2:3 (5246)

*spamReceiveTask: Jan 09 02:57:30.965: 00:18:18:1e:a4:ae DTLS Session established server (10.10.2.3:5246), client (10.10.3.24:59980)

*spamReceiveTask: Jan 09 02:57:30.965: 00:18:18:1e:a4:ae Starting wait join timer for AP: 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:57:30.969: 00:18:18:1e:a4:ae Join Request from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:57:30.970: 00:18:18:1e:a4:ae Join Version: = 117465600

*spamReceiveTask: Jan 09 02:57:30.970: 00:18:18:1e:a4:ae Join resp: CAPWAP Maximum Msg element len = 93

*spamReceiveTask: Jan 09 02:57:30.970: 00:18:18:1e:a4:ae Join Response sent to 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:57:30.970: 00:18:18:1e:a4:ae CAPWAP State: Join

*spamReceiveTask: Jan 09 02:57:30.970: 00:18:18:1e:a4:ae capwap_ac_platform.c:1216 - Operation State 0 ===> 4

*apfReceiveTask: Jan 09 02:57:30.973: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:57:30.973: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*spamReceiveTask: Jan 09 02:57:49.097: 00:18:18:1e:a4:ae DTLS connection closed event receivedserver (10:10:2:3/5246) client (10:10:3:24/59980)

*spamReceiveTask: Jan 09 02:57:49.097: 00:18:18:1e:a4:ae Entry exists for AP (10:10:3:24/59980)

*spamReceiveTask: Jan 09 02:57:49.097: 00:18:18:1e:a4:ae apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*spamReceiveTask: Jan 09 02:57:49.097: 00:18:18:1e:a4:ae apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*apfReceiveTask: Jan 09 02:57:49.097: 00:18:18:1e:a4:ae Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:57:49.097: 00:18:18:1e:a4:ae Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*spamReceiveTask: Jan 09 02:57:49.213: 00:18:18:1e:a4:ae Discovery Request from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:57:49.213: 00:18:18:1e:a4:ae Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =0

*spamReceiveTask: Jan 09 02:57:49.213: 00:18:18:1e:a4:ae Discovery Response sent to 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:57:49.213: 00:18:18:1e:a4:ae Received LWAPP DISCOVERY REQUEST to 00:1e:13:2a:42:20 on port '1'

*spamReceiveTask: Jan 09 02:57:49.213: 00:18:18:1e:a4:ae Discarding discovery request in LWAPP from AP supporting CAPWAP

*spamReceiveTask: Jan 09 02:57:59.210: 00:18:18:1e:a4:ae DTLS connection not found, creating new connection for 10:10:3:24 (59979) 10:10:2:3 (5246)

*spamReceiveTask: Jan 09 02:58:00.614: 00:18:18:1e:a4:ae DTLS Session established server (10.10.2.3:5246), client (10.10.3.24:59979)

*spamReceiveTask: Jan 09 02:58:00.615: 00:18:18:1e:a4:ae Starting wait join timer for AP: 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:58:00.618: 00:18:18:1e:a4:ae Join Request from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:58:00.619: 00:18:18:1e:a4:ae Join Version: = 117465600

*spamReceiveTask: Jan 09 02:58:00.619: 00:18:18:1e:a4:ae Join resp: CAPWAP Maximum Msg element len = 93

*spamReceiveTask: Jan 09 02:58:00.620: 00:18:18:1e:a4:ae Join Response sent to 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:58:00.620: 00:18:18:1e:a4:ae CAPWAP State: Join

*spamReceiveTask: Jan 09 02:58:00.620: 00:18:18:1e:a4:ae capwap_ac_platform.c:1216 - Operation State 0 ===> 4

*apfReceiveTask: Jan 09 02:58:00.622: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:58:00.622: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*spamReceiveTask: Jan 09 02:58:18.746: 00:18:18:1e:a4:ae DTLS connection closed event receivedserver (10:10:2:3/5246) client (10:10:3:24/59979)

*spamReceiveTask: Jan 09 02:58:18.746: 00:18:18:1e:a4:ae Entry exists for AP (10:10:3:24/59979)

*spamReceiveTask: Jan 09 02:58:18.746: 00:18:18:1e:a4:ae apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*spamReceiveTask: Jan 09 02:58:18.746: 00:18:18:1e:a4:ae apfSpamProcessStateChangeInSpamContext: Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*apfReceiveTask: Jan 09 02:58:18.746: 00:18:18:1e:a4:ae Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:58:18.746: 00:18:18:1e:a4:ae Deregister LWAPP event for AP 00:18:18:1e:a4:ae slot 1

*spamReceiveTask: Jan 09 02:58:18.862: 00:18:18:1e:a4:ae Discovery Request from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:58:18.862: 00:18:18:1e:a4:ae Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 12, joined Aps =0

*spamReceiveTask: Jan 09 02:58:18.862: 00:18:18:1e:a4:ae Discovery Response sent to 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:58:18.862: 00:18:18:1e:a4:ae Received LWAPP DISCOVERY REQUEST to 00:1e:13:2a:42:20 on port '1'

*spamReceiveTask: Jan 09 02:58:18.863: 00:18:18:1e:a4:ae Discarding discovery request in LWAPP from AP supporting CAPWAP

*spamReceiveTask: Jan 09 02:58:28.860: 00:18:18:1e:a4:ae DTLS connection not found, creating new connection for 10:10:3:24 (59980) 10:10:2:3 (5246)

*spamReceiveTask: Jan 09 02:58:30.257: 00:18:18:1e:a4:ae DTLS Session established server (10.10.2.3:5246), client (10.10.3.24:59980)

*spamReceiveTask: Jan 09 02:58:30.257: 00:18:18:1e:a4:ae Starting wait join timer for AP: 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:58:30.260: 00:18:18:1e:a4:ae Join Request from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:58:30.262: 00:18:18:1e:a4:ae Join Version: = 117465600

*spamReceiveTask: Jan 09 02:58:30.262: 00:18:18:1e:a4:ae Join resp: CAPWAP Maximum Msg element len = 93

*spamReceiveTask: Jan 09 02:58:30.264: 00:18:18:1e:a4:ae Join Response sent to 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:58:30.264: 00:18:18:1e:a4:ae CAPWAP State: Join

*spamReceiveTask: Jan 09 02:58:30.264: 00:18:18:1e:a4:ae capwap_ac_platform.c:1216 - Operation State 0 ===> 4

*apfReceiveTask: Jan 09 02:58:30.264: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 0

*apfReceiveTask: Jan 09 02:58:30.265: 00:18:18:1e:a4:ae Register LWAPP event for AP 00:18:18:1e:a4:ae slot 1

(Cisco Controller) >debug disable-all

(Cisco Controller) >debug capwap errors enable

(Cisco Controller) >*spamReceiveTask: Jan 09 02:58:59.919: 00:18:18:1e:a4:ae AP with same name AP0018.181e.a4ae exist. Using default name AP0018.181e.a4ae for this AP.

*spamReceiveTask: Jan 09 02:59:00.051: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:00.051: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:00.051: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:03.050: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:03.050: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:03.050: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:06.049: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:06.049: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:06.049: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:09.048: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:09.048: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:09.048: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:12.047: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:12.047: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:12.047: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:15.046: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:15.046: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:15.046: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59979

*spamReceiveTask: Jan 09 02:59:18.045: 00:18:18:1e:a4:ae DTLS connection was closed

*spamReceiveTask: Jan 09 02:59:29.563: 00:18:18:1e:a4:ae AP with same name AP0018.181e.a4ae exist. Using default name AP0018.181e.a4ae for this AP.

*spamReceiveTask: Jan 09 02:59:29.696: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:29.696: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:59:29.696: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:59:32.694: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:32.694: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:59:32.694: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59980

d*spamReceiveTask: Jan 09 02:59:35.693: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:35.693: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:59:35.693: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59980

debu *spamReceiveTask: Jan 09 02:59:38.692: 00:18:18:1e:a4:ae AP not registering with BASE MAC.

*spamReceiveTask: Jan 09 02:59:38.692: 00:18:18:1e:a4:ae State machine handler: Failed to process msg type = 5 state = 5 from 10.10.3.24:59980

*spamReceiveTask: Jan 09 02:59:38.692: 00:18:18:1e:a4:ae Failed to parse CAPWAP packet from 10.10.3.24:59980

Leo Laohoo · ‎01-08-2012

What is the exact model of the Cisco switch?

nikhilcherian · ‎01-08-2012

Can you issue the command " show power inline" when the AP is bouncing, i often see the AP having issues in getting power from the switch and which causes the ap to reboot. Against the AP port in the power inline command the AP name should come and not as IEEE PD

Thanks

NikhiL

mangesh-bhende · ‎01-09-2012

Hi,

Please find the output.

WIRELSS-SWITCH#sh ver

Cisco IOS Software, C3750 Software (C3750-IPSERVICESK9-M), Version 12.2(50)SE1, RELEASE SOFTWARE (fc2)

Compiled Mon 06-Apr-09 08:19 by amvarma

Image text-base: 0x00003000, data-base: 0x01D00000

ROM: Bootstrap program is C3750 boot loader

BOOTLDR: C3750 Boot Loader (C3750-HBOOT-M) Version 12.2(44)SE5, RELEASE SOFTWARE (fc1)

WIRELSS-SWITCH uptime is 5 weeks, 6 days, 23 hours, 31 minutes

System returned to ROM by power-on

System image file is "flash:c3750-ipservicesk9-mz.122-50.SE1/c3750-ipservicesk9- mz.122-50.SE1.bin"

This product contains cryptographic features and is subject to United

States and local country laws governing import, export, transfer and

use. Delivery of Cisco cryptographic products does not imply

third-party authority to import, export, distribute or use encryption.

Importers, exporters, distributors and users are responsible for

compliance with U.S. and local country laws. By using this product you

agree to comply with applicable laws and regulations. If you are unable

to comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to

export@cisco.com.

cisco WS-C3750-48P (PowerPC405) processor (revision K0) with 118784K/12280K bytes of memory.

Processor board ID FDO1147Z90V

Last reset from power-on

4 Virtual Ethernet interfaces

48 FastEthernet interfaces

4 Gigabit Ethernet interfaces

The password-recovery mechanism is enabled.

512K bytes of flash-simulated non-volatile configuration memory.

Base ethernet MAC Address : XX:XX:XX:XX:XX:XX

Motherboard assembly number : 73-9675-11

Power supply part number : 341-0029-05

Motherboard serial number : XXXXXXXXXXXX

Power supply serial number : XXXXXXXXXXXX

Model revision number : K0

Motherboard revision number : B0

Model number : WS-C3750-48PS-S

System serial number : FDO1147Z90V

SFP Module assembly part number : XXXXXXXXXXXX

SFP Module revision Number : A0

SFP Module serial number : XXXXXXXXXXXXX

Top Assembly Part Number : XXXXXXXXX

Top Assembly Revision Number : J0

Version ID : V05

CLEI Code Number : XXXXXXXXXXXXXXXX

Hardware Board Revision Number : 0x01

Switch Ports Model SW Version SW Image

------ ----- ----- ---------- ----------

* 2 52 WS-C3750-48P 12.2(50)SE1 C3750-IPSERVICESK9-M

Configuration register is 0xF

WIRELSS-SWITCH#sh power inline

Module Available Used Remaining

(Watts) (Watts) (Watts)

------ --------- -------- ---------

2 370.0 12.2 357.8

Interface Admin Oper Power Device Class Max

(Watts)

--------- ------ ---------- ------- ------------------- ----- ----

Fa2/0/1 auto off 0.0 n/a n/a 15.4

Fa2/0/2 auto off 0.0 n/a n/a 15.4

Fa2/0/3 auto off 0.0 n/a n/a 15.4

Fa2/0/4 auto off 0.0 n/a n/a 15.4

Fa2/0/5 auto off 0.0 n/a n/a 15.4

Fa2/0/6 auto off 0.0 n/a n/a 15.4

Fa2/0/7 auto off 0.0 n/a n/a 15.4

Fa2/0/8 auto off 0.0 n/a n/a 15.4

Fa2/0/9 auto off 0.0 n/a n/a 15.4

Fa2/0/10 auto off 0.0 n/a n/a 15.4

Fa2/0/11 auto off 0.0 n/a n/a 15.4

Fa2/0/12 auto off 0.0 n/a n/a 15.4

Fa2/0/13 auto off 0.0 n/a n/a 15.4

Fa2/0/14 auto off 0.0 n/a n/a 15.4

Fa2/0/15 auto off 0.0 n/a n/a 15.4

Fa2/0/16 auto off 0.0 n/a n/a 15.4

Fa2/0/17 auto off 0.0 n/a n/a 15.4

Fa2/0/18 auto off 0.0 n/a n/a 15.4

Fa2/0/19 auto off 0.0 n/a n/a 15.4

Interface Admin Oper Power Device Class Max

(Watts)

--------- ------ ---------- ------- ------------------- ----- ----

Fa2/0/20 auto off 0.0 n/a n/a 15.4

Fa2/0/21 auto off 0.0 n/a n/a 15.4

Fa2/0/22 auto off 0.0 n/a n/a 15.4

Fa2/0/23 auto off 0.0 n/a n/a 15.4

Fa2/0/24 auto off 0.0 n/a n/a 15.4

Fa2/0/25 auto off 0.0 n/a n/a 15.4

Fa2/0/26 auto off 0.0 n/a n/a 15.4

Fa2/0/27 auto off 0.0 n/a n/a 15.4

Fa2/0/28 auto off 0.0 n/a n/a 15.4

Fa2/0/29 auto off 0.0 n/a n/a 15.4

Fa2/0/30 auto off 0.0 n/a n/a 15.4

Fa2/0/31 auto off 0.0 n/a n/a 15.4

Fa2/0/32 auto off 0.0 n/a n/a 15.4

Fa2/0/33 auto off 0.0 n/a n/a 15.4

Fa2/0/34 auto on 12.2 AIR-LAP1131AG-A-K9 3 15.4

Fa2/0/35 auto off 0.0 n/a n/a 15.4

Fa2/0/36 auto off 0.0 n/a n/a 15.4

Fa2/0/37 auto off 0.0 n/a n/a 15.4

Fa2/0/38 auto off 0.0 n/a n/a 15.4

Fa2/0/39 auto off 0.0 n/a n/a 15.4

Fa2/0/40 auto off 0.0 n/a n/a 15.4

Fa2/0/41 auto off 0.0 n/a n/a 15.4

Fa2/0/42 auto off 0.0 n/a n/a 15.4

Fa2/0/43 auto off 0.0 n/a n/a 15.4

Fa2/0/44 auto off 0.0 n/a n/a 15.4

Fa2/0/45 auto off 0.0 n/a n/a 15.4

Fa2/0/46 auto off 0.0 n/a n/a 15.4

Fa2/0/47 auto off 0.0 n/a n/a 15.4

Fa2/0/48 auto off 0.0 n/a n/a 15.4

WIRELSS-SWITCH#

Leo Laohoo · ‎01-09-2012

Nuts. A WS-C3750-48P. This model doesn't support TDR.

mangesh-bhende · ‎01-09-2012

What TDR has to do with POE for AP?

Leo Laohoo · ‎01-09-2012

What TDR has to do with POE for AP?

Read this link: How to use Time-Domain Reflectometer (TDR)

mangesh-bhende · ‎01-09-2012

Hi,

I have 2 AP's of the same model and one is working perfectly fine and other is not. in that case can i conclude that the issue is not with switch and we dont need to check for the cable?

Leo Laohoo · ‎01-09-2012

in that case can i conclude that the issue is not with switch and we dont need to check for the cable?

That is not what I implied. Your switch, a Cisco WS-C3750-48P, does NOT support TDR so I cannot recommend you to test it. I would, however, urge you to replace all the patch cable and observe if the WAP still reboots.

mangesh-bhende · ‎01-09-2012

Hi leolaohoo,

Yes i tried but no lock.

Mangesh Bhende