Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 33 additions & 1 deletion release/models/platform/openconfig-platform-healthz-fault.yang
Original file line number Diff line number Diff line change
Expand Up @@ -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";
Copy link
Copy Markdown
Member

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

Suggested change
oc-ext:openconfig-version "0.1.1";
oc-ext:openconfig-version "0.2.0";


revision "2026-03-23" {
description
"Add remediation description and ACTION_FW_REPROGRAM";
reference "0.1.1";
}

revision "2025-08-05" {
description
Expand Down Expand Up @@ -126,6 +132,26 @@ module openconfig-platform-healthz-fault {
"Replace component.";
}

identity ACTION_FW_REPROGRAM {
Comment thread
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
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The 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 ACTION_POWER_CYCLE will also be set as a remediations/remediation/action.


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
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The 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 ACTION_FW_REPROGRAM ?


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";
Expand Down Expand Up @@ -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";
Expand Down
Loading