Graph Data Freshness

This guide helps you diagnose situations where the Remote Agent appears to be online, but graphs such as traffic, power usage, or sensors show old data.

Overview

EasyDCIM can show two different types of status:

• Polling freshness - tells you whether the Remote Agent has recently executed the polling cycle.
• Graph data freshness - tells you whether a specific graph has recently received new data points.

These two statuses are related, but they are not the same.

A Remote Agent can be online and polling can look fresh, while a specific graph is still stale. This may happen when only one data source fails, for example SNMP traffic, PDU power polling, or Redfish server sensors.

EasyDCIM polling uses different protocols depending on the graph type:

Graph data	Polling source used by the Remote Agent
Device and port traffic	SNMP, mainly IF-MIB::ifEntry and IF-MIB::ifXEntry
PDU outlet power and PDU load	SNMP PDU driver
Server power usage	Redfish getPowerUsage()
Server power sensors	Redfish getPower()
Server thermal sensors	Redfish getThermal()

For server sensors, EasyDCIM does not use ipmitool sensor as the polling source. The Remote Agent uses Redfish when the device is a server or blade and Redfish polling is enabled.

Affected Graphs

Graph freshness indicators may appear on graph views such as:

• device graphs,
• device traffic,
• device power usage,
• server power usage,
• colocation traffic,
• colocation power usage,
• device port graphs,
• sensors.

Common Symptoms

You may be affected by stale graph data if:

• the Remote Agent is marked as online,
• polling status is OK or recently updated,
• a traffic, power, or sensor graph does not show recent values,
• graph data stops at an older timestamp,
• billing-related traffic or power data is missing for the latest period.

How to Read the Freshness Indicator

When EasyDCIM detects that graph data is old, it displays a freshness indicator near the graph.

Typical states are:

• Fresh - the graph has recent data.
• Stale - the graph has data, but the newest point is older than expected.
• No Data - EasyDCIM cannot find graph data for the selected object and time range.

If available, hover over the freshness label to see the exact timestamp of the last data point.

Polling Freshness vs Graph Freshness

Polling is fresh, but graph data is stale

This usually means the agent is running, but a specific metric type is not being collected correctly.

Possible causes:

• SNMP is not responding for traffic or PDU metrics,
• the device no longer exposes the expected SNMP OID,
• Redfish is disabled or not configured for server power/sensor metrics,
• Redfish credentials or BMC address are incorrect,
• the Redfish board type is not supported by the Remote Agent driver,
• the polling module failed only for a subset of devices,
• the data was collected but not written to the graph storage,
• the selected graph time range does not include recent data.

Polling is stale and graph data is stale

This usually means the main polling cycle is not running correctly.

Start with the Remote Agent polling guide:

Remote Agent Polling

Basic Checklist

1. Check Remote Agent status

Open the Remote Agent summary and check:

• connection status,
• polling freshness,
• queue status,
• last polling API error,
• polling devices count,
• polling duration.

If the agent is offline or polling is stale, fix that first.

2. Check the graph freshness label

Open the affected graph and check:

• last data timestamp,
• whether the status is Stale or No Data,
• whether the problem affects one graph or many graphs.

If only one graph is stale, the problem is likely device-specific.

If many graphs are stale, the problem is likely agent, queue, or storage related.

3. Check the device or port configuration

For traffic graphs, verify:

• the device is assigned to the correct Remote Agent,
• SNMP is enabled and working,
• the interface or port still exists,
• polling is not disabled for this device or port.

For power and sensor graphs, verify the correct source for the graph type:

• PDU power graphs require working SNMP for the PDU.
• Server power usage and server sensors require Redfish.
• The device must be assigned to the correct Remote Agent.
• Redfish polling must not be disabled in the polling configuration.
• The device metadata must include Redfish support and valid BMC connection details.

In the current Remote Agent implementation, server power usage, power sensors, and thermal sensors are collected by the Server Redfish Sensors polling module.

4. Check if the issue affects billing data

If the stale graph is used for billing, treat it as high priority.

Collect:

• affected user or service,
• affected device or port,
• graph type,
• last fresh timestamp,
• expected billing period,
• Remote Agent name,
• latest polling status.

Manual Verification

Traffic data

If traffic data is stale, manually verify that the device responds to SNMP from the Remote Agent host.

Example checks:

ping [DEVICE_IP]
snmpwalk -v2c -c [COMMUNITY] [DEVICE_IP] IF-MIB::ifEntry
snmpwalk -v2c -c [COMMUNITY] [DEVICE_IP] IF-MIB::ifXEntry

The Remote Agent reads port data mainly from:

• IF-MIB::ifEntry - base interface data, including ifIndex, ifDescr, ifType, ifSpeed, ifPhysAddress, ifOperStatus, ifAdminStatus, ifInOctets, ifOutOctets, packet counters, and error counters.
• IF-MIB::ifXEntry - extended interface data, including high-capacity counters such as ifHCInOctets, ifHCOutOctets, ifHighSpeed, and ifAlias.

If MIB names are not available on the Remote Agent host, use numeric OIDs:

snmpwalk -v2c -c [COMMUNITY] [DEVICE_IP] .1.3.6.1.2.1.2.2.1
snmpwalk -v2c -c [COMMUNITY] [DEVICE_IP] .1.3.6.1.2.1.31.1.1.1

If these SNMP walks do not respond from the Remote Agent, EasyDCIM cannot update traffic graphs for that device.

PDU power data

PDU outlet power and PDU load are collected through SNMP. If PDU power graphs are stale, verify SNMP from the Remote Agent host to the PDU:

ping [PDU_IP]
snmpwalk -v2c -c [COMMUNITY] [PDU_IP]

If SNMP does not respond from the Remote Agent, EasyDCIM cannot update PDU power graphs.

Server power and sensor data

Server power usage, power sensors, and thermal sensors are collected through Redfish. They are handled by the Remote Agent Server Redfish Sensors polling module.

The module runs only when:

• the device is a server or blade,
• Redfish polling is not disabled,
• the device metadata has Redfish Support enabled,
• the device metadata contains valid BMC connection details, stored in EasyDCIM as IPMI IP Address, IPMI Username, and IPMI Password,
• the board type is supported by a Redfish driver.

Basic Redfish checks from the Remote Agent host:

ping [BMC_IP]
curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/
curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/Chassis

Then test the vendor-specific chassis endpoint used by the device. Common examples:

# Common generic path used by several vendors
curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/Chassis/1/Power
curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/Chassis/1/Thermal

# Dell iDRAC path used by the Dell Redfish driver
curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/Chassis/System.Embedded.1/Power
curl -k -u '[USER]:[PASSWORD]' https://[BMC_IP]/redfish/v1/Chassis/System.Embedded.1/Thermal

If /redfish/v1/ works but the Power or Thermal endpoint does not, the device may use a different chassis ID or may not expose the expected Redfish data. Check the output of /redfish/v1/Chassis to find the correct chassis member path.

Do not use ipmitool sensor as proof that EasyDCIM server sensor graphs should work. ipmitool may show sensor data through IPMI, while EasyDCIM server sensor graphs are collected through Redfish.

WARNING

Do not share SNMP communities, BMC passwords, API keys, or full command outputs containing secrets in support tickets without redacting them first.