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

[Rule] [Optane] [ipmctl_show_-a_-dimm] ConfigurationStatus != "Valid" #25

Closed
sscargal opened this issue Feb 3, 2022 · 0 comments · Fixed by #58
Closed

[Rule] [Optane] [ipmctl_show_-a_-dimm] ConfigurationStatus != "Valid" #25

sscargal opened this issue Feb 3, 2022 · 0 comments · Fixed by #58
Assignees
Labels
rule Create a new rule
Milestone

Comments

@sscargal
Copy link
Owner

sscargal commented Feb 3, 2022

Analyzer Module: Optane
Input File: ipmctl_show_-a_-dimm
Parameter: ConfigurationStatus
Description: This rule should check if the ConfigurationStatus != "Valid" and report an INFO message to the user

Rule Passes:

   ConfigurationStatus=Valid

Possible Values

ConfigurationStatus
           The status of the PMem module memory configuration. One of:

           •   Valid: The configuration is valid.

           •   Not Configured: The PMem module has not been configured.

           •   Failed - Bad configuration: The configuration is corrupt.

           •   Failed - Broken interleave: This PMem module is part of an interleave set that is not complete.

           •   Failed - Reverted: The configuration failed and was reverted to the last known good configuration.

           •   Failed - Unsupported: The configuration is not compatible with the installed BIOS.

           •   Unknown: The configuration cannot be determined.
@sscargal sscargal added the rule Create a new rule label Feb 3, 2022
@sscargal sscargal added this to the Version 1.0.0 milestone Feb 3, 2022
@sscargal sscargal self-assigned this Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
rule Create a new rule
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant