TE-17.1 modified TTL
This PR fixes the issues of expected TTL at egress for cluster as well as WAN originated traffic. When a packet enter a router, it outer header TTL will be reduced by one. Incase of decap scenario also the reduced TTL value of outer header will be copied to the inner header. With this PR the expected TTL value of a packet received at the destination OTG has be reduced by 1.
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
View this failed invocation of the CLA check for more information.
For the most up to date status, view the checks section at the bottom of the pull request.
Pull Request Functional Test Report for #4106 / e09dd61b9846abbfb186f6353e5acfc69f1fed1d
Virtual Devices
| Device | Test | Test Documentation | Job | Raw Log |
|---|---|---|---|---|
| Arista cEOS | TE-17.1: VRF selection policy driven TE |
|||
| Cisco 8000E | TE-17.1: VRF selection policy driven TE |
|||
| Cisco XRd | TE-17.1: VRF selection policy driven TE |
|||
| Juniper ncPTX | TE-17.1: VRF selection policy driven TE |
|||
| Nokia SR Linux | TE-17.1: VRF selection policy driven TE |
|||
| Openconfig Lemming | TE-17.1: VRF selection policy driven TE |
Hardware Devices
| Device | Test | Test Documentation | Raw Log |
|---|---|---|---|
| Arista 7808 | TE-17.1: VRF selection policy driven TE |
||
| Cisco 8808 | TE-17.1: VRF selection policy driven TE |
||
| Juniper PTX10008 | TE-17.1: VRF selection policy driven TE |
||
| Nokia 7250 IXR-10e | TE-17.1: VRF selection policy driven TE |
Hi @nkrishk , thank you for working on this! I think the PR might have been solved already by https://github.com/openconfig/featureprofiles/commit/42eb61873b161ff27d07f360c5576d94fa7a486c - could you please take a look , and if not - resolve the conflicts?
Hi @nkrishk , thank you for working on this! I think the PR might have been solved already by 42eb618 - could you please take a look , and if not - resolve the conflicts?
yes it is taken care already