Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[dual-tor] add missing SAI attribte in order to create IPNIP tunnel (#…
…2503) - What I did add SAI_TUNNEL_ATTR_DECAP_TTL_MODE and SAI_TUNNEL_ATTR_DECAP_DSCP_MODE - Why I did it Need to pass additional SAI attrib. Align encap end decap params 1 SAI_TUNNEL_ATTR_DECAP_DSCP_MODE Problem: Long time ago this attribute was defined as “mandatory on create” in SAI API, but at some point it was changed to “optional”. But MLNX SAI implementation didn’t change it and still expects this attribute to be always provided on tunnel creation. SONiC “dual ToR” implementation, when it creates IP-in-IP tunnel, does not provide this attribute because it is “optional”. So we get SAI error for creating tunnel because as mentioned above MLNX SAI implementation still expects this attribute as “mandatory on create”. Need to always set this attribute in “Dual ToR orchagent” on IP-in-IP tunnel creation 2 SAI_TUNNEL_ATTR_DECAP_TTL_MODE Problem: Long time ago this attribute was defined as “mandatory on create” in SAI API, but at some point it was changed to “optional”. SONiC “dual ToR” implementation, when it creates IP-in-IP tunnel, does not provide this attribute because now it is “optional”. SAI team reported: "We only support pipe, which is not the default API value of uniform, so user must provide explicit pipe This has always been the ip in ip behavior and limitation, which is also documented in our RN" So it is MLNX SAI implementation limitation that we support only “pipe” and since default value for this attribute is “uniform” we need to set it explicitly. And in our case it is becomes “mandatory on create” attribute which must be set to “pipe” value. As a result of this limitation we should update SONiC “Dual ToR” code in order to pass this attribute on IP-in-IP tunnel creation. - How I verified it tunnel successfully created Signed-off-by: Andriy Yurkiv <ayurkiv@nvidia.com>
- Loading branch information