Wireless Access

Reply
Contributor II

Aruba VMC Mobility Controller 8.3 - time-out connection between diferents vlans ?

Greetings fellows AirHeads,

I am trying to understand what can I do to make a deployment work.

 

I am using vsphere and I have 2 VMC installed on it, one with arubaOS 8.1 and another one with 8.3(currently 8.2), my controller with 8.2 have the definitive licenses, they are using the same vswitch, vminics e vlan labels and network adapters.

 

I tested in another envirioment/network and the VMC 8.2 and 8.3 was able to connect to my AP 305, using different firmwares(8.3, 6.5 and etc)

 

But not the controller with the definitive licenses, for some reason after the AP is converted(I do see the logs) I only receive hello-timeout logs. I do see the firewall receiving the aruba-papi from the AP, but the controller is not responding, I can ping and do ther other network test, the firewall show them, but aruba papi the controller is not responding. I first started supect that the problems was with the firmwares of the AP and VMC, but is the test showed that is not them.

 

Then I discovered that using different vlans (my controllers are in diferents vlan than the APs and the computers), when changing the firmware using TFTP, I am receiving time-out too.

I think this is the clue that is something on it, how to further explore the interfaces of the controller maybe they are somehow disycronized from the vspheres settings ?

Remember, the other VMC is working just fine, they have the same firewall rules because they are in the same vlan but SSIDs configurations and other parameters are diferent.

Contributor II

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

Ok, updates !
The test were wrong, only with the 8.3 version that timeout is happening, with version 8.2 and 8.1 on the same controller the APs are connecting.

Aruba Employee

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

Are these standalone controllers, or is there a VMM acting as the mobility master with both of these controllers?


Charlie Clemmer
Aruba Customer Engineering
Contributor II

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

In both cases they are Standalone.

 

The controller with 8.3, when downgrad it to 8.2 it works, but when upgrade to 8.3 it stops working. The aruba AP is sending aruba-papi but the controller don't respond, this behavior doesn't happen in the previos version.

Not only with the aruba-papi, with the TFTP is the same.

 

 

 

Aruba Employee

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

To summarize, you have an AP-305 to test connectivity to the VMC. When the VMC runs AOS 8.1.x or 8.2.x the AP-305 boots up, but when the VMC is upgraded to AOS 8.3.0.0 the AP-305 can not connect. Is that correct? Where do the different VLANs in the title come in to affect the testing?


Charlie Clemmer
Aruba Customer Engineering
Contributor II

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

The controller is able to responding in both version when the AP is in the same VLAN/subnet of the controller.

The same case with the TFTP server( or how would I be able to downgrad it back to 8.2)

The problem only happen when they are in different vlans, and no, the problem is not the gateway(firewall paloalto) I can see the traffic passing, other protocols like icmp(ping) respoding from both directions and etc.

 

 

Aruba Employee

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

I'm unclear on what the problem description is.

 

Is the problem just that with 8.3, the AP can only contact the controller when it's on the same VLAN and not traversing the PAN firewall? When using 8.2.x or 8.1.x, the AP does work when separated by the firewall?


Charlie Clemmer
Aruba Customer Engineering
Contributor II

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

Its almost like that, but the problem is not about traversing the firewall.

The problem is with the version 8.3 and when the controller is in differents vlan then the AP or the TFTP server(a windows machine) the controller is nos respoding the aruba-papi and for some reason is not connecting with the tftp server, the logs is like the hello-timeout and time-out.

 

Yes, it works when the version is 8.2 and 8.1, with the same controller or another VMC on the same hypervsor/server and both have the same networks settings.

 

Aruba Employee

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

It would be helpful to diagram the network connectivity and where the devices are connected to the network. 


Charlie Clemmer
Aruba Customer Engineering
Contributor II

Re: Aruba VMC Mobility Controller - time-out connection between diferents vlans ?

Here, you can look at the attachment.

Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: