Ya we deployed everything Manually essentially(used terraform, but did manually to start out), and have had none of the bandwidth issues. We are incredibly happy with how everything works, and how easy everything is to deploy.
Just double checking that you created the system information in Central before deploying? I am sure you probably did as I don't think it will deploy without it, but double checking. One of the options says how large(how much bandwidth) the system will have.
Original Message:
Sent: May 08, 2024 09:22 AM
From: mvanoverbeek
Subject: Virtual Gateway capped/unusable
Thanks for sharing! That looks extremely useful! I wanted to tackle the Aruba API but pushed it off till now. I will review the code and see if I can play around with it.
------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
Original Message:
Sent: May 08, 2024 02:41 AM
From: CrispyFi
Subject: Virtual Gateway capped/unusable
I was troubleshooting the same issue for a customer in Azure, they had two VGWs connected via Hub Mesh.
I did a diff of the config and discovered that one of the VGWs was missing the command 'system-bandwidth-contract mbits 500'.
From what I understand, this command should get added automatically when the gateway was deployed.
In our case the deployment is a manual VGW deployment (as opposed to orchestrated).
Not sure if it is related to licensing being removed/re-assigned and if a simple reboot would have fixed it?
In any case, I was able to resolve the issue by pushing the command 'system-bandwidth-contract mbits 500' using the CaaS API.
https://github.com/michaelrosejr/arubacentralcaas
Original Message:
Sent: May 03, 2024 10:52 PM
From: mvanoverbeek
Subject: Virtual Gateway capped/unusable
Hi Ariyap,
Yes we spend a good 1,5 hours troubleshooting. I am waiting ing on hearing back. I let Aruba central configure it and we confirmed that we were unable to do anything with contracts in central on the UI. The TAC engineer said he rarely has any cases on the gateway on ESXi. Very strange I find that. I am determined to fix it and when I finally have it operational I will update the instructions on airheads
Have a nice weekend
Original Message:
Sent: 5/3/2024 7:49:00 PM
From: ariyap
Subject: RE: Virtual Gateway capped/unusable
so you are using vg500? anyway see what TAC advises, but i think yu need to rebuild your vgateway, as the system bandwidth contract should be 500 Mbps for a vg500 and so on.
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
Original Message:
Sent: May 03, 2024 08:02 AM
From: mvanoverbeek
Subject: Virtual Gateway capped/unusable
I am using AOS 10.4.1.1_89267, any other (higher) version will not register in Aruba Central, which is a completely all different option.
------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
Original Message:
Sent: May 02, 2024 09:36 PM
From: ariyap
Subject: Virtual Gateway capped/unusable
The system bandwidth contract should be 500 Mbps. if your vGateway is VG500. as you know you can get VGateways for 500Mbps/2Gbps/4Gbps
what Firmware version are you using on your vgateway?
------------------------------
If my post was useful accept solution and/or give kudos.
Any opinions expressed here are solely my own and not necessarily that of HPE or Aruba.
Original Message:
Sent: May 02, 2024 05:16 PM
From: mvanoverbeek
Subject: Virtual Gateway capped/unusable
I have a strange problem with my virtual gateway, although I opened a TAC Case I thought, let's throw it out here in parallel
Although I was initially happy that I was able to configure a Gateway through Aruba Central, it turns out it is actually pretty unusable
Yes, I can ping from a remote location, resources in my private network and even sluggishly log into a server, the performance is however extremely poor
I did an Iperf from the remote client to the server and got the results depicted below
An iperf test from the LAN interface on the Virtual gateway gives a similar result.
When I use an Ubuntu server on the same ESXi Host and subnet I get normal results (940 Mbps)
It appears that there is some kind of CAP on the Virtual Gateway, but I cannot recall reading anything about a bandwidth license I need to install. In the configuration I did find this command, but I cannot really find much about it's purpose: system system-bandwidth-contract mbits 1
Any suggestions are welcome, otherwise I will update the group on my progress
------------------------------
Martijn van Overbeek
Architect, Netcraftsmen a BlueAlly Company
------------------------------