Skip to content

[Sonic-DASH] Dash Tunnel and FNIC changes#1911

Merged
prsunny merged 11 commits intomasterfrom
prsunny-dash_tunnel
Mar 11, 2025
Merged

[Sonic-DASH] Dash Tunnel and FNIC changes#1911
prsunny merged 11 commits intomasterfrom
prsunny-dash_tunnel

Conversation

@prsunny
Copy link
Copy Markdown
Contributor

@prsunny prsunny commented Feb 6, 2025

Updated to rev 2.4 for:

  1. Dash Tunnel behavior
  2. PA validation updates
  3. Switch attributes

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@prsunny
Copy link
Copy Markdown
Contributor Author

prsunny commented Feb 6, 2025

@prsunny
Copy link
Copy Markdown
Contributor Author

prsunny commented Feb 6, 2025

@KrisNey-MSFT

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@r12f r12f self-requested a review February 6, 2025 04:34
endpoints = list of addresses for ecmp tunnel
encap_type = vxlan or nvgre
vni = vni value for encap
vni = vni value for encap, create only attribute
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we mention create only attribute for encap_type as well ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed


For single endpoint, implmentation shall simply create a sai_dash_tunnel object with ```SAI_DASH_TUNNEL_ATTR_DIP=endpoint IP``` and ```SAI_DASH_TUNNEL_ATTR_MAX_MEMBER_SIZE=1```

For ECMP, implementation shall create ```sai_dash_tunnel_member``` and ```sai_dash_tunnel_next_hop``` with appropriate ```SAI_DASH_TUNNEL_ATTR_MAX_MEMBER_SIZE```
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please mention that though members can be updated, at any point the number of members cannot exceed the count provided at Dash tunnel create

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

addressed

- Telemetry and Monitoring
- Private Link
- Private Link NSG
- Express Route GW Bypass
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we have a config example for express route gw bypass ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will add as a next iteration (another PR)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added an example

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

"addresses": {{list of addresses}}
"encap_type": {{encap type}}
"vni": {{vni}}
"region_id": {{local region id}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Region ID is already added to the APPLIANCE table. This is the wrong deprecated Routing Appliance table

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Prince, the routing appliance table is not the appliance table.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for catching. addressed

"sip": {{ip_address}}
"vm_vni": {{vni}}
"local_region_id": {{region_id}}
"outbound_direction_lookup": {{dst_mac/src_mac}}
Copy link
Copy Markdown
Contributor

@mukeshmv mukeshmv Feb 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we still need this attribute if we have Floating NIC mode ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, if there is fnic mode disabled and need to change the lookup attribute. Basically, aligning with SAI model

Copy link
Copy Markdown
Contributor

@mukeshmv mukeshmv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

couple more comments

"addresses": {{list of addresses}}
"encap_type": {{encap type}}
"vni": {{vni}}
"region_id": {{local region id}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Prince, the routing appliance table is not the appliance table.

"sip": {{ip_address}}
"vm_vni": {{vni}}
"local_region_id": {{region_id}}
"outbound_direction_lookup": {{dst_mac/src_mac}}
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have a vni table? The will be multiple VNIs needing this.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have a VNI table currently.

DASH_PA_VALIDATION_TABLE is used only for additional PA validation. PA prefix can be either IPV4 or IPV6. Used for fastpath or other explicit PA validation cases

For more scale numbers, please refer to the [doc](https://github.com/sonic-net/DASH/blob/main/documentation/express-route-service/express-route-gateway-bypass.md)
Expected max number of 4K PA_VALIDATION entries. For more scale numbers, please refer to the [doc](https://github.com/sonic-net/DASH/blob/main/documentation/express-route-service/express-route-gateway-bypass.md)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe better to mention this in scaling requirements too, if missed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or simply move to there, in case inconsistent in future.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added to scale section and removed from here

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

endpoints = list of addresses for ecmp tunnel
encap_type = vxlan or nvgre
vni = vni value for encap
encap_type = vxlan or nvgre, create only attribute
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the encap_type can we add an explicit definishion of what is expected return packet?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a statement

@mssonicbld
Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines
Copy link
Copy Markdown

No pipelines are associated with this pull request.

@prsunny prsunny requested a review from mukeshmv February 12, 2025 03:17
@prsunny
Copy link
Copy Markdown
Contributor Author

prsunny commented Feb 12, 2025

@mzms, please review the expected dash config section for er gw

Copy link
Copy Markdown
Contributor

@prabhataravind prabhataravind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@prsunny prsunny merged commit 6f524f2 into master Mar 11, 2025
1 check passed
@mzms
Copy link
Copy Markdown

mzms commented Mar 12, 2025

looks good

prabhataravind added a commit to prabhataravind/sonic-swss that referenced this pull request Mar 26, 2025
 * If no value is specified, use a default value of SAI_DASH_ENI_MAC_OVERRIDE_TYPE_SRC_MAC, else use the specified value.

 Ref: sonic-net/SONiC#1911

Signed-off-by: Prabhat Aravind <[email protected]>
prabhataravind added a commit to prabhataravind/sonic-swss that referenced this pull request Mar 28, 2025
 * If no value is specified, use a default value of SAI_DASH_ENI_MAC_OVERRIDE_TYPE_SRC_MAC, else use the specified value.

 Ref: sonic-net/SONiC#1911

Signed-off-by: Prabhat Aravind <[email protected]>
prsunny pushed a commit to sonic-net/sonic-swss that referenced this pull request Mar 31, 2025
* Handle outbound_direction_lookup for DASH_APPLIANCE_TABLE
 * If no value is specified, use a default value of SAI_DASH_ENI_MAC_OVERRIDE_TYPE_SRC_MAC, else use the specified value.

 Ref: sonic-net/SONiC#1911
prabhataravind added a commit to prabhataravind/sonic-swss that referenced this pull request Apr 5, 2025
…3571)

* Handle outbound_direction_lookup for DASH_APPLIANCE_TABLE
 * If no value is specified, use a default value of SAI_DASH_ENI_MAC_OVERRIDE_TYPE_SRC_MAC, else use the specified value.

 Ref: sonic-net/SONiC#1911
r12f pushed a commit to sonic-net/DASH that referenced this pull request Apr 17, 2025
Referring to sonic-net/SONiC#1911 and
#665, to support FNIC pipeline,
this PR adds the followings:
- ENI mode VM, FNIC
- ENI drop counter `eni_trusted_vni_entry_miss_drop`
- Action `set_inbound_direction` is not defaultonly at table
`direction_lookup`
- table `global_trusted_vni` and `eni_trusted_vni`

---------

Signed-off-by: Junhua Zhai <[email protected]>
theasianpianist added a commit to sonic-net/sonic-dash-api that referenced this pull request Apr 18, 2025
As per sonic-net/SONiC#1911

---------

Signed-off-by: Lawrence Lee <[email protected]>
vkjammala-arista pushed a commit to vkjammala-arista/SONiC that referenced this pull request Jul 9, 2025
* Dash tunnel and FNIC changes
* Updated to rev 2.4 for:

Dash Tunnel behavior
PA validation updates
Switch attributes
prsunny pushed a commit to sonic-net/sonic-swss that referenced this pull request Jul 11, 2025
*[DASH] Support trusted VNIs for appliance and ENI objects (#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911
mssonicbld added a commit to mssonicbld/sonic-swss.msft that referenced this pull request Jul 16, 2025
<!--
Please make sure you have read and understood the contribution guildlines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

1. Make sure your commit includes a signature generted with `git commit -s`
2. Make sure your commit title follows the correct format: [component]: description
3. Make sure your commit message contains enough details about the change and related tests
4. Make sure your pull request adds related reviewers, asignees, labels

Please also provide the following information in this pull request:
-->

**What I did**
- Program trusted VNI info to SAI layer for appliance and ENI objects when available

**Why I did it**
As per sonic-net/SONiC#1911

**How I verified it**
Run the unit tests

**Details if related**
mssonicbld added a commit to Azure/sonic-swss.msft that referenced this pull request Jul 16, 2025
<!--
Please make sure you have read and understood the contribution guildlines:
https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

1. Make sure your commit includes a signature generted with `git commit -s`
2. Make sure your commit title follows the correct format: [component]: description
3. Make sure your commit message contains enough details about the change and related tests
4. Make sure your pull request adds related reviewers, asignees, labels

Please also provide the following information in this pull request:
-->

**What I did**
- Program trusted VNI info to SAI layer for appliance and ENI objects when available

**Why I did it**
As per sonic-net/SONiC#1911

**How I verified it**
Run the unit tests

**Details if related**
bobby-nexthop pushed a commit to bobby-nexthop/sonic-swss that referenced this pull request Jul 24, 2025
…3728)

*[DASH] Support trusted VNIs for appliance and ENI objects (sonic-net#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911
vivekrnv pushed a commit to vivekrnv/sonic-swss that referenced this pull request Aug 8, 2025
…3728)

*[DASH] Support trusted VNIs for appliance and ENI objects (sonic-net#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911
Janetxxx pushed a commit to Janetxxx/sonic-swss that referenced this pull request Nov 10, 2025
…3571)

* Handle outbound_direction_lookup for DASH_APPLIANCE_TABLE
 * If no value is specified, use a default value of SAI_DASH_ENI_MAC_OVERRIDE_TYPE_SRC_MAC, else use the specified value.

 Ref: sonic-net/SONiC#1911
Janetxxx pushed a commit to Janetxxx/sonic-swss that referenced this pull request Nov 10, 2025
…3728)

*[DASH] Support trusted VNIs for appliance and ENI objects (sonic-net#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911
balanokia pushed a commit to balanokia/sonic-swss that referenced this pull request Nov 17, 2025
…3728)

*[DASH] Support trusted VNIs for appliance and ENI objects (sonic-net#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911
theasianpianist added a commit to theasianpianist/sonic-swss that referenced this pull request Feb 4, 2026
…3728)

*[DASH] Support trusted VNIs for appliance and ENI objects (sonic-net#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911

Signed-off-by: Lawrence Lee <[email protected]>
baorliu pushed a commit to baorliu/sonic-swss that referenced this pull request Feb 23, 2026
…3571)

* Handle outbound_direction_lookup for DASH_APPLIANCE_TABLE
 * If no value is specified, use a default value of SAI_DASH_ENI_MAC_OVERRIDE_TYPE_SRC_MAC, else use the specified value.

 Ref: sonic-net/SONiC#1911

Signed-off-by: Baorong Liu <[email protected]>
baorliu pushed a commit to baorliu/sonic-swss that referenced this pull request Feb 23, 2026
…3728)

*[DASH] Support trusted VNIs for appliance and ENI objects (sonic-net#3728)
What I did
Program trusted VNI info to SAI layer for appliance and ENI objects when available
Why I did it
As per sonic-net/SONiC#1911

Signed-off-by: Baorong Liu <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants