Updating the golden tcam configuration for Arista

[ram-mac]

The golden tcam configuration file for Arista has been change. b/476134024
Hence making changes

[gemini-code-assist]

Summary of Changes

Hello @ram-mac, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the golden TCAM configuration for Arista devices, reflecting recent changes in the golden configuration file. The modifications primarily involve expanding the supported packet types for hardware TCAM, specifically adding GUE MPLS decap for IPv4 and IPv6, and enhancing IPv6 traffic policy by incorporating a destination port key field. Additionally, new hardware counter features have been enabled to provide more granular monitoring capabilities.

Highlights

• TCAM Configuration Update: Added new GUE MPLS decap packet types for both IPv4 and IPv6 forwarding within the hardware TCAM configuration.
• IPv6 Traffic Policy Enhancement: Included 'dst-port' as a key field in the IPv6 traffic policy configuration, enhancing its filtering capabilities.
• Hardware Counter Features: Introduced several new hardware counter feature configurations, including those for GRE tunnels, traffic policies (in/out), IPv4 routes, and nexthops.

Changelog

• internal/cfgplugins/dut_initialize.go
  • Added 'packet ipv4 gue mpls ipv4 forwarding routed decap' and 'packet ipv4 gue mpls ipv6 forwarding routed decap' to the IPv4 hardware TCAM configuration.
  • Added 'packet ipv6 gue mpls ipv4 forwarding routed decap' and 'packet ipv6 gue mpls ipv6 forwarding routed decap' to the IPv6 hardware TCAM configuration.
  • Included 'dst-port' in the 'key field' list for the 'feature traffic-policy port ipv6' configuration.
  • Introduced new 'hardware counter feature' configurations for 'gre tunnel interface out', 'traffic-policy in', 'traffic-policy out', 'route ipv4', and 'nexthop'.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[OpenConfigBot]

Pull Request Functional Test Report for #5124 / 1ca9715

No tests identified for validation.

Help

[gemini-code-assist]

Code Review

This pull request updates the golden TCAM configuration for Arista devices within the aristaNGPRTcamProfile string. The changes include adding support for GUE/MPLS decap packets in QoS features, including dst-port in the key fields for IPv6 traffic policies, and enabling several hardware counters. The updates appear to be in line with the goal of evolving the device configuration. I have one suggestion to improve formatting consistency within the configuration string, aligning with the repository's guideline to maintain consistent code patterns.