Hello Evan, Thank you for the second question.  I like your interest in this new product and will be glad to help. This can happen for a couple of reasons.  Start with the basic, are your APs connected and are the wireless networks on and the radios on the APs up? Generally, when I see this issue popping up I see that the SSIDs are outside of the defaullt AP group called "default-group".  If your WLAN ID number is higher then WLAN ID 16, your SSIDs are not placed in the Default-Group and your SSIDs are not broadcasted.  There are 2 ways to correct this.  Rewrite your WLAN config to a WLAN ID between 1-16 or create an AP group and assign an AP to the new AP group. Lets us know if you have any other questions. Nick ... View more

Hello Adel, I'm not too sure why the router is acting up.  If you want to root cause that I would suggest reaching out to Linksys support.  They will be able to provide more direction on that issue. Nick ... View more

The code you are running ins't a normal build of code.  You are correct that your country code is probably causing the issue here.  I'll need to direct you to open a TAC case for assitance with enabling support for the -Z country domain. Nick ... View more

Hello, This is fine.  There isn't a seperate switch and WLC with this as it is all intergrated.  This is a good guide on how to add your device to Prime. http://www.cisco.com/en/US/docs/wireless/controller/technotes/7.5/ConvergedAccessDG3_2_2.html#wp44456 Nick ... View more

Hello Evan, This is a good question.  Web authentication rediect failures can fail for a number of reasons.  These are the common issues seen here: Client missing an IP or unable to ARP for it'd default gateway. DNS resolution is failing Mis-config on the web authentication Captive portal disabled (relevant only for Apple devices) I would first suggest disabling web authentication and ensure your client can reach the internet and resolve DNS as this will confirm the first 2 items.  Next, take a look at the config and compare it to this section of the deployment guide.  Depending on your config you will need an AAA list, a global and seperte web auth paramater map configured, and your WLAN configure for web auth referencing these 2 things.  Lastly, enable captive portale if you are using Apple devices.  You may also want to consider being on 3.2.3 or 3.3 code for complete captive portal support. Web Auth Deployment Guide http://www.cisco.com/en/US/docs/wireless/technology/5760_deploy/CT5760_Centralized_Configuration_eg.html#wp1056876 If the above do not work to resolve the issue feel free to open a TAC case and we'll be able to look into this one further. Nick ... View more

Hello Francisco, This is a very good question.  The 3850 switch is limited to 50 APs.  When you stack switches together they become one logical switch.  The end result of that is 1 3850 stack will support upto 50 APs.  Please note that 2 seperate switches or 2 seperate stacks will support 50 APs each. Nick ... View more

