Hi,
Thanks for the heads-up! We use the same VLAN IDs in each different routed
precinct for our wireless subnets.
I saw this in the config guide:
On the 7.4 release, the WLCs that have the same mobility group, same VLAN ID,
and different IPv4 and IPv6 subnets, generate different IPv6 router
You are right, that command can cause some serious problems.
The good news is that we moved to a Microsoft RADIUS server as a temporary
check. It works great! I still need to wait until tomorrow morning for full
peak, but during medium load today it worked perfectly. It wasn’t working well
even
Hi Yu:
We went with option 2, setting up multiple server groups, aaa profiles, and
virtual-ap profiles.
As Tim says in that post, it's a pain to setup, but it works.
But in the end, you get some load balancing with failover capability to the
other server(s).
Good luck!
Tony
-Original Message
Tony,
Thanks for the information. Which option did you go with, 1) or 2)? We are
running 6.3.1.9. I'll check with our wireless team on the 6.4 code.
Yu Wang
Network Architect
Information Technology Services
The Florida State University
850-645-6810
yu.w...@fsu.edu
Hi Yu:
>> Since there is no load balancing on aruba controllers (I was told it's
coming this fall), all controllers send auth requests to one radius server.
With the current Aruba OS, there is a way to send the requests from each
controller to a different radius server.
See this post:
http://com
On Sep 1, 2014, at 1:20 AM, Tristan Gulyas wrote:
> Hi all,
>
> We’re about to enable IPv6 on our wireless network (Cisco WiSM2, engineering
> release which looks mostly like 7.6MR2) and we’d like to know if anyone has
> seen any big show stoppers or if there’s anything we should be aware of.
Yu,
What type of change did you make to the F5¹s we are seeing a similar
issues with are Cisco wireless and F5 and LDAP authentications
Tony Juarez, CCNP Wireless
Network Engineer II
IT Services
773-702-5592 (Office)
773-230-7923 (Cell)
On 8/27/14, 2:15 PM, "Wang, Yu" wrote:
>Where are al
Brandon,
We made following major changes over the summer:
1. changed F5 from 'bandwidth savings over WAN' load balancing to performance
load balancing;
2. Use read-only LDAP servers;
3. moved radius servers to the same subnet that wireless controllers are in;
4. added a new 7240 wireless control
Tristan,
Pay attention to the config guide on the section that talks about IPv6
Mobility. We had an issue in that past where we had three wireless core
locations, and at each location we had the same VLAN ID, but s different
subnet. This caused an issue where the controllers would forward RA's
I don't know if it was mentioned here, but you may want to look at this
if you have defined more than on raidus server on your controlers:
config radius aggressive-failover disable
This turns off the aggressive failover of RADIUS - this prevents the
situation where a unknown user attempts to co
+1.
Really, exactly the same sentiment.
(5508's with 7.6MR2)
On 9/2/2014 8:44 AM, Jerry Bucklaew wrote:
On 09/01/2014 02:20 AM, Tristan Gulyas wrote:
Hi all,
We’re about to enable IPv6 on our wireless network (Cisco WiSM2,
engineering release which looks mostly like 7.6MR2) and we’d like
On 09/01/2014 02:20 AM, Tristan Gulyas wrote:
Hi all,
We’re about to enable IPv6 on our wireless network (Cisco WiSM2,
engineering release which looks mostly like 7.6MR2) and we’d like to
know if anyone has seen any big show stoppers or if there’s anything
we should be aware of. Our limited
Don,
Yep the Timeout Requests counter on the controllers ticks up for the particular
RADIUS server they’re talking to. I’ve also noticed the Pending Request timer
increase at times but eventually it drops back to 0 when usage levels go down.
Which vendor supported RADIUS appliances did you swit
13 matches
Mail list logo
