-
Notifications
You must be signed in to change notification settings - Fork 699
platform: add fault description leaf and ACTION_FW_REPROGRAM #1455
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
base: master
Are you sure you want to change the base?
Changes from all commits
877a4e4
bf9bbb5
104aa6d
b35c401
cdf2911
90dc063
8589174
a3337db
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -23,7 +23,13 @@ module openconfig-platform-healthz-fault { | |
| description | ||
| "This model defines device reported fault"; | ||
|
|
||
| oc-ext:openconfig-version "0.1.0"; | ||
| oc-ext:openconfig-version "0.1.1"; | ||
|
|
||
| revision "2026-03-23" { | ||
| description | ||
| "Add remediation description and ACTION_FW_REPROGRAM"; | ||
| reference "0.1.1"; | ||
| } | ||
|
|
||
| revision "2025-08-05" { | ||
| description | ||
|
|
@@ -126,6 +132,26 @@ module openconfig-platform-healthz-fault { | |
| "Replace component."; | ||
| } | ||
|
|
||
| identity ACTION_FW_REPROGRAM { | ||
|
brianneville marked this conversation as resolved.
|
||
| base ACTION_BASE; | ||
| description | ||
| "Force-reprogram the firmware for the targeted component. | ||
| The targeted component may need to be powercycled | ||
| for the reprogramming to take effect. | ||
|
Comment on lines
+139
to
+140
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Recommend updating to say something like: if a power cycle is required, then |
||
|
|
||
| In comparison to ACTION_FACTORY_RESET action, | ||
| ACTION_FW_REPROGRAM does not necessarily involve resetting | ||
| the firmware back to its factory default. It also does not | ||
| involve resetting any certificates on disk or removing | ||
| any config files or OS images. | ||
|
Comment on lines
+142
to
+146
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can you elaborate on where the firmware is stored? Is this reloading firmware stored in the device filesystem? In particular are there any other actions that may need to be performed for |
||
|
|
||
| E.g. for the Chassis component this could mean | ||
| force-reprogramming all FPGAs and reloading | ||
| all drivers on the Chassis. | ||
| This reprogramming would be to the currently-installed | ||
| version, not the factory default version."; | ||
| } | ||
|
|
||
| grouping platform-health-faults { | ||
| description | ||
| "Grouping containing a component's active faults"; | ||
|
|
@@ -295,6 +321,12 @@ module openconfig-platform-healthz-fault { | |
| disruptive."; | ||
| } | ||
|
|
||
| leaf description { | ||
| type string; | ||
| description | ||
| "Description for the remediating action"; | ||
| } | ||
|
|
||
| leaf action { | ||
| description | ||
| "The specific action to be performed"; | ||
|
|
||
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.
Since we are adding yang, this should be a minor version increment per semver rules