WLC 5508 internal DHCP server issues
Hello
I'm hoping to get your comments around the issues of dhcp, I faced with two centrally switched Wireless LAN. I have attempted to explain the installation and the problems below and would be grateful if anyone can suggest a solution for the problems I am facing:
The configuration is the following:
-J' have a WLC 5508, which has been configured with 4 SSID, of which 2 are the Central authentication and commissioning.
-J' have a LWAP connected to the WLC in HREAP mode.
-WLC is configured as a DHCP server for clients that connect to the SSID "Guest." For the rest, I'm on external dhcp server.
-Only one scope of comments Interface is configured on the WLC.
Problems:
1. as far as I know, to WLC serve internal dhcp server, it is mandatory to have the proxy enabled, but the Clients connecting to 'Internet' SSID are
Unable to get an external dhcp server ip address, if the proxy dhcp is enabled on the WLC. If I disable the proxy, everything works fine.
2 DHCP does not release the ip addresses assigned to clients, even after that that they are connected.
3. If a machine that has previously been connected to "Guest" SSID connects to the 'Internet' SSID, he asks the same ip address, he was charged by the WLC assigned under "Guest", it gets the tag with the Vlan configured on the management interface.
The controller output *.
(Cisco Controller) > show sysinfo
Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.0.116.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
(Cisco Controller) > show interface summary
Name interface Vlan Id IP port address Type Ap Mgr. Gu
EST
-------------------------------- ---- -------- --------------- ------- ------ --
1 301 10.255.255.30 dynamic guest no no
Management 1 100 172.17.1.30 static yes no
service-port s/o s/o 192.168.0.1 static no no
n/a n/a 10.0.0.1 no nonstatic virtual
(Cisco Controller) > show wlan summary
Number of wireless LANs... 4
Profile WIFI WLAN ID name / name of the SSID status Interface
------- ------------------------------------- -------- --------------------
1 active LAN management
2 active Internet management
3 active active management management
4 comments comments enabled
(Cisco Controller) > show dhcp detailed comments
Scope: comments
Enabled.......................................... Yes
Lease Time....................................... 86400 (1 day)
Pool Start....................................... 10.255.255.31
Pool End......................................... 10.255.255.254
Network.......................................... 10.255.255.0
Netmask.......................................... 255.255.255.0
Default routers... 10.255.255.1 0.0.0.0 0.0.0.0
DNS Domain.......................................
DNS.............................................. 8.8.8.8 8.8.4.4 0.0.0.0
NetBIOS name servers... 0.0.0.0 0.0.0.0 0.0.0.0
(Cisco Controller) > show detailed interface management
... Management interface
MAC address... e8:b7:48:9 b: 84:20
IP Address....................................... 172.17.1.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 172.17.1.1
State IP NAT outside... People with disabilities
External IP NAT... 0.0.0.0
VLAN............................................. 100
Quarantine-vlan... 0
Active physical Port... 1
The primary physical Port... 1
Port of physical backup... Not configured
Primary DHCP server... 172.30.50.1
Secondary DHCP server... Not configured
Option DHCP 82... People with disabilities
ACL.............................................. Not configured
AP Manager....................................... Yes
Comments interface... NO.
L2 multicast... Activated
(Cisco Controller) > show detailed comments from interface
Interface name... Comments
MAC address... e8:b7:48:9 b: 84:24
IP Address....................................... 10.255.255.30
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.255.255.1
State IP NAT outside... People with disabilities
External IP NAT... 0.0.0.0
VLAN............................................. 301
Quarantine-vlan... 0
Active physical Port... 1
The primary physical Port... 1
Port of physical backup... Not configured
Primary DHCP server... Not configured
Secondary DHCP server... Not configured
Option DHCP 82... People with disabilities
ACL.............................................. Not configured
AP Manager....................................... NO.
Comments interface... NO.
L2 multicast... Activated
(Cisco Controller) > show dhcp leases
IP MAC remaining rental period
00:21: 6a: 9 c: 03:04 10.255.255.46 23 hours, 52 minutes, 42 seconds< lease="" remains="" even="" when="" the="" client="" is="">
Example of customer connected to the Vlan right with an ip address from the incorrect interface. *************
(Cisco Controller) > show customer detail 00:21: 6a: 9 c: 03:04
MAC address of the client... 00:21: 6a: 9 c: 03:04
User name of the client... N/A
AP MAC address... a0:cf:5 b: 00:49:c0
AP Name.......................................... mel
Status of the client... Associates
Customer of the NAC OOB State... Access
Wireless LAN Id... 2< 'internet'="">
BSSID... a0:cf:5 b: 00:49: this
Connected to... dry 319
Channel.......................................... 36
IP Address....................................... 10.255.255.46< ip="" address="" assigned="" from="" the="" 'guest'="" interface="" or="" dhcp="" scope="" on="" the="">
Association ID... 1
Authentication algorithm... Open System
Reason code... 1
Status code... 0
Session timeout... 1800
Client CCX version... 4
Version of E2E customer... 1
QoS Level........................................ Silver
Beacon priority P 802,1... disabled
Support WMM... Activated
Power Save....................................... OFF
State of mobility... Local
County of movement mobility... 0
Complete security policy... Yes
State Policy Manager... RUN
Policy Manager rule created... Yes
ACL name... no
Status to apply ACL... Not available
Type of strategy... N/A
Encryption Cipher... None
Protection management framework... NO.
EAP Type......................................... Unknown
Data HARVEST-H switching... Central
H - HARVEST authentication... Central
Management of the interface...
VLAN............................................. 100< right="">
Quarantine VLAN... 0
Access VIRTUAL LAN... 100
Well it's good news. At least you have to operate.
Thank you
Scott Fella
Sent from my iPhone
Tags: Cisco Wireless
Similar Questions
-
Cisco WLC 2504 internal DHCP does not work properly
Hi all
I m trials with a Cisco WLC 2504 and some APs of 1832. I set up a DHCP scope on the interface of the controller with 2
a large number of different configurations, but the DHCP protocol does not work and Don t Access Point to obtain an IP address. My first question: is it possible to do DHCP for Access Points or only for wireless clients?
These are my interfaces:
Interface of the PA-Manager:
My DHCP scope:
Advanced DHCP:
I forgot something? Is there anyone using DHCP for its access points?
Thank you!
Hello
On Cisco WLC internal DHCP, you can add the option 43 to say where APs must register. In this case, they will try to resolve the DNS CISCO-CAPWAP-CONTROLLER or CISCO-LWAPP entry.
Let me explain briefly how AP-Manager works on WLC:
- Boots of Access Point and sends a discovery request to the management interface of the controller using the intellectual property you configured as DHCP Option 43 (as described above, it can be resolved by the DNS entry)
- Controller, sends it a response discovered that contains the name of the system, addresses AP-Manager, the number of access points already connected to each interface AP-Manager and the overall capacity of the controller.
- Joints access point controller using the less loaded interface AP Manager.
With this, every AP Manager must have a good configured interface and be connected to a different port, no LAG.
I drop a post here sometimes there is which might help:
https://supportforums.Cisco.com/document/118311/configuring-multiple-AP-...
Thank you
PS: Please do not forget to rate and score as correct answer if this answered your question
-
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".
-
New DHCP server not to issue the IPS (2012 R2)
Having a new DHCP server is going. Authorized and not coming error. Turn off the old DHCP server and try to renew the lease of the IP, and nothing happens. What is the problem?
I forgot to change the IP addresses of switches support. :( Everything works. :)
-
Discovery of a new WLC 5508 AP
Hi all
I have a WLC EXISTING with the APs 5508 located in static 192.168.1.0/24 with 7.5 Cisco IOS.
I intend to add a NEW 5508 WLC as a PDC with CISCO IOS 8.0 and 5508 WLC existing as a secondary controller.
How can I move all the AP for the new 5508 and what will happen during the update of the firmware.
Kind regards
Hi Rasika, all the answer are helpful.
If our answers are useful, pls use the (Star) rating system to rate :)the wireless controller is now configured, but we have an issue with WLAN that is using radius server authentication. Should we enroll the NEW WLC to the Radius server?
Yes, you must add your WLC in your RADIUS server with the same credentials that you to define the RADIUS on your WLC server. Link below may provide some guidance on required WLC configs. http://www.Cisco.com/c/en/us/support/docs/wireless-mobility/WLAN-security/69730-EAP-auth-WLC.html HTH Rasika * Pls note all useful responses *. -
Hi, I own a WLC 5508 and (probably), I do not understand the AP Manager interfaces. I have a laboratory with 2 x 1242AG and 1 x 1252AG connected to c2960. APs in vlan 10 (192.168.10.0/24, configured via DHCP), APs are connected to interface 'switchport access mode. C2960 is connected via a trunk to c4506 and WLC is plugged into article gi1/3 and article gi1/4 (both through twingig). The two ports are configured as 'switchport mode trunk ". WLC management interface is IDE oucederomsurlesecondport WLC 8 (linked to article gi1/4), and AP-Manager is on port 1 (connected to article gi1/3) WLC. WLC management interface has 'Management dynamic AP' set to off, and AP-Manager defined activated. The two are interfaces to management and AP-Manager tag, vlan id 12 and 13 (subnets 192.168.12.0/24, 192.168.13.0/24) respectively. APs receive their IP through DHCP configuration (server located in vlan 20, 192.168.20.0, in use ip helper-address) and try to discover DNS resolution WLC (CISCO-CAPWAP - CONTROLLER.some.domain resolves to AP-Manager IP correctly). But AP has the status "not connected" in monitor/statistics/AP join APs do not join to the controller, said WLC "Discovery request Ignoring received on the management interface".
But if I put management interface as "Dynamic AP activated" and change the DNS to resolve CISCO-CAPWAP... it's IP everything works well - AP is associated with the time. Please help, how to reach the KNEES a AP-Manager interface? Sign up for the Manager of WLC is simple, but my design requires at least 2 interfaces AP Manager.
If you have a 5508, why you have the AP Manager?
-
How to retrieve the RADIUS shared secret key on the WLC 5508
Hi all
The wirelss privious admin left our company and did not let the other know the shared secret key on the WLC 5508 Radius.
The 5508 WLC runs on the 7.0.98.0 code. I can access the viao WLC CLI and GUI. I can also access the Win2003 Radius Server, but the button displays an asterisk for me. I have listed partial RADIUS config of the WLC below. How can I get the RADIUS shared secret key? Thanks in advance.
(Cisco Controller) > show RADIUS summary
Vendor Id backward compatibility... People with disabilities
Call Station Id... lower case
Dial the Station Id Type... IP address
Aggressive failover... Activated
Keywrap.......................................... People with disabilities
Rescue test:
Test Mode.................................... Off
Probe of username... cisco-probe
Interval (in seconds)... 300
MAC for authentication Messages... hyphen delimiter
MAC for Accounting Messages... hyphen delimiterAuthentication servers
The State of the Port Address Type server all RFC3576 IPSec - AuthMode idx / phase 1/group/life/Auth/BA
--- ---- ---------------- ------ -------- ---- ------- ------------------------------------------------
1 NM 10.xx.18.48 1645 on 2 off off - no/unknown/group-0/0 None/NoneAccounting servers
The State of the Port Address Type server all RFC3576 IPSec - AuthMode idx / phase 1/group/life/Auth/BA
-Other - or ITU (q)
--- ---- ---------------- ------ -------- ---- ------- ------------------------------------------------
1 N 10.xx.18.48 1646 enabled 2 N/A disabled - no/unknown/group-0/0 None/NoneKind regards
Robert
You can retrieve the RADIUS shared secret key as other passwords that are stored on the WLC by using the procedure at the following link:
NOTE: WPA keys are not available through these methods.
Basically, you can enable password in clear text on the wlc with 'config passwd-cleartext enable' and then issue a "view orders of the running-config' - your RADIUS configuration command should now display the shared secret.
-Pat
-
problem with the connectivity of customers after mixing several models with WLC 5508 Setup WLAN ap
Hello
I have 2 5508 wlc and AP 1130 and 1200 in my test harness.
Currently, WLAN set is in place and works very well but the customer become a frequent problem with the power of the weak signal same AP is installed very near the place of the customer.
I have my doubts, if I have a question because I use several models of AP in my set-up?
How to rectify the same question?
Some time customer gets limited connectivity, means that they usually get IP also.
What are all the parameters to check in WLC?
(1) very difficult for a person on a forum to respond. Check if your AAA server was indeed seen as inactive at the same time for other devices.
If this is not the case, check the network connectivity between the 2. Maybe packets are lost between wlc and aaa server...
(2) as I mentioned, it may have nothing to do with clent near or far from the AP. What happens if your DHCP server is not responding to the client? What happens if the dhcp request never reaches the level of the DHCP server for some reason any?
You must investigate all along path to find out why the customer is not getting an ip address.
Troubleshooting involves trace of sniffer, debug, client, etc...
-
I know that the PIX can act as a DHCP server, but can he have bookings MAC - IP?
I would like my PIX to issue dhcp for our internal network, but I need to have some reservations for clients.
Hello
This is launched from time to time, but I'm afriad that the answer is always that the PIX cannot make DHCP reservations. The server DHCP PIX feature is supposed to be * very * basic. The idea was really to provide functionality of DHCP server for SOHO environments, where another DHCP server did not exist. I doubt we'll ever add this feature to the PIX since other recommended more comprehensive DHCP servers are available. You can do this with IOS DHCP if there is an option. Sorry for the news, but I hope that this help save you some time research.
Scott
-
Trouble getting a Cisco 2600 series AP to stay connected to WLC 5508
Hello
I recently loaded the independent our old APs upgrade to LWAPs. We have a WLC 5508 to our Virtual Co - Lo and I use Flexconnect to accommodate local switch and dhcp on our sites. I have updated more than 50 APs and joined them to the controller. These include only the 1130AG and 1240AG models. However they work perfectly and stay connected to the controller. I'm having is with a new batch of 2600 series APs stay connected to the controller. I tried to do research in what may cause disconnect it but have yet to find a solution. I use DNS to resolve queries for CAPWAP & LWAPP APs to the controller on our EXTENSIVE network. Read other messages I thought that this is perhaps a problem with packages to drop but have had our provider that manages Sonicwalls at both ends of the WAN confirm for me that there is no packet loss. Here are the logs that I collected through the puttty of the WLC & AP. Any help would be greatly appreciated.
AP, I do the test on:
NAME: "AP2600', DESCR: 'Cisco Aironet 2600 Series (IEEE 802.11n) Access Point.
PID: AIR-CAP2602I-A-K9, VID: V01, SN: FTX1740J8V1
WLC in question:
Name of the manufacturer... Cisco Systems Inc..
Product name... Cisco controller
Version of the product... 7.3.112.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
System name... wificontroller
Location of the system... Corp
Contact System... Net engineer
ObjectID of system... 1.3.6.1.4.1.9.1.1069
Redundancy mode... People with disabilities
IP Address....................................... 10.250.32.8
Last Reset....................................... Software reset
Time system... 190 days 3 hours 34 minutes 24 seconds
Location of the time zone of the system... (GMT - 5:00) Eastern (USA and Canada)
The country is set... USA - United States
Operating environment... Utilities (0 to 40 ° C)
Limits the internal temperature alarm... 0 to 65 ° C
-Other - or ITU (q)
... Internal temperature 38 C
Outdoor temperature... + 20 C
Fan Status....................................... Ok
State of 802. 11 b network... Activated
State of 802. 11A network... Activated
Number of wireless LANs... 14
Number of Active Clients... 71
Built-in MAC address... C8:9 C: D: 8 1: 52:E0
Power supply 1... Currently, OK
Power supply 2... Absent
Maximum number of taken access points supported... 100
Here is the result which leaves on concluded that the AP joins the WLC for a short period and then goes offline
WT-4thFlr-AP3 #.
* 15:42:04.419 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
., 3)
* 15:42:11.443 Dec 14: EVT-4-AVT %: write flash: / done event.capwap
* 15:42:11.483 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode
* 15:42:11.487 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 15:42:11.487 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246
* 15:42:11.571 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.
* 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).
* 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 15:42:12.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246
* 15:42:14.303 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246
* 15:42:14.303 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8
* 15:42:15.127 Dec 14: "Promiscuous" from Ethernet mode
* 15:42:15.535 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP
* 15:42:15.667 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1
* 15:42:15.667 Dec 14: AC setting hop first MAC: 0017.c575.a23c
* 15:42:15.855 Dec 14: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller wificontroller
* 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
* 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file
* 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file
* 15:42:15.915 Dec 14: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file
* 15:42:15.915 Dec 14: % LWAPP-3-CLIENTERRORLOG: connected mode
* 15:42:23.639 Dec 14: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled
* 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 0 disabled
* 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 1 disabled
* 15:45:43.783 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST
(. 11).
* 15:45:43.787 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode
* 15:45:43.787 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION
* 15:45:43.787 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246
* 15:45:43.867 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.
* 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).
* 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller
* 15:45:44.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246
* 15:45:46.315 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246
* 15:45:46.315 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8
* 15:45:46.487 Dec 14: "Promiscuous" from Ethernet mode
* 15:45:49.903 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP
* 15:45:50.031 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1
* 15:45:50.031 Dec 14: AC setting hop first MAC: 0017.c575.a23c
Here are the results of the client debugging capwap event about to access:
WT-4thFlr-AP3 #debug capwap customer event
Display debugging EVENT customer CAPWAP is on
WT-4thFlr-AP3 #.
* 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.
* 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request
* 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8
* 15:55:08.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:08 UTC 14 December 2013
* 15:55:25.579 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:55:25.587 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response
* 15:55:25.827 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:55:25.835 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response
* 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.
* 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request
* 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8
* 15:55:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:56 UTC 14 December 2013
* 15:56:25.735 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:56:25.743 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response
* 15:56:25.983 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:56:25.991 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response
* 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.
* 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC
* 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request
* 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0
* 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.
* 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8
* 15:56:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:56:56 UTC 14 December 2013
Here are the results of debug capwap client package in detail:
WT-4thFlr-AP3 #.
* 14 Dec 15:59:01.823: < start="" of="" capwap="" packet ="">>
* 15:59:01.823 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 15:59:01.823 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST
* 15:59:01.823 Dec 14: Msg length: 0
* 15:59:01.823 Dec 14: Msg SeqNum: 44
* 14 Dec 15:59:01.823: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:01.831: < start="" of="" capwap="" packet ="">>
* 15:59:01.831 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:01.831 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:01.831 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE
* 15:59:01.831 Dec 14: Msg length: 15
* 15:59:01.831 Dec 14: Msg SeqNum: 44
* 15:59:01.831 Dec 14:
* 15:59:01.831 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11
* 15:59:01.831 Dec 14: the vendor identifier: 0 x 00409600
* 15:59:01.831 Dec 14:
* 15:59:01.831 Dec 14:
IE: UNKNOWN IT IS ABOUT 151
* 15:59:01.831 Dec 14: IE length: 5
* 15:59:01.831 Dec 14: decode the routine unavailable, Hex Dump printing
* 15:59:01.831 Dec 14:
52 80 46 00 AC
* 14 Dec 15:59:01.831: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:20.931: < start="" of="" capwap="" packet ="">>
* 15:59:20.931 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:20.931 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST
* 15:59:20.931 Dec 14: Msg length: 93
* 15:59:20.931 Dec 14: Msg SeqNum: 38
* 15:59:20.931 Dec 14:
* 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 89
* 15:59:20.931 Dec 14: the vendor identifier: 0 x 00409600
* 15:59:20.931 Dec 14:
* 15:59:20.931 Dec 14:
IE: RRM_NEIGHBOR_CTRL_PAYLOAD
* 15:59:20.931 Dec 14: IE length: 83
* 15:59:20.931 Dec 14: decode the routine unavailable, Hex Dump printing
* 15:59:20.931 Dec 14:
00 0 HAS FA 20 08 01 00 07 0A 20 08 03 00 01 FA F4
01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7
22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F
53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 01 06 0B
01 01 01
* 14 Dec 15:59:20.931: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:20.931: < start="" of="" capwap="" packet ="">>
* 15:59:20.931 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE
* 15:59:20.931 Dec 14: Msg length: 8
* 15:59:20.931 Dec 14: Msg SeqNum: 38
* 15:59:20.931 Dec 14:
* 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4
* 15:59:20.931 Dec 14: result of Code: CAPWAP_SUCCESS
* 14 Dec 15:59:20.931: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:21.139: < start="" of="" capwap="" packet ="">>
* 15:59:21.139 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:21.139 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:21.139 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST
* 15:59:21.139 Dec 14: Msg length: 111
* 15:59:21.139 Dec 14: Msg SeqNum: 39
* 15:59:21.139 Dec 14:
* 15:59:21.139 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 107
* 15:59:21.139 Dec 14: the vendor identifier: 0 x 00409600
* 15:59:21.139 Dec 14:
* 15:59:21.139 Dec 14:
IE: RRM_NEIGHBOR_CTRL_PAYLOAD
* 15:59:21.139 Dec 14: IE length: 101
* 15:59:21.139 Dec 14: decode the routine unavailable, Hex Dump printing
* 15:59:21.143 Dec 14:
01 0 TO FA 20 08 01 F4 00 07 0A 20 08 00 01 0C FA
01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7
22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F
53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 24 28 2
30 34 38 3 40 95 99 9 01 01 01 01 01 01 01 A1
01 01 01 01 01
* 14 Dec 15:59:21.143: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:21.143: < start="" of="" capwap="" packet ="">>
* 15:59:21.143 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 15:59:21.143 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE
* 15:59:21.143 Dec 14: Msg length: 8
* 15:59:21.143 Dec 14: Msg SeqNum: 39
* 15:59:21.143 Dec 14:
* 15:59:21.143 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4
* 15:59:21.143 Dec 14: result of Code: CAPWAP_SUCCESS
* 14 Dec 15:59:21.143: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:25.547: < start="" of="" capwap="" packet ="">>
* 15:59:25.547 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 15:59:25.547 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST
* 15:59:25.547 Dec 14: Msg length: 14
* 15:59:25.547 Dec 14: Msg SeqNum: 45
* 15:59:25.547 Dec 14:
* 15:59:25.547 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10
* 15:59:25.547 Dec 14: the vendor identifier: 0 x 00409600
* 15:59:25.547 Dec 14:
* 15:59:25.547 Dec 14:
IE: RRM_LOAD_DATA_PAYLOAD
* 15:59:25.547 Dec 14: IE length: 4
* 14 Dec 15:59:25.547: slot ccaLoad 0 rxLoad 0 txLoad 0 33
* 14 Dec 15:59:25.547: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:25.555: < start="" of="" capwap="" packet ="">>
* 15:59:25.555 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:25.555 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:25.555 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE
* 15:59:25.555 Dec 14: Msg length: 0
* 15:59:25.555 Dec 14: Msg SeqNum: 45
* 14 Dec 15:59:25.555: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:25.795: < start="" of="" capwap="" packet ="">>
* 15:59:25.795 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 15:59:25.795 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST
* 15:59:25.795 Dec 14: Msg length: 14
* 15:59:25.795 Dec 14: Msg SeqNum: 46
* 15:59:25.795 Dec 14:
* 15:59:25.795 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10
* 15:59:25.795 Dec 14: the vendor identifier: 0 x 00409600
* 15:59:25.795 Dec 14:
* 15:59:25.795 Dec 14:
IE: RRM_LOAD_DATA_PAYLOAD
* 15:59:25.795 Dec 14: IE length: 4
* 14 Dec 15:59:25.795: slot ccaLoad 1 rxLoad 0 txLoad 0 0
* 14 Dec 15:59:25.795: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:25.803: < start="" of="" capwap="" packet ="">>
* 15:59:25.803 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:25.803 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:25.803 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE
* 15:59:25.803 Dec 14: Msg length: 0
* 15:59:25.803 Dec 14: Msg SeqNum: 46
* 14 Dec 15:59:25.803: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:30.375: < start="" of="" capwap="" packet ="">>
* 15:59:30.375 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:30.375 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST
* 15:59:30.375 Dec 14: Msg length: 17
* 15:59:30.375 Dec 14: Msg SeqNum: 40
* 15:59:30.375 Dec 14:
* 15:59:30.375 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 13
* 15:59:30.375 Dec 14: the vendor identifier: 0 x 00409600
SlotId: 0
Mobile Mac Addr: BC:52:B7:E3:17:CB
* 14 Dec 15:59:30.375: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:30.375: < start="" of="" capwap="" packet ="">>
* 15:59:30.375 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE
* 15:59:30.379 Dec 14: Msg length: 8
* 15:59:30.379 Dec 14: Msg SeqNum: 40
* 15:59:30.379 Dec 14:
* 15:59:30.379 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4
* 15:59:30.379 Dec 14: result of Code: CAPWAP_SUCCESS
* 14 Dec 15:59:30.379: < end="" of="" capwap="" packet ="">>
* 14 Dec 15:59:30.387: < start="" of="" capwap="" packet ="">>
* 15:59:30.387 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 15:59:30.387 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 15:59:30.387 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE
* 15:59:30.387 Dec 14: Msg length: 0
* 15:59:30.387 Dec 14: Msg SeqNum: 47
* 14 Dec 15:59:30.387: < end="" of="" capwap="" packet ="">>
* 14 Dec 16:00:00.387: < start="" of="" capwap="" packet ="">>
* 16:00:00.387 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246
* 16:00:00.387 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST
* 16:00:00.387 Dec 14: Msg length: 0
* 16:00:00.387 Dec 14: Msg SeqNum: 48
* 14 Dec 16:00:00.387: < end="" of="" capwap="" packet ="">>
* 14 Dec 16:00:00.395: < start="" of="" capwap="" packet ="">>
* 16:00:00.395 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control
* 16:00:00.395 Dec 14: HLEN 2, Radio ID 0, WBID 1
* 16:00:00.395 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE
* 16:00:00.395 Dec 14: Msg length: 15
* 16:00:00.395 Dec 14: Msg SeqNum: 48
* 16:00:00.395 Dec 14:
* 16:00:00.395 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11
* 16:00:00.395 Dec 14: the vendor identifier: 0 x 00409600
* 16:00:00.395 Dec 14:
* 16:00:00.395 Dec 14:
IE: UNKNOWN IT IS ABOUT 151
* 16:00:00.395 Dec 14: IE length: 5
* 16:00:00.395 Dec 14: decode the routine unavailable, Hex Dump printing
* 16:00:00.395 Dec 14:
52 80 81 00 AC
* 14 Dec 16:00:00.395: < end="" of="" capwap="" packet ="">>
Try reducing the mtu on ap 2600.
-
DHCP server running Hyper-v comments
Original title: Hyper-V DHCP
Hi all
I'm having a problem with a DHCP server hyper-v guest.
The DHCP server is seeing demand fall, assignment of an address to the pool, but the client pc never receives the details.
Hyper-v host is 2012r2, the guest is 2012r2 running on a gen 2 VM.
On the same hyper-v host is our SBS 2011 VMS (which does not not on the legacy network adapter) run DHCP with no problems.
I'm obviously SBS DHCP services during the test.
The 2012r2 and the SBS invited to be on the same vSwitch with the only difference that I see the generation of VM.
Any ideas?
Thanks in advance,
Rob
This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)* -
The dhcp server has not seen a directory for authorization server
I recently upgraded from Server 2003 to windows server 2008 r2. After the upgrade, the DHCP server has started to not giving IP address after a lease has expired. For DHCP to provide IP addresses, I have to restart the server. I need help on how to configure my server to allow the service to restart. Any help will be much appreciated
This issue is beyond the scope of this site (for consumers) and to be sure, you get the best (and fastest) reply, we have to ask either on Technet (for IT Pro) or MSDN (for developers)* -
Requirement of DNS and DHCP Server Essentials 2012 home
I have a Server Windows Essentials 2012 acting as DNS and DHCP server with a domain name for backups etc on my home network. It's that everything works fine, no errors, no problem. Works well actually, telling me when the children did not install updates or restarted.
I have two groups of users. My sons step, 10 and 12, which I want to use OpenDNS as a provider external DNS with a policy very, very limited and my wife and me who want to use indications of root or Google DNS or any other DNS provider. Others, specific devices no user (box of the xBox, WII, Satellite, TV, CCTV etc.) can use.
Before the 2012 server, I had a 2 k 3 server running in a virtual machine for DHCP, alone and put my wife and my devices on static reservations with the just and external DNS provider used OpenDNS as the default scope, DNS. Unfortunately different bits of domain services 2012 don't seem to work unless the server of 2012 is the first DNS server listed on client machines (backups failed. Impossible to find other local computers). Currently, this means that we are all using OpenDNS.
What I would like is a way to say 2012 to send adult group DNS queries to another DNS provider and leave the rest at default to OpenDNS, while still having them register in the original DNS domain. Any suggestions?
This issue is beyond the scope of this site and must be placed on Technet or MSDN -
I use an Acer Asspire One with Windows XP. We have wireless through AT & T Uverse. The netbook has an Atheros AR5007EG Ethernet card.
A number of things have taken place lately: I had not used the Acer for some time and the battery was dead and would not recharge. I could book until when it was plugged, but could not get on the Internet. I found online that the solution to the battery problem was to download a new bios that worked wonderfully and it is now loaded. Recently, our AT & T router died and was replaced. I put the new WEP keys in two other computers, and they connect to the Internet. I can't connect to the Internet with the Acer. I tried ipconfig / renew and get the error message: "an error occurred during renewal of the wireless network connection interface: unable to contact your DHCP server.» Request a expires. No operation can be performed on Local area connection while it has its media disconnected. "On the tab"Choose a wireless network", it shows my network and said"absorbing the network address"but nothing happens. When I do ipconfig I see that there is no IP address.I took the computer to Starbucks this morning, ran ipconfig / renew and she acquired the IP address and I was able to connect to the Internet. I brought the computer home and tried and failed to connect. The IP address is back to 0.0.0.0 and the error message appears when I try to renew it.I hesitate to make a lot of changes since it was working with a different network.Original title: IP address is missingThese forums are wonderful. I tell myself that I've saved the cost of a new battery using the bios, I found on a forum!Hello
DHCP - Dynamic Host Configuration Protocol is a protocol used by devices computer network (DHCP clients) that dynamically distributes the IP address of the destination host. Now the error indicates that your computer is not able to communicate with the server and assign the IP address.
Method 1:
Let us try to disable the firewall and check the issue.
Note: Re-enable the firewall after checking the issue.
Check whether the problem is resolved.
Method 2:
If the issue is not resolved, you can follow the steps from the link provided and check if that helps.
How to reset the Protocol Internet (TCP/IP)
http://support.Microsoft.com/kb/299357
Hope this helps and let us know if you need more assistance.
-
PC Backup doesn't work no-internal error: Server execution failed - error Code 0 x 80080005
Hello
I use Vista Business SP2.
I'm having a problem with Windows complete PC Backup. When I click on the "create backup now" trying to create a full backup of the computer, spends about 15 seconds and then this message:
The backup application could not start due to an internal error:
Server execution failed (0 x 80080005)
Please check the configuration of your system and try again.
I click on ok, and the message appears once more.I'm trying to save on the same disk external I used for backups. Backup of the files on this drive works fine.
Here are a few things that may be useful to solve this problem:
- I recently uninstalled and tried to reinstall Sophos Anti-virus, but I can't reinstall.
- My computer has been restored using the backup of the computer in the past. I have not saved since.
- I recently changed the permissions/owner on the external hard drive that I support up to.
Thanks in advance.
If you have replaced TrustedIstaller with something else, which could very well be a part of the problem. It is a user of the system and it can be called by the name of some programs and if she isn't here so the program does not know what to do. I don't know how to solve this problem - I don't think add that a new administrator account to the user with this name will do (because it will have a different code). In my view, that a re - install is the only way to solve this particular problem.
Here is an article on the fixation of 4201 event viewer error: http://www.vistax64.com/tutorials/110886-event-viewer-error-4201-a.html but I wouldn't bother with this if you have an Installation of Windows Vista genuine disc. Come back if this disc does not (and I don't think it will be necessary).
CONGRATULATIONS on finding a disk for Installation of Windows Vista SP2 genuine - I guess that it's 32-bit (like your system). It is exactly what you need - a commercial version. The OEM versions do not work because they include device drivers specific to their computers and those who will hose your system unless they have exactly the same system for (and I don't think you can do an upgrade by using the OEM versions - at least not all of them - just a clean install {although I found a HP and it has used to update my XP system crashed then) ({I was waiting the disc of real update that I bought from Dell - not exactly kosher but finally in compliance}). Here is the procedure: http://www.vistax64.com/tutorials/88236-repair-install-vista.html. Although this will not affect your data, settings or programs, you should always back up your data before you start just be on the safe side (by copy and paste if necessary even if you can't use the full backup feature). If other procedures do not work, it is almost certain to work. You can have a lot of updates to re - install. What version of Vista do you have currently? I think that the drive will work with any version of Vista (they contain probably all versions on them and that they install is governed by the Code of the product used - but I have never actually tried using a different version of disc - I only heard this said by people who seem to know what they're talking about). The fact that it is SP2 means that you won't have to uninstall all the Service packs that is even better. I REALLY hope it works for you. Make sure you use the UPGRADE option or you're going to do a clean install. If the upgrade option is grayed out, it means that it will not work (but I don't think that this will be the case).
If the drive works (and after installing all updates), then there should be nothing to fix on your system - it should work like new. You should be able to do your backup with no error message. Have no other problems. This will fix the problem with TrustedInstaller so. I feel confident thiis will work.
I mentioned that Acronis because first of all, it's the best backup software and secondly because there could be a workaround, because it does seem like there was another solution because you do not want to delete this special software (but now that you have the disc - which is debatable – although it is still the best software {even though) ({, as you say, it's not free}).
As far as Windows7 goes, I refer you to the Windows7 Forum at: http://social.answers.microsoft.com/Forums/en-US/w7install/threads where the people who specialize in installation, the upgrade, and activation Windows7 will be more than happy to help you in the process. I have Windows7 (my computer is not compatible and it is too costly to update since it's several components that need to be changed and my other computers are even older, so he has no hope here - I just have to wait until the "I need a new computer" but strikes me to new, but that will probably not for one or two years). To be honest, I wouldn't intentionallly update at this point even if I could because I always wait a while before installing a new OS (generally up to the publication of its SP1 and in the case of Vista its SP2) to let other people work the new bugs - and there are some despite what you see in the ads. Spend time on Windows7 forums, if you don't believe me. Out of the box, she seems to be better than Vista did (which was awful) but there are still issues that need to be addressed - I'll wait instead until it is more stable (and a bit of my software is not compatible and I don't want to have to go out and buy all these updates at the same time (, because it will be too expensive overall). But if you want to upgrade, which is perfectly fine - thousands of others do (always, especially since Vista has problems after all this time) and I totally understand. This is just my own personal bias and procedure - I don't recommend to my clients that I recognize it as being just a personal preference rather than one-piece objective advice. Before installing Windows7, make sure that your system is ready with the Windows7 Upgrade Advisor to: http://www.microsoft.com/windows/windows-7/get/upgrade-advisor.aspx - you should perhaps update or remove some software and may not even need to upgrade certain hardware - better know before you start (especially if you go x 64 which I assume that your PC is able to treat - mine isn't).
I hope this helps and wish you all the best in your effort to make the repair/improvement of the system. I hope it works. Remember that you must use your own product key to activate the software if necessary. If it does not automatically have to activate manually, go to start, search, and type in slui 4 enter. Enter your country and press Next. You will be on a screen with a phone number and a bunch of codes below. Dial the number and browse automatic guests until you get to a human being. Have your handy product code because it will be asked. Explain that you had a problem and you need to reinstall the OS but it's the same PC. They should give you a code to enter on this screen to activate Vista.
Good luck! Lorien - MCSA/MCSE/network + / has + - if this post solves your problem, please click the 'Mark as answer' or 'Useful' button at the top of this message. Marking a post as answer, or relatively useful, you help others find the answer more quickly.
Maybe you are looking for
-
I noticed recently that WebGL does more for me in Firefox, even though she has worked in the past. I am currently in Firefox 14.0a1 nightly on Window 7 64-bit (although I also tried in FF11). When I opened up on: supports, he says 'Blocked for your g
-
husband abroad can send but not receive texts
MY husband is out of the country and he has an iphone as I was. Can send me texts, is not mine. When he returns from abroad once he turn on his phone it gets all my messages
-
Get an error warning in Outlook Express 6
My boss uses Outlook Express 6 in XP. For these last days, when he sent an e-mail, with or without attachments, there is an error event. Sends the message, but the error message appears. When I click on the tab "error message" see the error code, it
-
Hello support, I would like to just confirm that an ASA 5505 with two providers of Internet services on this subject, can build a P2P VPN off the coast of the backup ISP automatically once the main ISP goes down. It has only a single P2P VPN necessar
-
Hierarchical update in Essbase?
HelloWe have a cube ASO essbase (on 11.1.2.4), and we use 'update hierarchy' of EAS so far.Today, we are unable to see the updated plan option in EA-> when you click on edit outline.Pointers on this? (I use the credentials of the admin).