Scope
This document applies to xNode2, running firmware version 1.3.0 or later.
It’s important to note that the information displayed on this page and in this document generally points to a network issue, not a problem with the xNode2 hardware or software—in other words, the unit is reporting the issue, not causing it.
Introduction
xNode2 firmware version 1.3.0 introduced the Net Health page.
Network Health History
Displays network health statistics for the past 24 hours. Data is shown on a per-minute basis for the most recent hour, and on a per-hour basis for older periods. Only data collected since the last system startup is retained; earlier periods are displayed in gray.
Each row represents a specific statistic:
Most recent hour: Shown per minute using small ovals. Red indicates an issue occurred during that minute.
Earlier hours: Shown per hour using larger ovals.
Click a large oval to expand that hour into minute-level detail. The previously expanded hour will collapse back into a single large oval.
Hover over any oval to view detailed information for that time period.
Hover over the icons at the beginning of each row to display a tooltip describing that statistic. Click the icon to open the related section of this documentation in a new window.
Clock Sync
This section relates to audio clock synchronization. Click the “^” at the right end of the line to collapse all the values into a single display.
Poor Sync Quality
This line reports the worst (lowest) clock sync quality for the period. Scale is 0 to 12, with 12 being perfect synchronization.
PTP Leader Changed
This indicates that the system has selected a new PTP leader. While normal during startup or reconfiguration, unexpected changes during steady operation may indicate clocking instability or network issues.
Normal to show no data if PTP Sync is not used
PTP Leader Announce Interval Too Slow
Indicates that the PTP leader’s announce interval is slower than expected. This is typically a configuration mismatch—ensure that all devices in the PTP domain use the same announce interval.
Normal to show no data if PTP Sync is not used
PTP Leader Sync Interval Too Slow
Indicates that the PTP leader’s sync interval is slower than expected. This is typically a configuration mismatch—ensure all devices in the PTP domain are using the same sync interval.
Normal to show no data if PTP Sync is not used
Livewire Leader Changed
This indicates that the system has selected a new Livewire clock leader. While normal during startup or reconfiguration, unexpected changes during steady operation may indicate clocking instability or network issues.
Unexpected Livewire Clock Leader
Indicates that Livewire leader packets were received from a device other than the current leader. A small count may occur during a normal leader election or transition, but sustained or high counts suggest a leader conflict or misconfiguration.
AoIP Receive
This section relates to the AoIP receivers. Click the “^” at the right end of the line to collapse all the values into a single display.
Overflows
This indicates that received AoIP packets contain RTP timestamps significantly ahead of the device’s current clock. This may point to a synchronization issue (e.g., PTP misalignment) or a poorly behaving stream sender.
Underflows
This line shows AoIP packets with RTP timestamps that are too far behind the device's current time, which may indicate a synchronization issue or a poor stream sender.
Sequence Resets
This indicates that the RTP sequence numbers in a received AoIP stream have reset. In many cases, this suggests the transmitting AoIP device, stream, or sender process has restarted.
Sequence Errors
This line shows RTP sequence errors observed in received AoIP streams, which may indicate a high-traffic or unstable network.
Defective Packets
Indicates that received AoIP packets could not be placed into the receive buffer. This is typically caused by unexpected or invalid RTP timestamps from the sender.
Dropped Packets
This line shows dropped, missing, or lost AoIP packets, which may indicate network congestion, instability, or misconfiguration.
Duplicate Packets
This line shows duplicate AoIP packets received, which may indicate network instability or misconfiguration.
Malformed Packets
This line shows AoIP packets received with malformed headers, which may indicate a misconfigured or malfunctioning device on the network.
SSRC ID Changes
This line shows RTP SSRC ID changes observed in received AoIP streams, which may indicate a change in the stream's source or multiple senders sending to the same destination, neither of which is supported.
SSRC ID (Synchronization Source Identifier) is a key field in RTP (Real-time Transport Protocol) streams used in audio/video networking (like AES67, Livewire, VoIP, etc.).
Important behaviors
Randomly generated when a stream starts
Should be unique within a session
Can change if:
A device reboots
A stream restarts