Skip to content

Add AFT-4.1 README: AFT MPLS Label Entry Counters - #6122

Open
mithunaditya-gnt wants to merge 1 commit into
openconfig:mainfrom
mithunaditya-gnt:aft-4-1-mpls-label-counters-readme
Open

mithunaditya-gnt wants to merge 1 commit into
openconfig:mainfrom
mithunaditya-gnt:aft-4-1-mpls-label-counters-readme

Conversation

@mithunaditya-gnt

Copy link
Copy Markdown

Adds the test plan specification (README.md), metadata.textproto, and testregistry.textproto entry for AFT-4.1: AFT MPLS Label Entry Counters under feature/afts/mpls/otg_tests/afts_mpls_label_counters_test/.

Summary of Coverage

  • AFT-4.1.1: Static MPLS LSP Pop-and-Forward (Direct Next-Hop Forwarding) label entry telemetry counters (packets-forwarded, octets-forwarded).
  • AFT-4.1.2: Static MPLS LSP Pop-and-Lookup (Network-Instance FIB Lookup) label entry telemetry counters (packets-forwarded, octets-forwarded).
  • Includes Canonical OC JSON coverage blocks and OpenConfig telemetry path definitions validated against validate_readme_canonicalocspec, validate_readme_ocpaths, addrundata, and sync_test_registry.

cc @paramasivamn1

@mithunaditya-gnt
mithunaditya-gnt requested a review from a team as a code owner October 2, 2026 16:28
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! 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 introduces the test plan specification for verifying OpenConfig AFT MPLS label-entry telemetry counters. It covers the validation of packets-forwarded and octets-forwarded counters under two distinct MPLS forwarding modes: direct next-hop forwarding and network-instance FIB lookup. The changes provide the necessary documentation and registry entries to support future implementation and automated testing of these telemetry paths.

Highlights

  • Test Plan Documentation: Added a comprehensive README.md for AFT-4.1: AFT MPLS Label Entry Counters, detailing test procedures for both Pop-and-Forward and Pop-and-Lookup scenarios.
  • Metadata and Registry Updates: Included the necessary metadata.textproto and registered the new test plan in testregistry.textproto to ensure integration with the test suite.
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 the 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 counterproductive. 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.

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

OpenConfigBot commented Oct 2, 2026 •

Copy link
Copy Markdown

Pull Request Functional Test Report for #6122 / 3bede46

Virtual Devices

Device Test Status Test Documentation Job Raw Log
Arista cEOS status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Cisco 8000E status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Cisco XRd status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Juniper ncPTX status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Nokia SR Linux status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Openconfig Lemming status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters

Hardware Devices

Device Test Status Test Documentation Raw Log
Arista status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Cisco status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Juniper status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters
Nokia status
AFT-4.1: pending authorization
AFT-4.1: AFT MPLS Label Entry Counters

Help

@gemini-code-assist gemini-code-assist Bot left a comment

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.

Code Review

This pull request introduces a new test plan, AFT-4.1: AFT MPLS Label Entry Counters, along with its metadata and registry entries. The test plan details the verification of OpenConfig AFT MPLS label-entry telemetry counters (packets-forwarded and octets-forwarded) during MPLS-in-UDP (MPLSoGUE) decapsulation and forwarding across two modes: static MPLS LSP pop-and-forward and static MPLS LSP pop-and-lookup. There are no review comments, and the changes conform to the repository style guidelines; therefore, no additional feedback is provided.

@mithunaditya-gnt
mithunaditya-gnt force-pushed the aft-4-1-mpls-label-counters-readme branch from 17e6ab2 to 3bede46 Compare October 2, 2026 18:22

This branch has not been deployed

No deployments
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.

2 participants