-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Add support data for fabric monitoring in CONFIG_DB. #14170
Add support data for fabric monitoring in CONFIG_DB. #14170
Conversation
@sanmalho-git - please add reviewers as you see fit, thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
add comments, Please add some unit tests for this.
src/sonic-config-engine/minigraph.py
Outdated
@@ -1775,6 +1776,17 @@ def parse_xml(filename, platform=None, port_config_file=None, asic_name=None, hw | |||
results['PORT'] = ports | |||
results['CONSOLE_PORT'] = console_ports | |||
|
|||
# Get the global fabric monitoring data | |||
curDir = os.getcwd() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this needed, curDir is not used?
# alias to asic_port_name mapping | ||
if 'asic_port_name' in data: | ||
port_alias_asic_map[data['alias']] = data['asic_port_name'].strip() | ||
return (ports, port_alias_map, port_alias_asic_map) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
port_alias_map, port_alias_asic_map
is not used, is this needed?
/Azpw run Azure.sonic-buildimage |
/AzurePipelines run Azure.sonic-buildimage |
Azure Pipelines successfully started running 1 pipeline(s). |
@arlakshm looks like @jfeng-arista addressed all comments. Can we get this merged before the 202305 cut-off? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in #14170. #### How I did it This is a clone of @jfeng-arista's PR #14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
@gechiang if this is a bug fix and we needed in 202305, pls have ADO to track, each commit to 202305 need ADO. |
@StormLiangMS Thanks! |
Added support data for fabric monitoring in CONFIG_DB The CONFIG_DB now has the FABRIC_MONITOR|FABRIC_MONITOR_DATA table for default value for fabric port monitoring. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_MONITOR|FABRIC_MONITOR_DATA" {'monErrThreshCrcCells': '1', 'monErrThreshRxCells': '61035156', 'monPollThreshIsolation': '1', 'monPollThreshRecovery': '8'} The CONFIG_DB now also has a table for each fabric port for its isolate status. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_PORT|Fabric20" {'alias': 'Fabric20', 'isolateStatus': 'False', 'lanes': '20'}
Cherry-pick PR to 202305: #16045 |
Added support data for fabric monitoring in CONFIG_DB The CONFIG_DB now has the FABRIC_MONITOR|FABRIC_MONITOR_DATA table for default value for fabric port monitoring. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_MONITOR|FABRIC_MONITOR_DATA" {'monErrThreshCrcCells': '1', 'monErrThreshRxCells': '61035156', 'monPollThreshIsolation': '1', 'monPollThreshRecovery': '8'} The CONFIG_DB now also has a table for each fabric port for its isolate status. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_PORT|Fabric20" {'alias': 'Fabric20', 'isolateStatus': 'False', 'lanes': '20'} Co-authored-by: jfeng-arista <98421150+jfeng-arista@users.noreply.github.com>
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in sonic-net#14170. #### How I did it This is a clone of @jfeng-arista's PR sonic-net#14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in #14170. #### How I did it This is a clone of @jfeng-arista's PR #14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
Added support data for fabric monitoring in CONFIG_DB The CONFIG_DB now has the FABRIC_MONITOR|FABRIC_MONITOR_DATA table for default value for fabric port monitoring. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_MONITOR|FABRIC_MONITOR_DATA" {'monErrThreshCrcCells': '1', 'monErrThreshRxCells': '61035156', 'monPollThreshIsolation': '1', 'monPollThreshRecovery': '8'} The CONFIG_DB now also has a table for each fabric port for its isolate status. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_PORT|Fabric20" {'alias': 'Fabric20', 'isolateStatus': 'False', 'lanes': '20'}
#### Why I did it Introduce YANG model for FABRIC in CONFIG_DB, which was added in sonic-net#14170. #### How I did it This is a clone of @jfeng-arista's PR sonic-net#14282 to resolve conflicts with upstream changes. #### How to verify it Passing pipeline build is sufficient.
Added support data for fabric monitoring in CONFIG_DB The CONFIG_DB now has the FABRIC_MONITOR|FABRIC_MONITOR_DATA table for default value for fabric port monitoring. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_MONITOR|FABRIC_MONITOR_DATA" {'monErrThreshCrcCells': '1', 'monErrThreshRxCells': '61035156', 'monPollThreshIsolation': '1', 'monPollThreshRecovery': '8'} The CONFIG_DB now also has a table for each fabric port for its isolate status. An example output of getting this table is: sonic-db-cli CONFIG_DB hgetall "FABRIC_PORT|Fabric20" {'alias': 'Fabric20', 'isolateStatus': 'False', 'lanes': '20'}
Add support data for fabric monitoring in CONFIG_DB. (sonic-net#14170)
Added support data for fabric monitoring in CONFIG_DB
The CONFIG_DB now has the FABRIC_MONITOR|FABRIC_MONITOR_DATA table for default value for fabric port monitoring. An example output of getting this table is:
The CONFIG_DB now also has a table for each fabric port for its isolate status.
An example output of getting this table is:
Why I did it
How I did it
How to verify it
Which release branch to backport (provide reason below if selected)
Description for the changelog
Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.
Link to config_db schema for YANG module changes
A picture of a cute animal (not mandatory but encouraged)