5760 WLC Features

The release notes for the new 5760 WLC mention that "profiling and on boarding" are not yet supported.
http://www.cisco.com/en/US/docs/wireless/controller/3.2_0_se/release_notes/OL28115_3_2_se_rn.html
Does this mean that when using ISE with Guest Server features, device profiling or guest self registration isn't supported ??

Yes It is true that 5760 does not support "profiling and on boarding". But when you use ISE for the same it will support the entire feature which you looking for.

Similar Messages

Has anyone deployed converged access with 3850 switches and 5760 WLCs?

Has anyone deployed a converged access network architecture with 3850 switches and 5760 WLCs? I have done lots of projects with the 5508 WLCs In a centralized deployment. Basically with this design, I manage 2 logical networks as the wireless network is an overlay over the wired network. I can design firewall to segregate traffic between the wired and wireless hence I can carry both staff and guest traffic.
Now Cisco is telling us that there is new design such that the dats plane traffic can be dropped locally through the 3850 switched. I am not sold on this and have not found any recommended best practices on when should we use a converged access architecture.
Pros
With converged access, data traffic is terminated at the MA which is on the switches, hence the WLC will not be a bottleneck? This is to prepare adoption for 802.11ac?
Less hops for voice calls from user A to user B as data control traffic is dropped locally.
Cons
Now how do I segregate guest and staff traffic if my security folks say I need a firewall?
Troubleshooting wireless client mobility will be a nightmare as the 3850 switches are MA.
Pushing and upgrading code for the Code will mean upgrading the stack of switches in the LAN riser. This will be painful in a huge campus environment like an university.
Can someone convince me why would a customer choose converged access?
Sent from Cisco Technical Support iPad App

They choose CA because of the capwap termination at the switch. You can still use a 5508 and tunnel guest to a DMZ segment if you wish. You will need a 5508 though is you want to tunnel traffic to an anchor WLC.
Sent from Cisco Technical Support iPhone App

5508 as mobility anchor to 5760 WLC

I have 4 5508 WLCs in my environment now, installed at various locations. One 5508 is acting as an anchor for guest access. All other 5508s connect back to the anchor for the same SSID, the guest wireless WLAN. A new office is opening up with several new APs using a newer 5760 WLC running as an MC. Currently the 5508's do not have New Mobility enabled. I'm pretty sure I need to enable this on the anchor at least, but the question is do all 5508 WLCs need to be changed to support New Mobility; and if so, does it require any new configuration so that I don't break the guest wireless SSID? I am new to New Mobility so I am not sure what to expect. Other than rebooting a few WLCs to turn on New Mobility.
All 5508's run 7.6.130.0. The newer 5760 runs 03.06.02E.
Thanks
Jeff

