Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About pcroak
04-03-2019
Stats
Member since
07-23-2008
219
Posts
195
Helpful
45
Solutions
Created by
pcroak
in Wireless Security and Network Management
in Wireless Security and Network Management
02-17-2014
03:20 PM
02-17-2014
03:20 PM
Scott is correct, this issue does not impact Autonomous AP software. Thanks, Patrick
... View more
Created by
pcroak
in Wireless and Mobility
in Wireless and Mobility
06-12-2013
03:41 PM
06-12-2013
03:41 PM
Hello, There could be a number of issues that could cause your clients to not get DHCP. It looks like you have setup DHCP on the WLC itself. In order to proceed, we would likely need to collect more information from your configuration. I would recommend that you open up a TAC case and we can investigate it further. -Patrick
... View more
Created by
pcroak
in Wireless and Mobility
in Wireless and Mobility
06-11-2013
08:16 AM
06-11-2013
08:16 AM
Hi Patrick, Yes, mesh support is on the roadmap for the new architecture, which would include indoor & outdoor mesh. However, at this time I am not sure which upcoming release will bring this support. I know that the single country code issue has come up in discussions -- you are certainly not the only one asking about it. I would urge you to talk with your account team on this topic so that we can prioritize this enhancement accordingly. -Patrick
... View more
Created by
pcroak
in Wireless - Mobility Documents
in Wireless - Mobility Documents
06-10-2013
07:31 AM
06-10-2013
07:31 AM
Stephen, This issue is resolved in 7.4 code as well. If you are having other connectivity issues with clients, I would recommend collecting a client debug and opening a TAC case. -Patrick
... View more
Created by
pcroak
in Wireless and Mobility
in Wireless and Mobility
06-03-2013
09:07 AM
06-03-2013
09:07 AM
Hello Art, As of right now, the 3850 and 5760 can be configured via the CLI only. However, the next release (which should be this June/July) will contain a wireless configuration GUI. 3850/5760 Prime support will be coming with Prime release 2.0. The MC will be the aggregation point when it comes to AP licensing, the MAs will use the licenses available on the MC. As of right now, the wireless configuration will need to be applied to all of the MAs, but, in the future Prime should be able to assist with these tasks. -Patrick
... View more
Created by
pcroak
in Wireless and Mobility
in Wireless and Mobility
06-03-2013
09:00 AM
06-03-2013
09:00 AM
Hello Tenaro, Thanks for getting this discussion started! I will try to outline these solutions for you. The Cisco Unified Wireless Network (CUWN) solution is based on Wireless LAN Controllers running Airespace Operating System from the Airespace aquisition back in 2005. The controller models include the 2100, 2500, 4400, WISM/WISM2 (6500 service module), 5500, 7500, 8500. In this solution, access points will tunnel the wireless traffic to the controllers via CAPWAP. The Cisco Unified Access (UA) Wireless Solution is our new architecture that provides a converged model where you can manage your wired & wireless network configurations in the same place. This solution includes the 3850 series switch with integrated wireless support. The solution also includes the 5760 series wireless controller, which can act as an aggregation point for many 3850 switches. This platform is based off of IOS-XE, so the command structure & feel will be that of other IOS products. In this solution, the wireless traffic can terminate directly on the 3850 switch, so that it can be treated in similar fashion to a user that has a wired connection on the switch. We also have interoperability between the solutions in Airespace code version 7.3.112.0 -- so that you can integrate your existing 5508 and WISM2 modules with the new architecture as well. -Patrick
... View more
Created by
pcroak
in Wireless - Mobility Documents
in Wireless - Mobility Documents
04-19-2013
01:00 PM
04-19-2013
01:00 PM
WLC High Availability (AP SSO) Guidelines
This document is to provide education on issues we have seen with this feature for the various WLC code versions.
Overall Recommendations
If you are running any code version prior to 7.4.100.60 you need to upgrade the controller to avoid any of these issues. For HA deployments, it is recommended that even if you are running 7.4.100.60 that you upgrade to the latest MR which is 7.4.110.0.
Current 7.3 bugs
CSCuc34199 - Silent crash on WLC running 7.3.101.0
No workaround. The system does stay up, but switches back and forth between primary and secondary quite frequently.
CSCuc74677 - High Availability controller rebooting and losing its ap count license. You have to re-install the ap-count license on the active controller in order to recover from this bug.
CSCub95009 - Pmalloc memory corruption seen on the active HA WLC
Current 7.4 bugs
CSCue61613 : Privacy Bit not set in the Beacon after HA failover This causes dot1x clients to fail association after about an hour after failover. To be included in next MR. Workaround is to disable and re-enable the wlan after a failover.
CSCue02707 - HA redundancy does not fail-over to standby when powercycled To be included in next MR.
CSCue02718 - HA redundancy does not fail-over to standby when removing ETH cable
This bug has other symptoms like: Reload request Category: Default Gateway is not reachable.
To be included in next MR.
CSCud78928- HA secondary controller goes in a rebooting loop To be included in next MR.
CSCue33125 Unable to enable "bootp-broadcast" with HA SSO configured To be included in next MR.
CSCue17421 - RRM AP Neighbor list is not synced to HA Standby after switchover
CSCue90110 - Clients not removed from AP after HA failover
Use different SSID for local mode APs if you have local & flex APs.
Reboot APs after failover
CSCud98562 - HA redundancy configuration is not shown in run-config commands
CSCue38133 - Need to reset 90 day license timer on secondary controller
CSCue79462 - mobility to other WLCs (on 7.0/7.2) goes down after a failover to standby controller. This is an incompatibility between 7.3/7.4 and 7.0/7.2. Please keep in mind that this issue happens if the WLCs are on the same VLAN. A good workaround is to put the 7.3/7.4 HA pair on a different subnet to 7.0/7.2 controllers.
CSCuj17884 - Memory leak on HA AP SSO 7.4.110.0
This is resolved in the MR2 beta image that can be obtained via Tac or this support document 7.4MR2 Pre-release Image Download Available
Webauth Certificates
The webauth certificate has to be installed on BOTH controllers prior to setting up HA. If the controllers are already setup in HA and you install the certificate, it will only be installed on the primary wlc. It does not get copied to the secondary unit like the configuration. If the primary fails over to the secondary for some reason, webauth clients will get the certificate warning error until the primary becomes active again. This is noted in the configuration guide for 7.3 and 7.4, but worth mentioning here. If this is not done prior to enabling HA, then it will have to be disabled in order to install the certificate on the secondary controller.
... View more
Created by
pcroak
in Other Wireless - Mobility Subjects
in Other Wireless - Mobility Subjects
12-21-2012
08:26 AM
12-21-2012
08:26 AM
Autonomous AP architecture should not have this same issue -- I do not believe the MAC/IP address binding limitation is present. If you are experiencing issues, I would urge you to open a TAC service request. You could also run a packet capture on the AP switchport to see if the DHCP discover/requests from the VM client are making it on the wire. -Pat
... View more
Created by
pcroak
in Wireless Security and Network Management
in Wireless Security and Network Management
10-23-2012
02:37 PM
10-23-2012
02:37 PM
The bug is present in the WLC code, regardless of AP model in use. The 802.11w capability is handled incorrectly and the encryption handshake fails. -Pat
... View more
Created by
pcroak
in Wireless Security and Network Management
in Wireless Security and Network Management
09-11-2012
03:34 PM
09-11-2012
03:34 PM
Just a quick update: This issue is resolved in the 7.0.235.3 release(now available on cisco.com). It is also resolved in 7.3.101.0 (also available now). We will be releasing a version of 7.2 with the fix as well later this month, for those wanting to stay on 7.2. -Patrick
... View more
Created by
pcroak
in Other Wireless - Mobility Subjects
in Other Wireless - Mobility Subjects
05-10-2012
01:34 PM
05-10-2012
01:34 PM
Hi Cleber, Let me give a bit of background on the AP join process, it may help explain this scenario. There are 4 steps in the initial connection setup: 1. Discovery Request sent by AP to WLC - This discovery request must be sent to the *management* interface on the WLC. Only the management interface currently listens for discovery requests. 2. Discovery Response sent by WLC to AP - This response indicates the IP addresses of the available AP managers on the WLC. This will likely include the management IP address itself, and also any other interfaces you have set the Dynamic AP Management on. 3. Join Request sent by AP to WLC - This request is sent to the desired ap management interface, which can be either management or a dynamic AP management interface. 4. Join Response sent by WLC to AP - Confirmation of initial setup, DTLS tunnel is then created between AP and indicated interface. So, you can still use multiple AP managers to load balance the capwap traffic between interfaces/ports. However, the initial discovery request must be received by the management interface, and you need to tell your APs to send the discovery request to the management IP address, through DHCP option 43, DNS, or broadcast forwarding. Hopefully this clears up some of the confusion. -Pat
... View more
03-14-2012
02:09 PM
Now that you mention it, unfortunately I think multicast is one functional feature that does not work with directly connected APs. The 2500 uses Multicast > Multicast replication mode, meaning a multicast packet received is then sent via multicast to the APs (which are joined to the WLC multicast IP address configured). Directly connected APs may not properly join this multicast group, so they do not receive the traffic. It's possible that your switch software is also related, but you might hit a limitation with this deployment model on the WLC. -Pat
... View more
03-14-2012
08:13 AM
Basically, we did not formally test all scenarios with directly connected APs, and as such we cannot state that it is fully supported. It may work just fine as it is in your case, although there are some limitations (for example, I don't believe you can ping or telnet/ssh to the APs in this configuration). -Pat
... View more
Created by
pcroak
in Other Wireless - Mobility Subjects
in Other Wireless - Mobility Subjects
02-24-2012
02:29 PM
02-24-2012
02:29 PM
Hi Anna, Alright, one idea comes to my mind, we did have a bug in earlier 4.x WLC code: CSCsy79782: WLC uptime reset to 0 after being up for 497 days. Basically, counters WLC could reset if it was up for 497 consecutive days. The results after these counter resets are unpredictable, and intermittent issues can result. A code upgrade on the WLC should be considered if possible, but what is the current Uptime on your WLC? You might want to simply try a WLC reboot during a maintenance window if the above condition could be possible. Otherwise, if you can capture a full client debug of a failure we can take a look. -Pat
... View more
Created by
pcroak
in Wireless and Mobility
06-12-2013
06-12-2013
Hello,There could be a number of issues that could cause your clients to
not get DHCP. It looks like...
Created by
pcroak
in Wireless and Mobility
06-11-2013
06-11-2013
Hi Patrick,Yes, mesh support is on the roadmap for the new architecture,
which would include indoor ...
Created by
pcroak
in Wireless - Mobility Documents
06-10-2013
06-10-2013
Stephen,This issue is resolved in 7.4 code as well. If you are having
other connectivity issues with...
Created by
pcroak
in Wireless and Mobility
06-03-2013
06-03-2013
Hello Art,As of right now, the 3850 and 5760 can be configured via the
CLI only. However, the next r...
Created by
pcroak
in Wireless and Mobility
06-03-2013
06-03-2013
Hello Tenaro,Thanks for getting this discussion started! I will try to
outline these solutions for y...
Created by
pcroak
in Wireless - Mobility Documents
04-19-2013
04-19-2013
WLC High Availability (AP SSO) Guidelines This document is to provide
education on issues we have se...
Created by
pcroak
in Other Wireless - Mobility Subjects
12-21-2012
12-21-2012
Autonomous AP architecture should not have this same issue -- I do not
believe the MAC/IP address bi...
10-23-2012
The bug is present in the WLC code, regardless of AP model in use. The
802.11w capability is handled...
09-11-2012
Just a quick update:This issue is resolved in the 7.0.235.3 release(now
available on cisco.com).It i...
Created by
pcroak
in Other Wireless - Mobility Subjects
05-10-2012
05-10-2012
Hi Cleber,Let me give a bit of background on the AP join process, it may
help explain this scenario....
03-14-2012
Now that you mention it, unfortunately I think multicast is one
functional feature that does not wor...
03-14-2012
Basically, we did not formally test all scenarios with directly
connected APs, and as such we cannot...
Created by
pcroak
in Other Wireless - Mobility Subjects
02-24-2012
02-24-2012
Hi Anna,Alright, one idea comes to my mind, we did have a bug in earlier
4.x WLC code:CSCsy79782: WL...
Public Statistics
| Date Registered | 07-23-2008 11:22 AM |
| Date Last Visited | 04-03-2019 02:25 PM |
| Total Messages Posted | 219 |
| Total Helpful Votes Received | 195 |
Helpful Votes Given To
.jpg "Hall of Fame Community Legend"){kind=icon}
Helpful Votes From
