American Data Networks ONES 3.0 details multisite monitoring and SONiC support

ONES 3.0 adds a multisite application that aggregates ONES rule-engine health data across geographically distributed data centers, plus SONiC support updates including tech-support collection, syslog severity filtering, and ServiceNow ticketing tied to rule conditions. The changes affect how enterprise teams monitor global network health and route incidents through ITSM workflows.

Research Overview

The vendor describes ONES 3.0 as an update focused on scaling data center operations and expanding support for SONiC. The post highlights two feature areas: ONES Multisite for consolidated monitoring and ONES 3.0 enhancements for SONiC operations via tech support tooling, syslog filtering, and ServiceNow integration.

In the baseline ONES rule-engine model, incident detection and alert generation are scoped to the site managed by a given controller. The blog frames ONES Multisite as addressing the operational gap created when enterprise administrators need a cross-site view.

Key Findings

ONES Multisite enables geographically distributed ONES instances to register with a central multisite application, then periodically poll each site for the number of managed devices and the number of critical alerts. The multisite UI presents those results on a map, including site health status and last contact times.

The blog states that users can log in to individual data centers for more detailed information when needed. It also describes a color and blinking scheme to indicate whether a site is reachable with no critical alerts (green blink), reachable with critical alerts (amber blink), or not reachable (red).

Technical Breakdown

For ONES Multisite registration, the UI requires a site name, the multisite IP, and geographical coordinates using latitude and longitude in N and E. The post notes that the site coordinates can be auto-populated by default and overridden when required.

After registration, the multisite application “regularly gather[s] data” from each site for endpoint counts and critical alert counts. The blog also specifies how the ONES Tech Support feature works for SONiC: users select a managed switch in the UI, trigger a tech-support action, and the controller executes the underlying command and notifies the user when the download file is ready.

Product Update

The ONES 3.0 SONiC Tech Support feature is presented as a simplified method for collecting system information, logs, configuration data, core dumps, and other materials used for troubleshooting. The stated goal is to avoid manual steps such as logging into each switch, running commands, and downloading files individually.

The blog also covers syslog message handling in ONES, stating that users can view and download syslog messages through the ONES UI. ONES 3.0 adds filtering by severity levels, including error, warning, and an option to show all messages.

Operational Impact

The post explains that the ONES Rule Engine monitors configured thresholds and creates alerts for conditions such as sudden CPU usage surges, heavy traffic bursts, and component failures like PSU or FAN issues. It describes the ServiceNow integration as connecting ONES rule and alert processing to ticket creation in the ServiceNow Incident Management component.

According to the blog, when an ONES rule condition is met, ONES automatically logs a corresponding ticket in ServiceNow. The article positions this as a way to align automated alerting with incident workflow execution in an enterprise ITSM tool.

ONES 3.0 centers on consolidated multisite visibility for distributed data center monitoring and adds SONiC-focused operational functions, including remote tech-support dump collection, syslog severity filtering, and automated ServiceNow ticket logging when rule conditions occur. Blog Signals brief is a fact-based summary of the vendor blog.