OK, so to recap;
- place the 2nd WLC in the DMZ with only 1 port (set for dynamic AP management)?
- Then Anchor the guest SSID (on it's DMZ IP instead of management IP as is now)
And to make that kind of anchoring work, I have to open ports below on the firewall.. right?
UDP port 16666 for inter-WLC communication, and IP protocol ID 97 Ethernet in IP for client traffic.
and:
•TCP 161 and 162 for SNMP
•UDP 69 for TFTP
•TCP 80 or 443 for HTTP, or HTTPS for GUI access
•TCP 23 or 22 for Telnet, or SSH for CLI access
Thanks to confirm that

Attach WAP4410N as WGB to Cisco 5760 WLC with LWAP 3702

I have 5760 WLC with 3702 wireless infrastructure. Can i connect a WAP4410N AP as WGB to be attached to my current wifi network so i can provide connectivity to some wired devices? Any tips on doing so? And any limitation can be imposed for using this WAP instead of any other AP that are supported by WLC5760? If the wired clients are passive, configuring passive-client on WLC will work normally?

Thanks Eric for the reply, however, this AP is not expected to be controlled by WLC as you mentioned since it is not lightweight and not supported by this WLC for compatibility. But in this scenario, i'm talking about operating it in WGB mode to be attached to the unified wireless infrastructure. In this scenario, it is just attached as a client that pass the traffic of its clients to the other side.
I have noticed the below statement in this guide page (539)
http://hcsdemo.com/c/en/us/td/docs/switches/lan/catalyst3650/software/release/37e/consolidated_guide/b_37e_consolidated_3650_cg.pdf
When non-Cisco WGBs are used, the switch has no information about the IP address of the clients on the wired segment behind the WGB. Without this information, the switch drops the following types of messages:
• ARP REQ from the distribution system for the WGB client.
• ARP RPLY from the WGB client.
• DHCP REQ from the WGB client.
• DHCP RPLY for the WGB client.
Accordingly, if the switch will drop all this traffic, then no traffic will be passed from the WGB clients to the network ! what I’m missing here?!!!

5760 WLC Clean Air question

Hi,
My customer Cisco 5760 WLCs running as a HA pair. Clean Air has been configured on these boxes but when I do a sh ap dot11 5ghz cleanair summary all the APs show Spectrum Oper State as Down:-
CPIT-5760-WLC-1#sh ap dot11 5ghz cleanair summary
AP Name               MAC Address         Slot ID Spectrum Capable Spectrum Intelligence   Spectrum Oper State
AP1                   xxxx.xxxx.xxxx            1 Enabled           Enabled                 Down
AP2                   xxxx.xxxx.xxxx            1 Enabled           Enabled                 Down
AP3                   xxxx.xxxx.xxxx            1 Enabled           Enabled                 Down
Anyone got any ideas as to how I overcome this little obstacle?
Thanks
Alan

Thanks for the reply. As far as I can tell all the radios are operational:-
and Clean Air has been configured:-
ap dot11 24ghz cleanair
ap dot11 5ghz cleanair
Also the link you sent was for release 7 on the old series controllers whereas this is a HA pair of the 5760s running release 3.03.
I have been through the configuring Clean Air chapter for this release and it doesn't suggest anything I haven't already tried.
Alan

Cisco 5760 WLC initial config

Hi,
I am configuring up a Cisco 5760 WLC and wondering if it is required to put in a default route? In this document it says to put one in but i dont see why it is needed as it is connected to a switch via a layer 2 Trunk.
Reference:
https://supportforums.cisco.com/docs/DOC-34430
Another question, since there is no more Dynamic Interfaces and they are replaced with Layer 2 & 3 interfaces instead. Do all Layer 2 interfaces you create require a layer 3 interface IP address to be configured also? As shown below:
Thanks

So by default the 5760 has IP routing enabled so you will need to put in a default route. A default gateway won't work unless you disable IP routing first.
Sent from Cisco Technical Support iPhone App

HA clarification in cisco 5760 WLC

Hi Experts ,
We want to establish HA between two 5760 WLC's. These controllers will be there in seperate building . So IS there anyway that we can establish HA without using stacking cables?

Hi guys! We have 2 WLC 5760 and one of them is a HA SKU and they HAVE to be in different buildings. Can we configure the HA SKU WLC as standalone and use mobility groups for redundancy? Is there a License issue in this scenario?
Thanks in advance!

5760 WLC cross-satck port-channels?

Hi would anyone know if cross-stack port-channels can be configured on a stack of 5760 WLC's?
I need to aggregate x4 20Gb port-channels comprised of x8 10Gb 10G-LR SFP's
Thanks

Please check the below link
http://www.cisco.com/c/en/us/td/docs/wireless/controller/5700/software/release/3se/layer2/command_reference/b_lay2_3se_5700_cr/b_lay2_32se_5700_cr_chapter_010.html

5760 WLC compatability with 887 routers in unified mode

Hi,
I was wondering if cisco 5760 WLC is compatible with APs in 887 router when switched to unified mode? It seems like WLC is rejecting it says unsupported AP
Cheers

Not supported.
Here is the supported AP list as of IOS-XE 3.6.0 (1700 & 1570 series support added in 3.7.0E)
http://www.cisco.com/c/en/us/td/docs/wireless/technology/5760_deploy/CT5760_Controller_Deployment_Guide/Supported_Features.html#pgfId-1071753
HTH
Rasika
**** Pls rate all useful responses ****

5760 WLC and 5760 HA WLC question

Hi everyone,
I assume this information must exist... I just cannot locate it. Customer purchasing two 5760 WLCs:
1     AIR-CT5760-500-K9
1     AIR-CT5760-HA-K9
I am looking for info on how to configure these 2 WLCs to work together. How do you inform the production WLC that a HA WLC is available to sync with? Do WLCs have to be L-2 adjacent, or will HA operate at L-3? How does this HA setup work? etc.
Any help would be really appreciated.

Hi,
Any news regarding this issue?
We've have the same scenario:
1     AIR-CT5760-500-K9
1     AIR-CT5760-HA-K9
Both running
IOS XE 03.03.01SE
I've activated Global AP Failover Priority in both WLC and from a total of 47 APs, i've configured 8 with Priority Critical, 7 APs with Priority High and 3 APs with Priority Medium.
We've issued an reload to the primary WLC and it took 7 minutes for the APs recover from the Secondary to the Primary
13:14 - reload issued on the primary WLC
13:15 - service granted by the secondary WLC (required an shut/no shut to the "Network Status" of the radio interfaces)
13:22 - service recovered to the primary WLC
Edit - Forgot to mention that the priority values mentioned above didn't show much improvement in the AP recovery time...

Query: Cisco 5760 WLC

Hi All,
I'm looking at the feature set offered by the 5760 so far I like it.
However find it bit hard to locate an "all in one" configuration guide for the platform.
I came across individual pieces of the config guide which is based on CLI -IOS XE
http://www.cisco.com/en/US/partner/products/ps12598/products_installation_and_configuration_guides_list.html
What I'm after is a configuration guide similar to what we have for IOS 7.0 train which includes configurations done via GUI.
Unless I need to fine tune or debug I'm happy with the GUI when it comes to WLCs :-)
On a side note, would there be a chassis based equivalent to the 5760 ?
Any help is much appreciated.
Thanks,
Janesh

That is the only guides out right now. I guess you will have to wait a while before some better "How to Guides" be one available. As far as the chassis, I believe they will, but not anytime soon.
Sent from Cisco Technical Support iPhone App

5760 WLC & ISE 1.2 PEAP Issues

I have the following setup:
WLC 5508 (7.4.100)
WLC 5760 (03.03.02) (I'm replacing the 5508 with the 5760)
ISE 1.2
Im currently running 802.1x PEAP with external AD authentication, on the 5508 and everything is working 100%.
As soon as I switch the users over to the 5760 I get the following errors on the ISE:
Event
5440 Endpoint abandoned EAP session and started new
Failure Reason
5440 Endpoint abandoned EAP session and started new
Resolution
Verify known NAD or supplicant issues and published bugs. Verify NAD and supplicant configuration.
Root cause
Endpoint started new authentication while previous is still in progress. Most probable that supplicant on that endpoint stopped conducting the previous authentication and started the new one. Closing the previous authentication.
I took the config of a working 5760, why would this one give the above errors ?
Jaco

Hello!
Turn on debugs on your 5760 to track authentication activities. Most probably you'll spot the issue from them. If not - post them here, so we'll have a look as well.
Thanks, Irina

5760 WLC - Cant get webauth to work (redirect)

Hi All
Im trying to configure a 5760 for webauth.
But I cant get the client to be redirected to the internal webauth page of the WLC.
I have setup the globel parameter map like this:
parameter-map type webauth global
type webauth
virtual-ip ipv4 1.1.1.1 virtual-host guest-wlc.mycorp.net
And the dns server that the client can reach is configured with to resolve the host to ip 1.1.1.1 - just like "standard" WLC setup.
But when i open a browser on the client and type google.com nothing happens.
If i type in guest-wlc.mycorp.net i get the login prompt, but it will not redirect google.com to guest-wlc.mycorp.net
Right now i have just configured the WLAN with : security web-auth and no parameter-map.
I have also tried to configure the WLAN with parameter-map global.
And I have also tried to configure a additional parameter-map type webauth and set that on the WLAN.
There was no change in behavior.
Any suggestions ?
The configuration guide seems very unclear.

Welll ... I think that we might be : "talking past each other".
1: Yes the client can easily do DNS resolution. I have testet with NSLookup.
The client resolves both extermal URLs (like cisco.com) and even the Virtual URL.
2: The client IS getting DNS. And as explained before, when I type in the virtual URL or the virtual IP I get the login page.
3: if it was a certificate problem teh browser would report back an certificate error and that I could actually live with.
The problem is still that when I type in fx. www.cisco.com i do not get redirected to the loginpage as I would on any normal AireOS WLC.
Here below i have coppied some running configuration.
Somebody please fell free to point out what could be wrong.
As mentioned the client associates fine, gets IP address fine, and can do nslookup. Everything looks fine except I do not get redirected to the login prompt page when i enter fx. www.cisco.com
parameter-map type webauth global
virtual-ip ipv4 1.1.1.1 virtual-host guest-wlc.corp.com
wlan GuestWLAN 6 internet
band-select
client vlan Guest_WLAN_5760
no security wpa
no security wpa akm dot1x
no security wpa wpa2
no security wpa wpa2 ciphers aes
security web-auth
security web-auth parameter-map global <- This might not be necessary - I have tried with and without.
session-timeout 1800
no shutdown

3600 AP keeps bouncing between Primary & Secondary 5760 WLC

Hello All,
I am not sure if it was a good idea to change the controllers from software based to IOS based :(..... Anyway this is the first time I am working on the IOS based controllers and have been going through very unusual thing. I have a 3600 AP and a couple of 2600 AP, I am just at the start of the configuration for a new deployment. Even though I have many concerns but I will start with the one which is bothering me the most, which is the APs keep jumping from a primary controller to the secondary controller. I have attached the sh run, sh logging, and the sh version for a 3600 AP and the two controllers. All I can understand from the logs is that the capwap interface keeps going down which causes the AP to fall back to the other controller, I have also tried turning off the AP FALLBACK feature, still no luck.
Addiditional Confusions,
Does any one know as how to setup HA in these controllers, as I do not see any HA or RP (Port) on these controllers neither there is any stacking module on the controllers. Would it be the old way of doing it, which was defining Primary and Secondary Controllers on the APs, if yes than I should receive two different licenses for the Controllers. But these are my devices Part numbers:
Primary: AIR-CT5760-500-K9
Secondary: AIR-CT5760-HA-K9
for now I have enabled the evaluation license on both the devices. I hope that does not make any difference.

Hi,
I have been doing some of my own trouble shooting and found out that as soon as I create a layer 3 interface on the controller so as to map it to any SSID, all of my APs start to jump on to the secondary controller and since there is a primary and secondary controller configuration on each AP they tend to come back but than soon after they jump back to the secondary....... As soon as I delete the additional layer 3 interfaces, apart from the wireless management, I get all the APs back to normal register to the controller without a glitch, I am pasting the logs being received for the APs behaviour. I have marked the logs in between with Asterics to indicate when I cleared the layer 3 interfaces and from there onwards all the APs started coming up again
Mar 12 15:09:58.624: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 4 times.!]
Mar 12 15:09:58.624: *%CAPWAP-3-ECHO_ERR: 1 wcm: Did not receive heartbeat reply; AP: 1c1d.86ee.7b40
Mar 12 15:10:03.427: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:10:05.373: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap13, changed state to down
Mar 12 15:10:08.539: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 7 times/sec!.]
Mar 12 15:10:11.657: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times.!]
Mar 12 15:10:11.657: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1f:e0
Mar 12 15:10:11.660: %LINK-3-UPDOWN: Interface Capwap30, changed state to up
Mar 12 15:10:12.703: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap30, changed state to up
Mar 12 15:10:13.111: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap16, changed state to down
Mar 12 15:10:13.678: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap28, changed state to down
Mar 12 15:10:15.840: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1f:e0
Mar 12 15:10:15.840: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:10:18.070: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap11, changed state to down
Mar 12 15:10:18.268: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap20, changed state to down
Mar 12 15:10:20.695: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 4 times/sec!.]
Mar 12 15:10:25.608: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap14, changed state to down
Mar 12 15:10:32.273: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times/sec!.]
Mar 12 15:10:35.526: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap24, changed state to down
Mar 12 15:10:47.032: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap29, changed state to down
Mar 12 15:10:50.913: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 2 times/sec!.]
Mar 12 15:10:58.725: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times.!]
Mar 12 15:10:58.726: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
Mar 12 15:10:58.726: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
Mar 12 15:10:58.726: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:11:00.521: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap30, changed state to down
Mar 12 15:11:08.450: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times.!]
Mar 12 15:11:08.450: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
Mar 12 15:11:08.921: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Join Request) and state (CAPWAP Join Response) combination
Mar 12 15:11:09.318: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP f0:29:29:92:c7:f0
Mar 12 15:11:09.319: %LINK-3-UPDOWN: Interface Capwap15, changed state to up
Mar 12 15:11:10.319: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap15, changed state to up
Mar 12 15:11:13.413: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap27, changed state to down
Mar 12 15:11:14.095: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP f0:29:29:92:c7:f0
Mar 12 15:11:14.095: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:c0:a0
Mar 12 15:11:14.098: %LINK-3-UPDOWN: Interface Capwap23, changed state to up
Mar 12 15:11:15.098: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap23, changed state to up
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
Mar 12 15:11:56.713: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:c0:a0
Mar 12 15:11:56.713: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:12:06.178: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap23, changed state to down
Mar 12 15:12:06.899: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 5 times/sec!.]
Mar 12 15:12:10.411: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times.!]
Mar 12 15:12:10.411: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:ca:60
Mar 12 15:12:10.413: %LINK-3-UPDOWN: Interface Capwap1, changed state to up
Mar 12 15:12:11.266: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:ca:60
Mar 12 15:12:11.266: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 1c:1d:86:ee:7b:40
Mar 12 15:12:11.267: %LINK-3-UPDOWN: Interface Capwap3, changed state to up
Mar 12 15:12:11.413: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap1, changed state to up
Mar 12 15:12:12.267: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap3, changed state to up
Mar 12 15:12:16.889: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap4, changed state to down
Mar 12 15:12:30.365: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 1c:1d:86:ee:7b:40
Mar 12 15:12:30.365: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:e6:10
Mar 12 15:12:30.366: %LINK-3-UPDOWN: Interface Capwap22, changed state to up
Mar 12 15:12:31.366: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap22, changed state to up
Mar 12 15:12:33.942: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:e6:10
Mar 12 15:12:33.942: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:12:48.627: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap1, changed state to down
Mar 12 15:12:51.385: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 4 times/sec!.]
Mar 12 15:13:06.083: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap15, changed state to down
Mar 12 15:13:09.053: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times.!]
Mar 12 15:13:09.053: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
VIP_G_M_Core1(config-if)#
Mar 12 15:13:12.177: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
Mar 12 15:13:16.687: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 2 times.!]
Mar 12 15:13:16.687: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1f:e0
Mar 12 15:13:16.688: %LINK-3-UPDOWN: Interface Capwap31, changed state to up
Mar 12 15:13:17.689: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap31, changed state to up
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
Mar 12 15:13:20.998: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1f:e0
Mar 12 15:13:20.998: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1d:c0
Mar 12 15:13:21.001: %LINK-3-UPDOWN: Interface Capwap21, changed state to up
VIP_G_M_Core1(config-if)#
Mar 12 15:13:22.001: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap21, changed state to up
VIP_G_M_Core1(config-if)#
Mar 12 15:13:23.935: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap22, changed state to down
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
Mar 12 15:13:40.943: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1d:c0
Mar 12 15:13:40.943: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:13:41.815: %DOT1X-5-FAIL: Authentication failed for client (c0f8.da9f.8227) on Interface Ca21 AuditSessionID 0a06906e53207995000001b8
Mar 12 15:13:41.815: %AUTHMGR-5-FAIL: Authorization failed or unapplied for client (c0f8.da9f.8227) on Interface Ca21 AuditSessionID 0a06906e53207995000001b8
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
Mar 12 15:13:44.342: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 3 times.!]
Mar 12 15:13:44.342: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
Mar 12 15:13:44.344: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
VIP_G_M_Core1(config-if)#
Mar 12 15:13:54.081: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 2 times.!]
Mar 12 15:13:54.081: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
Mar 12 15:13:55.673: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap31, changed state to down
Mar 12 15:13:57.761: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Configuration Update Request) and state (CAPWAP Join Response) combination
Mar 12 15:13:57.761: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cd:01:f0
Mar 12 15:13:57.763: %LINK-3-UPDOWN: Interface Capwap6, changed state to up
Mar 12 15:13:58.642: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cd:01:f0
Mar 12 15:13:58.642: *%CAPWAP-3-ECHO_ERR: 1 wcm: Did not receive heartbeat reply; AP: 1c1d.86ee.7b40
Mar 12 15:13:58.763: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap6, changed state to up
Mar 12 15:13:59.044: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap18, changed state to down
Mar 12 15:13:59.512: *%CAPWAP-3-INVALID_STATE_EVENT: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination
Mar 12 15:14:07.361: *%LOG-3-Q_IND: 1 wcm: Invalid AP event (CAPWAP Discovery Request) and state (CAPWAP Join Response) combination[...It occurred 2 times.!]
Mar 12 15:14:07.361: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:6f:80
Mar 12 15:14:07.362: %LINK-3-UPDOWN: Interface Capwap2, changed state to up
Mar 12 15:14:08.111: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:6f:80
Mar 12 15:14:08.111: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:2d:60
Mar 12 15:14:08.115: %LINK-3-UPDOWN: Interface Capwap8, changed state to up
Mar 12 15:14:08.363: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap2, changed state to up
Mar 12 15:14:08.964: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap21, changed state to down
Mar 12 15:14:09.114: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap8, changed state to up
Mar 12 15:14:13.525: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap3, changed state to down
Mar 12 15:14:16.013: %RADIUS-4-RADIUS_DEAD: RADIUS server 10.6.5.132:1812,1813 is not responding.
Mar 12 15:14:16.013: %RADIUS-4-RADIUS_ALIVE: RADIUS server 10.6.5.132:1812,1813 is being marked alive.
THIS IS WHERE I DELETED THE LAYER 3 INTERFACES ON THE WLC
Mar 12 15:14:24.129: %DOT1X-5-FAIL: Authentication failed for client (c0f8.da9f.8227) on Interface Ca6 AuditSessionID 0a06906e532079bf000001b9
Mar 12 15:14:24.129: %AUTHMGR-5-FAIL: Authorization failed or unapplied for client (c0f8.da9f.8227) on Interface Ca6 AuditSessionID 0a06906e532079bf000001b9
Mar 12 15:14:42.537: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:2d:60
Mar 12 15:14:42.537: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:4d:80:10
Mar 12 15:14:42.539: %LINK-3-UPDOWN: Interface Capwap17, changed state to up
Mar 12 15:14:43.539: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap17, changed state to up
Mar 12 15:14:46.456: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:4d:80:10
Mar 12 15:14:46.456: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:22:a0
Mar 12 15:14:46.458: %LINK-3-UPDOWN: Interface Capwap5, changed state to up
Mar 12 15:14:47.459: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap5, changed state to up
Mar 12 15:14:52.018: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:22:a0
Mar 12 15:14:52.018: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:61:bc:d0
Mar 12 15:14:52.021: %LINK-3-UPDOWN: Interface Capwap0, changed state to up
Mar 12 15:14:53.021: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap0, changed state to up
Mar 12 15:14:58.080: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:61:bc:d0
Mar 12 15:14:58.080: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 7c:95:f3:54:0d:d0
Mar 12 15:14:58.083: %LINK-3-UPDOWN: Interface Capwap9, changed state to up
Mar 12 15:14:59.082: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap9, changed state to up
Mar 12 15:14:59.727: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 7c:95:f3:54:0d:d0
Mar 12 15:14:59.727: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:ca:60
Mar 12 15:14:59.730: %LINK-3-UPDOWN: Interface Capwap10, changed state to up
Mar 12 15:15:00.730: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap10, changed state to up
Mar 12 15:15:04.498: %SW_MATM-4-WIRELESS_MAC_MOVE_NOTIF: Host 40f0.2f58.a172 moving from Port Te1/0/1 to Port Ca17 as wireless entry
Mar 12 15:15:05.916: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:ca:60
Mar 12 15:15:05.916: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 24:b6:57:5b:7d:90
Mar 12 15:15:05.918: %LINK-3-UPDOWN: Interface Capwap7, changed state to up
Mar 12 15:15:06.918: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap7, changed state to up
Mar 12 15:15:11.247: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 24:b6:57:5b:7d:90
Mar 12 15:15:11.247: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:de:b0
Mar 12 15:15:11.248: %LINK-3-UPDOWN: Interface Capwap19, changed state to up
Mar 12 15:15:12.249: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap19, changed state to up
Mar 12 15:15:17.150: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:de:b0
Mar 12 15:15:17.151: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP f0:29:29:92:c7:f0
Mar 12 15:15:17.152: %LINK-3-UPDOWN: Interface Capwap26, changed state to up
Mar 12 15:15:18.152: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap26, changed state to up
Mar 12 15:15:19.211: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP f0:29:29:92:c7:f0
Mar 12 15:15:19.211: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:dd:60
Mar 12 15:15:19.212: %LINK-3-UPDOWN: Interface Capwap25, changed state to up
Mar 12 15:15:20.212: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap25, changed state to up
Mar 12 15:15:28.681: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:dd:60
Mar 12 15:15:28.681: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:ff:d0
Mar 12 15:15:28.684: %LINK-3-UPDOWN: Interface Capwap12, changed state to up
Mar 12 15:15:29.684: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap12, changed state to up
Mar 12 15:15:30.285: %SW_MATM-4-WIRELESS_MAC_MOVE_NOTIF: Host 286a.bae3.de95 moving from Port Te1/0/1 to Port Ca7 as wireless entry
Mar 12 15:15:31.078: %SW_MATM-4-WIRELESS_MAC_MOVE_NOTIF: Host e0b9.ba1e.02b4 moving from Port Te1/0/1 to Port Ca7 as wireless entry
Mar 12 15:15:34.781: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:ff:d0
Mar 12 15:15:34.781: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:a7:10
Mar 12 15:15:34.782: %LINK-3-UPDOWN: Interface Capwap13, changed state to up
Mar 12 15:15:35.783: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap13, changed state to up
Mar 12 15:15:37.962: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:a7:10
Mar 12 15:15:37.962: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:e6:10
Mar 12 15:15:37.964: %LINK-3-UPDOWN: Interface Capwap16, changed state to up
Mar 12 15:15:38.965: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap16, changed state to up
Mar 12 15:15:40.401: %SW_MATM-4-WIRELESS_MAC_MOVE_NOTIF: Host e0b9.ba1e.4c97 moving from Port Te1/0/1 to Port Ca7 as wireless entry
Mar 12 15:15:44.895: %AUTHMGR-4-UNAUTH_MOVE: (slow) MAC address (40f0.2f58.a172) from Ca0 to Ca17
Mar 12 15:15:50.124: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:e6:10
Mar 12 15:15:50.124: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:9b:20
Mar 12 15:15:50.127: %LINK-3-UPDOWN: Interface Capwap28, changed state to up
Mar 12 15:15:51.126: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap28, changed state to up
Mar 12 15:15:54.510: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:9b:20
Mar 12 15:15:54.510: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:a4:2f:00
Mar 12 15:15:54.512: %LINK-3-UPDOWN: Interface Capwap11, changed state to up
Mar 12 15:15:55.513: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap11, changed state to up
Mar 12 15:15:58.371: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:a4:2f:00
Mar 12 15:15:58.371: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:61:c9:10
Mar 12 15:15:58.374: %LINK-3-UPDOWN: Interface Capwap20, changed state to up
Mar 12 15:15:59.263: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:61:c9:10
Mar 12 15:15:59.263: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:ce:70
Mar 12 15:15:59.266: %LINK-3-UPDOWN: Interface Capwap14, changed state to up
Mar 12 15:15:59.373: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap20, changed state to up
Mar 12 15:16:00.265: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap14, changed state to up
Mar 12 15:16:02.655: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:ce:70
Mar 12 15:16:02.655: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:e7:10
Mar 12 15:16:02.658: %LINK-3-UPDOWN: Interface Capwap24, changed state to up
Mar 12 15:16:02.877: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:e7:10
Mar 12 15:16:02.877: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:4d:7f:a0
Mar 12 15:16:02.878: %LINK-3-UPDOWN: Interface Capwap29, changed state to up
Mar 12 15:16:03.659: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap24, changed state to up
Mar 12 15:16:03.879: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap29, changed state to up
Mar 12 15:16:07.595: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:4d:7f:a0
Mar 12 15:16:07.595: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1f:e0
Mar 12 15:16:07.598: %LINK-3-UPDOWN: Interface Capwap30, changed state to up
Mar 12 15:16:08.597: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap30, changed state to up
Mar 12 15:16:10.146: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1f:e0
Mar 12 15:16:10.147: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:d6:30
Mar 12 15:16:10.148: %LINK-3-UPDOWN: Interface Capwap27, changed state to up
Mar 12 15:16:10.821: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:cc:d6:30
Mar 12 15:16:10.821: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 1c:1d:86:ee:7b:40
Mar 12 15:16:10.824: %LINK-3-UPDOWN: Interface Capwap23, changed state to up
Mar 12 15:16:11.148: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap27, changed state to up
Mar 12 15:16:11.824: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap23, changed state to up
Mar 12 15:16:16.727: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 1c:1d:86:ee:7b:40
Mar 12 15:16:16.727: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:62:e0
Mar 12 15:16:16.730: %LINK-3-UPDOWN: Interface Capwap4, changed state to up
Mar 12 15:16:17.729: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap4, changed state to up
Mar 12 15:16:21.617: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:62:e0
Mar 12 15:16:21.617: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:61:bf:50
Mar 12 15:16:21.618: %LINK-3-UPDOWN: Interface Capwap1, changed state to up
Mar 12 15:16:22.619: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap1, changed state to up
Mar 12 15:16:23.266: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP dc:a5:f4:61:bf:50
Mar 12 15:16:23.266: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:c0:a0
Mar 12 15:16:23.268: %LINK-3-UPDOWN: Interface Capwap15, changed state to up
Mar 12 15:16:24.268: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap15, changed state to up
Mar 12 15:16:26.127: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:c0:a0
Mar 12 15:16:26.127: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1d:c0
Mar 12 15:16:26.128: %LINK-3-UPDOWN: Interface Capwap22, changed state to up
Mar 12 15:16:27.128: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap22, changed state to up
Mar 12 15:16:27.919: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:67:1d:c0
Mar 12 15:16:27.920: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:a7:e0
Mar 12 15:16:27.921: %LINK-3-UPDOWN: Interface Capwap31, changed state to up
Mar 12 15:16:28.922: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap31, changed state to up
Mar 12 15:16:30.051: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b8:a7:e0
Mar 12 15:16:30.051: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:a4:29:00
Mar 12 15:16:30.053: %LINK-3-UPDOWN: Interface Capwap18, changed state to up
Mar 12 15:16:31.054: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap18, changed state to up
Mar 12 15:16:32.695: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP 34:db:fd:a4:29:00
Mar 12 15:16:32.695: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:67:40
Mar 12 15:16:32.697: %LINK-3-UPDOWN: Interface Capwap21, changed state to up
Mar 12 15:16:33.697: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap21, changed state to up
Mar 12 15:16:34.336: *%LOG-3-Q_IND: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:a1:67:40
Mar 12 15:16:34.336: *%LWAPP-3-VALIDATE_ERR: 1 wcm: Validation of SPAM Vendor Specific Payload failed - AP d0:c7:89:b4:d0:20
Mar 12 15:16:34.339: %LINK-3-UPDOWN: Interface Capwap3, changed state to up
Mar 12 15:16:35.339: %LINEPROTO-5-UPDOWN: Line protocol on Interface Capwap3, changed state to up

Another 5760 WLC and 5760 HA WLC question

Hi all,
I have two 5760 Controllers, one licensed and one a HA SKU Controller. I have configured them for N+1 fail-over. They are configured to be in the same L2 management network and in the same Mobility Group. The customer had an issue and tried to fail-over the APs to the secondary controller at the weekend but only about 15 out of 185 APs actually failed-over. Does anyone have any thoughts as to why they all didn't fail-over. The controllers are both running 3.3.3SE code and High Availability under Global AP Configuration is set on bot the primary and secondary.
Thanks

Refer the document :
http://www.cisco.com/c/en/us/td/docs/wireless/controller/5700/software/release/3e/high_availability/configuration_guide/b_ha_3e_5700_cg.pdf

5760 WLC Features

Similar Messages

Maybe you are looking for