@fraggy2k7 wrote:
thanks i appreciate it, Just need a little better clarification which profiles i can directly apply to only my master and don't have to add my locals. Maybe a document if you have it on a break down as far as AP/group VAPS AAA/SSID profiles AP system profiles. Which i need to apply to both and which i can only apply to master.
Fraggy2k7,
Everything is Global Except:
- VLANs (must be defined locally)
- IP addresses
- Layer 2/3 information like routing configuration
- Interface Configuration
- SNMP Configuration
- mgmt-server type amp primary (turns on AMON)
- Captive Portal Web Pages (captive portal profile is defined globally, but web pages must be uploaded on each controller).
- Controller Server Certificates must be uploaded on each controller individually
- Local Administrator usernames and passwords (Configuration to Setup a a Radius/TACACS server for authentication is global, however)
- ip cp-redirect-address configuration (tells what ip address on the controller to answer captive portal requests on).
- Local Controller IPSEC keys to connect to the master
- VPN Pools for client connectivity
- Site to Site VPN Configuration
- Spanning Tree Configuration
- Airgroup Configuration
- Controller Timezone and Summertime Settings
- Radius Source Interface Settings
- The local database is global by default, but can be configure to use the local controller
Anybody else have anything to add? I like Nightshade's sumary of this...