What's New in Aviz ONES 3.1: Enhanced SONiC Management and Automation
December 17, 2025
ONES & SONiC
Summary
ONES 3.1 introduces a new GUI-based fabric configuration experience that replaces manual YAML edits with an intuitive, drag-and-drop orchestration workflow. It simplifies device onboarding, enables real-time topology visualization, supports granular configuration, and adds Day 2 flexibility for small and mid-sized enterprises.
Introduction
Earlier versions of ONES Fabric Manager used predefined intent-based YAML templates to generate configurations automatically. This simplified deployments, but limited granular control and required manual file modification.
ONES 3.1 solves this by introducing a powerful graphical interface that lets administrators onboard devices, design topologies, configure fabrics, and make changes visually. This update is designed for enterprises that want simplicity, precision, and real-time visibility without relying on YAML-based workflows.
What Is New in ONES 3.1 and Why Does It Matter?
ONES 3.1 introduces a fully visual, GUI-based fabric configuration interface that replaces manual YAML edits and gives administrators complete control over fabric, switch, and port-level settings.
The update enables faster deployment, intuitive topology design, and real-time visualization across small and mid-sized enterprises.
How Does the New GUI Improve Fabric Configuration?
The GUI brings an interactive drag and drop experience that lets administrators design topologies, configure links, and fine-tune settings from a single dashboard.
Key Improvements
- Visual configuration instead of YAML editing
- Real-time topology visualization
- Faster deployments with simplified workflows
- Dynamic changes without reloading templates
How Does ONES 3.1 Simplify Device Onboarding?
Administrators can onboard devices by dragging them into the topology workspace, selecting interfaces, and creating links visually.
Onboarding Capabilities
- View all switches and host servers in the inventory
- Drag and drop devices directly into the fabric
- Select interfaces to create connections
- Dynamically configure links in a few clicks
ONES 3.1 also supports adding external devices that are not part of the existing inventory. Administrators only need to provide credentials and basic network layer information to onboard these devices into the orchestration workflow.
What Key Features Does the GUI-Based Orchestration Provide?
Key Features
- Interactive fabric visualization for creating, configuring, and managing devices and links
- Granular control across fabric, switch, and port levels
- Dynamic configuration without modifying YAML files
- Real-time monitoring from a unified dashboard
These capabilities give enterprises more control and flexibility during deployments and expansions.
How Does ONES 3.1 Improve Day 2 Operations?
ONES 3.1 lets administrators modify existing templates or create new ones based on operational needs, allowing quick updates without rebuilding configurations from scratch.
Day 2 Advantages
- Modify deployed fabrics visually
- Update templates without re-deployment
- Faster operational changes
- No need for manual YAML editing
ONES 3.1 also introduces GUI-based orchestration for IP BGP CLOS designs, making deployment and management even more seamless.
Quick Checklist for ONES 3.1 GUI Orchestration
You need ONES 3.1 if you want:
- Visual drag and drop topology design
- Granular fabric, switch, and port-level configuration
- Easy device onboarding, including external devices
- Real-time topology visualization
- Simplified Day 2 operations without YAML edits
- Faster deployments for small and mid-sized enterprises
Conclusion
ONES 3.1 elevates fabric orchestration by shifting from YAML-driven workflows to a GUI-based experience. The platform now supports intuitive device onboarding, dynamic topology creation, granular configuration, and simplified Day 2 management. As ONES continues to evolve, upcoming updates will introduce expanded protocol support and even more intuitive orchestration features.
Frequently Asked Questions
What is the biggest change in ONES 3.1 compared to earlier versions?
Earlier versions used predefined YAML templates to generate configurations automatically. That simplified deployments but limited granular control and required manual file edits when anything needed changing. ONES 3.1 replaces that with a drag-and-drop GUI so administrators design topologies, configure fabrics, and make changes visually without touching a YAML file.
How does device onboarding work in the ONES 3.1 GUI?
Administrators drag devices directly into the topology workspace, select interfaces, and create links in a few clicks. All switches and host servers in the inventory are visible from the start. External devices not already in the inventory can also be onboarded by providing credentials and basic network layer information, no template modification needed.
What level of configuration control does the ONES 3.1 GUI provide?
Administrators get granular control at the fabric, switch, and port levels all from a single dashboard. Configuration changes happen dynamically without reloading or modifying YAML templates. Real-time topology visualization shows the state of the network as changes are made rather than requiring a separate validation step after the fact.
How does ONES 3.1 improve Day 2 operations for network teams?
Administrators can modify deployed fabrics visually, update templates without re-deploying, and make operational changes faster without manual YAML edits. ONES 3.1 also adds GUI-based orchestration for IP BGP CLOS designs. Changes to existing deployments no longer mean rebuilding configurations from scratch or navigating template files to find the right parameter.
Which organisations is ONES 3.1 specifically designed for?
ONES 3.1 is built for small and mid-sized enterprises that want simplicity, precision, and real-time visibility without relying on YAML-based workflows. The GUI-based experience is designed to make fabric orchestration accessible to teams that do not have dedicated automation engineers managing configuration files for every deployment or change.
Why did YAML-based fabric configuration create problems for teams that needed more granular control?
YAML templates simplified deployment by generating configurations automatically but that same automation removed direct control. When something needed a specific change outside the template's defaults, administrators had to modify files manually. That required understanding the YAML structure, risked introducing errors, and slowed down any change that did not fit the predefined template logic.
How does real-time topology visualisation change how teams manage fabric deployments?
With earlier versions, teams configured fabrics through templates and validated results separately. Real-time topology visualisation in ONES 3.1 shows the state of the network as administrators work. Links, interfaces, and device connections are visible immediately so teams confirm what they have built while they build it rather than discovering problems during a separate validation step later.
How does adding external devices to the ONES 3.1 topology work for devices not already in the inventory?
External devices that sit outside the existing inventory can be onboarded by providing credentials and basic network layer information. The device then joins the orchestration workflow without requiring a template rebuild or manual YAML modification. Teams managing environments with devices from outside the standard inventory list are not blocked from bringing everything under the same orchestration layer.
Ready to explore GUI-based SONiC orchestration with ONES 3.1?
Visit the ONES product page
Request a demo from the Aviz Networks team
Explore the full ONES documentation
