I do have some questions about the 7925 deployment guide. First of all let me say it is a great source of information on what is required to deploy a 7925 phone. And the CLI "config auto-configure voice" command in v7.4 is a great way to simplify the voice configuration required on the WLC. From what I understand the Advanced Network Profile setting allows you to select which channels to scan, the maximum TxPower level for each channel and the minimum physical rate. 1) Is the 7925 by default scanning all of the 2.4GHz (14) channels and all of the 5GHz (23) channels or a total of 37 channels? From what I understood it is recommended to only scan a maximum of 12 channels. 2) Does the phone only scan 802.11a when set to 802.11a and only 802.11b/g when set to 802.11b/g? 3) All of the channels max TxPower is configured for 17dB yet there are places in the 7925 deployment guide that indicates that the maximum TxPower for the 7925 phone is 16dB. What is the correct max TxPower and should the advanced network profile be set to match? 4) If deploying in a challenging enviroment that requires a 6Mbps data rate as recommended should the minimum physical rate be set to 6Mbps also?  5) Is the only way to change the advanced network profile settings using the Web GUI? Oh and just on a side note. It is no longer possible to set the session timeout to 86400 seconds as shown in an example in the document. The maximum now is 65535 seconds. Thanks! ... View more

I would first hghly recommend upgrading the IOS image on the 1200 Access Points. The current image installed 12.2 is no longer even available for download from Cisco. The latest 12.3 image available for the 1200 is c1200-k9w7-tar.123-8.JEE.tar with a release date of 10-DEC-2010. The first non-deferred release available is c1200-k9w7-tar.123-4.JA2.tar with a release date of 06-APR-2006.  The 12.3 IOS image will allow you to define each SSID globally instead of on each radio interface which will allow you to define guest-mode on both radios. ... View more

Just to add to what Scott stated. If you have specified a DNS name on the Virtual Interface then the DNS server must resolve that name to the virtual interface IP address of 1.1.1.1. The DHCP scopes are using the public DNS server 8.8.8.8 (Google) which will not work. Bill Jenkins Sent from Cisco Technical Support iPad App ... View more

The WLC does allow for Multiple DHCP scopes to be configured, however using it for the AP to discover the WLC is not supported. It also has been known to have issues. Utilizing a centralized DHCP server would be the best solution with the appropriate ip helper statement on the SVI. DHCP option 43 can be used or DNS to discover the WLAN controllers. https://supportforums.cisco.com/docs/DOC-5711 Bill Jenkins Sent from Cisco Technical Support iPad App ... View more

The 1130 and 1240 only support 802.11b/g and 802.11a and will never support 802.11n. The APs are supported on the vWLC but obviously will not have the same functionality as the newer model 802.11n APs. Sent from Cisco Technical Support iPad App ... View more

Here is a link to the data sheet on the vWLC. http://www.cisco.com/en/US/prod/collateral/wireless/ps6302/ps8322/ps12723/data_sheet_c78-714543.html The 1130 and 1240 APs are supported per the data sheet. Sent from Cisco Technical Support iPad App ... View more

You need to assign a different bridge group id to each VLAN on both the radio and ethernet interfaces. You assigned the same IP address to the Fast Ethernet0.60 Interface and the BVI1 interface. You also assigned an IP Helper to the FastEthernmet0.60 Interface and the BVI Interface. Only the BVI1 interface needs an IP address for mangement of the AP. The IP helper should be assigned to the L3 interface on your router or switch to forward the DHCP requests. I would also recommend not using a VLAN for management of the AP that is assigned an SSID especially on the Public/Guest WiFI. It also looks like the 1200 AP is on 12.3 from the listing. Here is a partial configuration example below for multiple VLANS. ! dot11 ssid (Secure) Staff/Faculty    vlan 70    authentication open    mbssid guest-mode ! dot11 ssid Public    vlan 65    authentication open    mbssid guest-mode ! ! interface Dot11Radio0.65 encapsulation dot1Q 65 no ip route-cache bridge-group 65 bridge-group 65 subscriber-loop-control bridge-group 65 block-unknown-source no bridge-group 65 source-learning no bridge-group 65 unicast-flooding bridge-group 65 spanning-disabled ! interface Dot11Radio0.70 encapsulation dot1Q 70 no ip route-cache bridge-group 70 bridge-group 70 subscriber-loop-control bridge-group 70 block-unknown-source no bridge-group 70 source-learning no bridge-group 70 unicast-flooding bridge-group 70 spanning-disabled ! ... ! interface FastEthernet0.60 encapsulation dot1Q 60 native no ip route-cache bridge-group 1 bridge-group 1 block-unknown-source no bridge-group 1 source-learning bridge-group 1 spanning-disabled ! interface FastEthernet0.65 encapsulation dot1Q 65 no ip route-cache bridge-group 65 bridge-group 65 block-unknown-source no bridge-group 65 source-learning bridge-group 65 spanning-disabled ! interface FastEthernet0.70 encapsulation dot1Q 70 no ip route-cache bridge-group 70 bridge-group 70 block-unknown-source no bridge-group 70 source-learning bridge-group 70 spanning-disabled ! ! interface BVI1 ip address 10.60.255.7 255.255.0.0 ! ip default-gateway 10.60.0.1 ! ... View more

Could you post the following command output from the WLC? show sysinfo show network summary show interface detailed management show port summary ... View more

The 2811 is a router and does not bridge between interfaces by default. There are some advantages to using routing vs bridging and all of the examples I can find show routing configured. However you might be able to configure IRB (Integrated Routing and Bridging) on the router. The fast Ethernet and the ISE interfaces would need to be in the same bridge group. This would be similar to how an autonomous AP is configured. However this may not be supported by Cisco. Also I do not know for sure if it will work or exactly how it would need to be configured. I would recommend using the routing solution. Bill Jenkins Sent from Cisco Technical Support iPad App ... View more

You could always automate this with a script (perl, VBS, etc) that would telnet/ssh to the WLC, list the clients associated to a file, then read the file and disconnect the clients that are only associated using the command Steve provided. Although as mentioned before, this will only temporarily remove a client that continues to associate. Bill Jenkins Sent from Cisco Technical Support iPad App ... View more