Search the Community
- ClearPass Recipe Review
- ClearPass Recipe Submission
- Admin Tool - Assign Role in Bulk
- Admin Tool - User Search
- CWNP Conf 2015
- Airheads Conference Vegas 2015
- Wlan Pro Conference 2015
- Airheads Conference Shanghai 2014
- WLAN Pro Conf EU 2014
- CWNP Conference 2014 (Sep 22 - 24)
- Airheads Local 2014
- Wireless Field Day 7 (Aug 6-8, 2014)
- Black Hat 2014 Contest
- Airheads EMEA Italy 2014 (June 9 - 13)
- Americas Airheads Conference 2014
- WLAN Professionals Summit 2014
- Airheads Roadshow 2013
- EMEA Airheads Conference 2013
- APJ Airheads Conference 2013
- Americas Airheads Conference 2013
- Americas Airheads Conference 2012
- APJ Airheads Conference 2012
- EMEA Airheads Conference 2012
- Airheads EMEA 2012 Contest: How to Enter - Contest Terms & Conditions
- Airheads EMEA 2012 Contest: Create your Entry to Win Here!
- Airheads Conferences Prior to 2012
- Americas Airheads Local Events 2012
- EMEA Airheads Local Events 2012
- Wireless Field Day 3 @ Aruba Networks
- Wireless Tech Field Day 2- Silicon Valley
- Wi-Fi Mobility Symposium- San Jose, CA USA
- SDN Apps
I got it straightened out by resetting the IAP-275, downloading the same firmware that the rest of ...
I got it straightened out by resetting the IAP-275, downloading the same firmware that the rest of the IAP-205's had(including the VC). I still couldn't get it to appear in the interface so I assighned a different IAP as Master and then it appeared and I configured it.
Hi , Create a duplicate or new group and move the IAP 105 cluster, using modify device tab...
Create a duplicate or new group and move the IAP 105 cluster, using modify device tab option.
Go to APs/Devices>List page and select proper folder where you have IAP 105 cluster and down the page, in devices list section on right side we have modify deivce type option, click and select all the devices which you want to move and choose proper group and folder from drop down list and click move.
If my post addressess your qurey, give kudos:)
To anyone that runs in to this. 6 days back and forth with TAC was not helpful, but I did fin...
To anyone that runs in to this. 6 days back and forth with TAC was not helpful, but I did find the answer by digging again in to these forums.
- bug ID 102807 was mentioned here, but the needed patch was not described
- a Google search found this Aruba doc which sheds the light that the needed Netgear patch is not a firmware upgrade, but rather a patch to make the 340U compatible with Linux
- this author provided the link to the Netgear patch
- alas the needed Netgear patch for Linux compatibility on the 340U
An update to this! I've updated to Release 184.108.40.206-220.127.116.11 from 18.104.22.168-22.214.171.124 ...
An update to this!
I've updated to Release 126.96.36.199-188.8.131.52 from 184.108.40.206-220.127.116.11 and have also limited TX power to 18, and am no longer seeing this issue.
Note that I had to update firmware manually; the auto updater didn't see a newer version.
Not sure which of the two resolved the issue, but something to try if anyone else is seeing the same problem!