Data Aggregator Health View Displays Incorrect Hostname in Fault Tolerant Environment

Products

• Network Observability
• CA Performance Management

Issue/Introduction

In a Fault Tolerant (FT) Data Aggregator (DA) environment, the System Health widget displays a static hostname or IP address

for the Data Aggregator that does not update when a failover event occurs.

The Health view appears to be monitoring the "incorrect" node, even though the Data Aggregator is successfully operating on the secondary (active) node.

Environment

DX NetOps :: All Supported Versions

Cause

This behavior occurs when Data Aggregator nodes are discovered as individual devices via SNMP.

When the system discovers DA nodes via SNMP, it assigns a unique identity to each node. During the initial discovery process, the "self-monitoring" item for the Data Aggregator is bound to the first DA node discovered. Because this identity is locked to a specific SNMP device, the system cannot dynamically migrate the self-monitoring facets (which control the UI labels and hostnames) to the other DA node when a failover occurs.

Consequently, while the DA nodes correctly switch between Active and Ready states, the UI label for the self-monitoring component remains fixed to the hostname of the first node that was originally discovered.

 

Resolution

This behavior is Functioning as Designed (FAD) for SNMP-discovered Data Aggregators. There is no configuration change or workaround available to make the hostname label dynamic.

Please note the following:

• Data Integrity: Although the hostname and label displayed in the System Health widget are static, the health metrics being reported are accurate and reflect the data from the currently active Data Aggregator node.
• Operational Note: This is an expected display limitation when using SNMP discovery for FT DA pairs. It is recommended to document this behavior as a known display caveat in your internal operational procedures.