Skip to content

Manually override HW switchover for planned operation#2210

Closed
chikkaiah-work wants to merge 9 commits into
opencomputeproject:masterfrom
chikkaiah-work:master
Closed

Manually override HW switchover for planned operation#2210
chikkaiah-work wants to merge 9 commits into
opencomputeproject:masterfrom
chikkaiah-work:master

Conversation

@chikkaiah-work

@chikkaiah-work chikkaiah-work commented Sep 22, 2025

Copy link
Copy Markdown
Contributor

Need capability to switch to primary or backup manually overriding the hardware switchover. DualToR architecture in SONiC requires this manual switching capability without any packet loss for planned operation in the datacenter.​

This will need a new SAI attribute in the nexthop protection group. Introducing a new enum attribute as admin_role {auto(default), primary, backup} which can override the hardware switching when not set as auto. ​

@chikkaiah-work
chikkaiah-work marked this pull request as ready for review October 1, 2025 20:04
@tjchadaga

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@tjchadaga

Copy link
Copy Markdown
Collaborator

@chikkaiah-work - could you please squash your commits to resolve the metachecker errors? Also, would you like to discuss this PR in the community meeting?

@chikkaiah-work

Copy link
Copy Markdown
Contributor Author

@chikkaiah-work - could you please squash your commits to resolve the metachecker errors? Also, would you like to discuss this PR in the community meeting?
Done. Yes, please have this for review in next meeting.
Thanks

@tjchadaga

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@tjchadaga

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

@tjchadaga

Copy link
Copy Markdown
Collaborator

@JaiOCP - could you please help review this PR?

@tjchadaga

Copy link
Copy Markdown
Collaborator

@chikkaiah-work - could you please try to rebase your branch to the latest master?

@chikkaiah-work

Copy link
Copy Markdown
Contributor Author

@chikkaiah-work - could you please try to rebase your branch to the latest master?

Done. Rebased to latest master.

@tjchadaga

Copy link
Copy Markdown
Collaborator

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines successfully started running 1 pipeline(s).

chikkaiah-work and others added 9 commits October 9, 2025 12:34
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>

change name from bacup to standby

Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>

fixes

Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>

fix error

Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
Signed-off-by: Prince George <prgeor@microsoft.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
Signed-off-by: Running Huang <runningh@nvidia.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
Signed-off-by: Martin Liao <marliao@marliao-mlt.client.nvidia.com>
Co-authored-by: Martin Liao <marliao@marliao-mlt.client.nvidia.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
The meta/Makefile contains several rules which are not correct
for parallel make. These rules contain several targets to the
left of the colon, and express the intent that the targets are
built together as a group. Unfortunately, that's not what the
syntax means:  Rather:

   t1 t2 t3 : prereq
           recipe # recipe generates all three!

is essentially a syntactic sugar condensing multiple rules
with the same recipe and prerequisites:

   t1 : prereq
           recipe # recipe generates all three!

   t2 : prereq
           recipe

   t3 : prereq
           recipe

Under parallel make these rules fire in parallel which can
wreak havoc, since they stomp on each other's files.

The issue can be addressed using the grouped targets feature:

   t1 t2 t3 &: prereq
           recipe # recipe generates all three!

The ampersand-colon separator &: means that there is only one
rule here which Make understands to be updating all three
targets.

This feature has been available since GNU Make 4.2.90.
Ubuntu-latest is on 4.3.

(The grouped targets feature was the subject of a bugfix before
4.4. The bug potentially causes a grouped target not to be
remade if it is deleted.  This is minor problem because it's
not expected that someone will be deleting, say, the generated
file saimetadata.c individually rather than doing a "make clean"
which deletes all the generated files.)

Signed-off-by: Kaz Kylheku <kazinator@arista.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
This proposal outlines the addition of a new port attribute designed to provide a standardized method for querying the active firmware revision of a port.

Proposal -

Add label SAI_ATTR_PORT_FW_REVISION under sai_port_attr_h in saiport.h to store firmware related information. This attribute will store a string denoting the current firmware version running on the port. This can denote either the SerDes firmware version or any other vendor specific firmware version that needs to be exported.

Signed-off-by: Tejas Pandey <pandeytejas@google.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
Signed-off-by: Dhruvkumar Patel <pdhruvkumarr@marvell.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
…iacl module) (#2202)

Signed-off-by: Kandankarunai Thiruppathi <kthiruppathi@marvell.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
Signed-off-by: Chikkegowda Chikkaiah <cchikkai@cisco.com>
@chikkaiah-work chikkaiah-work closed this by deleting the head repository Oct 9, 2025
@rajkumar38

Copy link
Copy Markdown
Contributor

@chikkaiah-work,
I see this PR is closed. Are you raising any new PR ?

@chikkaiah-work

Copy link
Copy Markdown
Contributor Author

@chikkaiah-work, I see this PR is closed. Are you raising any new PR ?

Hi @rajkumar38, it got master branch diffs while squashing the commits. Hence closed it and opened new one - #2219
#2219

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.

10 participants