"Branch Routed" is displayed an Monitor > Flows even though it does not use traffic bound to local connected / static / routed (underlay) destinations.
Article ID: 388080
Updated On:
Products
Issue/Introduction
It's possible that Monitor > Flows displays 'Branch Routed' in Route column even though the flow should be displayed as Cloud Via Gateway, Internet Via Direct Breakout, etc.
*The definition of Branch Routed can be found in the following document. This article describes the reason for displaying 'Branch Routed' if you don't use traffic bound to local connected / static / routed (underlay) destinations.
Environment
Velocloud SDWAN, VMware SDWAN, Business policy, Monitor > Flows
Resolution
If the traffic is blocked by Stateful Firewall, Monitor > Flows displays as 'Branch Routed'. Also if a TCP session is not established, the flow will not be displayed in Monitor > Flows.
If "Branch Routed" is displayed, it is possible that Internet traffic is being blocked by the Stateful Firewall because the TCP flow was removed from the Stateful Firewall session table after the Established TCP Flow Timeout expired.
The Established TCP Flow Timeout is configured in the Configure > Edges > Firewall > Stateful Firewall section. The default is 7440 seconds.
Feedback
