Skip to content

Conversation

@lakshmi-nexthop
Copy link

Details for supporting VOQ mode in single ASIC SONiC switch systems.

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

arlakshm
arlakshm previously approved these changes Jul 1, 2025
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

updates to use chassis db config file
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@deepak-singhal0408
Copy link

@arlakshm could you sign-off this HLD? thanks,

Copy link

@arista-nwolfe arista-nwolfe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The HLD doesn't talk about what to do with the existing internal ports for single-asic VOQ systems.
I.E. Ethernet-IB0 and Ethernet-Rec0
I believe neither of these ports are needed for single-asic VOQ and some changes will be required in mirrororch.cpp to avoid requiring Ethernet-Rec0 for everflow.

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@lakshmi-nexthop
Copy link
Author

The HLD doesn't talk about what to do with the existing internal ports for single-asic VOQ systems. I.E. Ethernet-IB0 and Ethernet-Rec0 I believe neither of these ports are needed for single-asic VOQ and some changes will be required in mirrororch.cpp to avoid requiring Ethernet-Rec0 for everflow.

updated the orchagent section.

@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

TSA applies for both chassis and non chassis case.
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@abdosi
Copy link
Contributor

abdosi commented Sep 17, 2025

  1. Egress Everflow do we need Recirc Port ==> Waiting for BRCM
  2. Do recirc port just for base use case of Regular Ingress Mirroring
    2.1 Regular Ingress mirroring does not need Recirc Port
    2.2 Regular Ingress Mirroring + Policer needs Recirc Port .

@arlakshm : Arista/Nexthop wants to starts with Recirc Port (maintain backward compatibility) and later can be removed as optimization. Please help close on this.

@abdosi
Copy link
Contributor

abdosi commented Sep 17, 2025

Please add code PR links here.

recirc ports are going to be present as per discussions.
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@abdosi
Copy link
Contributor

abdosi commented Oct 1, 2025

2. Do recirc port just for base use case of Regular Ingress Mirroring
2.1 Regular Ingress mirroring does not need Recirc Port
2.2 Regular Ingress Mirroring + Policer needs Recirc Port .

Nexthop confirmed both Ingress and Egress Everflow works fine with Recirc Port. Need to check for Policier.

@abdosi
Copy link
Contributor

abdosi commented Oct 1, 2025

@arista-nwolfe / @arlakshm please sign-off to merge this.

inband ports info
@mssonicbld
Copy link
Collaborator

/azp run

@azure-pipelines
Copy link

No pipelines are associated with this pull request.

@sridhartalari
Copy link

Can you please provide explanation on difference between regular single asic fixed system and single ASIC fixed sytem with VOQ. also the reason we need it . Please let us know if we have fabric ports even if it is single ASIC system

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: 📋 In Plan Features
Status: No status

Development

Successfully merging this pull request may close these issues.

10 participants