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
We are wanting to export the logs of the access tracker in CPPM. You can filter in there, but then getting those logs to someone else, is hard. I tried exporting the logs using the dump logs from the CLI, but that is WAY overboard for what I am wanting. I am wanting something simple like we see if the access tracker.
I must be missing an export button or something...
I have hear conflicting information regarding AP105's and how they will be compatible with AP 305's and AOS8.3.
Any document that points to how this would impact a migration from 6.x to 8.x?
Can you kindly elobarate more on 7200 Performance and capacity mentioned in data sheet.
i am not able to explain few details to clients such as Maximum concurrent devices, Concurrent GRE Tunnels (System BSSIDs),Concurrent Tunneled Ports,Concurrent IPsec sessions,Concurrent SSL fallback sessions
- 7200 controllers
Hey, below is the answers: Maximum concurrent devices = Users i.e a device in the User Table. Con...
Hey, below is the answers:
Maximum concurrent devices = Users i.e a device in the User Table.
Concurrent GRE Tunnels (System BSSIDs) = Each BSSID will generate a GRE tunnel, so this will add to the GRE tunnel count.
Concurrent Tunneled Ports = Allows a GRE tunnel to be established to another device e.g MAS
Concurrent IPsec sessions = 1 IPSEC session is created per RAP and VIA client.
Concurrent SSL fallback sessions = 1 SSL session is created when a VIA client falls back to SSL.
I'm trying to determine the optimal design (high level) for a large campus wireless solution. I've read through the ArubaOS 8 Fundamentals guide and it is packed with info; but I'm left curious if anyone has any hands on experience or strong preferences for the Centralized vs Distributed Cluster architecture.
The campus is very large and will have two data centers with several thousand APs. As mentioned in the Guide, primary applications are only in the DCs so it seems Centralized would be the logical choice.
Thank you for any guidance, experience, or even just opinions!
Opinion: Centralized as much as possible. - As long as you can provide enough ba...
Centralized as much as possible.
- As long as you can provide enough bandwidth to controllers from access points in that scenario (1 gigabit connection for every 100 access points to each controller), that is the preferred scenario.
- Configure as much as possible in common at the folder level. Controllers would have minimal configuration in specific and you would add or remove controllers to a cluster to add and remove capacity and leverage redundancy without tons of configuration.
- If you have two datacenters that data is actually being served out of, you would have the option of having two separate clusters, if it would make you more comfortable.
- A cluster boundary would be anywhere that all layer 2 VLANs can be shared with a group of controllers. If you cannot do that between your controllers, you should create a separate cluster, where you can do this.
Again, this is my opinion from working with organizations to both (1) Migrate from 6.x to 8.x and (2) Deploy enterprises from scratch on 8.x.
Adding my $0.02 from a decently sized higher ed deployment . . . Your core and distributio...
Adding my $0.02 from a decently sized higher ed deployment . . .
Your core and distribution topology will undoubtedly have influence on your chosen WLAN deployment. You essentially are looking at two options:
- Manage lots of lower capacity controllers in a distributed fashion, or
- Manage fewer high capacity controllers in a centralized fashion
With AOS 8, both methods are easy, as whether it is 1 controller or tens/hundreds, the configuration hierarchy makes them fairly easy to manage. However, I chose centralized in order condense the amount of infrastructure we are managing.
We have two data centers and each one has a separate "MM domain" (not sure that is a correct term, but it's what I use). Both DCs have 2 primary clusters of 7240XM controllers. One of the DCs has a third smaller cluster that we consider "early release" - a place to first install new code, try new features, etc, as it represents a sampling of academic, staff, residential, and classroom environments. Ideally, we would've only maintained a total of three clusters instead of five; however, we were exceeding the number of devices per Airwave server and needed to slice things up a bit to accommodate those limits.
Our configuration hierarchy for the controllers is set up as follows:
- All controller-specific configuration is added at the controller level. This includes things like hostname, vrrp, time, spanning-tree, management vlan, and interface config, including port-channeling
- All vlans, vlan pools/mapping, and airwave configuration is added at the cluster level. This ensures that we can maintain the L2-cluster configuration and avoid scenarios where an L2 cluster breaks and resorts to L3.
- ALL other configuration, including ap-groups and profiles therein, are created at the orgainzation level (/md/osu). This ensures that no matter where an AP first lands during master discovery, the cluster it first touches has the correct LMS IP (read: cluster VIP) and can migrate APs to the correct cluster.
- We write NO configuration at the top level (/md) as to avoid any Aruba defaults overwriting custom configurations made at that level
That's probably plenty of opinion, but if you have any targeted questions, feel free to follow up.
I am looking for the possible methods of redundancy for RAPs - I know in a master/standy scenario, you would NAT the public IP to the VIP and the VIP would handle the failover scenario with it's virtual IP and MAC. If two controllers are not within the same L2 network, meaning we can't setup VRRP, is LMS/Backup LMS a viable option? Obviously we would need (2) public IPs instead of (1) and the RAP would require a reboot, but in a DR scenario, is that a possible option? I've always used VRRP for this, but I understand it's limitations.
I looked through the RAP VRD as well, and it seems like best practice is VRRP in a Master/Standby setup.
2 public IPs. The VRRP implementation in ArubaOS does not work with RAP. EDIT: IF the V...
2 public IPs. The VRRP implementation in ArubaOS does not work with RAP. EDIT: IF the VRRP is behind a NAT boundary (e.g. static nat to private VRRP does not work).
Setup a DNS a-record
Populate that A-record with both ip addresses
Have your DNS server deliver the ip address as round-robin or both addresses at one time to the a-record that RAP points to.
Hello, our customer has asked if we can paint the some of the AP-365's that we are mounting on their building. What is the warranty implications if we have the AP's and mounts painted. Would Aruba be happy to replace and AP that has been painted if the issue was nothing to do with the paint. Obviosuly we would mask the weep holes, grounding points etc.
Hello, We asked Aruba this a couple of years ago. We have about 150 outdoor APs an...
We asked Aruba this a couple of years ago. We have about 150 outdoor APs and quite a lot of them have to be hidden as many are installed in 'historic locations' or on on listed buildings and the like. So we have had to paint a fair few of them!
Q: As long as the customer uses non-metallic paint can the APs be painted?
Warranty Comment If the painting process fouls the grounding location, LED, or any of the connector interfaces the warranty is void.
Dark colors should not be used in areas where the daytime temperature exceeds 45C
In the event of a failure Aruba does not assume any liability for painting costs of replacement units.
A: Use paint that is free of any metals, and thin enough to not block any vents.
• They should be primed then painted
• Connectors should be masked off. Want to paint just the plastic bits
• Primer - D61H75 "Polane 2.8 Plus Spray Fil"
• Top Coat - Polane Type "HS Plus Polyurethane"
I hope that helps
We have AP Aruba 225 that connected to Aruba Controller 7030.
Some users want to share connection using Mobile wifi (Mifi) device that connected to AP Aruba using SSID WPA2/PSK in controller.
AP Aruba ----- Mifi ---- Clients
How to configure for this case.
Is Aruba 7210 MAC authentication + Captive portal using Internal db possible?
OK this is a weird one. We have been using Airwave and IAPs for years without issues. We only use in read/monitor mode, not for actual management.
We recently added IAP-325s to a site in San Antonio. They were to have the same configs as our Dallas site other than the local network specific IP and naming info.
I added one of the new APs to our Dallas network for the configs to get loaded on it. I then took it to San Antonio, brought it up as the only AP and proceeded to make all the changes. I made sure the IPs, names, organization, etc. were set to their correct values for that site and put it in service. I then brought up the other APs at that site with no issues.
The problem is with Airwave. It wanted to add all the new APs to the Dallas group under the Dallas virtual controller. It also kept showing the San Antonio and Dallas VCs as being mismatched. I tried deleting the templates and creating new ones, but that didnt work. Then I tried deleting the VCs, but no luck there and In the end out of sheer frustration I deleted all the new San Antonio APs and the existing Dallas APs from Airwave as well as their respective groups figuring I would just start over. This is where the madness steps up a notch.
It shows a newly discovered device as the San Antonio virtual controller, but with the Dallas IP address and when I try to add it I get a message that says it is adding Dallas Virtual Controller to the Dallas group, then all of the Dallas and San Antonion APs show up in the down list, but with the San Antonio Virtual Controller.
I am about to scream, LOL Someone please tell me how I can make it so that the Dallas VC and San Antonio VC show up as two seperate devices (since they are two physically differnet deviecs in two different offices) along with their respective APs.
Any and all help is greatly appreciated!
Adding an access point into a cluster and having airwave manage it embeds the same v...
Adding an access point into a cluster and having airwave manage it embeds the same virtual-controller-key as the cluster which is what Airwave uses to keep track of what APS are in the same cluster. You should SSH into the access point for san antonio and try to put in a different "virtual-controller-key" and see if that will remove fix your issue.
New to Airwave. I am currently using it to monitor my HP / Aruba switches. as I have started to bring in my locations switches into thier repective groups I am getting a lot of mismatch alerts. the majortiy of them complaining about this. "Error(Telnet/SSH Error: No username specified) " I would prefer to not enter this information in per error / switch. Where can I set this globally please? Thanks.
It depends on which switch models, there's several categories under Device Setup -> Communi...
It depends on which switch models, there's several categories under Device Setup -> Communication for various Aruba / HPE models:
Aruba (covers general Aruba branded)
HPE (covers general HPE branded)
HPE OfficeConnect Switch
I've also filed a few defects to simplify this, and to address that there's not a 1-1 mapping between Device Setup -> Add selection vs Device Setup -> Communication options.