Problem Statement
Avaya Aura Device Services (AADS) node reports a minor alarm indicating that the AADS component has lost synchronization with its configured time server.
Impact
Time drift can affect logging accuracy, certificate validation, authentication, and correlation of events across Avaya Aura components. The reported severity is minor, but the condition should be corrected to maintain stable platform operation.
Alarm
avAADSTimeServerSynchronizationLost
Troubleshooting Steps
- Confirm the active alarm details in the monitoring dashboard for the Avaya Aura Device Services node. Verify the maintenance object is avAADSTimeServerSynchronizationLost and the description indicates synchronization with the time server is lost.
- Check whether the alarm is a duplicate of an existing active request or incident for the same AADS node and alarm. If it is a duplicate, merge or associate it with the active request according to support process.
- Verify the AADS node has network connectivity to the configured time server or NTP source. Check routing, firewall rules, DNS resolution if a hostname is used, and UDP/123 reachability where applicable.
- Review the AADS or underlying platform time/NTP configuration and confirm the configured time server values are correct and reachable from the node.
- Check the current system time, timezone, and synchronization status on the AADS node using the supported operating system or product administration tools.
- If the configured time source is unavailable, restore the time source or update the AADS node to use an approved reachable time server following the customer change-control process.
- After restoring synchronization, monitor the AADS node and confirm the avAADSTimeServerSynchronizationLost alarm clears from the dashboard.
- If synchronization does not recover after verifying configuration and reachability, collect relevant AADS/platform logs and escalate to the appropriate Avaya support path.
Resolution
Restore synchronization between the Avaya Aura Device Services node and its configured time server by correcting time-server reachability, configuration, or availability issues. Confirm the alarm clears in monitoring. If the alert is a duplicate of an already tracked incident, merge or close the duplicate per support process.