Yes this is possible.  You will need to do a basic config on your 3850, have your APs join, and configure both your data and voice WLANs.  By default all your data will be switched locally at the 3850.  In order to get your existing SSIDs data pushed to the 5508 you will need to create an auto anchor.  The first step in this process is to ensure your 5508 has new mobility architecture turned on.  This feature is only found in 7.3.112.0 or 7.5.x code or higher.  (7.4.x doesn't have this feature).  Next step is to create a mobility group between these 2 devices (you can also perform this as a SPG (switch pair group) if your 3850 is running in MA mode.  Once the mobility group is up and running you will configure the wlan on the 3850 to anchor the traffic to the 5508. There isn't a good tech tip on this exact deployment; however, there are some documents you can piece together to get this up and running.  Go ahead and review these and if you hit a snag go ahead and open a TAC case and we can get this configured for you. Mobility on 3850 http://www.cisco.com/en/US/docs/wireless/technology/5760_deploy/Mobility_Architecture.html#wp1054566 Mobility on 5508 http://www.cisco.com/en/US/docs/wireless/controller/7.5/config_guide/b_cg75_chapter_010010101.html ... View more

Hello Charles, Thanks for getting us started on this Ask the Expert event.  These are very good questions that TAC gets asked a lot.  Lets start with your second question.  In order for APs to join a 3850 switch they DO have to be directly connected to it.  They shouldn't be installed on a 2960 that is trunked to the 3850.  Also, keep in mind that your APs will need to be on the same VLAN as the 3850's wireless managment interface and be on access ports only. To answer your first question.  Documentation of this product is a little more limited then the classic WLC.  In the past couple months TAC has put together a lot of public facing documents with more on the way.  These links are great places to start. 3850/5760 Deployment Guide http://www.cisco.com/en/US/docs/wireless/technology/5760_deploy/CT5760_Controller_Deployment_Guide.html NGWC GUI Config http://www.cisco.com/en/US/docs/wireless/controller/technotes/7.5/ConvergedAccessDG3_2_2.html NGWC 802.1x Config http://www.cisco.com/en/US/products/ps12598/products_configuration_example09186a0080c1e307.shtml Nick ... View more

Patrick, This configuration isn’t seen every day in regards to requiring BOTH MAC Filtering and EAP Authentication. It sounds like you have this working with MAC Auth occurring locally on the WLC and EAP authenticating to a RADIUS server. If this part is working fine, then configuring the SSID with just MAC Auth and a RADIUS server listed on the AAA tab should make the WLC query the RADIUS server for a client’s MAC address. At the RADIUS server, you should configure the client’s MAC address as the username so that authentication is successful. This one would be best looked into via a TAC case. This should work fine now with current code. Nick ... View more

Shruti, In order to just achieve 802.11n, you will need at minimum to upgrade your Aps to newer models. 1140, 1250, 1260 and 3500 Aps will function on a 4402 with 7.0.116.0 code or higher. If you upgrade to 7.x code your 1130s and 1240s will remain supported. Keep in mind that the newer Aps such as the 1600, 2600, and 3600 will not be supported on the older 4400 platforms or older 7.0.x code. In order to have the newer features of those Aps as well as new features in 7.2 and later code you will need a 5508 WLC. In regards to 802.11n Aps connected to FA ports this is not recommended at all. 802.11n speeds give clients 300mbps+ (depending on the spatial streams on the newer Aps).  If a client is really trying to pull this much data it will overwhelm the port and will have undesired effects such as frame discards and even the AP falling off the WLC. I would suggest you review the release notes in the 7.0 train of code and determine if your needs are met by upgrading your 4400 code and replacing your APs with the 802.11n Aps supported by 7.0.x. Also, check out the release notes in the later codes such as 7.2, 7.3 and 7.4. There have been a lot of new features implemented into these codes. These newer codes also allow you to use the newer Aps such as the 1600s, 2600s, and 3600s. Release notes http://www.cisco.com/en/US/products/ps10315/prod_release_notes_list.html Nick ... View more

Hello Jimmy, The Cisco IP phones can run in either SIP mode or SCCP mode.  This is determined by the code version the phone is running.  There are builds of code for the phone that support SIP or SCCP.  If your phones are currently running in SCCP mode then you will need to install SIP capable code on the phone.  If you have any further questions regarding converting your phone to SIP please go ahead and open a TAC case so that we can provide more assistance with this conversion. Nick ... View more

Hello David, This is a very good question.  In a sentence, there isn't backwards compatibility with the classic mobility architecture.  This means that you will not be able to form a mobility group between a WLC running classic mobility architecture with another one running the next generation mobility architecture.  The best way to work around this is to have all WLCs in your mobility domain running 7.3.112.0 and supporting the new mobility architecture.  You can keep your CUWN mobility groups separate from your NGWC mobility groups; however, roaming will fail between the 2 devices. Nick ... View more

Hello Patrick, This  is a good question.  What the is trying to be explained in the answer  is that by default the 5760 WLC will operate as a mobility controller  while a 3850 will act as a mobility agent.  The mobility mode of the WLC  doesn't change which AP modes the controller supports.  At this time  all NGWC products (3850 and 5760) only support 4 AP modes: local,  se-connect, monitor, sniffer.  This is limitation is only seen on NGWC  products.  A CUWN WLC running the new mobility architecture will  continue to support all AP modes including Flexconnect and Mesh modes.   At this time there are plans to bring Flexconnect to the NGWC; however, I  can't comment on an ETA. It  looks like the 3500s were left out of that list.  The 3500 series are  supported on the NGWC platform.  A more accurate list of supported AP  for NGWC can be found here: http://www.cisco.com/en/US/docs/switches/lan/catalyst3850/software/release/3.2_0_se/release_notes/OL28114.html#wp149404 Nick ... View more