Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[202012][copp_cfg] Enable dhcp trap for BmcMgmtToRRouter #10596

Merged
merged 2 commits into from
Apr 19, 2022

Conversation

Blueve
Copy link
Contributor

@Blueve Blueve commented Apr 18, 2022

Why I did it

We need enable dhcp trap for BmcMgmtToRRouter

How I did it

Add BmcMgmtToRRouter to the enable list

How to verify it

Which release branch to backport (provide reason below if selected)

  • 201811
  • 201911
  • 202006
  • 202012
  • 202106
  • 202111

Description for the changelog

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

@Blueve Blueve requested a review from yxieca April 18, 2022 03:34
@Blueve Blueve force-pushed the dev/jika/bmcmgmttor branch from d076619 to af709e6 Compare April 18, 2022 15:17
@Blueve
Copy link
Contributor Author

Blueve commented Apr 19, 2022

/azp list

@Blueve
Copy link
Contributor Author

Blueve commented Apr 19, 2022

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@Blueve
Copy link
Contributor Author

Blueve commented Apr 19, 2022

/azp run Azure.sonic-buildimage

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@Blueve Blueve merged commit 4ee75f4 into sonic-net:202012 Apr 19, 2022
@Blueve Blueve deleted the dev/jika/bmcmgmttor branch April 19, 2022 07:59
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