Wireless Firmware 10.x

  • 17 November 2015
  • 35 replies
  • 1295 views


Show first post

35 replies

Userlevel 1
So software version 10.01.01.0129 is now available. I have the support contract, I can request the licenses for my C4110 controllers but I cannot use them because of the AP36xx devices:

Legacy AP26XX, AP36XX, AP4102 Series access points are not supported with V10.01 or later, however, these legacy APs will continue to be supported in maintenance mode only with V9.21 until they reach End-of-Support.

The decision to drop AP36xx devices in V.10 is final, right?
Userlevel 4
Yes, V10 does not support the 2600 nor 3600 Series. As I mentioned a few weeks ago you have a couple of options to expand your 2600/3600 network using 3700 or 3800 with V9.21 or you can work with one of our Partners and/or Extreme Sales representative to upgrade your legacy platforms to one of the newer platforms including the new 3900 Series Wave 2 APs.
This is really a disappoiting decission from ExtremeNetworks and forces us to think about our strategy for WLAN environment from Extreme in future.
What is the best practice from Extreme supporting 36xx with 39xx?
Userlevel 7
What is the best practice from Extreme supporting 36xx with 39xx? One controller for the "old" APs and one controller for the rest.
Userlevel 6
What is the best practice from Extreme supporting 36xx with 39xx? And presumably using Wireless Manager to keep configs in sync across both. Is there a good real-world guide to using Wireless Manager? I find it a lot harder to use than just the EWC web interface.
What is the best practice from Extreme supporting 36xx with 39xx? What if I need to coexist 36xx with 39xx? meaning in the same location 3610's will be within range of 39xx, I assume we can setup a mobility domain, but will that cause any issues? Will roaming work?
What is the best practice from Extreme supporting 36xx with 39xx? The response I got from GTAC:
Our recommendation is to place each site wholly within one controller pair or the other and not to mix APs from both pairs within the same site. Meaning a site should contain either v9 supported ap's or v10 supported ap's and not to mix them.

That's a bummer. I had to bring a location up with existing 3610's (70) and another portion of the same location with 3935's (12) I just turned down the signal so they didn't hear each other, but this location will be all 3935's soon, so if there are problems we can live through them. This is kind of forcing us to update faster rather than a slow phase in approach.
Userlevel 1
Would it be possible to setup the following:

- Upgrade the wifi controller pairs to V10
- Run the the 37xx, 38xx and 39xx with the controller

Next step: "Outsourcing" the management of AP36xx, i.e.:
- Convert the AP3610 to AP3630 using the standalone firmware
- Managing the standalone access points with SSH / CLI
- But still reusing the CAPWAP tunnel between the access points and the controller

Btw, will there be any V9 standalone software for AP3630?
Unfortunately I cannot download the standalone firmware for AP3610 (just for testing), as I only have a contract for the wifi controllers. Who can I contact to access the firmware?
Userlevel 7
Would it be possible to setup the following:

- Upgrade the wifi controller pairs to V10
- Run the the 37xx, 38xx and 39xx with the controller

Next step: "Outsourcing" the management of AP36xx, i.e.:
- Convert the AP3610 to AP3630 using the standalone firmware
- Managing the standalone access points with SSH / CLI
- But still reusing the CAPWAP tunnel between the access points and the controller

Btw, will there be any V9 standalone software for AP3630?
Unfortunately I cannot download the standalone firmware for AP3610 (just for testing), as I only have a contract for the wifi controllers. Who can I contact to access the firmware?
The standalone AP3630 doesn't use CAPWAP - so no, that is not possible,

Also as soon as you upgrade the controller to V10 all AP26xx/36xx are gone from the controller database as the AP type is no longer supported and the configuration is rejected during the config import after the upgrade.

Reply