Controllerless Networks

Why has the most recent version of Instant (available for a while) been removed from the support portal?

Ok, guess or fact?

Either way, not really enough information.. If we know where the problems are we know whether to stop working on the difficult issues we are troubleshooting. 

In particular fast roaming looks broken on 4.1.1.2.

The reason it was pulled was not specifically related to fast roaming.   If you are still concerned whether 4.1.1.2 is the cause of your current issues, your best course of action is to open a TAC case.    4.1.1.3 (with specific fixes for the issue identified in 4.1.1.2) is expected for release this week.

Hi everyone,

About 3 or 4 weeks ago, just before our spring break, I upgraded our entire district wireless IAP infrastructure (roughly 1900 APs) from 6.4.2.0-4.1.1.1_46936 to 6.4.2.3-4.1.1.2_48114.  A day or two after spring break was over, we started having some issues where random APs seemed to stop passing DHCP traffic.  Clients were getting 169.254 (automatic private) IP addresses, and couldn't connect to the network.  Rebooting the AP would solve the problem for a couple of days.  I opened a TAC case (#1650699 if anyone with TAC access wants to check out the history), but then the problem became a major epidemic.  Last week, while I was at Atmosphere 2015, I had to remove in (thank goodness for VPNs) and initiate a district-wide downgrade (thank goodness for Airwave!) back to 6.4.2.0-4.1.1.1_46936.  Since then, we've had no problems.

I suspect that perhaps this could be another reason why 6.4.2.3-4.1.1.2_48114 was pulled...??

Update: My DHCP problem doesn't seem to be limited to 4.1.1.2_48114.  The problem just happened again today at multiple site, with the previous code version.  I still have an open TAC case, but will post a separate thread here as well.

Would still appreciate Aruba advising the reason for the recall.

It's best to contact your Aruba rep or Aruba TAC.