All Posts

Re: VMware Velocloud Edge sizing Sizing

by VMware Employee in VeloCloud Discussions
‎10-10-2023 08:08 PM
‎10-10-2023 08:08 PM
VMware Solutions Architech would help you. As per my experience, I have seen customers using Edge 680 as the Hub for such set ups.  You may either go with a single Edge 680 or can deploy two Edge 6... See more...
VMware Solutions Architech would help you. As per my experience, I have seen customers using Edge 680 as the Hub for such set ups.  You may either go with a single Edge 680 or can deploy two Edge 680s in cluster. Thank you.

Re: What is the difference between following Events "Edge Interface Down" and "Link D

by VMware Employee in VeloCloud Discussions
‎10-10-2023 07:59 PM
1 Kudo
‎10-10-2023 07:59 PM
1 Kudo
@cblavend , As @khirom stated, the "Edge Interface Down" event would be triggered when the interface goes down physically. However, the "LINK DEAD" event would be triggered only on "WAN Overlay" ena... See more...
@cblavend , As @khirom stated, the "Edge Interface Down" event would be triggered when the interface goes down physically. However, the "LINK DEAD" event would be triggered only on "WAN Overlay" enabled interfaces when ALL the paths(not a single path should be alive) on that interface go down.

Re: DHCP option 121

by VMware Employee in VeloCloud Discussions
‎10-10-2023 07:56 PM
‎10-10-2023 07:56 PM
Hi @TalalTayyaroğlu This is not supported yet and no ETA on when this would be supported.

Re: Velocloud Business Policy "Link State" Logic broken

by VMware Employee in VeloCloud Discussions
‎10-10-2023 07:53 PM
‎10-10-2023 07:53 PM
Dear @KLC_Engineer , Was there a LINK DEAD event when the broadband was down? Thank you.

Re: Velocloud Business Policy "Link State" Logic broken

by Contributor in VeloCloud Discussions
‎10-10-2023 12:49 PM
‎10-10-2023 12:49 PM
That's somewhat amusing I think the legitimate way of doing that would be to make the BP rules for that traffic "Mandatory Wired" instead, since that is how it's supposed to function. VMware... See more...
That's somewhat amusing I think the legitimate way of doing that would be to make the BP rules for that traffic "Mandatory Wired" instead, since that is how it's supposed to function. VMware has confirmed that this issue is not fixed in 5.0.1.4, and advised it will be resolved in an upcoming release.

Re: Velocloud Business Policy "Link State" Logic broken

by Enthusiast in VeloCloud Discussions
‎10-10-2023 12:28 PM
‎10-10-2023 12:28 PM
Good day @KLC_Engineer ,   Thanks for the great information. I did not test this with the diagnostic tools, but we literally used this to block the backup traffic for a customer who is not paying ... See more...
Good day @KLC_Engineer ,   Thanks for the great information. I did not test this with the diagnostic tools, but we literally used this to block the backup traffic for a customer who is not paying for their backup link. So, I know it works because they started complaining.

Re: Velocloud Business Policy "Link State" Logic broken

by Contributor in VeloCloud Discussions
‎10-10-2023 12:24 PM
‎10-10-2023 12:24 PM
No, Our 510 edges are on 4.5.1, but we are currently upgrading them to 4.5.2 since I confirmed the problem is resolved there. We were able to reproduce this issue in 5.0.1.4 by making a business pol... See more...
No, Our 510 edges are on 4.5.1, but we are currently upgrading them to 4.5.2 since I confirmed the problem is resolved there. We were able to reproduce this issue in 5.0.1.4 by making a business policy rule for some destinations set to "Available Wired" and manually setting the active link to "Public Wireless". We found after doing this, we could not reach any destinations from a host connected through the edge in the Segment / VLAN applicable to that business policy. Keep in mind that testing from the edge directly via the remote diagnostics page (Ping Test) will not reproduce this issue, since the remote diag tools do not flow through the business policy logic of the control plane.

DHCP option 121

by Enthusiast in VeloCloud Discussions
‎10-10-2023 12:23 PM
‎10-10-2023 12:23 PM
Good day, I am trying to configure DHCP option 121. I know it is not officially supported on the Edge (I asked tech support). I tried to do something we have done with pfSense: use the "custom" set... See more...
Good day, I am trying to configure DHCP option 121. I know it is not officially supported on the Edge (I asked tech support). I tried to do something we have done with pfSense: use the "custom" setting and force it to mimic Option 121. However, in Edge, it specifically forbids me from doing so as can be seen in the attached photo. Anyone had some luck with this before?

