Werk #15633: cisco_fru_module_status: '14' is not a valid PhysicalClasses
| Component | Checks & agents | ||||||||
| Title | cisco_fru_module_status: '14' is not a valid PhysicalClasses | ||||||||
| Date | Jun 20, 2023 | ||||||||
| Level | Trivial Change | ||||||||
| Class | Bug Fix | ||||||||
| Compatibility | Compatible - no manual interaction needed | ||||||||
| Checkmk versions & editions |
|
Previously, the plugin cisco_fru_module_status would raise the error
ValueError ('14' is not a valid PhysicalClasses)
while parsing the section. With this Werk, the crash no longer occurs. The state '14' is now remapped to 'unknown'. Note, that the MIB v2/ENTITY-MIB.my does not list the state '14', so may we might have to update this mapping, if Cisco aligns their MIBs with the behaviour of their devices.