[Sonic-DASH] Dash Tunnel and FNIC changes#1911
Conversation
|
/azp run |
|
No pipelines are associated with this pull request. |
|
@theasianpianist , @mukeshmv , @prabhataravind , @kperumalbfn , @r12f, @oleksandrivantsiv, @marian-pritsak for viz |
|
/azp run |
|
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 | ||
| vni = vni value for encap, create only attribute |
There was a problem hiding this comment.
should we mention create only attribute for encap_type as well ?
doc/dash/dash-sonic-hld.md
Outdated
|
|
||
| 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``` |
There was a problem hiding this comment.
Please mention that though members can be updated, at any point the number of members cannot exceed the count provided at Dash tunnel create
| - Telemetry and Monitoring | ||
| - Private Link | ||
| - Private Link NSG | ||
| - Express Route GW Bypass |
There was a problem hiding this comment.
can we have a config example for express route gw bypass ?
There was a problem hiding this comment.
Will add as a next iteration (another PR)
|
/azp run |
|
No pipelines are associated with this pull request. |
doc/dash/dash-sonic-hld.md
Outdated
| "addresses": {{list of addresses}} | ||
| "encap_type": {{encap type}} | ||
| "vni": {{vni}} | ||
| "region_id": {{local region id}} |
There was a problem hiding this comment.
Region ID is already added to the APPLIANCE table. This is the wrong deprecated Routing Appliance table
There was a problem hiding this comment.
Yes. Prince, the routing appliance table is not the appliance table.
There was a problem hiding this comment.
Thanks for catching. addressed
doc/dash/dash-sonic-hld.md
Outdated
| "sip": {{ip_address}} | ||
| "vm_vni": {{vni}} | ||
| "local_region_id": {{region_id}} | ||
| "outbound_direction_lookup": {{dst_mac/src_mac}} |
There was a problem hiding this comment.
do we still need this attribute if we have Floating NIC mode ?
There was a problem hiding this comment.
Yes, if there is fnic mode disabled and need to change the lookup attribute. Basically, aligning with SAI model
doc/dash/dash-sonic-hld.md
Outdated
| "addresses": {{list of addresses}} | ||
| "encap_type": {{encap type}} | ||
| "vni": {{vni}} | ||
| "region_id": {{local region id}} |
There was a problem hiding this comment.
Yes. Prince, the routing appliance table is not the appliance table.
doc/dash/dash-sonic-hld.md
Outdated
| "sip": {{ip_address}} | ||
| "vm_vni": {{vni}} | ||
| "local_region_id": {{region_id}} | ||
| "outbound_direction_lookup": {{dst_mac/src_mac}} |
There was a problem hiding this comment.
Do we have a vni table? The will be multiple VNIs needing this.
There was a problem hiding this comment.
We don't have a VNI table currently.
doc/dash/dash-sonic-hld.md
Outdated
| 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) |
There was a problem hiding this comment.
Maybe better to mention this in scaling requirements too, if missed.
There was a problem hiding this comment.
Or simply move to there, in case inconsistent in future.
There was a problem hiding this comment.
added to scale section and removed from here
|
/azp run |
|
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 |
There was a problem hiding this comment.
For the encap_type can we add an explicit definishion of what is expected return packet?
|
/azp run |
|
No pipelines are associated with this pull request. |
|
@mzms, please review the expected dash config section for er gw |
|
looks good |
* 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]>
* 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]>
* 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
…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
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]>
As per sonic-net/SONiC#1911 --------- Signed-off-by: Lawrence Lee <[email protected]>
* Dash tunnel and FNIC changes * Updated to rev 2.4 for: Dash Tunnel behavior PA validation updates Switch attributes
*[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
<!-- 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**
<!-- 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**
…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
…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
…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
…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
…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
…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]>
…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]>
…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]>
Updated to rev 2.4 for: