How NetApp Filers KM for PATROL Reports 'Failed’ and ‘Degraded’ Status Values in the PATROL Console
KB1224 - Jun 28, 2018
Type: Best practice
Description: This article explains how 'failed’ and ‘degraded’ status values collected from the NetApp API are reported in the PATROL Console.
Additional Keywords: NetApp, Status, Events
Introduction
When monitored NetApp components report problems or errors, they do not always provide a clear portrait of what the issue consists in or information about its severity. Going through long files of command outputs from which it is often difficult to extract valuable information may become a difficult task. To establish a link between an issue reported by a component and an easily exploitable status, NetApp Filers KM for PATROL maps any value collected from a monitored NetApp system to the standard PATROL status. The table below provides the correlation between the collected data and the value reported in the PATROL console.
Values Correlation Table
Class | API (element/value) | Sentry Mapping (0=OK, 1=warning, 2=alarm) |
---|---|---|
Disk (7-mode) | disk-details/is-prefailed | 1 |
| disk-details/OK | 0 | |
| disk-details/is-replacing | 1 | |
| disk-details/is-zeroed | 0 | |
| disk-details/is-offline | 2 | |
| disk-details/broken-details/not failed | 0 | |
| disk-details/broken-details/zeroed | 0 | |
| disk-details/broken-details/labeled broken | 1 | |
| disk-details/broken-details/replacing | 1 | |
| disk-details/broken-details/admin removed | 1 | |
| disk-details/broken-details/bad label | 1 | |
| disk-details/broken-details/bypassed | 1 | |
| disk-details/broken-details/failed | 2 | |
| disk-details/broken-details/admin failed | 2 | |
| disk-details/broken-details/init failed | 2 | |
| disk-details/broken-details/pulled | 2 | |
Disk (Cluster) | media-scrubing | 0 |
| sparecore | 0 | |
| zeroed | 0 | |
| zeroing | 0 | |
| offline | 1 | |
| prefailed | 1 | |
| reconstructing | 1 | |
| replacing | 1 | |
| failed-registry | 2 | |
| failed | 2 | |
| admin-failed | 2 | |
| admin-removed | 2 | |
| admin-testing | 2 | |
| bad-label | 2 | |
| bypassed | 2 | |
| init-failed | 2 | |
| label-version | 2 | |
| labeled-broken | 2 | |
| label-maint | 2 | |
| lun-resized | 2 | |
| missing | 2 | |
| not-responding | 2 | |
| predict-failure | 2 | |
| rawsize-shrank | 2 | |
| recovering | 2 | |
| sanitizing | 2 | |
| sanitized | 2 | |
| trad-vol-disk | 2 | |
| snaplock-disk | 2 | |
| testing | 2 | |
| unassigned | 2 | |
| unknown-reason | 2 | |
Fan | cooling-element-is-error/true | 2 |
| cooling-element-is-error/false | 0 | |
FC Port | state/online | 0 |
| state/startup | 1 | |
| state/uninitialized | 2 | |
| state/initializing firmware | 1 | |
| state/link not connected | 1 | |
| state/waiting for link up | 1 | |
| state/link disconnected | 2 | |
| state/resetting | 1 | |
| state/offline | 2 | |
| state/offlined by user/system | 0 | |
iSCSI Port | state/online | 0 |
| state/offline | 0 | |
| state/partner | 0 | |
| state/local | 1 | |
| state/error | 2 | |
Node | is-node-healthy/false | 2 |
| is-node-healthy/unknown | 1 | |
| is-node-healthy/true + (env-failed-fan-count = null or env-failed-power-supply-count = null ) | 1 | |
| is-node-healthy/true + (env-failed-fan-count >0 or env-failed-power-supply-count >0 ) | 2 | |
| is-node-healthy/true + (env-failed-fan-count = 0 or env-failed-power-supply-count = 0 ) | 0 | |
Plex | is-online/true | 0 |
| is-online/unkown | 1 | |
Power Supply | power-supply-is-error/true | 0 |
| power-supply-is-error/false | 2 | |
Shelf | shelf-state/no status | 0 |
| shelf-state/online | 0 | |
| shelf-state/offline | 0 | |
| shelf-state/init required | 1 | |
| shelf-state/unknown | 1 | |
| shelf-state/missing | 2 | |
Sis | state/idle | 0 |
| state/active | 0 | |
| state/undoing | 0 | |
| state/downgrading | 0 | |
| state/pending | 1 | |
| state/initializing | 1 | |
| state/disabled | 2 | |
Replication | snapmirror-status/progress | 0 |
| snapmirror-status/failed | 2 | |
| snapmirror-status/invalid | 2 | |
| snapmirror-status/limbo | 0 | |
| snapmirror-status/mirror degraded | 1 | |
| snapmirror-status/mirror resynchronizing | 0 | |
| snapmirror-status/mirrored | 0 | |
| snapmirror-status/needs CP count check | 0 | |
| snapmirror-status/uninitialized | 0 | |
| snapmirror-status/unknown mirror state | 0 | |
| snapmirror-status/unmirrored | 0 | |
Temperature | temp-sensor-current-condition/normal_temperature_range | 0 |
| temp-sensor-current-condition/over_temperature_warning | 1 | |
| temp-sensor-current-condition/under_temperature_warning | 1 | |
| temp-sensor-current-condition/under_temperature_failure | 2 | |
| temp-sensor-current-condition/over_temperature_failure | 2 | |
| temp-sensor-current-condition/Unknown | 1 | |
vFiler | status/online | 0 |
| status/running | 0 | |
| status/inconsistent | 1 | |
| status/offline | 1 | |
| status/defunct | 1 | |
| status/stopped | 2 | |
Voltage | sensor-condition/normal_operating_range | 0 |
| sensor-condition/overvoltage_warning | 1 | |
| sensor-condition/undervoltage_warning | 1 | |
| sensor-condition/overvoltage_failure | 2 | |
| sensor-condition/undervoltage_failure | 2 | |
Volume | state/online | 0 |
| state/offline | 0 | |
| state/creating | 0 | |
| state/restricted | 1 | |
| state/partial | 1 | |
| state/mixed | 1 | |
| state/invalid | 2 | |
| state/unrecoverable | 2 | |
| state/failed | 2 | |
| state/unknown | 1 | |
Vserver | state/running | 0 |
| state/stopping | 1 | |
| state/starting | 1 | |
| state/stopped | 2 | |
Aggregate | state/creating | 0 |
| state/destroying | 1 | |
| state/failed | 2 | |
| state/frozen | 1 | |
| state/inconsistent | 1 | |
| state/iron_restricted | 1 | |
| state/mounting | 1 | |
| state/offline | 1 | |
| state/online | 0 | |
| state/partial | 1 | |
| state/quiesced | 1 | |
| state/quiescing | 1 | |
| state/restricted | 1 | |
| state/reverted | 1 | |
| state/unknown | 1 | |
| state/unmounted | 1 | |
| state/unmounting | 1 | |
CIFS | status/started | 0 |
| status/up | 0 | |
| status/stopping | 1 | |
| status/starting | 1 | |
| status/down | 1 | |
| status/stopped | 2 |
Related Topics
- Class-41 Events not Sent to Cell After Upgrading PATROL Agent to v9.5
- Closing Sentry Class-41 Events in BEM/BPPM when Class-9 Events are Generated
- Deduplicating PATROL Events with Different mc_origin_key Slot Values
- Empty Values for mc_object_class, mc_object and mc_parameter Slots in the Sentry KMs’ Events
- Enriching PATROL Events with More Meaningful Information
- Generating Test Events with Hardware Sentry KM for PATROL
- Handling PATROL Events of Class 11/41
- How to Manually Set Agent Thresholds in a CMA Policy
- Integrating the Events Generated by the KMs into BMC Event Manager
- Too Many Hardware Sentry Internal Events Generated in TrueSight/PATROL Consoles
- Troubleshooting Missed Events
- Updating the mc_host and mc_host_address Slots of Sentry Class-41 Events in BEM with the Actual Hostname and IP Address of the Remotely Monitored System
- Using Macros to Customize PATROL Event Alert Actions