DASH config diffs [draft]

[mgheorghe]

C: SONiC.202506.0-dirty-20250822.160349
N: SONiC.internal-202506.133519486-bd145c36c6

diff1:
C: {"DASH_APPLIANCE_TABLE:appliance-1000": {"sip": "221.0.0.1", "vm_vni": "1000", "local_region_id": "100", "trusted_vnis": "100" }, "OP": "SET"},
N: {"DASH_APPLIANCE_TABLE:appliance-1000": {"sip": "221.0.0.1", "vm_vni": "1000"}, "OP": "SET"},
local_region_id
trusted_vnis

diff2:
C: {"DASH_ROUTING_TYPE_TABLE:direct": {"action_name": "action-1000", "action_type": "direct"}, "OP": "SET"},
N:
have not tried yet new action type

diff3:
C: "DASH_ROUTING_TYPE_TABLE:privatelink": [{"action_name": "action-1", "action_type": "4_to_6"}
N: "DASH_ROUTING_TYPE_TABLE:privatelink": [{"action_name": "action-1", "action_type": "4to6"}
action type with _ or without

diff4:
C: {"DASH_VNET_MAPPING_TABLE:vnet-1000:1.4.0.1": {"routing_type": "privatelink", "underlay_ip": "221.2.0.0", "mac_address": "00:1B:6E:00:00:01", "use_dst_vni": "true",
N: {"DASH_VNET_MAPPING_TABLE:vnet-2000:1.4.0.1": {"routing_type": "privatelink", "underlay_ip": "221.2.0.0",
mac_address
use_dst_vni

diff5:
C: {"DASH_VNET_MAPPING_TABLE:vnet-1000:1.1.0.1": {"routing_type": "vnet_encap", "underlay_ip": "221.0.0.1", "mac_address": "00:1A:C5:00:00:01", "use_dst_vni": "true"}, "OP": "SET"},
N: TBD

[KrisNey-MSFT]

hi @prabhataravind and @mzms - Issue has been opened regarding the Config diffs, for us to pursue. TY!

[prabhataravind]

hi @mgheorghe @KrisNey-MSFT could you create issues in sonic-buildimage repo? All other issues are created there and tagged with "smartswitch" label so it becomes easier to track.

[KrisNey-MSFT]

hi @mgheorghe @KrisNey-MSFT could you create issues in sonic-buildimage repo? All other issues are created there and tagged with "smartswitch" label so it becomes easier to track.

hi @mgheorghe - would you be able to file this in the sonic-buildimage repo?

[prabhataravind]

@mgheorghe @KrisNey-MSFT

diff1: local_region_id and trusted_vnis are supported on both vendors - see sonic-mgmt fnic appliance config that is run on both vendors (https://github.com/sonic-net/sonic-mgmt/blob/0edc511fa847a2adb4f99d1695b5d9bbb31df49a/tests/dash/configs/privatelink_config.py#L71)

diff2: For PL scenarios, the action_types are "4_to_6" and "staticencap". The other types were primarily for vnet-vnet

diff3: The first one (4_to_6) appears to be correct based on the code

diff4: mac_address and use_dst_vni are optional - see https://github.com/sonic-net/SONiC/blob/master/doc/dash/dash-sonic-hld.md#3211-vnet-mapping-table

diff5: This also doesn't appear to be related to the PL MVP 2.0 scenario.

Is the scope of testing limited to PL or are you trying to test vnet-vnet?

There are sample configs in:

1. https://github.com/sonic-net/SONiC/blob/master/doc/dash/dash-sonic-hld.md
2. sonic-mgmt config @ https://github.com/sonic-net/sonic-mgmt/blob/0edc511fa847a2adb4f99d1695b5d9bbb31df49a/tests/dash/configs/privatelink_config.py that is used for PL scenario testing on both vendors

[KrisNey-MSFT]

there may be a newer version of the dynamic 2025_06 image, so might need to keep on top of changes until officially released @mgheorghe for viz...

[KrisNey-MSFT]

For this, we do not need to create a local mapping - take offline w/AMD w/Senthil, Michael Aronovic, and Mircea

diff5:
C: {"DASH_VNET_MAPPING_TABLE:vnet-1000:1.1.0.1": {"routing_type": "vnet_encap", "underlay_ip": "221.0.0.1", "mac_address": "00:1A:C5:00:00:01", "use_dst_vni": "true"}, "OP": "SET"},
N: TBD

[KrisNey-MSFT]

hi @mgheorghe and @aronovic - is this one pretty much closed? Thank you, Kristina

[mgheorghe]

validated diff5 is not needed anymore, so we can remove it as a diff

diff5:
C: {"DASH_VNET_MAPPING_TABLE:vnet-1000:1.1.0.1": {"routing_type": "vnet_encap", "underlay_ip": "221.0.0.1", "mac_address": "00:1A:C5:00:00:01", "use_dst_vni": "true"}, "OP": "SET"},
N: TBD

[mgheorghe]

we will need new images on both vendors to validate diff 1 and 4