1. Activate Advanced profile display by clicking on the user name in the top right-hand corner of the WEB GUI and then selecting Preferences.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/21cae8cc1d0c493eae64719af43adde7.png)
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/d38974b26c064f6d9f329055b11febce.png)
2. Under Configuration/AP Groups, select a group that contains site-to-site VPN connected CAPs. Click on Profiles on the right.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/1db4afccdf6c4b938a50a17b8d468872.png)
3. Click on AP, AP System. The AP System Profile used in this AP group will be displayed. Make a note of the profile name.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/a6b2f61bc4d54d85ab70563916e48760.png)
4. Repeat step 3 for each AP group with site-to-site VPN connected CAPs
5. Is the default profile used in each AP group? If yes, then the job is simple - we need just to clone the default profile, adjust MTU size and set the new profile in each AP group. If different profiles are used in the groups, it becomes more complicated. In this case, each profile must be cloned, customized and set in the corresponding group. We take this approach because different parameters may have been changed for different profiles. And we don't want configuration settings to be lost.
6. Go to the first AP group with site-to-site VPN connected CAPs, click Submit As at the bottom right and enter a name for the new AP system profile, e.g. ap-system.MTU1300. This will create a copy of the profile currently in use. In my example, the default profile is cloned.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/bbab06cf9d3d4743984b45aa3194170d.png)
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/5ad0303ab868479bbee904bc10e17dda.png)
Click again on AP, AP System. Select the newly created AP System Profile in the dropdown field.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/e35534b4ec104f9d8d8f0abc505d4c0b.png)
Scroll down and search for the SAP MTU field. Set the value to 1300.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/fa3f6d126d904863814910c4a90deb43.png)
Then click on Submit and then deploy the changes.
The first AP group is now set up. The AP now uses MTU size with 1300 bytes, the AP packets fit into the payload of the IPSec packets and are not fragmented.
7. Repeat step 6 for each AP group with site-to-site VPN connected CAPs. If the default ap system profile was used, you can simply replace it with the new profile in the remaining groups. If not, you have to clone the profiles as described in step 6. You can clone profiles with the same name only once and then replace them in the corresponding groups.
If you have never worked with profiles before, it is better to ask a local Aruba partner for assistance. The same applies to RAPs.
A CAP becomes a RAP when you mark it under Configuration/Acces Points, click on the "Provision" button and deploy it as a remote AP.
However, this is not enough for RAP operation, additional settings must be made. This has already been described by @Florian_Baaske in his blog.
------------------------------
Regards,
Waldemar
ACCX # 1377, ACEP, ACX - Network Security
If you find my answer useful, consider giving kudos and/or mark as solution
------------------------------
Original Message:
Sent: Jul 20, 2024 02:29 AM
From: JordanWifi
Subject: controller and a set of access points from mpls to site to site
I couldn't find it. Could you show me how to access it and also how to set up a remote AP
Original Message:
Sent: Jul 16, 2024 03:54 AM
From: lord
Subject: controller and a set of access points from mpls to site to site
As Herman wrote, the problem is the fragmentation. We had the same problem with a customer, the solution was to reduce the MTU size.
Go to the corresponding AP system profile and set the SAP MTU to 1300.
![](https://higherlogicdownload.s3.amazonaws.com/HPE/MessageImages/d13dcd7d95bb49efa8afaaad12c81e79.png)
------------------------------
Regards,
Waldemar
ACCX # 1377, ACEP, ACX - Network Security
If you find my answer useful, consider giving kudos and/or mark as solution
Original Message:
Sent: Jul 15, 2024 12:08 PM
From: Herman Robers
Subject: controller and a set of access points from mpls to site to site
That is a lot of questions, and moving to Aruba Instant or AOS10 may be a better solution. But the way you deploy and use your network is critical to understand in order to make the best decision. Your question could be answered, but probably will not result in the best solution without further understanding. This is where normally partners come in the picture as they can check your network and business, and map that to the optimal design.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 15, 2024 09:10 AM
From: JordanWifi
Subject: controller and a set of access points from mpls to site to site
how can i convert from compose Compuse Ap to remote ap ?and how i can make APs
work as controller when controller is disconnect?
![compus](https://higherlogicdownload.s3.amazonaws.com/HPE/UploadedImages/HVwVw50OTGGhHi74ENjg_controler-L.png)
Original Message:
Sent: Jul 15, 2024 08:04 AM
From: Herman Robers
Subject: controller and a set of access points from mpls to site to site
Running Campus APs with a controller over a WAN/VPN is not supported.
One difference between MPLS and a VPN is that most VPNs are configured between stateful firewalls. That means that out-of-state traffic (packets for which the firewall doesn't know an established connection) as well fragmented traffic is dropped. Some firewalls also handle/inspect IPSec traffic (udp/4500), but the traffic between AP and controller must be untouched. Make sure there is no processing/inspection on the traffic between AP and controller. The connection between AP and controller should support large MTU, low latency and high bandwidth. You probably broke one of those parameters; where it's hard to do all correct on VPN/WAN, and which is why it's unsupported.
What may help troubleshooting is to capture traffic on the port to your AP, and on the port to your gateway, then find traffic which is modified/fragmented/dropped. From there find out where that happens and remediate; which still doesn't make the solution supported, but it may work.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
Original Message:
Sent: Jul 13, 2024 02:55 AM
From: JordanWifi
Subject: controller and a set of access points from mpls to site to site
I have a controller and a set of access points located across multiple sites. Initially, there were no issues when the branches were connected to the main site via MPLS. However, after transitioning to site-to-site VPN, many problems arose: access points disconnecting, wireless networks not appearing, and sometimes access points remain offline for up to 8 hours before reconnecting.
How can I perform troubleshooting and identify the problem? Note that the VPN is stable and all other services are stable; only the controller and access points are affected. I have already updated the controller and access points, but the issue persists.