From 1d527a72b4bbe4ca22622fb1ac6107d70c70c071 Mon Sep 17 00:00:00 2001 From: Riff Date: Wed, 22 Nov 2023 11:45:06 -0800 Subject: [PATCH] [DASH] Fix incorrect IP in SONiC-DASH HLD VNET to VNET example. (#1515) [DASH] Fix incorrect IP in SONiC-DASH HLD VNET to VNET example --- doc/dash/dash-sonic-hld.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/dash/dash-sonic-hld.md b/doc/dash/dash-sonic-hld.md index 6eb6ef34ea..c7e10ff0fb 100644 --- a/doc/dash/dash-sonic-hld.md +++ b/doc/dash/dash-sonic-hld.md @@ -1242,7 +1242,7 @@ For the example configuration above, the following is a brief explanation of loo For the inbound direction, after Route/ACL lookup, pipeline shall use the "underlay_ip" as specified in the ENI table to VXLAN encapsulate the packet and VNI shall be the ```vm_vni``` specified in the APPLIANCE table - 5. Inbound packet destined to 10.1.2.5 with source PA 101.1.2.3 and VNI 45654 + 5. Inbound packet destined to 10.1.1.1 with source PA 101.1.2.3 and VNI 45654 a. After setting direction to inbound, the Route Rule table is looked up based on priority b. First Inbound rule gets hit as PR prefix and VNI key match c. PA validation is set to true and Vnet is given as Vnet1.