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
I have a Aruba 600 controller, which act as a master.Now i want to install another controller in the same network. [for testing purpose]
My question is
1. does the 2nd controller import all configuraton from master?
2. I dont want to define it as local, if i dont is there any problem?
3. There is one dhcp server in the network, so i want to give the controller and ap [which i'm going to implement with 2nd controller] both static ip,
and in ap i think to define the 2nd controller as a master controller, so from where this ap will import configuration?
Controllers are different from Instant. In order to utilize the same configuration and be able to...Controllers are different from Instant. In order to utilize the same configuration and be able to terminate APs, you'll have to add it as a local. Your other option would be to take a backup and then restore but I would not put them on the same subnet.
It won't because these are not talking to each other , any config you put in place in either contro...It won't because these are not talking to each other , any config you put in place in either controller will not be share
To turn on adp on the test controller again use the same command but instead of disable use enable....To turn on adp on the test controller again use the same command but instead of disable use enable.
Don't turn it off in your production controller just on test controller
I have a Aruba 3600 controller.
there is two vlan.
vlan1= 172.16.0.0 network
vlan2= 172.18.0.0 network.
controller is on vlan 1 [controller ip =172.16.0.254]
from controller i am not able to ping any device on vlan2 & from any device in vlan2 i cant able to any device on vlan1 [controller also]
please tell me what i have to do?
i want that they can able to ping each other.
We are testing Aruba equipment at the moment and have connected 2 x 7240 controllers to a Master VM. The network that I have these connected to are our internal management network and not the AP termination network (different vlans).
The question is, does the switch ip network used for the communication between master vm and controllers have to be the same as the AP termination network?
The cluster has been configured and is connected at L2 no problems, but I am unfamiliar with how this works with the ap termination. There is no vrrp configuration so would I need to add one in the cluster that is on the ap management vlan?
Thanks in advance!
...-Mobility-Controllers/ta-p/282686": Just put one of the MD ip address as the LMS IP, then the APs...
Just put one of the MD ip address as the LMS IP, then the APs will automatically build tunnel to other MD as its backup. The IP doesnt have to be in the same VLAN, but AP must able to reach it.
A Hitless AP failover: When MDs are part of a cluster, APs that come up will connect to their LMS IP (i.e. one of the cluster members), called the Active AP Anchor Controller (or A-AAC). The AP builds a standby tunnel to a Standby AAC (or S-AAC) that is selected by the cluster leader. When the A-AAC goes down, the AP seamlessly fails over to the S-AAC. This is similar to how AP Fast Failover (HA) works in AOS 6.x.
- Yopianus Linga-
I've been struggling to setup a new Aruba 7030 in my school enviroment. I've spent the better part of two days on what I'm sure is going to amount to something trivial, but as of yet its not obvious to me.
Ultimately I want my controller on my Management VLAN (ex: VLAN-1), my APs on another (VLAN-2), and my users on their own VLAN (VLAN-3). My controller currently has GE0/0/0 connected to my switch, and planned to put this on a untagged VLAN1 port on my switch. GE0/0/4-7 I planned to create an LACP bond with VLAN2-VLAN4 ( I would *like* to have my SSID's on different VLANS to set different rules on my content filter ).
Please see the attached diagram. I have decided to start from scratch on a config, so I didn't post that. I am migrating from an Aruba Instant based system consisting of AP-105s.
If there is a better way, I'd love to learn.
With Spanning-Tree, it's finding a version that is supported across all of the network devices that...
With Spanning-Tree, it's finding a version that is supported across all of the network devices that need to speak it. MST is backwards compatible with RSTP, but does depend on some configuration to ensure that compatibility. At this point, my suggestion to disable STP on the 7030 was just to eliminate or identify STP as the problem source, in order to move forward with getting this working.
I have Aruba controllers 7010 (version 220.127.116.11) that gets rebooted (wlsxColdStart Detected),
From the Webgui, the logs show that the controller was down and back up,
From CLI, I noticed that the logs were showing (killing dogma and watchdog) before and after the reboot,
It doesn't really say what caused the reboot,
Is there some other ways to find out what cause the reboot?
...: This issue was observed in controllers running ArubaOS 18.104.22.168.
Bug id : 167418
Symptom: A master controller rebooted after DPI was disabled. The log file listed the reason for the event as Reboot Cause: Datapath timeout (SOS Assert) (Intent:cause:register 54:86:50:2). The fix ensures that the controller works as expected.
Scenario: This issue was observed in controllers running ArubaOS 22.214.171.124.
I have an issue with my wifi connection bandwith and i need to make a rule on my controller to indicate the user has the right just to just one connection .
I use authentication by AD.
From a colleague: " There is a “maximum concurrent session” parameter for local accounts...
From a colleague:
"There is a “maximum concurrent session” parameter for local accounts (when the controller is used as a RADIUS server, but with external authentication like AD, I don’t believe it is possible to enforce this."
If you have a Policy Engine like ClearPass, it would be possible to do it with radius accounting. Microsoft Radius servers do not have this capability.
I have a AP that is causing me trouble. The controller keeps requsting a reboot of a AP when I join it to the controller to be managed as a Campus AP. I have another Campus AP that the controller managers, and this one has no issues staying up.
I have factory reset the AP in question a couple of times, and get the same rebooting result when trying to convert to a controller managed device.
I have a controller Aruba 650 Release 126.96.36.199.
I need to change the netmask of the controller on interface vlan 1 from 255.255.255.0 to 255.255.252.0.
When I try to do it, I obtain the following error:
"Error occurred while executing CLI command :interface vlan 1 ip address 192.168.0.239 255.255.252.0:Error:IP Address Matches the master ip"
On web user interface, I see that Master IP and loopback interface are the same, so I assigned to the loopback interface an ip address on vlan 150.
But still I get the same error, when I try to change the netmask of vlan 1.
Any idea of why I'm getting this error?
@Michele wrote: I moved the loopback interface in another network and it doesn't work. ...
I moved the loopback interface in another network and it doesn't work.
I found this string in the running configuration:
"controller-ip vlan 1"
Could it be the reason because I can't change the netmask of vlan 1?
To be clear, setting a loopback interface allows you to state what ip address and VLAN will be the controller's ip address. Unfortunately setting a loopback interface consumes a second ip address on a VLAN that already has an ip address. Setting a loopback is an old way of setting the controller's ip address. "Controller-ip vlan xxx" should be used instead, because it does not consume an ip address. Controller-ip vlan xxx conflicts with a loopback and only one should be used. Changing the controller's ip address or vlan typically requires a reboot, because that is the official ip address that it uses to communicate with access points and external systems.
Long story short, just use controller-ip vlan xxx and remove the loopback (will probably require a reboot).
We are implementing wireless IP phones system, which uses SIP protocol, in the network.
I have so far enabled shaping policy(WMM Traffic Management Profile) for voice traffic for respective AP profile.
I have come across this setting in the Stateful Firewall page. It's about Stateful SIP Processing. Should I be enabling this checkbox or disabling this?
Will this affect the voice quality and performance?
does anyone know if you can set up a ipsec tunnel between two controllers. NOT a site-site but need to map a VLAN from head office to a controller network. I know you can do a GRE tunnel but that has problems across NATted boundaries.
ok thank you, just wanted to know how do you set up the IPSEC tunnel between two controllers?
ok thank you,
just wanted to know how do you set up the IPSEC tunnel between two controllers?
thanks Jonas, here's my thinking:- Site-site between controllers with the public IP addresses of...
here's my thinking:-
Site-site between controllers with the public IP addresses of the headquaters and DMZ as the destination ip.
GRE tunnel between the controller provate ip addresses.
how does this sound?
Hi Pete, You can setup a VPN tunnel between the controllers first and within that tunnel...
You can setup a VPN tunnel between the controllers first and within that tunnel you can create a L2 GRE tunnel to transport the vlan between the sites.
Jonas, tried out that solution works just fine thanks for your help. cheers pete
tried out that solution works just fine thanks for your help.