WLC roaming debug assistance
I'm in a position where I need to prove that a suppliers device doesn't truly roam between APs on a WLC. The device will eventually drop the AP when the signal is low enough and then re-authenticate to a new AP, but it doesn't seamlessly roam.
As far as proving it, on the WLC Client Detail page, the device doesn't support CCX extensions, which, as far as I understand, is probably evidence enough in itself.
I've also logged the device and have only ever seen
xx:xx:xx:xx:xx Association received from mobile on BSSID aa:aa:aa:aa:aa
I've never seen a
xx:xx:xx:xx:xx Reassociation received from mobile on BSSID aa:aa:aa:aa:aa
Is that evidence enough that that device doesn't actually roam?
Is there a more elegant way, in layman's terms, to prove the point?
Hi
I can see multiple time given client authentication failed. So it is look like given client unable to connect to the network. See the reference time interval & Access-Reject message for this client.
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 Processing Access-Reject for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 apfMsPeapSimReqCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 apfMsPeapSimReqFailureCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 PMK: Sending cache delete
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 Removing PMK cache entry for station 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 1 PMK-remove groupcast messages sent
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 Removing PMK cache due to EAP-Failure for mobile 00:80:48:78:50:65 (EAP Id 167)
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 Sending EAP-Failure to mobile 00:80:48:78:50:65 (EAP Id 167)
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.536: 00:80:48:78:50:65 Entering Backend Auth Failure state (id=167) for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.537: 00:80:48:78:50:65 Setting quiet timer for 5 seconds for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:43:20.537: 00:80:48:78:50:65 dot1x - moving mobile 00:80:48:78:50:65 into Unknown state
*osapiBsnTimer: Sep 22 10:44:31.404: 00:80:48:78:50:65 802.1x 'timeoutEvt' Timer expired for station 00:80:48:78:50:65 and for message = M0
*dot1xMsgTask: Sep 22 10:44:31.404: 00:80:48:78:50:65 Retransmit 1 of EAP-Request (length 95) for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.418: 00:80:48:78:50:65 Received EAPOL EAPPKT from mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.419: 00:80:48:78:50:65 Received EAP Response from mobile 00:80:48:78:50:65 (EAP Id 231, EAP Type 25)
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.419: 00:80:48:78:50:65 Resetting reauth count 0 to 0 for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.419: 00:80:48:78:50:65 Entering Backend Auth Response state for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 Processing Access-Reject for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 apfMsPeapSimReqCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 apfMsPeapSimReqFailureCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 1 PMK-remove groupcast messages sent
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 Removing PMK cache due to EAP-Failure for mobile 00:80:48:78:50:65 (EAP Id 231)
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 Sending EAP-Failure to mobile 00:80:48:78:50:65 (EAP Id 231)
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 Entering Backend Auth Failure state (id=231) for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 Setting quiet timer for 5 seconds for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:44:31.423: 00:80:48:78:50:65 dot1x - moving mobile 00:80:48:78:50:65 into Unknown state
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.319: 00:80:48:78:50:65 Resetting reauth count 0 to 0 for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.320: 00:80:48:78:50:65 Entering Backend Auth Response state for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Processing Access-Reject for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 apfMsPeapSimReqCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 apfMsPeapSimReqFailureCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 1 PMK-remove groupcast messages sent
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Removing PMK cache due to EAP-Failure for mobile 00:80:48:78:50:65 (EAP Id 140)
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Sending EAP-Failure to mobile 00:80:48:78:50:65 (EAP Id 140)
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Entering Backend Auth Failure state (id=140) for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 apfBlacklistMobileStationEntry2 (apf_ms.c:6172) Changing state for mobile 00:80:48:78:50:65 on AP 6c:99:89:77:41:e0 from Associated to Exclusion-list (1)
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Scheduling deletion of Mobile Station: (callerId: 44) in 10 seconds
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 10.0.45.201 8021X_REQD (3) Change state to START (0) last state 8021X_REQD (3)
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 10.0.45.201 START (0) Reached FAILURE: from line 5620
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Scheduling deletion of Mobile Station: (callerId: 9) in 10 seconds
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Max AAA failure for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 Setting quiet timer for 5 seconds for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:47:28.327: 00:80:48:78:50:65 dot1x - moving mobile 00:80:48:78:50:65 into Unknown state
*osapiBsnTimer: Sep 22 10:47:33.204: 00:80:48:78:50:65 802.1x 'quiteWhile' Timer expired for station 00:80:48:78:50:65 and for message = M0
*osapiBsnTimer: Sep 22 10:47:38.204: 00:80:48:78:50:65 apfMsExpireCallback (apf_ms.c:632) Expiring Mobile!
*apfReceiveTask: Sep 22 10:47:38.204: 00:80:48:78:50:65 Freeing EAP Retransmit Bufer for mobile 00:80:48:78:50:65
*apfReceiveTask: Sep 22 10:47:38.204: 00:80:48:78:50:65 Sent Deauthenticate to mobile on BSSID 6c:99:89:77:41:e0 slot 0(caller apf_ms.c:7065)
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.223: 00:80:48:78:50:65 Sending EAP Request from AAA to mobile 00:80:48:78:50:65 (EAP Id 31)
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.223: 00:80:48:78:50:65 Reusing allocated memory for EAP Pkt for retransmission to mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.233: 00:80:48:78:50:65 Received EAPOL EAPPKT from mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.233: 00:80:48:78:50:65 Received EAP Response from mobile 00:80:48:78:50:65 (EAP Id 31, EAP Type 25)
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.233: 00:80:48:78:50:65 Resetting reauth count 0 to 0 for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.233: 00:80:48:78:50:65 Entering Backend Auth Response state for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.240: 00:80:48:78:50:65 Processing Access-Reject for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.240: 00:80:48:78:50:65 apfMsPeapSimReqCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.240: 00:80:48:78:50:65 apfMsPeapSimReqFailureCntInc
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.241: 00:80:48:78:50:65 1 PMK-remove groupcast messages sent
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.241: 00:80:48:78:50:65 Removing PMK cache due to EAP-Failure for mobile 00:80:48:78:50:65 (EAP Id 31)
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.241: 00:80:48:78:50:65 Sending EAP-Failure to mobile 00:80:48:78:50:65 (EAP Id 31)
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.241: 00:80:48:78:50:65 Entering Backend Auth Failure state (id=31) for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.241: 00:80:48:78:50:65 Setting quiet timer for 5 seconds for mobile 00:80:48:78:50:65
*Dot1x_NW_MsgTask_5: Sep 22 10:52:47.241: 00:80:48:78:50:65 dot1x - moving mobile 00:80:48:78:50:65 into Unknown state
Also few times client forced to go to START status from RUN status with below reasoning. Make sure you disable management frame protection (802.11w) on this WLAN. Also if this is FlexConnect deployment, make sure you use FlexConnect Group if you required to support Opportunistic Key Caching (kind of fast roaming)
*apfMsConnTask_7: Sep 22 11:02:23.723: 00:80:48:78:50:65 apfValidateDot11wGroupMgmtCipher:1552, Received NULL 11w Group Mgmt Cipher Suite for STA, hence returning
*apfMsConnTask_7: Sep 22 11:02:23.723: 00:80:48:78:50:65 AID 1 in Assoc Req from flex AP 68:86:a7:29:cf:60 is same as in mscb 00:80:48:78:50:65
*apfMsConnTask_7: Sep 22 11:02:23.723: 00:80:48:78:50:65 apfMsRunStateDec
*apfMsConnTask_7: Sep 22 11:02:23.723: 00:80:48:78:50:65 apfMs1xStateDec
*apfMsConnTask_7: Sep 22 11:02:23.723: 00:80:48:78:50:65 10.0.45.201 RUN (20) Change state to START (0) last state RUN (20)
HTH
Rasika
**** Pls rate all useful responses ****
Similar Messages
-
GUest WLAN with Anchor WLC - roaming problems
Hello,
my wireless network consists in 3 WLC 4402 which manage 40 APs.
I have a fourth WLC which I installed on my DMZ for guest vlan anchoring and web autentication.
Everiting works fine but I have a problem:
If my client associates with an AP and then I authenticate I'm ready to make traffic. As soon as my client roams to an AP managed by a differnt WLC I need to authenticate again. If I roam back to the first AP i need to reauthenticate.
In my guest WLAN I use WEB authentication provided by the internal web server of the Anchor WLC.
Thnks everybodyHere are the output of show mobility summary.
The last WLC is the anchor.
WLC1
Symmetric Mobility Tunneling (current) .......... Disabled
Symmetric Mobility Tunneling (after reboot) ..... Disabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... mob1
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0x392f
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 2
Mobility Control Message DSCP Value.............. 0
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Sta
tus
00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
00:23:04:7d:73:20 10.20.1.21 mob1 0.0.0.0 Up
WLC2
Symmetric Mobility Tunneling (current) .......... Disabled
Symmetric Mobility Tunneling (after reboot) ..... Disabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... mob1
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0x392f
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 2
Mobility Control Message DSCP Value.............. 0
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Sta
tus
00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
00:23:04:7d:62:a0 10.20.1.22 mob1 0.0.0.0 Up
WLC3
Symmetric Mobility Tunneling (current) .......... Disabled
Symmetric Mobility Tunneling (after reboot) ..... Disabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... mob1
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0x392f
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 2
Mobility Control Message DSCP Value.............. 0
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Sta
tus
00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
00:23:04:7d:79:80 10.20.2.21 mob1 0.0.0.0 Up
WLCAnchor
(Cisco Controller) >show mobility summary
Symmetric Mobility Tunneling (current) .......... Disabled
Symmetric Mobility Tunneling (after reboot) ..... Disabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... mob1
Multicast Mode .................................. Disabled
Mobility Domain ID for 802.11r................... 0x392f
Mobility Keepalive Interval...................... 10
Mobility Keepalive Count......................... 3
Mobility Group Members Configured................ 4
Mobility Control Message DSCP Value.............. 0
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Multicast IP Sta
tus
00:23:04:7d:3e:e0 10.25.1.21 mob1 0.0.0.0 Up
00:23:04:7d:62:a0 10.20.1.22 mob1 0.0.0.0 Up
00:23:04:7d:73:20 10.20.1.21 mob1 0.0.0.0 Up
00:23:04:7d:79:80 10.20.2.21 mob1 0.0.0.0 Up -
Hello,
I have more different client networks with one ssid, when a client is in another network gets an ip it still from the old network.
How can I to the wlc change this so he gets one right address.
I have a Cisco WLC 5508 and 1262/1252 Access point
thanksPerhaps I'm missing the point of your post......
But we need to clarify what you are asking for.
From the few posts here, I understand that Client 1 at Site A gets an IP address from site A. When Client 1 roams to Site B, they continue to have the IP address from Site A. You don't want this?
So what is happening:
Layer 3 mobility.
When you roam from Site A to Site B, you should be anchored back to your original controller and should function with your IP address. So from client perspective, absolutely nothing should be wrong.
Now, are you trying to say that Clients that Roamed from Site A to Site B, cannot talk to Site B resources with the Site A address? That would be the only reason I can think of where you'd "not work".
If you absolutely don't want Layer 3 roaming, then you have two options:
1) Do not allow your WLCs to be mobility aware. If they do not have each other in the mobility domain, no mobility will take place and your client will stay Layer 2.
2) (theory) Change your Virtual IP address between the two controllers. Mobility Handoff is rejected if the Virtual IP does not match. So when your client is handed off layer 3, the Site A WLC will not accept it and will remove the client instead of anchor.
The problem with that above however is that you need a client that is stupid enough to re-DHCP as soon as it roams....
If you have IP 10.10.1.10, and you roam to a new stie, with no L3 roaming, you're going to need a client that will either always re-dhcp, or will quickly learn 10.10.1.10 is not valid.....
Long Story short:
L3 Mobility is there for a reason and there is no "disable" button. Either allow your network to function with L3 clients, or configure it so L3 mobility will not happen. -
Student Requests Debug Assistance
Hello, I am a new Java Programmer.
Recently I was assigned a computer science project at my school - To create a Tic-Tac-Toe game.
Seeing as I have some previous programming experience, I had no serious trouble creating the game logic and output and so on. However, I did run into trouble when I attempted to create a way for the user to input text into the application (this is not an applet, by the way!)
If anyone would be so kind as to see if they can spot my error, the program can be found here: http://docuk.ath.cx/work/TicTacToe.java
I have commented all functions and where I believe the error to originate. I think it is easier to solve the problem if you compile the program yourself, however, and play a game through.
Thank you in advance for your assistance!
DocUKWell it seems that the method read reads the next byte of data from the input stream. The value byte is returned as an integerm but the integer will be -1 if the end of the stream has been reached.
However, I don't see how this could possibly be causing the extra print. When you say there are new lines and carriage returns too, that makes me think that when i see the added "Enter the field:" it is because the program 'automatically' enters newline and or carriage return.
I still do not see how I can solve this problem, however... :( -
WLC 5760 - show client ccx roam-history
Hi,
We're running an WLC 5760 with the latests version (3.3.1). We have several wlans, with diferent authentication methods, and they are all working fine.
However we noticed that the roaming is working correctly but no information is displayed if the "show ccx roam-history".
WLC1#sh wireless client mac-address 8853.2e9e.f70a det | i CCX
Client CCX version : 4
WLC1#debug dot11 ccx-roam all
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Mobile 8853.2e9e.f70a associated
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending Neighbor List packet to Mobile 8853.2e9e.f70a
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending L2Roam Packet to mobile 8853.2e9e.f70a
Dec 12 17:11:40.963: 00000000: 1 wcm: 01 1a 33 81 88 53 2e 9e f7 0a c0 25 5c 68 50 50 ..3..S.....%\hPP
Dec 12 17:11:40.963: 00000010: 1 wcm: 28 11 c0 25 5c 68 50 50 01 00 02 01 06 ab 0d 0d (..%\hPP........
Dec 12 17:11:40.963: 00000020: 1 wcm: 03 b8 05 28 11 c0 25 5c ec 05 a0 0b 00 07 01 06 ...(..%\........
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000030: ab 0d 0d 03 b8 05 28 11 0c 68 03 ea 52 10 06 00 ......(..h..R...
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000040: 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 03 d6 e4 .........(..h...
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000050: 00 0b 00 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 ............(..h
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000060: 03 4d d0 60 01 00 07 01 06 ab 0d 0d 03 b8 05 28 .M.`...........(
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000070: 11 0c 68 03 ea 40 70 01 00 07 01 06 ab 0d 0d 03 ..h..@p.........
Dec 12 17:11:40.963: %IOSXE-7-PLATFORM: 1 process wcm: 00000080: b8 05 28 11 0c 68 03 ea 4b 10 01 00 07 01 06 ab ..(..h..K.......
Dec 12 17:11:40.963: 00000090: 1 wcm: 0d 0d 03 b8 05 28 11 c0 25 5c 68 50 5f 3c 01 04 .....(..%\hP_<..
Dec 12 17:11:40.964: 000000a0: 1 wcm: 01 06 ab 12 12 03 b8 05 28 11 c0 25 5c ec 05 af ........(..%\...
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000b0: 24 01 07 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 $..........(..h.
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000c0: ea 52 1f 24 01 07 01 06 ab 12 12 03 b8 05 28 11 .R.$..........(.
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000d0: 0c 68 03 ea 4b 1f 38 01 07 01 06 ab 12 12 03 b8 .h..K.8.........
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 000000e0: 05 28 11 0c 68 03 d6 e4 0f 38 01 07 01 06 ab 12 .(..h....8......
Dec 12 17:11:40.964: 000000f0: 1 wcm: 12 03 b8 05 28 11 c0 25 5c a3 f4 8f 30 01 07 01 ....(..%\...0...
WLC1#
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 00000100: 06 ab 12 12 03 b8 05 28 11 0c 68 03 ea 40 7f 30 .......([email protected]
Dec 12 17:11:40.964: %IOSXE-7-PLATFORM: 1 process wcm: 00000110: 01 07 01 06 ab 12 12 03 b8 05 ..........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Received Neighbor List Request from Mobile 8853.2e9e.f70a
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending Neighbor List packet to Mobile 8853.2e9e.f70a
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending L2Roam Packet to mobile 8853.2e9e.f70a
Dec 12 17:12:51.006: 00000000: 1 wcm: 01 1a 33 81 88 53 2e 9e f7 0a c0 25 5c 68 50 50 ..3..S.....%\hPP
Dec 12 17:12:51.006: 00000010: 1 wcm: 28 11 c0 25 5c 68 50 50 01 00 02 01 06 ab 0d 0d (..%\hPP........
Dec 12 17:12:51.006: 00000020: 1 wcm: 03 b8 05 28 11 c0 25 5c ec 05 a0 0b 00 07 01 06 ...(..%\........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000030: ab 0d 0d 03 b8 05 28 11 0c 68 03 ea 52 10 06 00 ......(..h..R...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000040: 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 03 d6 e4 .........(..h...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000050: 00 0b 00 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 ............(..h
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000060: 03 4d d0 60 01 00 07 01 06 ab 0d 0d 03 b8 05 28 .M.`...........(
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000070: 11 0c 68 03 ea 40 70 01 00 07 01 06 ab 0d 0d 03 ..h..@p.........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000080: b8 05 28 11 0c 68 03 ea 4b 10 01 00 07 01 06 ab ..(..h..K.......
Dec 12 17:12:51.006: 00000090: 1 wcm: 0d 0d 03 b8 05 28 11 c0 25 5c 68 50 5f 3c 01 04 .....(..%\hP_<..
Dec 12 17:12:51.006: 000000a0: 1 wcm: 01 06 ab 12 12 03 b8 05 28 11 c0 25 5c ec 05 af ........(..%\...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000b0: 24 01 07 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 $..........(..h.
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000c0: ea 52 1f 24 01 07 01 06 ab 12 12 03 b8 05 28 11 .R.$..........(.
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000d0: 0c 68 03 ea 4b 1f 38 01 07 01 06 ab 12 12 03 b8 .h..K.8.........
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 000000e0: 05 28 11 0c 68 03 d6 e4 0f 38 01 07 01 06 ab 12 .(..h....8......
Dec 12 17:12:51.006: 000000f0: 1 wcm: 12 03 b8 05 28 11 c0 25 5c a3 f4 8f 30 01 07 01 ....(..%\...0...
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000100: 06 ab 12 12 03 b8 05 28 11 0c 68 03 ea 40 7f 30 .......([email protected]
Dec 12 17:12:51.006: %IOSXE-7-PLATFORM: 1 process wcm: 00000110: 01 07 01 06 ab 12 12 03 b8 05 ..........
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Received Neighbor List Request from Mobile 8853.2e9e.f70a
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending Neighbor List packet to Mobile 8853.2e9e.f70a
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 8853.2e9e.f70a Sending L2Roam Packet to mobile 8853.2e9e.f70a
Dec 12 17:15:48.712: 00000000: 1 wcm: 01 07 33 81 88 53 2e 9e f7 0a c0 25 5c 68 81 20 ..3..S.....%\h..
Dec 12 17:15:48.712: 00000010: 1 wcm: 28 11 c0 25 5c 68 81 20 01 00 02 01 06 ab 0d 0d (..%\h..........
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 00000020: 03 b8 05 28 11 0c 68 03 ea 52 10 06 00 07 01 06 ...(..h..R......
Dec 12 17:15:48.712: %IOSXE-7-PLATFORM: 1 process wcm: 00000030: ab 0d 0d 03 b8 05 28 11 0c 68 03 ea 4a f0 0b 00 ......(..h..J...
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000040: 07 01 06 ab 0d 0d 03 b8 05 28 11 0c 68 03 d6 eb .........(..h...
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000050: 20 01 00 07 01 06 ab 0d 0d 03 b8 05 28 11 c0 25 ............(..
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000060: 5c ec 05 a0 0b 00 07 01 06 ab 0d 0d 03 b8 05 28 \..............(
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000070: 11 0c 68 03 d6 e4 00 0b 00 07 01 06 ab 0d 0d 03 ..h.............
Dec 12 17:15:48.713: 00000080: 1 wcm: b8 05 28 11 c0 25 5c 68 50 50 01 00 07 01 06 ab ..(..%\hPP......
Dec 12 17:15:48.713: 00000090: 1 wcm: 0d 0d 03 b8 05 28 11 c0 25 5c 68 81 2f 38 01 04 .....(..%\h./8..
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000a0: 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 ea 4a ff ........(..h..J.
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000b0: 2c 01 07 01 06 ab 12 12 03 b8 05 28 11 0c 68 03 ,..........(..h.
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000c0: ea 52 1f 24 01 07 01 06 ab 12 12 03 b8 05 28 11 .R.$..........(.
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000d0: 0c 68 03 d6 e4 0f 38 01 07 01 06 ab 12 12 03 b8 .h....8.........
Dec 12 17:15:48.713: 000000e0: 1 wcm: 05 28 11 c0 25 5c ec 05 af 24 01 07 01 06 ab 12 .(..%\...$......
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 000000f0: 12 03 b8 05 28 11 0c 68 03 d6 eb 2f 3c 01 07 01 ....(..h.../<...
Dec 12 17:15:48.713: %IOSXE-7-PLATFORM: 1 process wcm: 00000100: 06 ab 12 12 03 b8 05 .......
WLC1#show wireless client mac-address 8853.2e9e.f70a ccx roam-history
Shouldn't the output be the same as the AireOS command "show client roam-history client-mac"?
Kind regards,
Vasco CostaObtaining CCX Client Roaming Information (CLI)
Step 1
View the current RF parameters configured for client roaming for the 802.11a or 802.11b/g network by entering this command:show {802.11a | 802.11b} l2roam rf-param
Step 2
View the CCX Layer 2 client roaming statistics for a particular access point by entering this command:show {802.11a | 802.11b} l2roam statistics ap_mac
This command provides the following information:
The number of roam reason reports received
The number of neighbor list requests received
The number of neighbor list reports sent
The number of broadcast neighbor updates sent
Step 3
View the roaming history for a particular client by entering this command:show client roam-history client_mac
This command provides the following information:
The time when the report was received
The MAC address of the access point to which the client is currently associated
The MAC address of the access point to which the client was previously associated
The channel of the access point to which the client was previously associated
The SSID of the access point to which the client was previously associated
The time when the client disassociated from the previous access point
The reason for the client roam
Debugging CCX Client Roaming Issues (CLI)
If you experience any problems with CCX Layer 2 client roaming, enter this command:
debug l2roam [detail | error | packet | all] {enable | disable} -
How can I debug Aggressive Load Balancing on the WLC ?
Hello Cisco-Experts,
I'm looking for the command on the Cisco WLC to debug Aggressive Load-Balancing.
There is a nice document, ID 107457 describing this feature, but it lacks the command.
Please investigate and help me and maybe improve YOur documentations.
Thanks in advance
WinfriedHello NetPros,
I have disabled now "Agressive Load Balancing" now on the WLC. To my surprise, still Load-balancing packets are received from our HREAP-APs via a WAN-Link on the central WLC.
Here is an example:
Tue Jan 13 15:35:59 2009: 00:1c:bf:4a:3f:2e LBS data stored for Mobile 00:1c:bf:4a:3f:2e from AP 00:23:5d:0e:e9:e0(0) new saved RS
SI (A -128, B -53), SNR 41, inUse 1, [rcvd RSSI (A -128, B -54), SNR 40]
Tue Jan 13 15:35:59 2009: 00:1c:bf:4a:3f:2e LBS data rcvd for Mobile 00:1c:bf:4a:3f:2e from AP 00:23:5d:0e:e9:e0(0) with RSSI (A -
128, B -55), SNR 42
Tue Jan 13 15:35:59 2009: 00:1c:bf:4a:3f:2e LBS data stored for Mobile 00:1c:bf:4a:3f:2e from AP 00:23:5d:0e:e9:e0(0) new saved RS
SI (A -128, B -54), SNR 41, inUse 1, [rcvd RSSI (A -128, B -55), SNR 42]
It is remarkable that the MAC-addresses of many of the WLAN-clients do not belong to our company and packets are send via a WAN-link.
Why do I see these packets while load-balancing is disabled ?
How is this working ?
Thank You for any explanation.
Winfried -
AP 360021 cannot join WLC 5508
Dears,
I have a cisco 5508 WLC and 40 cisco 360021 APs.
I configured the WLC and assign the management interface IP and also configured a DHCP pool on my Cisco 4507 core switch wit option 43.
But the problem that the APs connot join the WLC.
The below message appears:-
Nov 7 09:08:28.953: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 7 09:08:28.954: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
*Nov 7 09:08:38.968: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Nov 7 09:08:39.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: x.x.x.x pe6
*Nov 7 09:08:39.000: %CAPWAP-5-CHANGED: CAPWAP changed state to
Please support me to solve this issue.
Regards,Dears,
Also find the attched debug and the requirements that you asked for.
AP cisco debug:
*Oct 13 01:33:32.691: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:34.691: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Oct 13 01:33:35.691: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Oct 13 01:33:35.691: %SYS-6-LOGGINGHOST_STARTSTOP: Logging to host 255.255.255.255 started - CLI initiated
*Oct 13 01:33:37.815: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Oct 13 01:33:37.903: status of voice_diag_test from WLC is false
*Oct 13 01:33:37.907: %CAPWAP-3-ERRORLOG: Not sending discovery request AP does not have an Ip !!
*Oct 13 01:33:37.907: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:38.815: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:38.867: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:38.875: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:39.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:39.223: %DHCP-6-ADDRESS_ASSIGN: Interface GigabitEthernet0 assigned DHCP address 10.10.107.58, mask 255.255.255.0, hostname APfc99.47a2.2ef7
*Oct 13 01:33:39.223: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:39.899: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:40.899: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Oct 13 01:33:43.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:43.259: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 10.10.107.58, mask 255.255.255.0, hostname APfc99.47a2.2ef7
*Oct 13 01:33:43.259: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Oct 13 01:33:47.907: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Oct 13 01:33:48.315: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Oct 13 01:33:48.379: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (10.10.18.1) (10.10.18.100)
ministratively down
*Oct 13 01:33:48.467: status of voice_diag_test from WLC is false
*Oct 13 01:33:48.471: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:49.379: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:49.431: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:49.439: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:49.471: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Oct 13 01:33:49.471: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Oct 13 01:33:50.463: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:51.463: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Oct 13 01:33:52.475: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:52.483: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:53.475: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:53.507: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:54.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 23 23:47:46.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 23 23:47:46.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 23 23:47:46.583: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
*Mar 23 23:47:47.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 23 23:47:48.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 23 23:47:48.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 23 23:47:48.211: status of voice_diag_test from WLC is false
*Mar 23 23:47:48.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 23 23:47:49.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 23 23:47:49.171: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 23 23:47:49.179: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 23 23:47:50.207: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 23 23:47:51.207: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 23 23:47:51.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 23 23:47:51.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 23 23:47:52.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 23 23:47:52.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 23 23:47:53.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
CAPWAP-3-ERRORLOG: Failed to process encrypted capwap packet from 10.10.107.5
*Mar 24 00:25:36.579: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 24 00:25:36.579: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 24 00:25:36.579: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
APfc99.47a2.2ef7#
%CAPWAP-3-ERRORLOG: CAPWAP SM handler: Failed to process message type 10 state 5.
*Mar 24 00:33:27.519: %CAPWAP-3-ERRORLOG: Failed to handle capwap control message from controller
*Mar 24 00:33:28.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 00:33:28.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 00:33:28.043: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 00:33:28.051: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 00:33:29.079: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 00:33:30.079: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 00:33:32.519: %CAPWAP-5-SENDJOIN: sending Join Request to 10.10.107.5
*Mar 24 00:33:32.523: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 00:33:32.531: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 00:33:33.523: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 00:33:33.555: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 00:33:34.555: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radi
The Time on AP is not same time on the WLC
Oct 13 01:34:13.411: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:02:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:02:36.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
User Access Verification
Username:
*Mar 24 02:02:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:02:37.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:02:37.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:02:38.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Username:
*Mar 24 02:03:05.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
Username: Cisco
Password:
APfc99.47a2.2ef7>
*Oct 13 01:34:13.411: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:02:36.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:02:36.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
User Access Verification
Username:
*Mar 24 02:02:36.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:02:37.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:02:37.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:02:38.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Username:
*Mar 24 02:03:05.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
Username: Cisco
Password:
APfc99.47a2.2ef7>
*Mar 24 02:04:31.603: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880?
memory set memory parameters
APfc99.47a2.2ef7#set
*Mar 24 02:04:33.103: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-start
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar 24 02:04:33.207: %CAPWAP-3-ERRORLOG: Failed to process timer messag
APfc99.47a2.2ef7#
*Mar 24 02:04:38.159: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:04:38.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:04:38.315: status of voice_diag_test from WLC is false
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:04:38.315: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:04:39.223: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:04:39.275: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:04:39.283: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
%DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 24 02:06:58.999: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:05:59.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:05:59.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:05:59.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:06:00.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:06:00.039: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:06:01.039: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
APfc99.47a2.2ef7#
APfc99.47a2.2ef7#
*Mar 24 02:09:50.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
APfc99.47a2.2ef7#
APfc99.47a2.2ef7#
APfc99.47a2.2ef7#
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:10:20.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 24 02:10:21.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:10:21.123: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:10:21.207: status of voice_diag_test from WLC is false
*Mar 24 02:10:21.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:22.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:10:22.175: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:10:22.183: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:10:23.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:24.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:10:25.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 24 02:10:25.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 24 02:10:25.787: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
*Mar 24 02:10:30.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:10:30.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:10:30.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:10:31.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:10:31.251: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:32.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:10:49.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:10:49.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:10:49.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:10:50.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:10:50.251: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:10:51.251: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:11:08.211: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:11:08.215: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:11:08.223: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:11:09.215: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:11:09.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:10.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:11:16.607: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
*Mar 24 02:11:18.107: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Mar 24 02:11:18.211: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Mar 24 02:11:23.163: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:11:23.227: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:11:23.319: status of voice_diag_test from WLC is false
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:11:23.319: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:24.227: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:11:24.275: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:11:24.283: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:11:25.311: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:26.311: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:11:33.319: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:11:33.323: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:11:33.331: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:11:34.323: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:11:34.355: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:11:35.355: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:11:43.319: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Mar 24 02:12:43.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.10.107.5 peer_port: 5246
*Mar 24 02:12:43.003: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:12:43.011: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:12:44.003: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:12:44.035: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:12:45.035: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
*Mar 24 02:17:05.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 10.10.107.5:5246
*Mar 24 02:17:06.055: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Mar 24 02:17:06.119: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 24 02:17:06.203: status of voice_diag_test from WLC is false
*Mar 24 02:17:06.207: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:07.119: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:17:07.171: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:17:07.179: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:17:08.203: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:09.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:17:10.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
*Mar 24 02:17:10.787: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
*Mar 24 02:17:10.787: %MESH-6-LINK_UPDOWN: Mesh station fc99.47a2.2ef7 link Down
*Mar 24 02:17:15.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:17:15.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:17:15.219: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:17:16.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:17:16.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:17.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:17:53.207: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
*Mar 24 02:17:53.211: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Mar 24 02:17:53.219: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Mar 24 02:17:54.211: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 24 02:17:54.247: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Mar 24 02:17:55.247: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*Mar 24 02:18:01.607: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
*Mar 24 02:18:03.107: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
*Mar 24 02:18:03.207: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Mar 24 02:18:03.207: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Even
Show requirement for AP:-
APfc99.47a2.2ef7#show version
Cisco IOS Software, C3600 Software (AP3G2-K9W8-M), Version 12.4(25e)JA, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Fri 27-Jan-12 21:27 by prod_rel_team
ROM: Bootstrap program is C3600 boot loader
BOOTLDR: C3600 Boot Loader (AP3G2-BOOT-M) LoaderVersion 12.4(23c)JY, RELEASE SOFTWARE (fc1)
APfc99.47a2.2ef7 uptime is 7 minutes
System returned to ROM by power-on
System image file is "flash:/ap3g2-k9w8-mx.124-25e.JA/ap3g2-k9w8-mx.124-25e.JA"
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
[email protected].
cisco AIR-CAP3602I-A-K9 (PowerPC) processor (revision A0) with 167926K/81920K bytes of memory.
Processor board ID FGL1644Z15P
PowerPC CPU at 800Mhz, revision number 0x2151
Last reset from power-on
LWAPP image version 7.2.1.72
1 Gigabit Ethernet interface
2 802.11 Radio(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: FC:99:47:A2:2E:F7
Part Number : 73-14521-02
PCA Assembly Number : 800-37501-02
PCA Revision Number : A0
PCB Serial Number : FOC16414A83
Top Assembly Part Number : 800-35852-02
Top Assembly Serial Number : FGL1644Z15P
Top Revision Number : C0
Product/Model Number : AIR-CAP3602I-A-K9
Configuration register is 0xF
show inventry
NAME: "AP3600", DESCR: "Cisco Aironet 3600 Series (IEEE 802.11n) Access Point"
PID: AIR-CAP3602I-A-K9 , VID: V01, SN: FGL1644Z15P
show requirement on WLC
(Cisco Controller) >show sysinfo
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.4.100.0
Bootloader Version............................... 1.0.1
Field Recovery Image Version..................... 6.0.182.0
Firmware Version................................. FPGA 1.3, Env 1.6, USB console 1.27
Build Type....................................... DATA + WPS
System Name...................................... Cisco_61:d8:84
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1069
Redundancy Mode.................................. Disabled
IP Address....................................... 10.10.107.5
Last Reset....................................... Software reset
System Up Time................................... 0 days 1 hrs 4 mins 25 secs
System Timezone Location......................... (GMT +3:00) Baghdad
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
Configured Country............................... IQ - Iraq
Operating Environment............................ Commercial (0 to 40 C)
--More-- or (q)uit
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +40 C
External Temperature............................. +24 C
Fan Status....................................... OK
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Memory Current Usage............................. Unknown
Memory Average Usage............................. Unknown
CPU Current Usage................................ Unknown
CPU Average Usage................................ Unknown
Burned-in MAC Address............................ 00:06:F6:61:D8:80
Power Supply 1................................... Present, OK
Power Supply 2................................... Absent
Maximum number of APs supported.................. 100
WLC after debug enable
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV6 Address len = 99
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: Mwar type payload len = 110
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery resp: Time sync payload len = 125
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.60:8944
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.60:8944
*spamApTask6: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 WTP already released
*spamApTask2: Mar 24 04:56:19.133: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 94
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 50
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 45
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 40
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Total msgEleLen = 26
(Cisco Controller) >*sshpmLscTask: Mar 24 05:02:01.461: sshpmLscTask: LSC Task received a message 4
*Oct 13 01:33:48.191: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
User Access Verification
Username:
Username:
Username:
*Oct 13 01:33:50.191: %LINK-3-UPDOWN: Interface BVI1, changed state to up
*Oct 13 01:33:50.191: %IP-4-DUPADDR: Duplicate address 10.10.107.5 on BVI1, sourced by 0006.f661.d880
*Oct 13 01:33:51.191: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message. Event 29, state 4
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
*Oct 13 01:33:52.019: %CAPWAP-3-ERRORLOG: Failed to process timer message.
*Oct 13 01:33:53.251: %LWAPP-3-CLIENTERRORLOG: LWAPP LED Init: incorrect led state 255
*Oct 13 01:33:53.315: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to ad
Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)ministratively down
*Oct 13 01:33:53.407: status of voice_diag_test from WLC is false
*Oct 13 01:33:53.411: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:54.315: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Oct 13 01:33:54.367: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
*Oct 13 01:33:54.375: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
*Oct 13 01:33:55.399: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
*Oct 13 01:33:56.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to up
*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
nable
(Cisco Controller) >*spamApTask2: Mar 24 04:56:19.133: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Total msgEleLen = 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 1. 0 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 2. 232 3
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 3. 0 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 4. 100 0
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: AC Descriptor message element len = 40
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 acName = Cisco_61:d8:84
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV6 Address len = 99
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: Mwar type payload len = 110
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery resp: Time sync payload len = 125
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 Discovery Response sent to 10.10.107.5:8944
*spamApTask2: Mar 24 04:56:19.134: 54:78:1a:43:ca:d0 WTP already released
*spamApTask6: Mar 24 04:56:28.440: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.60:8945
*spamApTask6: Mar 24 04:56:28.440: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.60:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.60:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 94
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 50
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 45
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 40
*spamApTask7: Mar 24 04:56:28.441: fc:99:47:a2:2e:f7 CAPWAP Control Msg Received from 10.10.107.61:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 packet received of length 123 from 10.10.107.61:8945
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Msg Type = 1 Capwap state = 0
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 26
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery Request from 10.10.107.61:8945
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 20
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 94
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 40 msgEleType = 39
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 50
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 41
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 45
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 1 msgEleType = 44
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 1. 0 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 40
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 2. 232 3
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 10 msgEleType = 37
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 3. 0 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 4. 100 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 26
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 msgEleLength = 22 msgEleType = 37
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: AC Descriptor message element len = 40
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Vendor specific payload from AP 54:78:1A:43:CA:D0 validated
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 acName = Cisco_61:d8:84
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Total msgEleLen = 0
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp:AC Name message element length = 58
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: WTP Radio Information msg length = 67
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Join Priority Processing status = 0, Incoming Ap's Priority 4, MaxLrads = 100, joined Aps =0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 1. 0 0
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 2. 232 3
*spamApTask6: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 Discovery resp: CAPWAP Control IPV4 Address len = 77
*spamApTask7: Mar 24 04:56:28.441: 54:78:1a:43:ca:d0 3. 0 0 -
Hi,
I have two WLC 8500 working in SSO and with nat enable feature configure in management interface.
SSO is working, but i have to configure NAT before SSO becasuse when SSO is up, ip address and nat are greyed out in managemente interface.
Some AP's must join the controller in the private address of the management interface and others AP must join in the public ip address configured in NAT address.
for some reason, there are a lot of AP's that can't join the controller, i have 3 ap's joined in the public ip address and 3 ap's joined in the private ip address
config network ap-discovery nat-only disable is already configured, from the console of one AP that can't not join i see the following:
*Sep 10 12:32:48.115: %CAPWAP-3-ERRORLOG: Selected MWAR 'GI12WLC001A'(index 0).
*Sep 10 12:32:48.115: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 10 12:35:48.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 212.89.5.130 peer_port: 5246
*Sep 10 12:36:17.999: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2176 Max retransmission count reached!
*Sep 10 12:36:47.999: %DTLS-5-SEND_ALERT: Send FATAL : Close notify Alert to 212.89.5.130:5246
*Sep 10 12:36:47.999: %CAPWAP-3-ERRORLOG: Selected MWAR 'GI12WLC001A'(index 0).
*Sep 10 12:36:47.999: %CAPWAP-3-ERRORLOG: Go join a capwap controller
*Sep 10 12:35:48.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.35.0.78 peer_port: 5246
the AP is trying both private and public ip address to join the WLC but can't join properly.
From the WLC console:
debug capwap errors enable:
*spamApTask4: Sep 10 13:13:49.837: 00:10:db:ff:50:06 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 10.35.1.13:47807)since DTLS session is not established
*spamApTask3: Sep 10 13:13:49.958: 1c:6a:7a:5b:e0:30 ApModel: AIR-CAP3702I-E-K9
*spamApTask3: Sep 10 13:13:49.958: Unknown AP type. Using Controller Version!!!
*spamApTask3: Sep 10 13:13:49.958: Unknown AP type. Using Controller Version!!!
*spamApTask3: Sep 10 13:13:49.958: 1c:6a:7a:5b:e0:30 ApModel: AIR-CAP3702I-E-K9
*spamApTask3: Sep 10 13:13:49.958: Unknown AP type. Using Controller Version!!!
*spamApTask3: Sep 10 13:13:49.958: Unknown AP type. Using Controller Version!!!
*spamApTask2: Sep 10 13:13:52.103: 00:10:db:ff:50:06 Discarding non-ClientHello Handshake OR DTLS encrypted packet from 10.35.1.11:21207)since DTLS session is not established
*spamApTask1: Sep 10 13:13:52.224: 1c:6a:7a:5e:0f:10 ApModel: AIR-CAP3702I-E-K9
*spamApTask1: Sep 10 13:13:52.224: Unknown AP type. Using Controller Version!!!
*spamApTask1: Sep 10 13:13:52.224: Unknown AP type. Using Controller Version!!!
*spamApTask1: Sep 10 13:13:52.224: 1c:6a:7a:5e:0f:10 ApModel: AIR-CAP3702I-E-K9
*spamApTask1: Sep 10 13:13:52.224: Unknown AP type. Using Controller Version!!!
*spamApTask1: Sep 10 13:13:52.224: Unknown AP type. Using Controller Version!!!
the AP model are the same, this is not the problem, but for some reason there are AP's that have problems with the NAT configuration, if i disable NAT option, every AP with private ip address config can join the WLC.
I've tried to break SSO, desconfigure NAT, and private ip address AP join the controller without problem.
anybody can give me a clue?
Regards!it seens like DTLS connection can't be stablished between AP and WLC.
The AP sends discovery request
the WLC respond with two discovery responds, the firts one, contains the public ip address of the WLC and the second one contains the private ip address.
once discovery proccess is complete, the AP tries to send DTLS hello packet to the WLC, but this packet never arrives to WLC.
because hello doesn't arrive, the AP sends a close notify alert to the WLC and tries to send the DTLS hello packet to the WLC private address with same result.
the AP get into a loop trying to send DTLS hello packets to both private and public address.
DTLS hello packet never arrive, but close notify alert arrive to WLC.
theres is FW in the middle doing NAT, but i can understand why close notify alert packets error arrives WLC and Hello DTLS packets don't. this packets uses the same protocol UDP and the same port.
Regards -
VS2013 not running in debug mode on Windows 10 Technical Preview Build 10041
am getting the following errors every time i try to run my projects in debug mode what can be the issue.
Managed Debugging Assistant 'FatalExecutionEngineError' has detected a problem in 'C:\Program Files (x86)\IIS Express\iisexpress.exe'.
Additional information: The runtime has encountered a fatal error. The address of the error was at 0x73c0d5a5, on thread 0x1a0c. The error code is 0xc0000005. This error may be a bug in the CLR or in the unsafe or non-verifiable portions of user
code. Common sources of this bug include user marshaling errors for COM-interop or PInvoke, which may corrupt the stack.
Then when I continue the following appears
An unhandled exception of type 'System.AccessViolationException' occurred in System.Data.dll
Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Then it stops..
This happens when a database call is made and only does this when debug, when I run it using the browser link all is good. The applications work well.Hi Bigmachini,
According to my solution, what about your issue now?
If you have been solved the issue, would you mind sharing us the solution here? So it would be helpful for other members who get the same issue.
If not, please let us know the latest information about it.
@Malik, could you please tell me if you try to check your issue by the above suggestion as I said?
If no, please try the above suggestions to check this issue and then tell me the latest message about this issue.
>>The error mostly occurs when debugging ADO.NET or database function calls. If code is run without debugging then there is no issue at all.
You could also try to copy your project and then debug your project in debug mode on a another machine you install same Windows 10 OS check this issue again.
Best Regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Bonjour Discovery browser and cisco WLC mDNS
Hello
I'm using a Bonjour Discovery browser on an iPad to see if I can check what Bonjour services are available on a cisco 2504 running code 7.5.102.0. WLC is configured as per cisco documentation for mdns:
Multicast disabled on WLC
wired vlan (with bonjour services) is trunked to WLC
mdns profile configured and bonjour services are visible on WLC
mdns profile applied to WLAN
when i connect an ipad to the wlan and start the browser, no services appear (2 are visible on the WLC). Debug on the WLC shows the following (where XX:XX:XX:XX:XX:XX is the iPad mac)
*Bonjour_Msg_Task: Nov 04 10:51:06.674: XX:XX:XX:XX:XX:XX Failed to updated data to Service Provider DB
*Bonjour_Msg_Task: Nov 04 10:51:12.798: processBonjourPacket : 935 Queried service-string : _dns-sd._udp.local. is not configured in MSAL-DB
Is it possible to get Bonjour Discovery browser working with cisco WLC?
thanks
andyI have used Avahi when I have had deployments that were FlexConnect and the site had multiple subnets for Apple TV's and or the devices that would be using the Apple TV, printers, etc. Avahi is free and my customers would spin this up on an available PC or laptop and connect it to the network.
mDNS AP
1. This feature enhancement allow controllers to have the visibility of wired service providers which are on VLANs that are not visible to the controller.
2. User configuration is required to configure APs as mDNS AP. This configuration allows AP to forward mDNS packets to WLC.
3. VLAN's visibility at WLC is achieved by APs forwarding the mDNS advertisements to controllers. The mDNS packet between AP and controller are forwarded in CAPWAP data tunnel similar to mDNS packets from wireless client.
4. APs can either be in access or trunk mode to learn the mDNS packets from wired side and forward it to the controller.
5. This configuration also allows the user to specify the VLANs from which the AP should snoop the mDNS advertisements from wired side. The maximum number of VLANs that AP can snoop is 10.
6. If the AP is in access mode, the user should NOT configure any VLANs for AP to snoop.
AP will send untagged packets when a query is to be sent. When an mDNS advertisement is received by mDNS AP, VLAN information is not passed to the controller. Hence the service provider's VLAN, learnt via mDNS AP's access VLAN will be maintained as 0 in the controller.
7. If the AP is in trunk mode, then the user has to configure the VLAN on the controller on which AP would snoop & forward the mDNS packets. The native VLAN snooping is enabled by default when mDNS AP is enabled. AP will send VLAN information as 0 for packets snooped on native VLAN.
8. This feature is supported on local and monitor mode AP, and not on Flexconnect mode APs.
9. If a mDNS AP joins/resets (or) joins the same/another controller, the behavior is as follows:
a. If global snooping is disabled on the controller, then a payload will be sent to AP to disable mDNS snooping.
b. If global snooping is enabled on the controller, then configuration of the AP previous to reset/join procedure will be retained.
Thanks,
Scott
*****Help out other by using the rating system and marking answered questions as "Answered"***** -
Hello,
We are implementing a new corporate wireless network with Cisco 5508 WLC 7.6 and 3700i LWAP. We are not running any RADIUS or EAP at the moment and are starting with WPA2 w/ AES with a pre-shared key to start
we configure profiling as following :
each device have an specific vlan on each floor and configure AP group to separate the AP
The issue we are having is iOS based devices (iPhone/iPad/android) doesn't take the correct vlan that assigned for each one of them ,instead
sometimes take an ip from the management vlan some time form the same vlan on other floor
Does anyone have any ideas or have run into this problem before?
Any help would greatly be appreciated.
Thanks!sometimes take an ip from the management vlan some time form the same vlan on other floor
You cannot guaranteed, that given floor client always connect to the same floor AP. Also if client moving from one floor to another, then client will retain the IP obtained from the other floor, even he moved to different floor. I would not do floor wise vlan assignment (at least building wise if that require).
If you take "debug client <mac_address>" output that will tells you what's going on. Below post gives you some reference how it should be under normal working condition.
http://mrncciew.com/2014/10/17/wlc-client-debug-part-2/
HTH
Rasika
**** Pls rate all useful responses **** -
hey
my wireless network has 20 LAPS,recently my controller lost 11 LAPS,i did a reboot on the controller and the remaining 9 LAPS were also lost.
i have tried several suggestions but nothing has workd
i upgraded the controller from 3.2.119. image to 4.0.219.0.i also changed to LAPS from LAPS to APS and back but nothing seem to work.
does anyone have an idea as to what the problem might be.Hello,
your topology is not trivial. I would say :
1) be sure about propper IP layer configuration - ping from the controller to LAPs
2) what about the controller discovery on LAPs ? If the LAPs know the right conntroller you must see a registration attempts. Try to switch on "debug lwapp events", "debug lwapp packets" and "debug lwapp errors". Best to try on only one LAP.
3) on older converted APs there can be a problem with a certificate. It can be watched on the WLC by "debug pm pki"
I have had LAP registration problems many times but it was always some stupid mistake. -
Unable to integrate WLC with cisco ACS
Hi,
I am not able to integrate Cisco Tacas with WLC
Below are the error logs in Juniper firewall
WLC IP: 10.210.126.133
Cisco ACS: 10.116.45.131
Date/Time
Source Address/Port
Destination Address/Port
Translated Source Address/Port
Translated Destination Address/Port
Service
Duration
Bytes Sent
Bytes Received
Close Reason
2013-11-04 16:31:03
10.210.126.133:49098
10.116.45.131:49
10.210.126.133:49098
10.116.45.131:49
TCP PORT 49
2 sec.
591
428
Close - TCP FIN
2013-11-04 16:31:03
10.210.126.133:51759
10.116.45.131:49
10.210.126.133:51759
10.116.45.131:49
TCP PORT 49
2 sec.
525
326
Close - TCP FIN
2013-11-04 16:31:09
10.210.126.133:51759
10.116.45.131:49
10.210.126.133:51759
10.116.45.131:49
TCP PORT 49
9 sec.
475
238
Close - TCP FIN
2013-11-04 16:31:09
10.210.126.133:49098
10.116.45.131:49
10.210.126.133:49098
10.116.45.131:49
TCP PORT 49
9 sec.
519
318
Close - TCP FIN
Pls suggest further whether any changes needs to be done in any end
Cisco ACS Srver
11/04/2013
16:31:01
Author failed
ads.shalder
DCN-BANG2&BANG5-RW
127.0.0.1
Service denied
service=ciscowlc protocol=common
10.210.126.133
ads.shalder
No
1
10.210.126.133
Pls suggest further
Br/SubhojitHi,
we are getting this error on WLC side debug
(Cisco Controller) >*tplusTransportThread: Nov 05 09:51:32.683: Forwarding request to 10.116.45.131 port=49
*tplusTransportThread: Nov 05 09:51:32.689: tplus auth response: type=1 seq_no=2 session_id=5b675ca1 length=16 encrypted=0
*tplusTransportThread: Nov 05 09:51:32.689: TPLUS_AUTHEN_STATUS_GETPASS
*tplusTransportThread: Nov 05 09:51:32.689: auth_cont get_pass reply: pkt_length=25
*tplusTransportThread: Nov 05 09:51:32.689: processTplusAuthResponse: Continue auth transaction
*tplusTransportThread: Nov 05 09:51:32.700: tplus auth response: type=1 seq_no=4 session_id=5b675ca1 length=6 encrypted=0
*tplusTransportThread: Nov 05 09:51:32.700: tplus_make_author_request() from tplus_authen_passed returns rc=0
*tplusTransportThread: Nov 05 09:51:32.700: Forwarding request to 10.116.45.131 port=49
*tplusTransportThread: Nov 05 09:51:32.705: author response body: status=16 arg_cnt=0 msg_len=0 data_len=0
*tplusTransportThread: Nov 05 09:51:32.705: Tplus authorization for ads.shalder failed status=16
WLC hardware is: AIR-CT2504-K9V01
Br/Subhojit -
Hi all,
I have an SSID where clients cannot get DHCP addresses. I have captured the following debug and from what I can see the WLC recieves the DHCP address from the DHCP server and then attempts to forward that to the Station but the station does not get it.
Is my thinking correct? If so, what can cause the client not to recieve the DHCP offer packet from the WLC?
Thanks
Mario
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP xid: 0xc7944f1b (3348385563), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 350, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:33.034: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 295,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP setting server from OFFER (server 192.168.254.254, yiaddr 192.168.254.184)
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP transmitting DHCP OFFER (2)
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP xid: 0xc7944f1b (3348385563), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 192.168.254.184
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:35.042: ac:7b:a1:10:21:74 DHCP server id: 192.0.2.1 rcvd server id: 192.168.254.254
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 329,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP transmitting DHCP REQUEST (3)
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP xid: 0xc7944f1b (3348385563), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP requested ip: 192.168.254.184
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP server id: 192.168.254.254 rcvd server id: 192.0.2.1
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 374, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:35.045: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 278,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP transmitting DHCP NAK (6)
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP xid: 0xc7944f1b (3348385563), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:35.050: ac:7b:a1:10:21:74 DHCP server id: 192.0.2.1 rcvd server id: 192.168.254.254
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 0.0.0.0 VLAN: 0
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP xid: 0xa0788169 (2692252009), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 350, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:35.056: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
fastpath Configures the fastpath debug options.
flexconnect Configures debug of flexconnect.
fmchs Configures the FMCHS debug options.
ft Configures the 802.11r debug options.
group Configures debug of wlan apgroup.
iapp Configures the IAPP debug options.
ipv6 Configures the IPV6 debug options
l2age Configures debug of Layer 2 Ago Timeout Messages.
l2roam Configures the L2 Roam debug options.
license Configures Debugging of Licensing
location Configures the Location debug options.
lwapp This command has been deprecated. Please use debug capwap instead
mac Configures MAC debugging
media-stream Configures the media-stream debug options
memory Configures debug of memory allocation/release.
mesh Configures the Mesh debug options.
mobile-concierge Configures the Mobile Concierge debug options.
mobility Configures the Mobility debug options.
nac Configures debug of Network Access Control (NAC).
nmsp Configures the NMSP debug options.
ntp Configures debug of NTP.
packet Configures packet debugging options.
pem Configures the access policy manager debug options.
--More-- or (q)uit
pm Configures debug of security policy manager module
profiling Configures the Profiling debug options
rbcp Configures the RBCP debug options
rf-profile Configures debug of rf-profile
rfid Configures the Rfid debug options.
service Configures the debug options for different Services.
snmp Configures the SNMP debug options.
spectrum Configures the spectrum debug options.
transfer Configures the transfer debug options.
voice-diag Enable Diagnostics for Voice Clients.
wcp Configures debug of WLAN Control Protocol (WCP).
web-auth Configures debugs for web-auth client.
wips Configures the WIPS debug options.
wps Configures debug of WPS.
(Cisco Controller) >debug A*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP xid: 0xa0788169 (2692252009), secs: 768, flags: 0
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 350, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
Incorrect usage. Use the '?' or <TAB> key to list commands.
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >
(Cisco Controller) >*DHCP Socket Task: Dec 15 15:57:40.021: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 295,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:40.021: ac:7b:a1:10:21:74 DHCP setting server from OFFER (server 192.168.254.254, yiaddr 192.168.254.186)
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP transmitting DHCP OFFER (2)
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP xid: 0xa0788169 (2692252009), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 192.168.254.186
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP server id: 192.0.2.1 rcvd server id: 192.168.254.254
*DHCP Socket Task: Dec 15 15:57:40.023: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 329,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP transmitting DHCP REQUEST (3)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP xid: 0xa0788169 (2692252009), secs: 768, flags: 0
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP requested ip: 192.168.254.186
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP server id: 192.168.254.254 rcvd server id: 192.0.2.1
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 374, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 278,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP transmitting DHCP NAK (6)
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP xid: 0xa0788169 (2692252009), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP server id: 192.0.2.1 rcvd server id: 192.168.254.254
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 0.0.0.0 VLAN: 0
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP xid: 0x99a9937f (2578027391), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:40.044: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:40.045: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 350, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:40.045: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
debug*DHCP Socket Task: Dec 15 15:57:40.045: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 295,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP setting server from OFFER (server 192.168.254.254, yiaddr 192.168.254.191)
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP transmitting DHCP OFFER (2)
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP xid: 0x99a9937f (2578027391), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 192.168.254.191
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:42.058: ac:7b:a1:10:21:74 DHCP server id: 192.0.2.1 rcvd server id: 192.168.254.254
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 329,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP transmitting DHCP REQUEST (3)
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP xid: 0x99a9937f (2578027391), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP requested ip: 192.168.254.191
*DHCP Socket Task: Dec 15 15:57:42.061: ac:7b:a1:10:21:74 DHCP server id: 192.168.254.254 rcvd server id: 192.0.2.1
*DHCP Socket Task: Dec 15 15:57:42.062: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 374, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:42.062: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:42.062: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONE
*DHCP Socket Task: Dec 15 15:57:42.069: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 278,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP transmitting DHCP NAK (6)
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP xid: 0x99a9937f (2578027391), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:42.070: ac:7b:a1:10:21:74 DHCP server id: 192.0.2.1 rcvd server id: 192.168.254.254
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 308,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 0.0.0.0 VLAN: 0
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP xid: 0x35c06675 (901801589), secs: 0, flags: 0
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP chaddr: ac:7b:a1:10:21:74
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP ciaddr: 0.0.0.0, yiaddr: 0.0.0.0
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP siaddr: 0.0.0.0, giaddr: 192.168.254.253
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP sending REQUEST to 192.168.254.254 (len 350, port 1, vlan 51)
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP selecting relay 2 - control block settings:
dhcpServer: 0.0.0.0, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:42.076: ac:7b:a1:10:21:74 DHCP selected relay 2 - NONEThe client shows it is receiving the offer and sending a request back to the DHCP server. The server is sending a NAK back to the client's request.
DISCOVER
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP transmitting DHCP DISCOVER (1)
*DHCP Socket Task: Dec 15 15:57:37.486: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
OFFER
*DHCP Socket Task: Dec 15 15:57:40.021: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 295,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:40.021: ac:7b:a1:10:21:74 DHCP setting server from OFFER (server 192.168.254.254, yiaddr 192.168.254.186)
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:40.022: ac:7b:a1:10:21:74 DHCP transmitting DHCP OFFER (2)
REQUEST
*DHCP Socket Task: Dec 15 15:57:40.023: ac:7b:a1:10:21:74 DHCP received op BOOTREQUEST (1) (len 329,vlan 0, port 1, encap 0xec03)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP selecting relay 1 - control block settings:
dhcpServer: 192.168.254.254, dhcpNetmask: 0.0.0.0,
dhcpGateway: 0.0.0.0, dhcpRelay: 192.168.254.253 VLAN: 51
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP selected relay 1 - 192.168.254.254 (local address 192.168.254.253, gateway 192.168.254.254, VLAN 51, port 1)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP transmitting DHCP REQUEST (3)
*DHCP Socket Task: Dec 15 15:57:40.024: ac:7b:a1:10:21:74 DHCP op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
NAK!
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP received op BOOTREPLY (2) (len 278,vlan 51, port 1, encap 0xec00)
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP sending REPLY to STA (len 414, port 1, vlan 0)
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP transmitting DHCP NAK (6)
*DHCP Socket Task: Dec 15 15:57:40.040: ac:7b:a1:10:21:74 DHCP op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
The WLC is sending the traffic properly. The DHCP server is sending back a NAK to the Client REQUEST. It's a bit odd because the client is making a Request to the same DHCP server, with the same transaction ID, with the same "offered" IP address. Once the DHCP Server sends back an "ACK" instead of a "NAK", then you will be good.
What is the device offering DHCP? You might consider getting rid of DHCP-Proxy and simply bridging the traffic over. Can you take a "wired" client and place them on VLAN 51 of that same switch and get an IP address? -
I've run into an issue where saving a new CrystalEnterprise.Program instance is throwing an ambiguous exception with no other information than a generic HRESULT code and the even less useful error message "File Repository Server error". I've debugged the code using the COMException managed debugging assistant and Reflector to get to the callsite of the COM object, but there is nothing there to indicate what the actual File Repository error is attributed to. Logging for the InputFileRepository service in the CMS was been set to HIGH, but nothing shows there as a result of my code executing.
The call to myInfoStore.Commit(...) is where the COMException is thrown.
protected void CreateProgramObject(InfoStore infoStore)
using(PluginManager pluginManager = infoStore.PluginManager)
using(InfoObjects newCollection = infoStore.NewInfoObjectCollection())
using(PluginInfo programPlugin = pluginManager.GetPluginInfo("CrystalEnterprise.Program"))
using(Program tempProg = (Program)newCollection.Add(programPlugin))
const string USER_FOLDER_QUERY =
"Select SI_ID From CI_INFOOBJECTS Where SI_NAME = '[email protected]'";
using(InfoObjects folders = infoStore.Query(USER_FOLDER_QUERY))
if(folders.Count < 1)
Response.Write("No user folder was found!");
return;
using(InfoObject userReportFolder = folders[1])
tempProg.Title = "Scheduled File";
tempProg.Description = "My new program";
tempProg.ParentID = userReportFolder.ID;
tempProg.ProgramType = CeProgramType.ceScript;
tempProg.Files.Add(@"E:\sample.bat");
try
infoStore.Commit(newCollection);
catch(SystemException snx)
Trace.Write(snx.ToString());
Has anyone run into this issue and found a resolution?Thank you for the reply. I changed the file path on the BOE Server to match the path I'm using in the Files.Add(...) call. At least now I get a different error message, but it's still not enough to resolve the issue. The message is "File Repository Server error : File system operation for D:\Scripts\test.bat on File Repository Server failed. If the problem persists, please contact your system administrator for event log information." I verified the service account the SIA service runs under can access that path, but still no luck.
Using a UNC path resulted in the original "File Repository Server error" message in the Exception.
Maybe you are looking for
-
"Home Shared" Apps are asking for original iTunes Account?
my Dad just got his iPad (64GB WiFi) and asked me to set it up for him (register, transfer content, etc) i've had mine (32GB 3G) for a while, so i have a bunch of apps (free and paid). i've never used _Home Sharing_ before but i figured that would be
-
In MAC, I want to change document size from 8.5X11 to 18X24 to create a poster to print through Staples. I created the doc originally in WORD, changed the size in WORD, converted to PDF doc. But PDF doc is still in 8.5X11. Read ADOBE support help inf
-
Output display problem in alignment
i am displaying vendor wise purchase register details in my output i have many line items per each vendor. i want to display vendor wise line items. suppose AFTON CHEMICALS is coming 10 times in the output i want to display this with all line items
-
Copy of BW causing issues while connecting to R/3
Hi; I have done a copy of our Dev BW system (640) and trying to restore the existing source system connections to R/3 (640). I am getting the errors while restoring it; it says source system already connected to A1 (original) logical system and askin
-
Hi, We are in migration from CCM 2.0 SRM MDM. In CCM , we are uploading the catalogs with UNSPSC and material group. Either any one is mandatory. If they give UNSPSC code in catalog, while uploading we are mapping to correspoding material group. But