WLC 4400 issue
Hello
I have a question: can WLC 4400 management bridges?
Can you show me a document where to mention this point?
Thank you very much
WLC can handle that KNEES which is to be set up in Local mode or mode H-REAP. Now if you do MESH bypass and Yes, any other type of basic bridging IOS then no.
Tags: Cisco Wireless
Similar Questions
-
Problems with towers 1252 and WLC 4400
I have problem with performance customers 1252 tours and WLC 4400. When clients are connected, they have slow transfer, about 800 ms in the ping command. Can someone help me?
What about the APs event logs?
-
In the Wireless LAN Controller 4400 series, that configuration didn't was not automatically que la configuration n' etait pas automatiquement synchronisees synchronized between the same group of the mobility of controllers, the configuration has been done by hand in each WLC, in the 5500 WLC is the same or configuration is automatically synchronized between them?
Hi Ricardo,
Hope all is well my friend
With the 5500 series of WLC are the config is NOT
automatically synchronized between them. Identical to the 4400's.
See you soon!
Rob
Thank you to support CSC helps Haiti
https://supportforums.Cisco.com/docs/doc-8895
https://supportforums.Cisco.com/docs/doc-8727
EDIT: Dan... .you have forged my typing skills miserable as usual. + 5 my friend!
-
RADIUS & WLC 4400 account management
Hello
We have a 4400 WLC, validate users against FreeRadius. Don t of RADIUS accounting messages appear the names of TOUR but the MAC address of the APs. Is it possible to change this behavior?
Thank you.
Hello Daniel
In Radius Accounting Request packet, NAS-identify attribute must be able to provide the name of the Radius clients. If the NAS-identify attributes to come in packages of accounting, then it will be visible.
Thank you
Nelson
-
WLC 4400 not authetnicating between the COMMENTS and private networks
Hello
I have a problem. I have a 4400 WLC and the meeting I m problem is that when an authetnicates of user to the private network, then tryies to autheticate the guest network, it just stays there, it does nothing. All around, if authenticate you with the network of comments and change the private network, it just sits there. I have showing that the problem is with the authentication, but do not know if I m correct.
Can someone help me? What ifnormation will take to recover from the WLC see there the rub?
I'll get the debug mac addr
and repeat the question to see if I get anything for the customer. Thanks for the help
Tony
I would check if his blocking on obtaining IP address or authentication. Probably try to manually set the IP address if you switch between networks and see if works.
-
1602i-e-k9 AP and WLC 5508 issue of Cisco
Dear forum participants,
I experience a problem connection Access Point 1602i-e-k9 to WLC 5508
I upack and taken an AP on the network, it appears on the WLC (monitor > all APs), I can see it using the link details for several time.
Then he desappears, restart does not help.
I searched the forum for solutions, made AP reset via command "cli rommon-like" + button "MODE" and "reset" . After that, the same thing happens again: he appears on WLC and disappears.
What I am doing wrong?
Brief info on devices and newspapers partial
Please see the full changelog of the AP attached (contains info after the reset command has been entered).
The AP Info
looking at the picture...
extracting information (283 bytes)
Image info:
Version suffix: k9w8-. 152 - 2.JB
Image name: ap1g2-k9w8 - mx.152 - 2.JB
The release directory: ap1g2-k9w8 - mx.152 - 2.JB
The iOS Image size: 9400832
Total image size: 9769472
Image device: Wireless LAN | LWAPP
Family pictures: AP1G2
Wireless switch management Version: 7.4.100.0
WLC Info
Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.4.100.0
Bootloader Version... 1.0.1
Retrieving Image Version field... 6.0.182.0
Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27
Build Type....................................... DATA + WPS, LDPE
Journal of the AP
reset
[BEGIN] 20.03.2013 14:09:31
Are you sure you want to reset the system (y/n)? There
System reset...
Boot from flash
* 00:00:15.627 Mar 1: % LWAPP-3-CLIENTERRORLOG: Config flash load failed. Initialization of Cfg
* 00:00:15.631 Mar 1: % CAPWAP-3-Journal of ERROR: could not load the configuration of flash. Reset to the default configuration
* 00:00:16.671 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed to uplwapp_crypto_init: MIC present and analyzed successfully
No source of bridge-Group 1-learning
^
Invalid entry % detected at ' ^' marker.
% Without Gateway default route, if not an interface point, may affect performance
* 00:00:46.131 Mar 1: % CDP_PD-4-POWER_OK: all disabled radio - power INJECTOR_CONFIGURED_ON_SOURCE online source
* 00:00:49.411 Mar 1: DHCP-6-ADDRESS_ASSIGN %: BVI1 Interface assigned address DHCP 172.17.254.6, mask 255.255.255.0, hostname AP0006.f618.1d3b
Translate "CISCO-CAPWAP-CONTROLLER"... the domain server (172.17.254.1)
* 00:01:00.347 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.17.254.203 drive address obtained by DHCP
* 00:01:00.347 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:01:09.347 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
* 00:01:19.347 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller
looking at the picture...
extracting information (283 bytes)
Image info:
Version suffix: k9w8-. 152 - 2.JB
Image name: ap1g2-k9w8 - mx.152 - 2.JB
The release directory: ap1g2-k9w8 - mx.152 - 2.JB
The iOS Image size: 9400832
Total image size: 9769472
Image device: Wireless LAN | LWAPP
Family pictures: AP1G2
Wireless switch management Version: 7.4.100.0
Extraction of the files...
AP1G2-k9w8-MX.152-2.JB/ (directory) 0 (bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/K5.bin (75790 bytes)
* 14:10:57.000 20 Mar: % CA
extraction ap1g2-k9w8-mx.152-2.JB/S2.bin (9328 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/S5.bin (106106 byte) PWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:10:57.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:10:57.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:10:57.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:10:57.543 Mar 20: % CAPWAP-3-Journal of ERROR: could not process the encrypted package capwap 172.17.254.203perform archive download capwap: / ap1g2 tar file
* 14:10:57.547 Mar 20: % CAPWAP-6-AP_IMG_DWNLD: not found required image on AP. image controller download.
extraction ap1g2-k9w8-mx.152-2.JB/info (283 bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/ (directory) 0 (bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/ (directory) 0 (bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/1/ (directory) 0 (bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/forms.js (17492 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/appsui.js (563 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/ap_home.shtml.gz (1297 bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/1/images/ (directory) 0 (bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/info.gif (399 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/cisco-logo-2007.gif (1648 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/background_web41.jpg (732 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/images/login_homeap.gif (19671 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/config.js (25507 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/sitewide.js (16554 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/html/level/1/officeExtendap.css (41801 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/1/back.shtml (512 bytes)
AP1G2-k9w8-MX.152-2.JB/HTML/level/15/ (directory) 0 (bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapBanner.htm (7114 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapConfig.shtml.gz (2864 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapSummary.htm (718 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapHelp.htm (5013 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapMain.shtml.gz (3350 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/html/level/15/officeExtendapEvent.shtml.gz (988 bytes)
extraction ap1g2-k9w8-mx.152-2.JB/K2.bin (5830 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/8005.img (200872 bytes)
extraction of ap1g2-k9w8-mx.152-2.JB/ap1g2-k9w8-mx.152-2.JB (9196955 bytes)
* 14:12:57.694 Mar 20: % 3-CAPWAP-ERRORLOG: white event 48 & combination State 10.
* 14:12:57.694 Mar 20: % 3-CAPWAP-ERRORLOG: SM Manager: failed to process the message of the timer. Event 48, State 10
* 14:12:57.694 Mar 20: % CAPWAP-3-Journal of ERRORS: do not handle the message from the timer.
* 14:12:57.694 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the message of the timer.
extraction info.ver (283 bytes)
Removal of target version: flash:/ap1g2-k9w8-mx.152-2.JB...done.
New image of the software installed in flash:/ap1g2-k9w8-mx.152-2.JB
System to use new IMA configuration
Flash event log entry: / event.log...
GE... done.
Download of archive: 212 seconds
* 14:14:28.389 Mar 20: upgrade successfully, the system image is now reloading
* 14:14:28.425 Mar 20: % SYS-5-RELOAD: reload requested by capwap image download proc. reload reason: NEW IMAGE DOWNLOAD.
* 14:14:28.425 Mar 20: % LWAPP-5-CHANGED: CAPWAP changed State to DOWN
Event.log written
Boot from flash
* 00:00:53.107 Mar 1: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 00:00:54.031 Mar 1: DHCP-6-ADDRESS_ASSIGN %: BVI1 Interface assigned address DHCP 172.17.254.7, mask 255.255.255.0, hostname AP0006.f618.1d3b
* 00:00:54.107 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 00:00:54.163 Mar 1: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 00:00:55.163 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
Translate "CISCO-CAPWAP-CONTROLLER"... the domain server (172.17.254.1)
* 00:01:04.927 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.17.254.203 drive address obtained by DHCP
* 00:01:04.927 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:01:13.927 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-CAPWAP-CONTROLLER
* 00:01:23.927 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:16:30.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:30.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:30.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:16:30.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:16:30.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:16:49.211 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:16:49.211 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:16:49.211 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:16:49.267 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:16:49.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:16:49.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:16:49.303 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:16:49.343 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:16:50.287 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:16:50.335 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:16:50.343 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:16:51.327 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:16:51.335 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:16:51.379 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:16:51.387 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:16:51.395 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:16:52.379 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:16:52.387 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:16:52.423 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:16:53.423 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:16:59.343 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:16:59.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:59.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:16:59.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:16:59.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:16:59.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:17:17.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:17:17.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:17:17.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:17:17.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:17:17.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:17:17.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:17:17.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:17.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:18.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:18.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:17:18.827 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:17:19.811 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:19.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:17:19.863 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:19.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:17:19.879 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:17:20.863 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:17:20.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:20.907 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:21.907 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:27.819 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:17:28.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:28.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:28.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:17:28.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:17:28.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:17:47.203 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:17:47.203 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:17:47.203 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:17:47.259 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:17:47.275 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:17:47.275 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:17:47.287 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:47.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:48.275 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:48.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:17:48.331 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:17:49.315 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:49.323 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:17:49.367 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:17:49.375 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:17:49.383 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:17:50.367 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:17:50.375 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:17:50.411 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:17:51.411 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:17:57.323 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:17:57.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:57.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:17:57.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:17:57.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:17:57.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:18:15.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:18:15.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:18:15.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:18:15.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:18:15.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:18:15.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:18:15.799 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:15.831 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:16.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:16.835 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:18:16.843 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:18:17.827 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:17.835 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:18:17.879 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:17.887 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:18:17.895 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:18:18.879 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:18:18.887 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:18.923 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:19.923 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:25.831 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:18:26.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:26.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:26.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:18:26.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:18:26.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:18:44.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:18:44.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:18:44.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:18:45.163 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:18:45.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:18:45.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:18:45.195 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:45.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:46.183 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:46.231 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:18:46.239 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:18:47.223 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:47.231 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:18:47.275 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:18:47.283 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:18:47.291 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:18:48.275 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:18:48.283 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:18:48.319 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:18:49.319 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:18:55.227 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:18:55.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:55.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:18:55.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:18:55.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:18:55.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:19:13.695 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:19:13.695 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:19:13.695 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:19:13.751 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:19:13.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:19:13.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:19:13.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:13.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:14.767 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:14.827 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:19:14.835 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:19:15.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:15.827 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:19:15.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:15.879 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:19:15.887 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:19:16.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:19:16.879 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:16.915 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:17.915 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:23.815 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:19:24.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:24.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:24.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:19:24.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:19:24.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:19:42.695 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:19:42.695 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:19:42.695 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:19:42.751 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:19:42.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:19:42.767 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:19:42.783 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:42.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:43.767 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:43.815 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:19:43.823 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:19:44.807 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:44.815 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:19:44.859 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:19:44.867 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:19:44.875 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:19:45.859 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:19:45.867 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:19:45.903 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:19:46.903 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:19:52.815 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:19:53.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:53.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:19:53.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:19:53.547 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:19:53.547 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:20:12.111 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:20:12.111 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:20:12.111 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:20:12.167 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:20:12.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:20:12.183 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:20:12.199 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:12.231 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:13.183 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:13.235 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:20:13.243 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:20:14.227 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:14.235 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:20:14.279 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:14.287 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:20:14.295 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:20:15.279 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:20:15.287 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:15.323 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:16.323 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:22.231 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:20:22.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:22.543 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:22.543 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:20:22.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:20:22.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:20:40.699 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:20:40.699 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:20:40.699 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:20:40.755 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:20:40.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:20:40.771 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:20:40.787 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:40.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:41.771 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:41.819 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:20:41.827 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:20:42.811 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:42.819 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:20:42.863 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:20:42.871 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:20:42.879 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:20:43.863 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:20:43.871 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:20:43.907 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:20:44.907 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:20:50.819 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:20:51.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:51.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:20:51.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:20:51.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:20:51.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
* 14:21:10.107 Mar 20: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (UNKNOWN_MESSAGE_TYPE (5))
., 1)
* 14:21:10.107 20 Mar: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 14:21:10.107 Mar 20: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.17.254.203:5246
* 14:21:10.163 Mar 20: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255
* 14:21:10.179 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively
* 14:21:10.179 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed state down administratively
* 14:21:10.191 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:21:10.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:21:11.179 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:21:11.227 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to down
* 14:21:11.235 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 14:21:12.219 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:21:12.227 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 14:21:12.271 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio1, changed State to
* 14:21:12.279 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to down
* 14:21:12.287 Mar 20: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 14:21:13.271 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 14:21:13.279 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 14:21:13.315 Mar 20: % LINK-6-UPDOWN: Interface Dot11Radio0, changed State to
* 14:21:14.315 Mar 20: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
* 14:21:20.227 Mar 20: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 14:21:20.000 Mar 20: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.17.254.203 peer_port: 5246
* 14:21:20.539 Mar 20: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.17.254.203 peer_port: 5246
* 14:21:20.539 Mar 20: % CAPWAP-5-SENDJOIN: send request to join 172.17.254.203
* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: white event 10 & combination State 5.
* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: CAPWAP SM Manager: unable to process the message status type 10 5.
* 14:21:20.543 Mar 20: % 3-CAPWAP-ERRORLOG: could not manage capwap control message from the controller
* 14:21:20.543 Mar 20: % CAPWAP-3-Journal of ERROR: failed to process the encrypted package 172.17.254.203 capwap
[END] 20.03.2013 14:21:55
Azim,
I wonder if the regulatory domain of the AP is correct.
Please provide the result following (authorization according to Leo)
1 WLC: sh sysinfo
2 PA: sh version
3 PA: HS inventory
Thank you.
Amjad
Rating of useful answers is more useful to say "thank you".
-
I administer a network comprising 11 APs, ASA 5510, 4402 WLC and 1760 router wireless.
The network share an internet connection to all guests free of charge so I did not need authorization.
I want to implement a cover page which would have shown to all clients when they connect first. The start page is suppoused have only the basic information on the service provided and no logon.
Is it possible to do without buying an ACS?
Thank you for your help.
Hello!
Yes, if you do not need authentication (which would require to define users locally on the WLC or by using a RADIUS external.. like ACS server), you can directly activate Web Auth Passthrough on the WLC.
Check out this example config:
http://www.Cisco.com/en/us/products/ps6366/products_configuration_example09186a00809bdb5f.shtml
In any case, this thread should better go to the wireless community if ACS does not participate.
I hope this helps!
Kind regards
Federico
--
If this answers your question please mark the question as "answered" and write it down, so other users can easily find it. -
Routing capabilites of 4400 WLC
Do WLC 4400 has routing capabilities... ??
as I m using WLC 4402 for AP association and management of clients and router that provides the interface of L3 for AP and Client for routing there subnets. It is possible by only using WLC for AP and Client Mgmt and removing the defect of a road?
Concerning
Hitesh salvation,
The WLC 4400 is a device that attaches to your network, but does not work as a router. There must be a layer 3 device routes packets between the VLANS. The WLC maps the SSID of the VIRTUAL LAN subnet clients and put their return on the interface of management for upstream routers to route the packets.
http://www.Cisco.com/en/us/products/ps6366/products_qanda_item09186a008064a991.shtml
I hope this helps!
Rob
-
I find contradictory documentation; the 3500th is supported on the WLC 4400 w / version 7.x code?
Docs, I found say 3500 is CAPWAP only so that only the 5508 CAPWAP.
Thank you.
Anything over version 5.2 software WLC > CAPWAP
Anything below version 5.2 software WLC > LWAPP
Now go back to 3500th... version minimum necessary to get the 3500 AP with WLC is 7.0 and 7.0 is compatible with the 4400... That is why 3500 is supported on 4400 running the WLC version 7.0 and later...
This has answered your qiestion?
Concerning
Surendra -
Need help with the installation of 4400 WLC
I have a client that is running 2 separate networks. One is configured with 10 LWAPs connected to a 4400 WLC by using MAC authentication. The other is 2 autonomous 1200 Series APs configured with RADIUS of a Server IAS Ms.
The customer wants to combine the WLANs separated in 1; Indeed, integrating all the APs the WLC, RADIUS configuration for all and maintain the 2 separate SSID.
Is this possible with the 4400 series? If so, could you please direct me to the guides for this configuration.
1 convert 1200 Series APs in LWAPs
2 configure the RADIUS about WLC 4400
3. set up 2 separate SSID on 1 WLC times by using the same authentication method
4 change the if necessary air on MS Windows 2003 IAS RADIUS
1 convert 1200 Series APs in LWAPs
http://www.Cisco.com/en/us/docs/wireless/access_point/conversion/LWAPP/upgrade/guide/lwapnote.html
2 configure the RADIUS about WLC 4400
http://www.Cisco.com/en/us/products/ps6366/products_configuration_example09186a00808e5d6b.shtml
3. set up 2 separate SSID on 1 WLC times by using the same authentication method
> This should be fairly simple...
4 change the if necessary air on MS Windows 2003 IAS RADIUS
There are several examples of IAS here configuration:
http://www.Cisco.com/en/us/products/ps6366/prod_configuration_examples_list.html
-
AIR-LAP1242AG-A-K9 cannot adhere to WLC
Guys,
I have problem, I try to connect AIR-LAP1242AG-A-K9 AP WLC 4400 with the 7.0.98.218 software, but the HA indicator is blink and always request new IP address (based on console logg AP), this device can ping from LAN but unstable (based on logg, the always AP request new IP address).
Anyone have experience with this case?
It's newspaper when I try the console to AP.
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
XMODEM file system is available.
flashfs [0]: 15 files, 4 folders
flashfs [0]: 0 orphaned files, orphaned directories 0
flashfs [0]: Total number of bytes: 15998976
flashfs [0]: bytes used: 10084864
flashfs [0]: available bytes: 5914112
flashfs [0]: flashfs fsck took 36 seconds.
Basic Ethernet MAC address: 00: 1 d: 45:36:86:ca
Initialization of the ethernet port 0...
Reset the ethernet port 0...
Reset done!
upward, 100 Mbps, full-duplex Ethernet link
Ethernet port initialized 0: connection is established
Loading "flash:/c1240-k9w8-mx.124-23c.JZ/c1240-k9w8-mx.124-23c.JZ"...########################################################################################################################################################################################################################################################################################################################################################################################################################################################
'Flash:/c1240-k9w8-mx.124-23c.JZ/c1240-k9w8-mx.124-23c.JZ' file, unzipped and installed, point of entry: 0 x 3000
execution of...
Legend restricted rights
Use, duplication, or disclosure by the Government is
subject to such restrictions as set out in paragraph
(c) Commercial - limited computer software
The rights to FAR clause 52.227 - 19 and subparagraph s
(c) (1) (ii) rights to technical and computer data
Clause of DFARS 252.227 - 7013 section software.
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco IOS software, software of C1240 (C1240-K9W8-M), Version 12.4 (23 c) JZ, RELEASE SOFTWARE (fc1)
Technical support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Updated Thursday, April 6, 11 15:01 by prod_rel_team
Proceed with the initialization of the system
Proceeding to unmask interrupts
Initialization of flashfs...
flashfs [1]: 15 files, 4 folders
flashfs [1]: 0 orphaned files, orphaned directories 0
flashfs [1]: Total number of bytes: 15740928
flashfs [1]: bytes used: 10084864
flashfs [1]: available bytes: 5656064
flashfs [1]: flashfs fsck took 5 seconds.
flashfs [1]: the complete initialization... done Initializing flashfs.
Radio0 present A506 7100 E8000000 A0000000 80000000 3
Radio1 present A506 6700 E8000100 A0040000 80010000 2
This product contains cryptographic features and is under the United States
States and local laws governing the import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third party approval to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. laws and local countries. By using this product you
agree to comply with the regulations and laws in force. If you are unable
to satisfy the United States and local laws, return the product.
A summary of U.S. laws governing Cisco cryptographic products to:
http://www.Cisco.com/WWL/export/crypto/tool/stqrg.html
If you need assistance please contact us by mail at
Cisco AIR-LAP1242AG-A-K9 (PowerPCElvis) Prozesseur (revision A0) 25590K / 7168K bytes of memory.
Card processor ID FTX1135B3ZF
PowerPCElvis CPU at 262 Mhz, revision number 0 x 0950
Last reset of tension
Image LWAPP 7.0.98.218 version
1 interface FastEthernet
2 802.11 radios
32K bytes memory simulated by flash not volatile configuration.
Basic Ethernet MAC address: xxxxxxxxxx
Part number: 73-9925-06
Kit numbered PCA: 800-26579-05
Revision number of PCA: xxxxx
Serial number of PCB: xxxxxxx
Top of page Assembly part number: xxxxxxx
Top of page the Assembly serial number: xxxxxxx
Top of page revision number: A0
Product/model number: AIR-LAP1242AG-A-K9
% Please first set a domain name.
Press RETURN to get started!
* 00:00:06.526 Mar 1: % SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: crypto IOS FIPS self-test passed
* 00:00:08.150 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on Dot11Radio interface 0
* 00:00:09.747 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on 1 Dot11Radio interface
* 00:00:09.863 Mar 1: % LWAPP-3-CLIENTEVENTLOG: reading and initialized AP event log (contains 1024 messages)
* 00:00:09.895 Mar 1: State of the voice_diag_test of WLC is false
* 00:00:12.004 Mar 1: % LINK-3-UPDOWN: Interface FastEthernet0, changed State to
* 00:00:12.072 Mar 1: % SYS-5-RESTART: System restarted.
Cisco IOS software, software of C1240 (C1240-K9W8-M), Version 12.4 (23 c) JZ, RELEASE SOFTWARE (fc1)
Technical support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Updated Thursday, April 6, 11 15:01 by prod_rel_team
* 00:00:12.072 Mar 1: % SNMP-5-start COLD: SNMP agent on host AP001d.4536.86ca knows a cold start
* 00:00:12.154 Mar 1: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY
* 00:00:12.161 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio1, changed State to reset
* 00:00:12.161 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset
* 00:00:12.369 Mar 1: % SSH-5-ACTIVATED: SSH 2.0 has been activated
* 00:00:13.016 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed State to
* 00:00:13.170 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio1, change of State down
* 00:00:13.170 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs
* 00:00:20.493 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx
* 00:00:30.976 Mar 1: State of the voice_diag_test of WLC is false
* 00:00:31.083 Mar 1: message logging LWAPP to 255.255.255.255.
* 00:00:34.263 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online
* 00:00:34.304 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio1, changed State to
* 00:00:34.342 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to
* 00:00:35.265 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed State to
* 00:00:35.265 Mar 1: % SYS-6-LOGGINGHOST_STARTSTOP: logging to host started 255.255.255.255 - initiated CLI
* 00:00:35.304 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to
Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
* 00:00:42.131 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:00:42.135 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net
* 00:00:42.139 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net
* 00:01:32.143 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.
* 00:01:34.274 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online
Not in a bound State.
* 00:01:40.659 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.
* 00:01:40.778 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx
Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
* 00:01:48.652 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:01:48.655 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net
* 00:01:48.657 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net
* 00:02:28.661 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.
Not in a bound State.
* 00:02:37.173 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.
* 00:02:37.290 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxx.xxxx
Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
* 00:02:45.164 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:02:45.167 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net
* 00:02:45.169 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net
* 00:03:25.170 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.
Not in a bound State.
* 00:03:33.681 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.
* 00:03:33.798 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx
Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
* 00:03:41.673 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:03:41.676 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net
* 00:03:41.678 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net
* 00:04:21.679 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.
Not in a bound State.
* 00:04:30.191 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.
* 00:04:30.308 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx
Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
* 00:04:38.181 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:04:38.184 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net
* 00:04:38.187 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP - CONTROLLER.tester .net
* 00:05:18.191 Mar 1: % CAPWAP-5-DHCP_RENEW: could not find WLC by using DHCP IP. Renew DHCP IP.
Not in a bound State.
* 00:05:26.703 Mar 1: % 3-CAPWAP-ERRORLOG: event white 38 & combination of State 2.
* 00:05:26.820 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface FastEthernet0 assigned address DHCP 10.10.11.150, mask 255.255.255.0, hostname AP001d.xxxx.xxxx
Translate "CISCO-CAPWAP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
Translate "CISCO-LWAPP - CONTROLLER.tester .net '... the domain server (10.10.10.40)
* 00:05:34.694 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings.
* 00:05:34.696 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CAPWAP-CISCO - CONTROLLER.tester .net
* 00:05:34.699 Mar 1: % 3-CAPWAP-ERRORLOG: could not resolve CISCO-LWAPP-CONTROL
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Thank you!!!
Hi John,.
If your WLC mgt vlan does not enable DHCP, yes you can try to manually configure an IP address like below (IP & Gateway and WLC mgt IP info that you need to change to according to your intellectual property regime). If the keyword CAPWAP does not use LWAPP keyword in the syntax of the command
LWAP #debug capwap console cli
LWAP #capwap ap 10.10.110.5 ip address 255.255.255.0
LWAP #capwap ap ip default gateway - 10.10.110.1
IP LWAP ap controller 10.10.110.10 #capwap
LWAP #debug lwapp console cli
LWAP #lwapp ap 10.10.110.5 ip address 255.255.255.0
LWAP #lwapp ap ip default gateway - 10.10.110.1
IP LWAP ap controller 10.10.110.10 #lwapp
This refer for details
http://mrncciew.com/2013/03/17/AP-registration/
Position the console AP output this time if it does not work
HTH
Rasika
Pls note all useful responses *.
-
Is there a way to start a backup of a series of WLC 4400 of the CLI configuration?
(1) connect controller cli.
(2) enter transfer upload config datatype
(3) If you want to encrypt the following
(a) enter transfer encrypt enable
(b) enter transfer encrypt whole-key
(4) enter transfer upload Ipserver
(5) enter the download transfer path
(6) enter transfer download filename
(7) enter the beginning of transfer download
(8) to confirm the give 'y '.
-
Hello
I need to deploy authentication of certificate based for some devices of client for Intermec for a customer. I intend to use a separate SSID for this. There are other existing SSID who based radius authentication.
question: if I don't select any server radius for this eap tls ssid and select only "BOND", going to work? Or will the WLC always find already defined radius servers and authentication failure?
Question2: If above is not possible, I have to go for eap tls with ACS. someone had some easy steps to get eap tls operational? (1252, wlc 4400, acs 4.1 windows CA LAP)
concerning
Joe
You will be able to use local for jump car as long as you do not specify a server radius on this ssid. Then you can have a different ssid to break the eap - tls pointing to a RADIUS.
Sent by Cisco Support technique iPhone App
-
Primary/secondary RADIUS server
Hey all,.
I tried to find out for awhile how primary and secondary RADIUS servers work about WLC 4400 s. If the primary RADIUS server goes down, and the secondary image is used, when the controller will return to the primary once it is up? He waits until the secondary breaks down, or done immediately switch back to the primary when it becomes available?
Thanks in advance!
The f
On versions 4.2 and earlier, if the principal fails, then the secondary image is used until the secondary level is not available. So if you want the main for the radius server to use purpose, restart the secondary image. Then the tertiary then back to the primary. 5.0 has a feature in which you can define a Dungeon alive so that when the primary comes back upward, the primary will be used again. 5.0 code not a version of good code, however.
-
SSC and authorization - question
I AROUND 1250 and I want to install my own Sertificate tour because I want to have a secure communication between LAP 1252 and WLC 4400 LWAPP. How to install can have the certificate from CA MS kneeling?
I have already installed my MS WLC CA certificate to seamlessly .pem format
Help, please
Nenad
Once you LAP are registered with a wlc. This TOUR will have the information we need to find the wlc primary, secondary and or tertiary. This info comes from the configuration of mobility and the configuration of the ap group. This will not prevent any fat s PA to connect to your network. Wired safety is what you need to do this. IDS, port security, close ports, etc..
Maybe you are looking for
-
Selection/removal of the forms of evil
I use Pages for years and have never had a problem with this issue. I want to just add a round shape in my document and copy it several times and make some labels. I want to spend the circles in the document away somehow. For some reason I can't c
-
Properties of specification to Build FPGA, compactRIO
Hello I am in particular by following this guide: example LabVIEW FPGA project - but I also experience the issue in all other projects I do To define the FPGA to "Run during the loading at the FPGA" I have to open the specifications of construction a
-
TCPIP VISA is difficult to establish
I am writing a program to set and play an instrument of iTC Oxford via interface ehthernet. The problem is, once I stopped the program and run it again, I get a time-out error. Each time, I try several times Run/Stop to make it work again. In the pr
-
[January 4, 2016] I was about to upgrade my laptop for Windows 10. But my laptop has restored the previous version (Windows 7) Any solution? -Portable features- Name of the laptop: ACER One Laser Version of Windows currently using: Windows 7 Professi
-
How to convert (Action Script 3.0) .as files to work on HTML5 Canvas?
So I did an ActionScript 3.0 game in CC animate using files as with packages and classes rather than use actions for exampleThere is a Game.as file:package { import flash.display.MovieClip; import flash.events.Event; import flash.utils.Timer;