Re: Velocloud Business Policy "Link State" Logic broken

by Enthusiast in VeloCloud Discussions
‎10-10-2023 12:14 PM
‎10-10-2023 12:14 PM
Good day @KLC_Engineer  I am using 510 with version 5.0.1.4 and we are not experiencing this issue. Are your edges on 5.2.0?

Re: What is the difference between following Events "Edge Interface Down" and "Link D

by Enthusiast in VeloCloud Discussions
‎10-10-2023 12:06 PM
1 Kudo
‎10-10-2023 12:06 PM
1 Kudo
Hello @khirom ,   What is astonishing is the fact that VMware has yet to publish a document describing the series of messages we see in the Events tab. I know for sure that other vendors (Cisco fo... See more...
Hello @khirom ,   What is astonishing is the fact that VMware has yet to publish a document describing the series of messages we see in the Events tab. I know for sure that other vendors (Cisco for example) provide extensive and well prepared documents that covers every single parameter in detail

Re: VPN to Non-SD-WAN destination (NSD) directly from Edge?

by Enthusiast in VeloCloud Discussions
‎10-10-2023 12:04 PM
‎10-10-2023 12:04 PM
Hello @khirom  After the latest Orchestrator update, I can no longer access the Legacy Orchestrator since the button to access it has been removed. Also since VMware are shifting their focus on the... See more...
Hello @khirom  After the latest Orchestrator update, I can no longer access the Legacy Orchestrator since the button to access it has been removed. Also since VMware are shifting their focus on the new UI, it would be better to learn to use it. I have been using it solely since we migrated to this platform

Re: VMware Velocloud Edge sizing Sizing

by Enthusiast in VeloCloud Discussions
‎10-10-2023 12:00 PM
‎10-10-2023 12:00 PM
Hello, I would highly suggest you talk to your VMware partner/reseller. Their presales engineers will have much more reliable answer than any of us here. Note that this is a new product, with not m... See more...
Hello, I would highly suggest you talk to your VMware partner/reseller. Their presales engineers will have much more reliable answer than any of us here. Note that this is a new product, with not much information circulating on the web.

VMware Velocloud Edge sizing Sizing

by Contributor in VeloCloud Discussions
‎10-03-2023 08:01 AM
‎10-03-2023 08:01 AM
Hello, What Edge size should I use, a VCE-3800 or a VCE-680, for a VCE-HA hub.  I have a network (Hub-Spoke) with 150 branch sites, all of them with 1 Internet connection  25/15Mbps + LTE failover. ... See more...
Hello, What Edge size should I use, a VCE-3800 or a VCE-680, for a VCE-HA hub.  I have a network (Hub-Spoke) with 150 branch sites, all of them with 1 Internet connection  25/15Mbps + LTE failover. The Hub has 2 Internet cnxs ( 500Mbps and 200Mbps). The number of tunnels that the hub will have to support is  150 (sites) * 2 ( HUB WAN connections) = 300 tunnels +  4 tunnels to the SD-WAN gateways.   The VCE680 has a 800 Tunnel capacity and an IMIX of 2G, so in paper, a VCE680 seems a good choice, however I wonder if  I may run into pereformance problems eventually. the VCE300 seems a bit of a overkill but for sure it will work.  Any advice will be much appreciated. 

Re: VPN to Non-SD-WAN destination (NSD) directly from Edge?

by Enthusiast in VeloCloud Discussions
‎10-03-2023 02:11 AM
‎10-03-2023 02:11 AM
Sorry, I wrote in the wrong thread.I leave the following as is. This may not be correct. It may be better to try the NSD via Gateway settings in the old UI instead of the new UI. The parameters ... See more...
Sorry, I wrote in the wrong thread.I leave the following as is. This may not be correct. It may be better to try the NSD via Gateway settings in the old UI instead of the new UI. The parameters available in the new UI and the old UI are different. Here is what I consider to be a good procedure 1. Confirm VPN establishment with the parameters available in the old UI. 2. After confirming, adjust the parameters to the stronger cryptographic strength in the new UI. If the old UI is not available, contact support and they may be able to enable it.

Re: What is the difference between following Events "Edge Interface Down" and "Link D

by Enthusiast in VeloCloud Discussions
‎10-02-2023 04:58 PM
‎10-02-2023 04:58 PM
Hi, I think "Edge Interface Down" is physical NIC down and "Link Dead" is WAN Setting = DMPO Tunnel down. "Link Dead" description appears when you hover your mouse over the information icon on the ... See more...
Hi, I think "Edge Interface Down" is physical NIC down and "Link Dead" is WAN Setting = DMPO Tunnel down. "Link Dead" description appears when you hover your mouse over the information icon on the alert settings.

What is the difference between following Events "Edge Interface Down" and "Link Dead".

by Contributor in VeloCloud Discussions
‎09-29-2023 08:30 AM
‎09-29-2023 08:30 AM
I see Events for Edge Interface Down  and Link Dead.  They sound the same is there a difference. I couldn't find any documentation about it.

Velocloud Business Policy "Link State" Logic broken

by Contributor in VeloCloud Discussions
‎09-25-2023 04:43 PM
‎09-25-2023 04:43 PM
I recently discovered the Business Policies we have configured in the Velocloud Orchestrator for our Edges isn't working properly when defining "Available Wired" as the link preference. Normally, th... See more...
I recently discovered the Business Policies we have configured in the Velocloud Orchestrator for our Edges isn't working properly when defining "Available Wired" as the link preference. Normally, this option steers the applicable traffic to a Wireless link (backup in our case) when a Wired link is not available. However, I discovered this option is acting as "Mandatory Wired" - where the Velocloud edge will not send traffic over a wireless link under any circumstances. We are currently deploying a new Voip solution, and the Voice team made us aware that when a location was temporarily operating on a wireless connection after a broadband failure while using an edge 510, none of their phones could register. We ultimately discovered that relabeling the Wireless link to "Wired" immediately resolved the problem and phones could register again. We also duplicated this behavior by relabeling a Wired (Comcast) link as Wireless, and observed the traffic then failing. This problem surfaced in past software versions (and was fixed) before, but appears it has resurfaced. Vmware advised this is a known bug, and was resolved in version 5.0.1.4, however I have confirmed that is not the case - the bug is still present and demonstrable in this latest software version. I just wanted to post this here in case anyone is unaware of this bug and has certain traffic flows failing over a wireless link. Our vendor has an open case with Vmware for this issue. I find it curious that I don't see any other reports of this problem anywhere. Anyone else having this experience?

Re: Two Questions about SD-WAN 5.2.0

by VMware Employee in VeloCloud Discussions
‎09-16-2023 07:22 AM
‎09-16-2023 07:22 AM
First issue is a defect in 5.2 https://docs.vmware.com/en/VMware-SASE/5.2.0/rn/vmware-sase-520-release-notes/index.html Defect ID #123619

Re: Edge Serial number for Activation

by VMware Employee in VeloCloud Discussions
‎09-16-2023 06:54 AM
2 Kudos
‎09-16-2023 06:54 AM
2 Kudos
The hardware models like 6X0 or 3X00 are manufactured by Dell. So it would not be mandatory to have the serial number start with VC. If the hardware is manufactured by Velocloud Networks, we expect ... See more...
The hardware models like 6X0 or 3X00 are manufactured by Dell. So it would not be mandatory to have the serial number start with VC. If the hardware is manufactured by Velocloud Networks, we expect to see the serial number starting with "VC" I have seen the WiFi models(Velocloud Networks manufactured) that have not been activated yet broadcast the WiFi SSID velocloud-123 where 123 are the last three digits of the serial. For Dell manufactured, I have seen the devices broadcast just the serial number(7-digit). Hope this helps.

Re: Support Bundle

by VMware Employee in VeloCloud Discussions
‎09-16-2023 06:41 AM
1 Kudo
‎09-16-2023 06:41 AM
1 Kudo
Enterprise users do not have access to view the bundle however they can generate the diagnostic bundle using the shortcut keys. Partner and Operator users have access to download the bundles.  If t... See more...
Enterprise users do not have access to view the bundle however they can generate the diagnostic bundle using the shortcut keys. Partner and Operator users have access to download the bundles.  If the "Superuser" role is at the enterprise level, then this is expected.