Troubleshoot Hardware Sensor Status Mapping Issues

Troubleshooting hardware sensor status mismatches

Network devices from different vendors report hardware and environmental health using varied SNMP status values. These values are often vendor-specific, inconsistent, or ambiguous, which can make it difficult to understand the actual health of a device at a glance.
This document explains how Site24x7 interprets and normalizes SNMP sensor statuses reported by supported vendors and maps them to a consistent status. The goal is to provide clear visibility into hardware health and ensure predictable alerts across multi-vendor network environments.

Use case

The SNMP sensor status mapping table given below helps you:

  • Understand why a device or hardware component is shown as Up, Trouble, or Down in Site24x7.
  • Interpret vendor-specific SNMP values, such as non operational, stand by, over heat yes, or out of range.
  • Troubleshoot hardware alerts related to power supplies, fans, temperature sensors, and other components.
  • Validate sensor behavior after onboarding a new device or enabling hardware monitoring.
  • Avoid false positives by understanding how unknown or unsupported SNMP states are handled.

SNMP sensor status mapping reference table

The table below consolidates SNMP sensor status mappings across all supported vendors. Use this single reference to quickly identify how a vendor‑specific SNMP status is interpreted in Site24x7.

Vendor

Sensor type

SNMP status

Site24x7 status

Cisco Nexus

Temperature

ok

Up

Temperature

unavailable

Down

Temperature

non operational

Down

Cisco ASA / ASR / ISR / NCS / Meraki

Default

ok

Up

Default

unavailable

Down

Default

non operational

Down

Cisco Firepower

Default

operable

Up

Default

inoperable

Down

Default

degraded

Trouble

Default

powered off

Down

Default

power problem

Down

Default

voltage problem

Down

Default

thermal problem

Down

Default

performance problem

Trouble

Default

disabled

Down

Default

malformedFru

Down

Cisco (Default)

Default

normal

Up

Default

warning

Trouble

Default

critical

Down

Default

shutdown

Down

Default

not present

Down

Default

not functioning

Down

Juniper

Default

running

Up

Default

ready

Up

Default

reset

Up

Default

running at full speed

Up

Default

stand by

Down

Default

unknown

Down

Default

down

Down

Hewlett Packard

Temperature

over heat yes

Down

Temperature

over heat no

Up

Fan

failed

Down

Fan

removed

Down

Fan

off

Down

Fan

underspeed

Trouble

Fan

overspeed

Trouble

Fan

ok

Up

Fan

max state

Trouble

Power

ps not present

Down

Power

ps not plugged

Down

Power

ps powered

Up

Power

ps failed

Down

Power

ps perm failure

Trouble

Power

ps max

Trouble

Default

good

Up

Default

warning

Trouble

Default

bad

Down

Default

unknown

Down

Default

not present

Down

Hewlett Packard Router

Default

enabled

Up

Default

not supported

Down

Default

disabled

Down

Default

dangerous

Down

Huawei

Default

normal

Up

Default

supply

Down

Default

sleep

Trouble

Default

unknown

Down

Fortinet FortiManager

Default

ok

Up

Default

failed

Down

Default

out of range not critical

Trouble

Default

out of range critical

Down

Default

out of range not recoverable

Down

Default

input lost

Trouble

Default

not present

Down

Ericsson

Default

normal

Up

Default

failed

Down

Default

absent

Down

Default

unknown

Down

Broadcom

Default

ok

Up

Default

unavailable

Down

Default

non operational

Down

3Com

Default

active

Up

Default

deactive

Down

Default

not install

Down

Default

unsupport

Down

Arista Networks

Default

ok

Up

Default

unavailable

Down

Default

non operational

Down

Avaya

Default

ok

Up

Default

unavailable

Down

Default

non operational

Down

F5 Networks

Default

good

Up

Default

bad

Down

Default

not present

Down

Ubiquiti Networks

Temperature

low

Trouble

Temperature

normal

Up

Temperature

warning

Trouble

Temperature

critical

Down

Temperature

shutdown

Down

Temperature

not present

Down

Temperature

not operational

Down

Default

operational

Up

Default

failed

Down

Default

powering

Down

Default

nopower

Down

Default

not powering

Down

Default

incompatible

Down

Notes
If a sensor status is not listed, Site24x7 treats it as unknown by default to avoid masking potential hardware failures.

Related links

    • Related Articles

    • Troubleshooting hardware sensor monitoring

      This guide helps you troubleshoot issues related to hardware sensor monitoring across supported network devices. If temperature, voltage, fan, or power sensors are missing, show incorrect status, or fail to report values, this document walks you ...

    • Troubleshooting VMware ESX hardware monitor sensor data

      If your VMware ESX hardware monitor displays inaccurate or outdated sensor data that does not reflect the actual state of the ESX server, follow these steps to refresh the hardware health data: Steps to fix outdated sensor data: Log in to the VMware ...

    • Troubleshooting tips for log collection errors

      The following is a list of possible log collection errors and the solutions to fix them: Error message Reason Solution Upload Limit Reached You might have reached the maximum upload limit configured for this log type in the current billing cycle. ...

    • Synthetic browser module prerequisite and troubleshooting guide for On-Premise Pollers

      Introduction This document provides a structured troubleshooting guide for resolving issues encountered during the download process of On-Premise Poller for Synthetic (Browser) Module. It covers possible statuses, check-up steps, remedies, and ...

    • How to configure the NGINX status page for monitoring NGINX performance

      The NGINX plugin uses the NGINX status page to pull the performance metrics of the NGINX server. You may encounter the following errors while installing the NGINX plugin integration: Error_code : HTTP Error 404: This error usually indicates that the ...