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
- Connector Translation Testing area
An issue I can think of is that essentially the Public and and Corp devices may end up within the s...
An issue I can think of is that essentially the Public and and Corp devices may end up within the same VLAN? You could enable deny inter user traffic but the preferred option would be to have segregated VLAN's. Questions are also raised with DHCP and DNS, the Corp users on a Guest VLAN may need to access Corporate DNS/DHCP servers which maybe off limits? Is this a controller or controller-less solution?
If this is a physical controller you could have a direct connection from the WLAN controller to the firewall so the Guest VLAN exists only between the WLAN controller and the firewall.
I ended up tracing all switches between IAP and Core switch and vlan 100 was not created on a coupl...
I ended up tracing all switches between IAP and Core switch and vlan 100 was not created on a couple of switches. Thanks for helping me walk through this... This is completely different than what Cisco does with vlans.
Were they on the same rev of code before attempting to join to the 205 to make a cluster? Even thou...Were they on the same rev of code before attempting to join to the 205 to make a cluster? Even though they are both in the 200 series class, they do run different images. Upgrade the 207 to the same version of the 205, then try to have it join thee cluster again.
You can't "configure" the port, but can use an ethernet jumper to connect E0 and PT on the back of ...
You can't "configure" the port, but can use an ethernet jumper to connect E0 and PT on the back of the AP to achieve the same result.
The PT to E0/PT connection is a simple passive one; bridging PT to E0 on the back effectively moves E0 to the bottom E0/PT port.
You will need a low-profile, short and flexible ethernet jumper cable for that. We ship it with the AP-303H-MNTD desk mount and AP-303H-MNTW wall mount. We currentlly do not offer that as a separate orderable item. If you want to use the standard thin mount bracket that ships with the AP (to attach it to a wiring box) for direct wall mount, it will be a tight fit even with that cable. Which is why we offer the MNTW kit.
I may be able to get you a few to test it out. Please reach out by e-mail directly to firstname.lastname@example.org if you're interested.
Hi, I am very happy to announce you that I have done my experiment successfully.I downloaded the f...
I am very happy to announce you that I have done my experiment successfully.I downloaded the firmware version 220.127.116.11 for both series access points and manually upgraded the firmware. now both my access points working in the same cluster.
This is the web site for downlode the firmware http://support.arubanetworks.com/LifetimeWarrantySoftware/tabid/121/DMXModule/661/EntryId/25165/Default.aspx
After upgrade Your login address will change to : https://setmeup.arubanetworks.com:4343/#home
thanks all for the support..
Hi, you can do as long as the IAP115 are running a minimum firmware version of Aruba InstantOS...
Hi, you can do as long as the IAP115 are running a minimum firmware version of Aruba InstantOS 18.104.22.168 (the minimum supported firmware of the IAP215).
If its a single IAP215 then just upgrade it to the same version of the IAP115's then add it to the cluster.
You need to do a couple of things: - Create an "address pools" for the RAP to get an inter...
You need to do a couple of things:
- Create an "address pools" for the RAP to get an internal controller IP address
- Add the wired mac address of the RAP in the RAP whitelist
- You need to create an AP-Group that has the public IP address that the RAP will use to reach the controller (Make sure that you allow UDP/4500 for that IP address on your firewall for incoming traffic coming from the internet)
You need add the public IP address in the provisioning profile (Master IP)
- If your RAP109 is up and running you should see the "instant" SSID connect to it, open your browser and type "instant.arubanetworks.com" , then go to the Maintenance tab >Convert and use the following option and type the public IP address that the controller should be reached from the remote location
Another update. I worked with support to figure out what was going on. The behavior of th...
I worked with support to figure out what was going on.
The behavior of the IAP is actually correct based on the circumstances.
- I first booted up the IAP out of the box with firmware 6.4.x.x
- I then immediately updated the IAP to firmware 22.214.171.124
- I then immediately udpated the IAP to firmware 126.96.36.199
Up until this point the IAP functions as expected
- I then immediately updated the IAP to firmware 6.5.4
It is at this point that the IAP attempts to find the controller on the network and converts itself to a CAP
Where I went wrong was not configuring a dummy SSID. By not configuring any SSID, the IAP doesn't know it is to act as an IAP, so if it finds a controller on the network, it will convert itself to a CAP.
You can see in the boot log two different messages that will indicated what the IAP is doing.
- ADP Running...
This message indicates the IAP is looking for a controller
- ADP is disabled by uap_controller_less
This message indicates the IAP is actually an IAP and will not look for a controller.
I am sure I have not described this 100% accurately, but this is what I learned and at least now I know how to avoid it in the future.
As always, not an Aruba issue, but a user issue :D