H - HARVEST and local switching issue (LAN)
Cisco documentation indicates that H-REAP is designed for WAN environments, but I'm interested in the use of REAP H and local switching in a LAN environment. Basically want to control and data + auth traffic are separated.
Also because the controller is local that I have to use H-REAP, I can just do local switching?
Does anyone have experience with this? All suggestions, feedback will be much appreciated.
Hi Mohammed;
Yes, local switching is a sub-feature of REAP H so it must be HREAP to local switching.
The only advantage that you find using the local switching without WAN is that you don't need a big connection to the WLC since it will not process the data traffic, so you can plug a port of the WLC only. Depending on how your network look like, enlighten you really the network between APs and WLC, because traffic goes directly from AP to the destination, without transiting by for WLC.
On the other hand, you lose the advantage of having a roaming and similar advantage brought by the WLC couche3 WLC.
Tags: Cisco Wireless
Similar Questions
-
H - HARVEST in central auth and local switching has any backup auth method?
Hello
In REAP: solution with central authentication and local switching, do we have any fallback, authentication method in the case of the controller failure or WAN link to controller fails. As authentication WPA/WPA2 PSK for LWAPP REAP H in stand-alone mode.
Thank you
Arun
What guarantees do you intend to use?
If you are using PSK, you're fine as the live keys on the AP. So if you lose the controller, customers will always authenticate. If you use 802. 1 X, it's another story.
-
WLC5508 problem with dhcp and flexconnect local switching
Hello
I have a new WLC 5508 with firmware 8.0.133.0 (suggested one right now) and I'm trying to set up a WLAN with flexconnect and local switching, but when I try to connect a client it is not getting an IP address.Here's what I did:
-put the AP mode flexconnect
-support vlan in the AP has allowed
-local switching license and only in wlan
-spread the vlan from AP to the local gateway
-put the IP helper on local and pointed the wlc management ip gateway
-set up a scope for the vlan Server dhcp internal WLC
-set up a working group with the vlan-wlan association flexconnectHere is what I checked:
-l'AP obtains an IP address in dhcp in the vlan, and a lease for that appear in the DHCP Server internal to the WLC
-If I put the interface vlan on a switch in DHCP it gets the ip address of the same way
-If I set the static IP address in the wireless client it ping the local gateway and navigate normally
-J' tried the deactivation/activation proxy DHCP in the management connected to the WLAN interface, but nothing happened
-J' tried Central DHCP activation of treatment with no luckIt seems a dhcpdump on the wireless client client ask for an IP address, but get no response, as if it were the DHCP request is be filtered or diverted somehow.
All you other ideas?
DHCP on the controller is not a real dhcp server, see it that way. The management interface is used when defining aid ip and proxy dhcp must be enabled for internal dhcp. In your configuration, dhcp only works for the AP and should not work for any cable customer. You should be able to use the IP helper pointing to your WLC management interface but also make sure that you create an interface on the WLC for the local subnet and assign the interface to a correct address, even if it is not actually using it. Then in the new dynamic interface of this local subnet, you create, make sure that the primary dhcp is the ip address of the controller management. I think it works.
I would really use a true if possible dhcp server or even put a dhcp scope on the interface of L3 on the production site.
-Scott
Please evaluate the useful messages *.
-
The PowerConnect 6248 switch, RAY and selected methodological issues
I think this should be simple enough, but doesn't work that way. I have multiple 6248 and a handful of other switches in PC and I'm RADIUS deployment as primary authentication mechanism. I'm going through some preliminary tests here and a simple thing is not just to work this way. Profile networklist I put RAY first of all that the method of selection and LOCAL for the second. The RADIUS user authenticates very well, but while trying to search the LOCAL user, it is rejected. I thought that if the local user is not found by DEPARTMENT policy, he is sent to the next method? I'm only using telnet for the moment method before changing the HTTP methods. Any thoughts would be appreciated. Thank you!
Could answer my own question here, but I think that the NPS server should probably 'time' or not meet the demand of the initial authentication for the local aspect until you reach? have not tested, but may do so shortly.
-
Database update issue with JavaScript and local storage
Hi all
I come from a PHP background and a newbie with HTML5 and JavaScript, and local storage
Currently I'm building a mobile web application that uses a remote database.
I have a question about the update database.
Currently, I set it up so that when the user logs on successfully - Local Storage fields are loaded from the remote database query using a jQuery.Get. This seems to work well.
When it's time to update the data, I fill the form in local storage, allow the user edit fields, then:
-a form post to send data to the remote php page that updates the database...
Here is where I have a question: How can I make sure the edit went through good - what is better to do it now?
-Can I set up a json response to say whether or not the update was successful
or
-Query the database once more and recover the fields to compare the edit results
or
-Another technique to do of course change it went through OK
- then if successful, I can update the local storage
Q: what is the best way to ensure that the database has been correctly updated (and also not lose time with Access database useless)?
Is there a recommended for this?
In addition, if possible this beginner can use a clear example...
Why not to use jquery get () callback status where if the success is returned then to update local storage?
best,
Shocker
-
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".
-
3 local network connection and local network connection
I have a Dell with Netgear router wireless. On my computer, I have two connections to the LAN. 3 local network connection and local area connection. When I activate 3 internet works on the computer, but the wifi does not work. When I activate the connection to the internet LAN doesn't work at all. someone know how to fix the wifi?
What else shows in network connections (start > run > ncpa.cpl > OK)? Please list all icons.
On the Local network connection, right click and select Properties. Which shows in the 'Général' tab in the box under "connect using"?
On Local Area Connection 3, right-click and select Properties. Which shows in the 'Général' tab in the box under "connect using"?
- With both items enabled, open a command prompt window (start > run > cmd > OK).
- Type the following command in the black command prompt window and press ENTER after each line
ipconfig/all > "% userprofile%\Desktop\ipinfo.txt".
Notepad '% userprofile%\Desktop\ipinfo.txt '.- Copy the contents of the Notepad window and paste it into your reply here
- Close Notepad and windows command prompt and remove the file ipinfo.txt to your desktop
-
public static IP on the same subnet of both internet and local
I need to configure my little guy with ip static on the same subnet on the side of the router/internet and the side room, but it does not.
I will allow me to dhcp on the side of the router/internet and then statically assign an ip address from the same subnet on the local side, but then it does not pass on my dhcp server dhcp queries.
suggestions?
Yes. Configure the WRT with a LAN inside your main LAN IP address. Disable the DHCP server on the WRT. Wire then a main WRT to your local area network LAN port. Do not use the internet port on the WRT.
-
External display using Vision Switcher issues
* Original title: external display issues
Hi all
I have problems with external screens.
First of all:
Windows 7 pro
ATI Radeon HD 5450
I need to be a source of the computer, a switch of vision vision. When I plug the changer (after that I got the computer, so that the true monitor displays already) the computer goes into double mode with the secondary monitor displaying only. It is, the mixer is the second monitor, and the switch does not display the vision (I go to black magic for this part of the problem).
Unfortunately, windows + P does not change the external display settings.
Windows + P changes display settings when I have two different monitors connected (not the selector).
Until I plug in an external display, is there a way to force the computer to always mirror appears with two monitors output? Note that I plugged a second true monitor and changed the mirror screen and the display of these two. When I put the selector, he returned to display only mirrored, high school.
Or y at - it a keyboard shortcut to switch the primary and secondary monitors around? Or if I could write a macro?
Just to say it again - I do not see the computer where no matter what windows.
Thanks in advance!
Hello
I understand the inconvenience caused. Let me help you with the issue.
This could be a problem with the display settings. I suggest you to this first set the primary monitor as the primary monitor. Follow the steps from the link http://windows.microsoft.com/en-IN/windows-vista/Change-display-settings-on-multiple-monitors.
Connect the switch, then check if the problem persists. If the problem persists, then update your drivers for your adapter display card on the Web site of the manufacturer and the device and check if it helps.
Just reply with the results and we will continue to help you further.
-
I currently have 5 switches catalyst as the backbone of my data center 3548XL. I want to my network of the segment that is planning to do so using a combination of VLANS, VTP on the switches and using my router gateway as a router-on-a-stick with virtual interfaces for each subnet. Then I decided that what we really need, is to move to a GB LAN that would ease some of the time slow transfer we, network backups, and all SQL replication that we do.
Which led me to look at new switches and I try to get a few questions about the 3560 and 3750 switches. Any help is appreciated.
I think that both the 3560 and 3750 are layer three switches, right?
If they are three layer which eliminates the need for a router to route between the VLANS?
I use a Netflow monitor for my routers. I would be able to monitor switches using Netflow?
According to the intro video on the Cisco's Web site the 3560 is the stand-alone version of the 3750. Is the main difference between the two, just stackwise technology? Is stackwise replacement of VTP?
The 3560 s always use VTP since they do not have the ability stackwise?
How the ACL is implemented on switches? They are VLAN based, port based, MAC based?
If I have a dish network (single subnet with no VLAN) could I use an ACL on an IP or a specific port and limit traffic to it?
Quinton
No need to apologize, I just need to explain it more clearly.
Let's say you have 3 VLAN
VLAN 10 = 192.168.5.0/24
VLAN 11 = 192.168.6.0/24
VLAN 12 = 192.168.7.0/24
For the moment, you have a router interface fa0/1 connected in your switch. This connection is a trunk link. So you should have something like this on your router
int fa0/1.10
encapsulation dot1q 10
192.168.5.1 IP address 255.255.255.0
int fa0/1.11
encapsulation dot1q 11
192.168.6.1 IP address 255.255.255.0
int fa0/1.12
encapsulation dot1q 12
192.168.7.1 IP address 255.255.255.0
To replace this configuration with a 3560. On the 3560, you need the VLANS created for the layer level 2
VLAN 3560 (config) # 10
3560(config-VLAN) # name v10
and similarly for the vlan 11 and 12
Next, you create the IVR L3
int vlan 10
192.168.5.1 IP address 255.255.255.0
No tap
int vlan 11
192.168.6.1 IP address 255.255.255.0
No tap
VLAN 12 int
192.168.7.1 IP address 255.255.255.0
No tap
You then have another separate network to the router for example. 192.168.10.0/30. The connection between the switch and the router will now be a trunk connection not routed a L2
on the interface on the 3560 the router connects to
int gi0/1
No switchport
IP 192.168.10.1 255.255.255.252
router interface fa0/1
int fa0/1
address 192.168.10.2 255.255.255.252
Then, if you do not use a dynamic routing protocol, IE. just static. On the 3560
IP route 0.0.0.0 0.0.0.0 192.168.10.2
the VLAN because they are directly related to the 3560 will be able to route between them. The default route above is these VLANS can reach the rest of your network.
On the router
IP route 192.168.5.0 255.255.255.0 192.168.10.1
IP route 192.168.6.0 255.255.255.0 192.168.10.1
IP route 192.168.7.0 255.255.255.0 192.168.10.1
This is so the router knows how to get to the VLAN on the 3560.
If you don't like the idea of static, you can use EIGRP on the 3560 to share roads.
Jon
-
NSX design with cisco UCS/fabric interconnects and Nexus switches
Hi Experts
I am new to NSX design and deployment and working on a project. We deploy NSX for applications of level 4 (web, app, db, DC). I use logic, DLR, ESG and DFW switches. I next we intend to use roads static confusion..
1. do we cover all the VLAN from the virtual to the physical environment? for example mgmt VLAN, level vlans(web,app,db), vxlan transport vlan or it should be only a VLAN specific? which means would be I have set all the VLANS in environment NSX in my physical switching environment?
2 vds? don't we create not only 1 vds initially during the deployment of vcenter or more? Should we take any special consideration while deploying to the deployment of the NSX?
3 static routes - we configure static routes on the DLR and the GSS? Should I use the default routes upstream? on the physical router should we be routing all subnets from virtual environment to the GSS.
4. where and who should create virtual machines? Via vCenter or before the deployment of the nsx NSX?
5. we have a level of domain controller. Should it be part of 3 or separate applications with allow any any rule on DFW?
Thank you
Sam
(1) the VLANs which exist for physical Machines span the logical switch VXLAN NSX in the following cases:
- If the current deployment there are physical Machines in the same Vlan and subnet IP with Virtual Machines. If this common Port Vlan group is migrated to a switch logic VXLAN Backed port group and not possible to change the IP addresses of the virtual machines, and then a bridge DLR (Distributed logical router) works as the conversion between Vlan physical and virtual VXLAN
- If Conversion of P-to-V of the physical Machines continue on this Vlan
VLAN which cover only the virtual machines or virtual local networks which cover only physical Machines must not be delayed.
(2) for the deployment of the NSX, there may be more than 1 dVS or only 1 vDS according to the design. There may be another type of traffic other VXLAN base of virtual machines such as backup, storage, VMotion and the overall design, management, best practices apply here as well. A requirement of the NSX is a common VDS that spans the entire Cluster. For each Cluster, this "common VDS' may be different. Yet once this VDS maybe a separate VDS dedicated VTEP or VTEP features functionality can be added to the existing VDS. It may be best to separate the VTEP vDS.
(3) for the DLR, a default gateway is usually sufficient. If static routes are used, the GSS must then drive by default upstream and the static routes with the next hop of the DLR downstream for the subnets in the subnets IP VM logical switch. On the physical router static route to the VM, but also DLR - ESG logical subnets Subnet switch is required. Management of static routes is easier if route summarization is possible, or if necessary, close to the IP subnets, so it may be a good idea to use the dynamic routing such as Ospf or BGP protocol. There are also features of IP address management in Vrealize and other IPAM solutions if Automation is necessary for large and dynamic environments.
(4) NSX has no functionality in the creation of the VM, it only creates Services network such as switches, routers, Firewalls, Load Balancing. The creation of the part VM continiues the same way as before. A point to note is maybe the logic is created appear as VXLAN named port groups on the VDS. NSX Manager creates groups of ports on the VDS, the only difference is that the name includes VXLAN. The virtual machine is like before added to this group of VXLAN Backed Port settings, or added to the logical switch from NSX Manager interface that appears again as a Plugin for VCenter. VCENTER is so point to create virtual machines and add these VMs to the logic is.
(5) level of domain controller can be a separate layer, or other third party, may be preferable to upgrade separated except 3 applications. Usually, it's the same design without NSX. dFW rules can help protect the domain controller with allowing only ports of the virtual machine or physical Machines being admitted. dFW rules can apply to VXLAN based logical switches NSX so that VLAN based DVS Port groups because it's the kernel module.
-
Impossible to find contacts and local mail after Windows 10 re - install
I have upgraded to Windows 10. Due to the age of the PC, I chose to do a clean install, keeping all my data etc. I reinstalled Firefox without any problems - all bookmarks etc are here. I then installed Thunderbird. The address books and local e-mail were not imported nor find a tab drop-down that would allow me to do.
You make it difficult when there is an add-on. (see Matt the link)
-
Help on upgrading 10.7.5 El captain in MS Office and other possible issues
Hello!
I have a Mac Book Pro December 2011, OS X 10.7.5. I struggled with the implementation of php and many other issues and have been repeatedly invited to improve my OS. As a newbie in CS, I frankly scared - it's the only computer I have, and I can't lose/break/brick/etc, because I won't be able to fix any serious problem at the moment, not until I know what's best. But I'm really tired of losing time because of low productivity, constant freezing and other issues; and also feel ashamed bothers people on forums like this one, only because I have an obsolete system and lack of appropriate knowledge (the latest is not shameful because I learn, but the first can be really annoying for people who help me).
Please, help me with this question:
(1) is it safe to upgrade directly to el Captain 10.7.5?
(2) If Yes on first, what are the possible problems that may arise and what should I do to avoid problems?
(3) should I reinstall MS Office to upgrade the OS? This is crucial for me because I found out that I have to buy new MS Office, as Microsoft staff informed me. This isn't really the best money for me at the moment.
Thank you very much for your help and your understanding!
-First clone your boot existing to another disk drive.
http://nyacomputing.com/how-to-create-a-bootable-clone-of-your-Mac-hard-drive/
-Consult the developer of your applications if they will work with El Capitan. Some may require updates and some may simply not work, and you must buy an upgrade. A MS Office for Mac license will be valid when upgrading to El Capitan, if the version you have is compatible with El Capitan.
-In EL Capitan Apple strengthened for some hardware will require drivers drivers updated signature. For some hardware updated drivers are not available.
-
Firefox is not fully load site Barclaycard of authentication. It load regarding the demand for certain letters in my password but does not load the button 'Submit', so I can't continue with my purchase and I switch to IE8 browser to buy anything on the internet. Clues?
This has happened
A few times a week
Is a few weeks ago
Your UserAgent string in Firefox is totally messed up by another program that you have installed and Barclays does not know you use Firefox 3.6.6 - it is probably similar to IE 6.0 on this site.
http://en.Wikipedia.org/wiki/USER_AGENTtype of topic: config in the URL bar and press ENTER.
If you see the warning, you can confirm that you want to access this page.
Filter = general.useragent.
Preferences are "BOLD", a line at a time, and then select reset, right click
Then restart Firefox -
Satellite C660 - how to activate and use WAKE ON LAN?
Hi all
Previously, I posted asking about the use of Wake on Wireless LAN and was very helpfully informed that it was impossible, so I started to explore the Wake ON LAN option.
I have a Toshiba C660 PSC0LE-00500JEN and helped Wake ON LAN in the BIOS and have connected a LAN cable between my router and the laptop, which recognize each other, if the cable looks ok.
However, if I use an app to WAKE ON LAN on my android, or I use a site online "wake on lan via browser ', the laptop stay asleep.
Can someone advise?
Thank you
James
Hello
Wake Up on Lan option would work if send you a magic packet to the remote machine (laptop).
I have no experience using the Android app, who knows if it works properly
Try the other method. For example, using software such as wake on Lan for Windows (GUI) graphical user Interface
Google for it to download this software.
In addition, go to the device-> LAN card Manager-> properties-> Advanced tab and check here if the WOL is activated too
Maybe you are looking for
-
How to connect to the internet with no phone service
I cancelled the phone service to my iphone 4 and now try to erase all content and settings but it rises as unable to join the network. My network is fine as I use it on my new phone. How can I get this phone to connect to the wi - fi so it will era
-
Satellite L655 - upgrade RAM causes the system crash
I bought and inserted 2 RAM Kingston 4 GB chips. When I boot the Windows and Ubuntu 14.04 (I have a dual boot) fails. If I run a test memory Ubuntu start menu, the system hangs. I put the old RAM and all is well. To resolve this problem, I tried upgr
-
How can I remove a dialog box that never ceases to appear saying only 2?
Each unique Web site, I, a dialog box appears and says '2 '. Only this. He does for EVERY SINGLE site that I will. How can I stop this? I have tried various web browsers, restarted my computer and even a system restore and nothing.
-
HP 2000-2b44DX laptop PC: Bluetooth compatibility?
I am aware that my product is not Bluetooth compatible. I have recently updated and download the new drivers of HP and Windows 8.1 for my product. I noticed that I have installed a new driver in the driver-network section called "Qualcomm Atheros Q
-
I want to make my windows 7 pro laptop dual booting with fedora 8, I want windows 7 is compatible with fedora 8