Rich,
We have 3 controllers and so define 3 separate radius servers/groups and 3
correlating entries in the switches.conf In the Aruba radius servers
config, we use different "fake" NAS/IP NAS/ID entries that match separate
entries in switches.conf. For example:
For controller 1:
Radius defined with NAS ID and NAS IP of 221.222.222.222
hits this in switches.conf
[221.222.222.222]
mode=production
controllerIp=122.110.1.17
deauthMethod=RADIUS
SNMPVersionTrap=2c
type=Aruba
SNMPVersion=2c
uplink=dynamic
radiusSecret=xxxxxx
For controller 2
Radius defined with NAS ID and NAS IP of 222.222.222.222
will hit on this entry with different controller ip so deauths will work:
[222.222.222.222]
mode=production
controllerIp=122.110.1.18
deauthMethod=RADIUS
SNMPVersionTrap=2c
type=Aruba
SNMPVersion=2c
uplink=dynamic
radiusSecret=xxxxxx
Then create different AP groups for each controller and associate the
different radius AAA configs with them. I hope this helps, this works
well for us.
Will
Will Rossing
*Manager, Network Services * | 218.723.6729 | [email protected]
------------------------------------------------------------------------------
LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99!
1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint
2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes
Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13.
http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
