Aviz Networks outlines ONES 2.1 with a ONE Data Lake and multi-NOS telemetry

Aviz Networks’ ONES 2.1 release adds a ONE Data Lake integration with AWS S3 and Splunk, extends telemetry beyond SONiC to multi-NOS environments, and updates AI-Fabric support with RoCE-based anomaly detection. For enterprise IT and security teams, the changes affect how telemetry is stored, correlated, and used for operations and troubleshooting across mixed networks.

Research Overview

The vendor describes ONES 2.1 as an update focused on network visibility, orchestration, and support workflows. The post attributes the update to new telemetry inputs, storage and analytics options for telemetry, and orchestration tools for network configuration and topology representation.

In the same release description, Aviz Networks highlights monitoring additions for SSD health and expanded support for anomaly detection in AI-Fabric networks. The article frames these updates as additions to the rule engine and related monitoring and alerting paths.

Key Findings

ONES 2.1 introduces integration for telemetry storage using AWS S3 and Splunk via a “ONE Data Lake.” The vendor says this enables migration of ONES telemetry data to storage nodes hosted in cloud or on premises for later analytics and trend analysis.

The release also expands network telemetry support to Cisco NX-OS, Arista EOS, and Cumulus NOS. The article positions this as adding multi-vendor observability beyond SONiC-based deployments.

Technical Breakdown

For storage and analytics, the post states that ONES 2.1 includes a cloud data lake with AWS S3 and Splunk integration. It describes the purpose as moving ONES telemetry data to customer-defined storage nodes for analytics use cases.

For SONiC support, the vendor adds SSD health monitoring tied to mean time to failure of one to 1.5 million hours and ties monitoring needs to SSD failures reported as a replacement driver in data centers. The post also describes AI-Fabric anomaly detection by incorporating RoCE-related metrics into a rule engine and using interface, queue, and PFC counters, alongside existing failure detection metrics such as link and device failures.

Operational Impact

On orchestration, the post describes a Network Config Illustrator that generates visual topology representations from input configuration files to help users depict and analyze network structure. It also mentions access to “Over 70+ Pre-Validated Templates” via a YAML template repository.

The article further describes an improved Fabric Manager CLI (FMCLI) with extended support for multi-vendor environments that includes x86 and ARM devices. It says FMCLI adds multi-session support to maintain session integrity and avoid accidental overrides.

Leadership Perspective

The vendor’s narrative links the ONES 2.1 changes to support team troubleshooting for AI-Fabric deployments and to earlier detection of anomalies. It also presents the orchestration additions as tools that support configuration management workflows and topology understanding.

In the FAQ section, Aviz Networks summarizes the added capabilities as ONE Data Lake integration, multi-NOS telemetry, SSD health monitoring, AI-Fabric anomaly detection with RoCE metrics, and orchestration updates including topology tooling and pre-validated templates. The same section states that multi-NOS telemetry enables centralized visibility and management across diverse vendor environments.

Blog Signals brief: ONES 2.1 expands Aviz Networks’ telemetry pipeline with a ONE Data Lake for AWS S3 and Splunk, broadens observability to multi-NOS environments, and adds SSD health monitoring and RoCE-based AI-Fabric anomaly detection, alongside orchestration tools for topology visualization, templates, and enhanced FMCLI operations. This fact-based summary of the vendor blog is intended to support enterprise decision-makers evaluating how the update could affect monitoring, storage, and operational workflows.