SD-WAN

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

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?

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

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. 

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?

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

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.

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. 

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?

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

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.

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. 

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?

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

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

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.

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. 

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?

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

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. 

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

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.

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. 

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?

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

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

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.

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. 

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?

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

I wasn't able to use the script, unfortunately I don't think it is maintained, it was 2 years old and I ran into a whole bunch of dependency issues even in the venv. My python has gotten a bit rusty over the years so I parked it for now. I was able to resolve it by issuing the commands:

disaster-recovery on

configuring : "system-bandwidth-contract mbits 500", saving the configuration and then go out of disaster-recovery. To my surprise after doing this the command disappears completely from the configuration. All solved now

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

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.

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. 

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?

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

Thanks for the tip on the system bandwidth contract @ 1mbps. 

I started to question where the throughput issues were as well. I had issues with the original deployment via full orchestration on legacy central on behalf of azure. I know everyone is really waiting for orchestration to be available in cnx before much can be done. 

Both my vpnc's came up as 1 mbps. I even started running iperf to the external interface and disabling routing intent to try to isolate a path issue. I felt as I missed something to create this much of a negative experience. Since I am in the process of porting over wan rules for shaping. I wanted to make sure it wasn't something I created in the ipsec-maps with tx rates, or wan scheduler.  

I will provide feedback when I get a resolution. I am not seeing any way to update this in legacy central. Setting a local override seems to reset itself upon reload.

-------------------------------------------

Original Message:
Sent: May 10, 2024 09:58 AM
From: mvanoverbeek
Subject: Virtual Gateway capped/unusable

I wasn't able to use the script, unfortunately I don't think it is maintained, it was 2 years old and I ran into a whole bunch of dependency issues even in the venv. My python has gotten a bit rusty over the years so I parked it for now. I was able to resolve it by issuing the commands:

disaster-recovery on

configuring : "system-bandwidth-contract mbits 500", saving the configuration and then go out of disaster-recovery. To my surprise after doing this the command disappears completely from the configuration. All solved now

------------------------------
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

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
------------------------------