Benjaman Tracker

Re: Internal routing

Benjaman — Mon, 23 Oct 2023 15:18:23 GMT

I second what @yusukehirata01 said above.

Re: Flow report is showing 2 different Route for the same Next Hop, Source and Destination IPs

Benjaman — Sun, 22 Oct 2023 03:58:13 GMT

Kindly check from "Remote Diagnostics" - "Flow Dump" to see what business rule this flow is actually taking. I suspect it might be hitting two types of business rules. One is the Application category(Rule defined just with Application) and the other could be the rule which is under the bottom pointing to "Internet" and might have been backhauled to the Hub.

Depending on the load of the edge, its model, traffic patterns, and the number of applications used, the edge also might be exhausting its application identification database due to which it is failing to hit the top rule.

If route 52.123.128.14 is learned from a specific remote branch, today there is no visibility to which branch it's going in the "Flows" tab. This should be an enhancement.

The Route types can either be "Branch to Branch", "Cloud via Gateway", "Branch to datacenter", or "Brach to backhaul" depending on the destination route.

If this is the only spoke that shows Branch to Branch, then there should not be a route 52.123.128.14 learned from any other branches. If there is not already then we need to check further on why it displays "Branch to Branch" instead of "Cloud via Gateway" as I expect it should hit the gateway route if the business rule with just application-defined matches.

Route table dump in "Remote Diagnostics" would help and also "Overlay Flow Control" would help from which branch this route is being initiated.

Probably this might need more eyes from a support stand point if you see any discrepancies. Please feel free to create a support ticket after you research a bit more.

Re: Flow report is showing 2 different Route for the same Next Hop, Source and Destination IPs

Benjaman — Sun, 22 Oct 2023 02:25:50 GMT

Hi @amirimran

Thank you for providing the screenshot. I think there are a few things to consider.

Firstly, if you see the route as "Branch to Branch" or "Branch to Backhaul" on the spoke side "Flows" tab, it is completely expected if

1. There is a business rule using just the "Application Name" and not the IP address in the destination IP field and

2. A business rule under the above indicating the destination as "Internet" and backhauling traffic to the Hub.

Reason is that VCE takes a few packets from the flows to read and identify the application name from the flow which involves a bit of time. During this process, as the application name for that flow is not yet determined, VCE sends the traffic out using the next best business rule.

So for a few flows, seeing "Branch to Backhaul" is expected since it's backhauling the traffic to the Hub, and for many more flows "Brach to Branch" should be seen since the subsequent flows start hitting the policy that has just the application name.

With respect to the Link Name not reflecting for a few flows, it's expected since for the flows that are being load-shared, it does not reflect the Interface or Link Name as it sends the traffic out of multiple links.

Coming to the original query on why you are unable to access the application -

1. Please check if it's expected that the public route i.e., in the Flow dump that you shared, the route towards 52.123.128.14 is expected to be learnt from a remote branch. If not, please stop advertising it at the source VCE.

If it's expected to be learnt from the remote branch, then you can take captures on the LAN side of both VCEs to check if the packets that are actually sent are reaching the other side.

2. Try configuring the business rule with IP address and play with it sending "Direct"/"Multipath"/"Backhaul" and observe the results.

If you feel that VCE is dropping the traffic, please feel free to engage support and take it forward as this would have confidential data of your customer which they might not want to be discussed in this forum.

Re: Flow report is showing 2 different Route for the same Next Hop, Source and Destination IPs

Benjaman — Sun, 22 Oct 2023 00:50:00 GMT

@amirimran

Can you help share the outputs that you are observing? Like screenshots etc.

Re: Velocloud Business Policy "Link State" Logic broken

Benjaman — Wed, 11 Oct 2023 06:09:11 GMT

@KLC_Engineer
From the symptoms, I think the set up is hitting the defect which is not fixed in 5.0.1.4 or 4.5.1.

The defect ID is #97152

This is fixed in 5.1.0.x, 4.5.2 and 4.3.1

Please feel free to check the release notes of those versions.

https://docs.vmware.com/en/VMware-SASE/5.1.0/rn/vmware-sase-510-release-notes/index.html

Re: VMware Velocloud Edge sizing Sizing

Benjaman — Wed, 11 Oct 2023 03:08:47 GMT

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

Benjaman — Wed, 11 Oct 2023 02:59:08 GMT

@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

Benjaman — Wed, 11 Oct 2023 02:56:16 GMT

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

Benjaman — Wed, 11 Oct 2023 02:53:51 GMT

Dear @KLC_Engineer , Was there a LINK DEAD event when the broadband was down?

Thank you.

Re: Two Questions about SD-WAN 5.2.0

Benjaman — Sat, 16 Sep 2023 14:22:31 GMT

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

Benjaman — Sat, 16 Sep 2023 13:54:38 GMT

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

Benjaman — Sat, 16 Sep 2023 13:41:41 GMT

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.