Search the Community
- Global Forums
- Airheads Channel Group - UK and Ireland
- Airheads Channel Group (German speaking)
- Airheads Channel Group - France
- Airheads Channel Groep – Nederland
- Airheads Channel Group - Italy
- Airheads Channel Group - Taiwan
- Airheads Channel Group - Singapore
- Airheads Channel Group - Malaysia
- Airheads Channel Group – Norway
- Airheads Channel Group South Africa
- Airheads Channel Group Bechtle
- 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
What is AirRecorder
A Java based tool that will run several common CLI commands for checking controller, AP, and wireless device health. AirRecorder supports ArubaOS, Instant VC (IAP) and MeshOS (MSR). AirRecorder runs on any operating system that supports a Java Platform Standard Edition version 6 or later.
Login to support.arubanetworks.com go to Tools> Airrecorder Folder
At time of writing this is version 1.2.16.
After downloading the distribution ZIP file, unpack it to a directory or folder of choice. On successful unpacking, you should at least find following files:
Please note that "samples" is a folder that contains sample files.
To run the tool, please open a DOS command window or Linux/MacOS terminal and type:
java -jar AirRecorder-1.2.16-release.jar
You should see an output similar to:
AirRecorder (c)2011-2014 Thomas Bastian, Aruba Networks
usage: AirRecorder [options] [<controllerip>]
If you don’t see an output similar to above, then most likely you don’t have Java installed. Please download the proper Java for your system from:
AirRecorder records the output of CLI commands in a file. By default, the list of commands is read from a file named "commands" or "commands.txt". Please go
ahead and create a file named "commands.txt" in the distribution directory. Enter a single line into the file:
0,show ap active
and save the file.
You are now ready to run your first AirRecorder session. In the Windows command (DOS) window or Linux/MacOS Shell terminal window, please type:
java -jar AirRecorder-1.2.16-release.jar <controller>
<controller> is the IP address or hostname of the controller you would like to run the session against.
As the session begins, you will be prompted for the username, password and enable password to be used to login into the controller (if you have
"enable bypass" activated on the controller, just hit RETURN when prompted for enable password).
At the end of the session, a new file should have been created:
Please use your favorite editor to look at the contents recorded (it should contain the output from the command “show ap active”).
AirRecorder can read the username, password and enable password for login into the controller:
- from the command line: -u <username> -p <password> -e <enable password>
java -jar AirRecorder-1.2.16-release.jar -u admin -p admin -e enable <controller>
- from a file named either "<controller>" or "<controller>.txt" argument provided (i.e. in the above case, a file named: "192.168.0.196" or
"192.168.0.196.txt"). In this case, the file should contain the username, password and enable password each on a separate line in the file. If
"enable bypass" is enabled on the controller, leave the third line blank.
Working With Commands
AirRecorder can read commands from any file. Please use the command line argument:
-c <command file>
to specify an alternate commands file to be used.
The commands file syntax is as follows:
- one command specification per line
- lines starting with # are skipped
- a command specification takes the form: [<trigger>;]<schedule>,<command>
i.e.: 0,show ap active
<trigger> is an optional field and can be omitted. TRIGGERS will be discussed later.
<schedule> is further broken down as:
<interval>[;<execution count>[;<cycle interval>[;<cycle count>]]]
<interval> is the interval in *SECONDS* between consecutive executions. A value of zero will run the command once. Please be cautious when selecting the interval since smaller values may impact controller performance.
<execution count> is the optional number of times the command will be executed. When unspecified the command will repeat for ever. Otherwise the command will be executed the specified amount *PER* cycle. Note that if <cycle interval> is not specified, the command will be executed <execution count> number of times, then never again.
<cycle interval> is the optional interval between the start of repeating cycles. If this is omitted, the command will be executed just <execution count> times.
<cycle count> is the optional number of times to run the cycles.
<command> is the command string that is being sent to the controller. The string is sent as is to the controller with the exception of placeholder and variable processing.
Both interval and cycle interval are expressed in seconds. However, adding the m or h suffix will provide values in minutes and hours respectively.
0,show ap active: will run the command "show ap active" once.
1;1,show ap active: will run the command "show ap active" just once, i.e. "one shot"
1m,show ap active: will run the command "show ap active" every minute.
1m;2,show ap active: will run the command "show ap active" twice spaced by one minute.
1m;2;1h,show ap active: will run the command "show ap active" twice spaced by one minute every hour.
1m;2;1h;3,show ap active: will run the command "show ap active" twice spaced by one minute every hour for three times.
...;use of the "--disable-fast-login" option should be added to tutorial.  ...
Same as Carlos, I had to use the "--disable-fast-login" option. Example:
java -jar AirRecorder-1.4.2-release.jar --disable-fast-login <controller IP>
I think use of the "--disable-fast-login" option should be added to tutorial.
How can we find the cloud activation key for Aruba switches?
We can use the following command to find the cloud activation key :
Aruba# show activate provision
Configuration and Status - Activate Provision Service
Activate Provision Service : Enabled
Activate Server Address : device.arubanetworks.com
Activation Key : LKMNOPAB
The above command applies to the following switches:
Aruba 2920 Switch Series—WB.16.02.0012 or later
Aruba 2930F Switch Series—WC.16.02.0012 or later
Aruba 2540 Switch Series—YC.16.02.0012 or later
...switch ? -> yes 2. Do you have DNS server configured on the switch ? -> yes 3. What is the...
I have the same problem with an 2530-24g.
1. Is the clock reflecting correct time on the switch ? -> yes
2. Do you have DNS server configured on the switch ? -> yes
3. What is the firmware running on the switch ? YA.16.04.0009
4. Attach the output for :
Keys: W=Warning I=Information M=Major D=Debug E=Error ---- Reverse event Log listing: Events Since Boot ---- I 12/18/17 11:34:11 04611 job: Job Scheduler enabled I 12/18/17 11:33:58 05101 amp-server: AMP server configuration is disabled due to first configuration. I 12/18/17 11:33:57 05226 activate: Successfully resolved the Activate server address device.arubanetworks.com to 126.96.36.199. I 01/01/90 01:00:45 05225 activate: Loading security certificates and synchronizing time with NTP. I 01/01/90 01:00:45 05224 activate: Zero-touch provisioning enabled; connecting to Aruba Activate server to provision system. I 01/01/90 01:00:45 03783 dhcp: DHCP server did not offer all the DNS parameters on Primary VLAN I 01/01/90 01:00:45 00025 ip: DEFAULT_VLAN: ip address 192.168.100.110/24 configured on vlan 1 I 01/01/90 01:00:45 05177 ip: Setting IP address 192.168.100.99 as default gateway. thank you, thomas
The tutorial describes the device profiling feature of ArubaOS. Not all wireless deployments are done via controller. Some also use model called local forwarding or based on instant AP's. In these situations it's important to have correct VLAN's assigned to switche ports where these AP's connect in order to deliver multiple services. Device profiling automatically detects Aruba AP's and push configured profile to port.
In this session, we will go through a step-by-step reference architecture guide in designing a high performance, highly available campus access, distribution and core infrastructure. We will cover unique features offered by HP switching platforms and review interoperability with other networking infrastructure.
ASE Link: Go to the solution
This solution is here to give the full set of commands needed to configure and enable VXLAN between ArubaOS Switches.
For now, it can only be used to create one Tunnel, and 1 Virtual-Network.
If you need more, please duplicate the related part of the configuration (Virtual-Network, Tunnel, and VXLAN mapping)
Minimum Software Version Required
16.xx version is required.
VXLAN is an encapsulation mechanism, also known as Network Virtualization, using MAC-in-UDP. It allows to easily create L2 networks (Overlay Network) over L3 (Underlay Network), using UDP Tunnels.
2 architectures can be implemented : Meshed Network and Hub and Spoke Network.
Several steps have to be done :
- Create a Virtual Network, also known as VNI, which will match the incoming traffic with the associated VXLAN.
- Create a VXLAN tunnel
- Associate the VLAN with the newly created tunnel. Each VLAN needs to have its own VN ID before being associated with a VXLAN Tunnel.
BGP EVPN and ENDP are not supported on ArubaOS-Switch.
Some other things need to be checked, and/or set, before implementing VXLAN :
- As VXLAN is an encapsulation mechanism (MAC-in-UDP), you may have to enable Jumbo Frames on the path between each VTEPs (Your Switches). You may also have to activate the Jumbo Frames on the VLAN, using the "vlan <Your_Underlay_VLAN> jumbo" command.
- VXLAN uses the UDP Port 4789 by default. For security reasons, if you need to use another UDP Port, you will have to use the "vxlan udp" command.
- To guarantee a high level of tunnel's availability, please set loopback interfaces on source and destination devices, and use them as tunnel's source and destination IPs.
This has been tested on Aruba 3810M and 5400R, with v3 modules.
5400R in v2 compatibility mode does not support VXLAN - You have to disable the "allow-v2-module" before using the vxlan commands.
No license required.
If you need more information, you can use the "Advanced Traffic Management Guide" of each compliant platform.
The routing enablement is not covered by this solution. If more information is needed to configure this, you can refer to the "Multicast and Routing" Guide of each compliant platform.
If you need to interconnect ArubaOS Switch with Comware devices through VXLAN, you can also refer to the "HPE_VXLAN_between_12900_and_5400R_TCG_v1.1_Mar2016.pdf" document.
ASE Link: Go to the solution
This solution will configure OpenFlow on an ArubaOS-Switch device, allowing the switch to connect to the VAN SDN Controller.
Minimum Software Version Required
This feature requires ArubaOS-Switch 15.18 or later, running on a 2920, 2930F, 3800, 3810, or 5400R switch. Targeted VAN SDN Controller version is 2.7.16.
Use this solution to configure OpenFlow to connect to the VAN SDN Controller. This solution will setup the OpenFlow configuration on the switch to use the optimal and recomended configuration.
Do not use this solution when multiple OpenFlow instances are configured on the switch. All VLANs that are desired to be participating in the VAN SDN Solution should be configured as member VLANs.
For switches, none required. For VAN SDN Controller, standard licensing applies.
ASE Link: Go to the solution
This solution will configure SNMPv3 credentials on a switch running ArubaOS-Switch (or the legacy ProVision OS).
MINIMUM SOFTWARE VERSION REQUIRED
Minimum version varies by switch model; should work on any ProCurve/ArubaOS-Switch device running 15.13 or newer.
This solution will configure SNMPv3 credentials, including user accounts, groups, and SNMP options.
Aruba 2530 running YA.16.01.0004