1 of 100

ONES-3.0

ONES GA v3.0

Open Networking Enterprise Suite (ONES)

Introduction and Overview

Open Networking Enterprise Suite (ONES) is a Network Orchestration, Visibility, and Assurance solution for multi-vendor and multi-NOS operated Network Infrastructure. ONES provides a one-stop solution from delivering deep visibility into your datacenter networks to extending 24x7 support functions for SONiC. It also hosts a powerful analytics engine that assists users to identify network issues and troubleshoot their networks, in case of common network anomalies and disruptions.

ONES uses Auto-discovery for SONiC devices and a YAML or CSV-based template for adding non-SONiC devices during the onboarding process and continuously collects streaming telemetry data from them to provide insights on:

Data Center Inventory
Network State
Platform and System Health
Control and Data Plane resource Utilisation
Traffic Utilisation
Software Compliance
AI Fabric
Underlay and Overlay protocols view

ONES monitors various control and data plane metrics to provide these insights.

Rule Engine

ONESv3.0 application has the capability to trigger notifications via Slack app notifications when certain user-defined threshold values are breached.

In data centre operations, a rule engine with alerts for various metrics is essential for proactive monitoring and management of critical components and services. Rule Engine pushes the configured rule notification in case any device breaches the threshold value configured under the rule to SLACK Channel, Zendesk Support and ServiceNow Ticketing Service integration

Let's see the different types of rule engine metrics for specific Entity/features in a data centre environment

CPU and Memory Utilisation
Fan and PSU LED status
Traffic Bandwidth
ASIC Routes
Health Services
Traffic Errors and Discard Counters
BGP Neighbours flapping notification
Device down status
Link flap status
Device SSD Memory Utilization, Health and Temperature
ROCE Counters

ONES Orchestration

ONES orchestration provide network admins to automate the fabric configuration using configuration templates for provisioning physical interfaces, layer 3 configuration for building IP-CLOS fabric using

BGP as a routing protocol including BGP-unnumbered
Symmetric/Asymmetric IRB
BGP Peering with PO
L2/L3 MC-LAG
EVPN MultiHoming
Layer2 Leaf-Spine (L2/L3 Mode)
Rack-to-Rack Deployment
BGP Peering over MC-LAG PeerLink
BGP Peering using separate Link between MC-LAG Peers
SFLOW
DHCP Relay
RoCE Config
AI Fabric config
SAG / SVI
NTP, SNMP, SYSLOG
Incremental Config update for L2VNI/L3VNI
Enhanced backup and restore options via UI
Enhanced API support - Config Replace

ONES orchestration not only configures the fabric but also make sure the Fabric is operational by doing verifying the configuration at every stage.

ONES provides north bound API access for configurations originating from external orchestration tools.

Data Lake

A data lake is a centralized repository that allows you to store vast amounts of structured, semi-structured, and unstructured data in its raw format. Unlike traditional data warehouses where data is stored in a structured manner, a data lake retains the data in its native format until it's needed for analysis or processing. ONES provide the capability to store the RAW data of all the Metrics to Cloud and then user will be able to use that RAW data for any deployment or any other use cases.

Here are key components and characteristics of a ONE DL.

Storage of Diverse Data Types: A data lake can store various types of data, including structured data (like relational databases), semi-structured data (like JSON, XML), and unstructured data (like documents, images, videos). This flexibility allows organizations to ingest and store data from different sources without the need for extensive preprocessing.
Scalable and Cost-Effective Storage: Data lakes are typically built on scalable storage systems, such as cloud-based object storage (e.g., Amazon S3, Azure Data Lake Storage) or Splunk . These systems can efficiently handle large volumes of data and offer cost-effective storage solutions.
Schema-on-Read Approach: In contrast to traditional data warehouses that use a schema-on-write approach (where data must be structured and conform to a predefined schema before storage), data lakes adopt a schema-on-read approach. This means that data is stored in its original form, and the schema is applied at the time of data retrieval or analysis. This flexibility allows users to apply different schemas and interpretations to the same dataset based on their analytical needs.
Support for Big Data Processing and Analytics: Data lakes serve as a foundational component for big data analytics and processing. Users can perform various analytics tasks, including exploratory data analysis, data mining, machine learning, and real-time analytics, directly on the data lake. Tools like Apache Spark, Apache Hive, and Presto are commonly used for querying and processing data stored in data lakes.
Support for Data Discovery and Self-Service Analytics: Data lakes enable data discovery and self-service analytics, empowering users to explore and analyze data without extensive dependencies on IT teams. Data scientists, analysts, and business users can access relevant data directly from the data lake, speeding up insights generation and decision-making processes.

In summary, ONE DL provides a flexible and scalable platform for storing, managing, and analyzing diverse data types at scale. By leveraging a schema-on-read approach and supporting various analytics tools, ONE DL facilitate advanced data analytics and enable organizations to derive valuable insights from their data assets. However, proper governance, security, and metadata management are crucial to ensure the usability, reliability, and integrity of data lakes.

ONES Application

Overview

Below are the primary components of ONES Application

ONES Telemetry Collector(s) for Network Visibility
Server Telemetry
ONES Rule Engine
ONES Orchestrator for Fabric Configuration
ONES Supportability
ONES Security
ONE DL (DataLake)

ONES Telemetry Collector(s) and Visibility

Overview

ONES Telemetry Collector(s) and Analytics bring truly unparalleled visibility across all your switches running SONiC (both community and vendor distros), regardless of the underlying ASIC. ONES front end (UI), will enable network admins to;

Manage inventory of your network devices running SONiC on Broadcom, Cisco, Marvell, and Nvidia ASICs
View the topology of the entire fabric across multiple hardware platforms, and network operating systems
Monitor traffic, system health, bandwidth utilization, & more

Topology is the default page for ONES application

Topology page can be filter as per Datacenter or AI-ML type topology
This page shows Underlay, Overlay, RoCE telemetry view & other Advance Filtering view
The same Topology page allows a user to connect to the device SSH and Console
Enhanced Traffic Page shares the PFC enabled Interfaces
Protocol page shows new metrics of VXLAN, LACP, MCLAG information and QoS related metrics.

DataCenter Topology Type

AI-ML Topology Type

Track Switch CPU/memory consumption, bandwidth, link failures, traffic errors, and more in real-time
Proactively identify and resolve issues that may lead to network downtime
Instantly connect to individual devices for maintenance and troubleshooting

Inventory Page

Syslog extraction for device, Console access, Add/Remove Non-SONiC devices via YAML or CSV, export or download inventory
Firmware information is added in Device details section

ONESv3.0 offers different licensing modes

SONiC Trail (8 device & 30Days)

Network Telemetry
- Topology visualization
- Inventory (Hardware & System, PSU, Fan, SSD etc health)
- Control Plane (BGP, LACP, MCLAG, VXLAN)
- Data Plane (ASIC Tables Utilization)
- Links (Ports Inventory, Transceivers, Flaps, Cabling)
- Traffic (In/Out Packets, Errors, Queue Counters, RoCE Visibility)
Support
- Image Management (ZTP, Custom)
- Access & Management (SSH, Console, SYSLOGs, Reboot)

SONiC Support

Network Telemetry
- Topology visualization
- Inventory (Hardware & System, PSU, Fan, SSD etc health)
- Control Plane (BGP, LACP, MCLAG, VXLAN)
- Data Plane (ASIC Tables Utilization)
- Links (Ports Inventory, Transceivers, Flaps, Cabling)
- Traffic (In/Out Packets, Errors, Queue Counters, RoCE Visibility)
Support
- Image Management (ZTP, Custom)
- Access & Management (SSH, Console, SYSLOGs, Reboot)

SONiC NetOps (Includes SONiC Support)

Orchestration
- Intent-Driven Orchestration for IPCLOS, L2LS, EVPN-VXLAN, EVPN-Multihoming
- Policies, System Config & QOS
- Day 2 Operations (Incremental Config etc) with API
- Config Generate, Validate, Apply & Diff
Integration & Alerting
- Rule Engine with alerting on metrics
- Integration with Slack, Zendesk and ServiceNow.
ONE-DL
Network Performance Monitoring
- Packet Loss & Latency

ONES Time Scale Metric Calculation

Overview

ONES Agent pushes all the telemetry at every 20 seconds to the ONES Collector, so DB will have the values of every 20sec, Further as per time series selection ONES-UI plots the Graph with different average values.

Below are the Average values Calculated by ONES-UI as per Time-Scale:

ONES Rule Engine

Overview

In data center operations, a rule engine with alerts for various metrics is essential for proactive monitoring and management of critical components and services. Let's discuss the need for rule engine alerts for specific metrics in a data centre environment

CPU and Memory Utilisation
Fan and PSU LED status
SSD Memory Utilization, Health and Temperature Status
Traffic Bandwidth
ASIC Routes
Health Services
Device Down alerts
BGP Neighbour Down alter
Component failure
Interface Flap Alerts
Traffic Errors and Discard Counters
PFC Counters
Device Queue Counters

Rule engine alerts ensure efficient resource utilization, timely troubleshooting, early detection of potential issues, and overall operational stability within the data centre environment.

Notification

ONES-App is capable of triggering breached threshold values to

Slack Channel
Zendesk Support
ServiceNow

Rules are categorized based on the metric hierarchy

Device Level
Interface Level

List of all the Metrics Supported by Rule Engine with possible units and measured value a user can use

Hierarchy

Metrics

Unit

Measure

Value

Device

CPU Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Device

Memory Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Device

Failed Fans

Count ()

MIN/MAX

Count

Device

Failed PSU

Count ()

MIN/MAX

Count

Device

CPU Core Temperature

Celsius ()

AVG/MIN/MAX

Celsius

Device

PSU Temperature

Celsius ()

AVG/MIN/MAX

Celsius

Device

FAN Speed

Percentage (%)

AVG/MIN/MAX

0/100

Device

ASIC IPv4 Routes Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Device

ASIC IPv6 Routes Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Device

BGP Nbrs Operationally Down

Count ()

AVG/MIN/MAX

Count of Nbrs

Device

FRR Container CPU Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Device

Syncd Container CPU Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Device

Device Down

Device

Queue Counter

Count()

AVG/MIN/MAX

Count

Device

SSD Health

Percentage(%)

0/100

Device

SSD Temperature

Celsius ()

AVG/MIN/MAX

Celsius

Device

SSD Memory

Percentage(%)

0/100

Interface

Int Flap

Interface

PFC Counters

Count ()

AVG/MIN/MAX

Count

Interfaec

Queue Counters

Count ()

AVG/MIN/MAX

Count

Interface

TX Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Interface

RX Utilization

Percentage (%)

AVG/MIN/MAX

0/100

Interface

In Errors

Count ()

AVG/MIN/MAX

User defined

Interface

Out Errors

Count ()

AVG/MIN/MAX

User defined

Interface

In Discards

Count ()

AVG/MIN/MAX

User defined

Interface

Out Discards

Count ()

AVG/MIN/MAX

User defined

Interface

Tranx TX Power

dBm

AVG/MIN/MAX

User defined

Interface

Tranx Rx Power

dBm

AVG/MIN/MAX

User defined

Interface

Tranx Temperature

Celscius ()

AVG/MIN/MAX

User defined

Interface

Tranx Voltage

Volts ()

AVG/MIN/MAX

User defined

ONES Orchestration

Why do we need Network Orchestration?

Orchestration refers to tasks or actions required to achieve a set of objectives for your Network Infrastructure operations

A centralized application like ONES translates these objectives into a network configuration template, applies and monitors to validate the operational efficiency and functionality

Automated tasks are performed on your Network Fabric in a purposeful order and each step is verified for success before moving to the next

ONES Orchestration - Overview

ONES Orchestration function, referred to as Fabric Manager (FM), lets you compose, deploy, and validate network configurations across any SONiC, be it a Community version or a Vendor distro.

As part of the initial release, ONES Orchestration supports to

Create and configure CLOS topology for ToR, Leaf, Spine, and Super-Spine layers
Apply and validate configurations pre- and post-deployment
Compare running configs against applied configs at any point
Upgrade devices with a single click via ZTP or custom NOS images
Restore & Backup configuration feature
Yaml-based config for VXLAN, MCLAG, BGP IP CLOS & EVPN(L2VPN), EVPN Multihoming, L3 EVPN Symmetric IRB, L3EVPN symmetric IRB with MCLAG.
RoCE configuration parameters supported
Automate Configuration of interfaces, layer 3 interfaces, BGP-unnumbered and Common Services like NTP, SNMP, SYSLOG etc.

ONES Orchestration use cases are configured using a set of pre-defined YAML-based templates on ONES Web User Interface

FMCLI

Fabric Manager CLI

FMCLI is an Industry standard Command Line Interface

Once the user installs Orchestrator Agent (Fabric Manager Agent) on the device, it enables FMCLI

FMCLI provides a user interface to configure all the open standard protocols and is user-friendly

To use FMCLI, the user can run fmcli command on the device to enter in the configuration mode and can configure the protocols or any other required feature

Example of BGP config using fmcli

admin@fmcli:~$ fmcli
fmcli# configure terminal 
fmcli(config)# router bgp 1001
fmcli(config-router)# neighbor 10.10.10.1 remote-as 100
...
...

Supported FMCLI Features

Zero Touch Provisioning
Image Management
Configuration Management
Interface Management
VLAN's
Spanning Tree Protocol
VXLAN
L2 Forwarding Database
LLDP
LACP
DHCP Relay
IP Management
ARP
PING
Traceroute
Routing
BGP*
NTP
SYSLOG
Platform Details
SFLOW
NAT
Forward Error Correction
BFD
SNMP
VRF
AAA & TACACS
Drop Counters
ERSPAN
IP Based ACL
Prefix-list
EVPN Multihoming
Route-map
RoCE

NetOps API

NetOps API can be used to integrate into customer-running applications, and can be used to perform the Day 1 and Day N configuration, Using NetOps API a user can do all the configurations and can also perform the Partial Configuration

Few Operations can be done By NetOps API

Day-1 Operations: intent upload
SONiC NOS upgrade
Device Reboot
Difference between the Golden Config and running configuration //running & applied configuration
Backup Running Configuration
Replace Config
- If config is done by the ONES then only the user can use this replace option to modify the config.
ZTP Upgrade

ONE DL

Data Lake

Here are key components and characteristics of a ONE DL 1.0.0

Storage of Diverse Data Types: A data lake can store various types of data, including structured data (like relational databases), semi-structured data (like JSON, XML), and unstructured data (like documents, images, videos). This flexibility allows organizations to ingest and store data from different sources without the need for extensive preprocessing.
Scalable and Cost-Effective Storage: Data lakes are typically built on scalable storage systems, such as cloud-based object storage (e.g., Amazon S3, Azure Data Lake Storage) or Splunk . These systems can efficiently handle large volumes of data and offer cost-effective storage solutions.
Schema-on-Read Approach: In contrast to traditional data warehouses that use a schema-on-write approach (where data must be structured and conform to a predefined schema before storage), data lakes adopt a schema-on-read approach. This means that data is stored in its original form, and the schema is applied at the time of data retrieval or analysis. This flexibility allows users to apply different schemas and interpretations to the same dataset based on their analytical needs.
Support for Big Data Processing and Analytics: Data lakes serve as a foundational component for big data analytics and processing. Users can perform various analytics tasks, including exploratory data analysis, data mining, machine learning, and real-time analytics, directly on the data lake. Tools like Apache Spark, Apache Hive, and Presto are commonly used for querying and processing data stored in data lakes.
Support for Data Discovery and Self-Service Analytics: Data lakes enable data discovery and self-service analytics, empowering users to explore and analyze data without extensive dependencies on IT teams. Data scientists, analysts, and business users can access relevant data directly from the data lake, speeding up insights generation and decision-making processes.

In summary, ONE DL provides a flexible and scalable platform for storing, managing, and analyzing diverse data types at scale. By leveraging a schema-on-read approach and supporting various analytics tools, ONES DL facilitate advanced data analytics and enable organizations to derive valuable insights from their data assets. However, proper governance, security, and metadata management are crucial to ensure the usability, reliability, and integrity of data lakes.

ONES Cloud Service Integration

As of now ONES support 2 different platforms where customer can get the RAW data

Splunk
Amazon S3

Users can control the behaviour of the Catalog

Users will have the option to tune the frequency of streaming the metric to the cloud platform, user will have the option to tune frequency starting from 1 minute to 60 minutes.

Users can select/unselect the Network state metrics using the above catalogue option

ONES Supportability

AVIZ Support Overview

Network Assurance helps the NetOps team validate policy and security compliance checks before making a change in network configuration, an intelligent set of proactive and predictive techniques that validate the Network for readiness without error, conflicts, and disruptions

Aviz Support team is located across four timezones offering 24x7 SONiC and related product support for multi-vendor switches and ASICs. Using our support portal, we offer you to

Collaborate with our SONiC experts to expedite your evaluations
Speed up your SONiC troubleshooting SLAs to as low as 15 minutes regardless of the underlying Switch/ASIC platform
Minimize operational delays by centralizing issues across multiple platforms

Supports Options are available:

Integrated Chat
Submit a Ticket
Send an email to support@aviznetworks.com

ONES Supportability

To connect with customer support users can choose the support option available on ONES-UI

ONES Security

ONES is a support application for SONiC stack. It is designed for customer's engineering team such as SRE’s, HW and SW engineering teams for their daily network diagnosis and troubleshooting needs. In addition to that ONES exposes the API to integrate with external tools or customer homegrown applications.

This section describes how ONES authenticates users and secures communication.

RBAC: Role-Based Access Control

Secure Access to the Application

ONES application provides HTTPs over standard port 443 supporting both self-signed and CA signed certificates.

HTTPS Support CA Signed
HTTPS Self Signed

Secure Access to the switch*

ONES utilizes gRPC infrastructure to communicate with switch agents. TLS (Transport Layer Security) is the primary security protocol used by gRPC to secure communication between the client and the server. TLS provides authentication, confidentiality, and integrity of data. Authentication is achieved using digital certificates, which verify the identity of the client and the server.

With an added extra layer of security, ONESv3.0 support Certificate based communication between switches and ONES Controller, and all the metrics will be streamed using the certificate-based encryption

ONESv3.0 allows a user to use password based authentication between Controller and Switches, all the communication can be done by the implementation of password based agent.

Agent Based Deployment with TLS certificate

Transport Layer Security (TLS) is a crucial protocol that ensures secure communication between ONES Controller and Agent, Whenever Agent will register to ONES server and further it will start sending the update it will encapsulate all the metrics and will do the encryption based on certificate provided at the time of installation, by using this all the communication will be encrypted between ONES agent and ONES controller TLS relies on digital certificates issued by trusted Certificate Authorities (CAs) to authenticate servers and sometimes clients. These certificates validate the identity of the entities involved in the communication and establish trust in the encrypted connection.

Password based Agent Deployment

Password-based authentication can be implemented between the agent and controller, allowing all devices to register using a shared password. This method relies on OpenSSL for encrypting the communication, ensuring secure transmission of credentials and data. OpenSSL employs robust encryption algorithms to safeguard the authentication process and prevent unauthorized access.

ONES 3.0 Multisite

One single solution to monitor all the data centre availability and one-click access to sites.

The ONES rule engine enables the detection of incidents and the generation of alerts, but this information is limited to the specific site managed by the corresponding controller. While this data is valuable for data center administrators to address and resolve issues, enterprise-level administrators or executives interested in the overall health of the entire network must access individual ONES instances at each data center to view the status. This process can be inefficient and cumbersome.

To solve this, ONES 3.0 Multisite provides a solution by offering a geospatial representation of anomalies across multiple sites, spread over different geographical locations, giving a comprehensive view of network health. ONES instances from data centers around the world can register with a central ONES 3.0 Multisite application. Once registered, the multisite system regularly polls each site for key data, such as the number of managed devices (endpoints) and critical alerts, and presents this information on a map, displaying individual sites and their last contact times. Additionally, ONES Multisite allows users to log in to individual data centers to access more detailed information if needed.

For a quicker glance about the health conditions, different colors and blinking patterns are used,

Green blink : Site is reachable with no critical alerts
Red blink : Site is reachable but there are critical alerts
Red : Site is not reachable

What's new?

ONES Package

Password based agent installation
ONES-Multisite Package
Server_GPU Telemetry Package

ONES UI

New Topology Page:
- DataCenter Type
- AI-ML Type
Server GPU
Ticketing Tool for Alerts
- ServiceNow
QOS Page

ONES Telemetry

Server Health metrics
- GPU Based metrics
AI Fabric Telemetry add-on

ONES Orchestration

AI Fabric configuration
RoCE configuration

ONES Rule-Engine

New Rules added for Server GPU Telemetry

Getting Started

Supported Switch Platforms and NOS

SONiC Supported Broadcom Platforms:

Speed

Vendor (Models)

Accton (AS4625, AS4630), Celestica (DS1000), Supermicro (G3748), Micas(M2-W6510-48GT4V)

10/25G

Accton (AS5812, AS5835, AS7326), Celestica(DS2000), Dell (5212, 5248), Micas(M2-W6510-48V8C)

100G

Accton (AS7712, AS7726, AS7816), Celestica (DS3000), Dell(5232)

400G

Accton (AS9716), Arista (7060), Dell (Z9332)

800G

Celestica (DS4101)

SONiC Supported Cisco Platforms:

Speed

Models

100G

8101-32H, 8102-64H

400G

8101-32FH

SONiC Supported Marvell Platforms:

Speed

Vendor (Models)

Wistron (ES1227, ES2227)

400G

Wistron (6512)

SONiC Supported NVIDIA Platforms:

Speed

Models

SN2201

10/25G

SN2010, SN2410, SN3420

100G

SN2100, SN2700, SN3700C, SN3800, SN4600C

400G

SN4410, SN4700

800G

SN5600

Vendor NOS Support:

Cumulus Linux, Arista EOS & Cisco NX-OS platforms are considered by ONES as Agent-less and supports metrics available using NVUE and EOS APIs

Vendor

NOS

Version

Arista

EOS

4.x

Cisco

NXOS

9.x

NVIDIA

Cumulus Linux

5.9, 5.11

Agent-based vs Agent-less

SONiC-based switches require ONES Agents (Agent-based) to be installed on the switch being monitored, as a pre-requisite for ONES Telemetry and orchestrator-based functions to work.

ONES Telemetry Agent
ONES Orchestrator Agent

NX-OS expose its own way of metric collection using GRPC

ONES does not support Orchestrator-based functions on Proprietary NOS (non-SONiC).

Agent requirements

SSH access
SONiC versions beyond 202012 or 202111 are supported
Only x86 intel-based architectures are supported

Scalability

ONES Function

Device/Switch Count

Telemetry for Visibility

1024

Orchestration

1024

Subscription

ONES provides the following subscriptions to manage and monitor the devices.

Subscription Type

Details

Support up to 8 devices

Support up to 16 devices

Support up to 32 devices

Support up to 64 devices

128

Support up to 128 devices

256

Support up to 256 devices

512

Support up to 512 devices

1024

Support up to 1024 devices

Free(30 Days Trial)

Support up to 8 devices

License Module Subscription

SONiC Trail License
SONiC Support
SONiC NetOps (Includes SONiC Support)

For Trail License Engineer needs to contact to AVIZ support Team.

ONES Installation

Installation Pre-requisites

Installation Overview

ONES Installation follows the below steps in the order sequence of:

License Readiness
Preparing and Installing ONES Application machine
Installing ONES Agents on SONiC Switches for Orchestrator and Telemetry
Enabling OpenConfig on non-SONiC Switches for Telemetry

License Readiness

After installation of ONES application user needs to contact AVIZ support to generate a trail license, trail license works for 8 devices and upto 30 days a customer can use.

ONES Application License (As per device count)

Trail license support feature

Telemetry Visibility (Monitor, inventory, analytics)
Add/remove Non-SONiC devices via YAML or CSV
Support (Zendesk)- Ability to open a ticket with inventory dump
Syslog access, Console/SSH access for device

To obtain a license, contact support@aviznetworks.com providing the below details;

License Duration - In Years (1-5)
Devices Count - 8, 16, 32, 64, 128, 256, 512 or 1024
ONES installation ID
Email ID: (For Account creation)

Users can get the ONES installation ID on the ONES-UI Login page after the installation

System Hardware Requirements – ONES Application

In the current release, ONES can support managing up to 1024 devices. For ONES Application Installation, the system hardware requirements vary based on the number of devices to manage;

Devices

Processor and Cores

RAM

Storage

x86/x64 based,

16-core CPU

32GB

160GB or more

x86/x64 based,

16-core CPU

64GB

320GB or more

x86/x64 based,

16-core CPU

128GB

640GB or more

x86/x64 based,

32-core CPU

256GB

1.2TB or more

128

x86/x64 based,

32-core CPU

256GB

3 TB or more

256

x86/x64 based,

32-core CPU

512GB

6 TB or more

512

x86/x64 based,

64-core CPU

1TB

12 TB or more

1024

x86/x64 based,

64-core CPU

1TB or more

20 TB or more

System Software Requirements - ONES Application

Libraries

Ubuntu 18.0 or later

docker, docker-compose

python3, python3-pip

paramiko

scp

Task

Command

Validation

Ubuntu Server

Installer file (Version 18 or higher)

lsb_release -a

Update to latest packages

sudo apt-get update

Install Docker

sudo apt-get install docker.io

docker ps

Install Docker-compose

sudo apt-get install docker-compose

docker-compose version

Install Python3

sudo apt-get install python3

python3 –-version

Install Python3-pip

sudo apt-get install python3-pip

pip3 –-version

Install Paramiko

sudo apt-get install python3-paramiko

pip show paramiko

Install SCP-Client

sudo pip3 install scp

pip show scp

ONES Application package will take care of this prerequisite at the time of installation, Package verify the availability of the dependencies first then execute the application scripts

Note* Script do not take care about the update to latest version of ubuntu

Customer Firewall Configuration (Ports to be opened)

Ports to be open from Agent(Source) to ONES controller(Destination)

These ports has to be enable on ONES Controller

ONES Service

Port Numbers

ONES Collector

50053

Ports to be open from ONES controller(source) to Agent(Destination)

These ports has to be enable on Device(Switch)

ONES Service

Port Numbers

Switch Access over SSH

ONES Monitoring

50052

Ports to be open on ONES Server for ONES Services

ONES Service

Port Numbers

gNMI Gateway (Telemetry)

9339

ONES Telemetry Database

5432

ONES Orchestrator

8787

ONES Orchestrator Database

2345

pty-server

8885

API-Server

8080

stream-processer

8093

ksqldb-server

8088

kafka-connect

8083

schema-registry

8081

broker

29092, 9101, 9092

Zookeeper

2181

ONES Collector

50053

Ports to be open for HTTPS Access

HTTPS port has to be enable if a firewall is present in between User-machine and ONES-Controller

ONES Service

Port Numbers

ONES Web GUI

443

These port numbers should be available to use and all ports must be allowed in the firewall if the Database server and devices are in the different DMZ zone

sudo iptables -L // This command can be used to verify the used ports

Network Switch (Managed Node) Configuration Requirement

SSH is enabled
Network Reachability from ONES Application
OpenConfig feature is enabled (for non-SONiC Switches)

Browser Requirements for ONES Web User Interface access

Google Chrome version 107 or later
Mozilla Firefox version 106 or later

ONES Multisite

Ubuntu 18.0 or later can be used for Multisite app
ONES Multisite has to be installed on separate server
ONES Multisite use TCP port 443
Reachability between ONES sites and Multisite instance.

Download ONES Package

User can download the Latest version of ONES on Support Portal.

Work with Aviz Sales/Support contact to create an account on Aviz Networks Support Portal
Click on the Downloads section, under ONES, click to download ONES Release 3.0
- File to install on Ubuntu
  - ONES 3.0 Installation package
- File to install on VMware, ESXI, vSphere, and vCenter setup
  - ONES 3.0 OVA
- File to install on Hypervisor, KVM, LibVirt Manager
  - ONES 3.0 QCOW2
- To download ONES Multisite application
  - ONES 3.0 Multisite
- To download ONE-DL
  - ONE-DL 1.0

Installing ONES Application

These steps will guide a user how to install a tar-ball package on base Linux based machine

ONES Application system - Installation Steps

Enable super-user mode

user@ones-application:~$ sudo su

Extract the contents of the downloaded ONES Installer tar.gz file

root@ones-application:~$ tar -xvf ONES-3.0.0.tar.bz2

Go to ONES-3.0 folder on the server machine

root@ones-aplication:~$ cd ONES-3.0

Run ones-installer.sh to Install the ONES application function

root@ones-application:~/ONES-3.0$ ./ones-installer.sh

The installer file automatically detects & processes fresh installation or upgrade to the new version

While upgrading there is no dependency of prevision version files, Once the upgrade process is completed, user manually have to delete the previous version files/Packages from the device, Script do not touch old version files

By default, the installer does not provide any license, user needs to contact AVIZ support Team.

ONESv3.0 support SSL certificate integration

User can choose YES if the User wants to integrate their own SSL certificate

Installing Open Networking Enterprise Suite (ONES)
..................................................
Installing prerequisites for ONES application
....................
....................
....................
....................
Installing sshpass...
dpkg: warning: downgrading sshpass from 1.09-1 to 1.06-1
(Reading database ... 116659 files and directories currently installed.)
Preparing to unpack .../sshpass_1.06-1_amd64.deb ...
Unpacking sshpass (1.06-1) over (1.09-1) ...
Setting up sshpass (1.06-1) ...
Processing triggers for man-db (2.10.2-1) ...
ONES is getting installed for the first time, choose appropriate options when prompted...
....................
Installing ONES application...

Do you want to install domain SSL certificate(if not, installation will proceed with a self signed certificate)? [y/n]: y
Enter the path to the private key file: /home/aviz/server.pem
Enter the path to the certificate file: /home/aviz/server.crt.pem

Note* Replace the Private key & certificate path to correct location

Choose No, if the user wants to use a self-signed certificate that is integrated into ONES package

Installing Open Networking Enterprise Suite (ONES)
..................................................
Installing prerequisites for ONES application
....................
....................
....................
....................
Installing sshpass...
dpkg: warning: downgrading sshpass from 1.09-1 to 1.06-1
(Reading database ... 116659 files and directories currently installed.)
Preparing to unpack .../sshpass_1.06-1_amd64.deb ...
Unpacking sshpass (1.06-1) over (1.09-1) ...
Setting up sshpass (1.06-1) ...
Processing triggers for man-db (2.10.2-1) ...
ONES is getting installed for the first time, choose appropriate options when prompted...
....................
Installing ONES application...

Do you want to install domain SSL certificate(if not, installation will proceed with a self signed certificate)? [y/n]: n
Using self signed certificates...

Enable or disable the ONE DL feature

User can choose YES if the User wants to enable ONES DataLake feature.

Do you want to enable ONE-DL feature? [y/n]: y
Since ONE-DL configuration has been chosen, please provide the information below...
Enter EC2 ONE-DL Backend Public DNS Endpoint: <Path>

User can choose No if need not to enable ONES DataLake feature
```
Do you want to enable ONE-DL feature? [y/n]: n
```

The installation allows a user to enable DB backup
1. Users can choose the local or remote location to backup the database
2. By default, the application creates a database backup every 86400 seconds(1 day), but the user can modify it as per the requirement
Local and Remote Backup
1. By-default application creates 1 backup for local and for remote,
2. It has a range of 1 to 3 and once it will add one more it will remove the first copy of the database,
3. User can modify the number of backup files at the time of installation
4. By-default ONES create ./backup directory to maintain local database

Local backup:
Do you want to enable DB backups? [y/n]y
Where do you want to store the backups? [local/remote]: local    #local keyword trigger local database on server
Enter the backup directory: ./backups     #Enter the server directory in which user wants to take backup
Enter the number of backups (between 1 and 3) to retain (Older backups will be deleted): 1   #Enter the number of backup user wants to create
Enter the backup interval in seconds (3600 seconds or higher): 86400 #Enter the value in seconds to take a backup

Remote backup:
Do you want to enable DB backup feature? [y/n]: y
Where do you want to store the backups? [local/remote]: remote    #remote keyword trigger remote database on server
Please make sure the remote server is reachable via SSH
Enter the remote machine IP: 10.0.0.1    
Enter the remote machine username: admin
Enter the remote machine password: 
Enter the backup directory: ~/backups    #Enter the remote server directory in which user wants to take backup
Backup is being done in 10.0.0.1 at ~/backups
Enter the number of backups (between 1 and 100) to retain (Older backups will be deleted): 5    #Enter the number of backup user wants to create
Enter the backup interval in seconds (3600 seconds or higher): 86400    #Enter the value in seconds to take a backup

ONESv3.0 support certificate-based authentication between ONES App and devices for GNMI and Auto-discovery

For agent auto-discovery agent will act as a client and the collector as a server. For normal gnmi communication, the agent will act as a server and the collector as a client. Need certificates based on this.

No:
Do you want to enable certificate based authentication between ONES controller and devices? [y/n]: n

Yes:
Do you want to enable certificate based authentication between ONES controller and devices? [y/n]: y
Enter the path to the ca-cert.pem file: ca-cert.pem    
Enter the path to the server-cert.pem file: server-cert.pem    
Enter the path to the server-key.pem file: server-key.pem
Enter the path to the client-cert.pem file: client-cert.pem
Enter the path to the client-key.pem file: client-key.pem
Proceeding with certificates for Agent Auto Registration
Enter the path to the ca-cert-reg.pem file: ca-cert-reg.pem
Enter the path to the server-cert.pem file: server-cert.pem
Enter the path to the server-key.pem file: server-key.pem
Enter the path to the client-cert.pem file: client-cert.pem
Enter the path to the client-key.pem file: client-key.pem

The user needs to provide the certificate path and replace the key name with the path of the certificate to be used here

ONES Application support IP-based Access & FQDN Access

Enter the ONES App URL: https:// #Replace the input with IP or FQDN

IP based

Enter the ONES App URL: https://192.168.1.1

FQDN based

Enter the ONES App URL: https://ones.aviznetworks.com

ONESv3.0 support password-based(MD5) authentication between ONES App and devices for GNMI and Auto-discovery
1. User can choose yes if need password based authentication
  Do you want to enable agent authentication ? [y/n]: y Enter the ones-agent username: admin Enter the ones-agent password: YourPaSsWoRd
2. User can choose no if there no requirement of authentication
  Do you want to enable agent authentication ? [y/n]: n

Users cannot simultaneously select both certificate-based authentication and password-based authentication between the agent and the ONES application. They must choose one authentication method at a time for securing communication between the agent and the ONES app if required.

Installation begins

root@aviz:/home/aviz/GA_3.0/ones-1725445069-onprem# ./ones-installer.sh
Installing Open Networking Enterprise Suite (ONES)
..................................................
Installing prerequisites for ONES application
....................
....................
....................
....................
Installing sshpass...
dpkg: warning: downgrading sshpass from 1.09-1 to 1.06-1
(Reading database ... 116659 files and directories currently installed.)
Preparing to unpack .../sshpass_1.06-1_amd64.deb ...
Unpacking sshpass (1.06-1) over (1.09-1) ...
Setting up sshpass (1.06-1) ...
Processing triggers for man-db (2.10.2-1) ...
ONES is getting installed for the first time, choose appropriate options when prompted...
....................
Installing ONES application...

Do you want to install domain SSL certificate(if not, installation will proceed with a self signed certificate)? [y/n]: y
Enter the path to the private key file: /home/aviz/server.pem
Enter the path to the certificate file: /home/aviz/server.crt.pem
Do you want to enable ONE-DL feature? [y/n]: n
Do you want to enable DB backup feature? [y/n]: y
Where do you want to store the backups? [local/remote]: remote    
Please make sure the remote server is reachable via SSH
Enter the remote machine IP: 10.0.0.1    
Enter the remote machine username: admin
Enter the remote machine password: 
Enter the backup directory: ~/backups   
Backup is being done in 10.0.0.1 at ~/backups
Enter the number of backups (between 1 and 100) to retain (Older backups will be deleted): 5   
Enter the backup interval in seconds (3600 seconds or higher): 86400     
Do you want to enable certificate based authentication between ONES controller and devices? [y/n]: n
Enter the ONES App URL for Rule-Engine Alert [https://<host-ip or domain>]: https://10.20.0.80
Do you want to enable agent authentication ? [y/n]: y
Enter the ones-agent username: admin
Enter the ones-agent password: YourPaSsWoRd
Setting up the environment and loading essential dockers...
2bb80ba200dd: Loading layer [==================================================>]  68.32MB/68.32MB
2a9822159dc0: Loading layer [==================================================>]  2.048kB/2.048kB
2db080db4c83: Loading layer [==================================================>]  143.2MB/143.2MB
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
Loaded image: avizdock/ones-collector:v3.0.0
f99617b4857d: Loading layer [==================================================>]  2.081GB/2.081GB
598cad3fc7f2: Loading layer [==================================================>]  4.096kB/4.096kB
a2cac5263de0: Loading layer [==================================================>]  1.536kB/1.536kB
4d9c9e7cdef2: Loading layer [==================================================>]  3.584kB/3.584kB
a76669129b6a: Loading layer [==================================================>]   98.3kB/98.3kB
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
85f57de39b33: Loading layer [==================================================>]   7.68kB/7.68kB
21cdd2e0b4ef: Loading layer [==================================================>]  2.048kB/2.048kB
12f4e967e13f: Loading layer [==================================================>]  10.75kB/10.75kB
5e93cea4ec38: Loading layer [==================================================>]  11.26kB/11.26kB
ce0cf0b53390: Loading layer [==================================================>]  77.59MB/77.59MB
0344a1894c78: Loading layer [==================================================>]  161.2MB/161.2MB
Loaded image: avizdock/timescaledb:latest
ones-collector-db-data
0280eb3c2596: Loading layer [==================================================>]  1.536kB/1.536kB
6dde90cacd10: Loading layer [==================================================>]  86.02kB/86.02kB
2aa52ba420da: Loading layer [==================================================>]  296.4MB/296.4MB
be57349b17a3: Loading layer [==================================================>]  6.353MB/6.353MB
0ec41b6d891c: Loading layer [==================================================>]  2.349MB/2.349MB
d5f95e6a3021: Loading layer [==================================================>]  115.2MB/115.2MB
05f76cb3b696: Loading layer [==================================================>]  6.619MB/6.619MB
2511c56b8490: Loading layer [==================================================>]  5.766MB/5.766MB
Loaded image: avizdock/ones-ui:v3.0.0
ones-ui-data
952d1ba246e9: Loading layer [==================================================>]  1.536kB/1.536kB
aa5bb983ae7a: Loading layer [==================================================>]  3.072kB/3.072kB
29500ccb4fdd: Loading layer [==================================================>]    243MB/243MB
0d1d24f6d697: Loading layer [==================================================>]  223.8MB/223.8MB
370ce41daeb2: Loading layer [==================================================>]  6.291MB/6.291MB
53f7f3605d6c: Loading layer [==================================================>]  2.992MB/2.992MB
05dc8de6e8f6: Loading layer [==================================================>]  158.2kB/158.2kB
Loaded image: avizdock/pty-server:v3.0.0
64a5ccd06307: Loading layer [==================================================>]  2.048kB/2.048kB
ca4c2e6e9d9e: Loading layer [==================================================>]  1.203MB/1.203MB
5296c36b9ebf: Loading layer [==================================================>]  862.7MB/862.7MB
5943159c673a: Loading layer [==================================================>]  41.97MB/41.97MB
Loaded image: avizdock/ones-gateway:v3.0.0
4f28916f37e9: Loading layer [==================================================>]  129.5MB/129.5MB
2a5df58ba97f: Loading layer [==================================================>]  29.52MB/29.52MB
c7fd29476165: Loading layer [==================================================>]  156.6MB/156.6MB
c7e74d262dff: Loading layer [==================================================>]  38.24MB/38.24MB
e851c0af7c3d: Loading layer [==================================================>]  359.7MB/359.7MB
2ef53f757b83: Loading layer [==================================================>]  40.77MB/40.77MB
bc8e8be8d143: Loading layer [==================================================>]  2.048kB/2.048kB
83fa77e03e24: Loading layer [==================================================>]  59.91MB/59.91MB
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
d0feb9122054: Loading layer [==================================================>]   2.56kB/2.56kB
7219b0fcbd58: Loading layer [==================================================>]   2.56kB/2.56kB
c529643b8d45: Loading layer [==================================================>]  527.4MB/527.4MB
d69f335ef8e6: Loading layer [==================================================>]  44.73MB/44.73MB
1644861feacd: Loading layer [==================================================>]  145.9kB/145.9kB
Loaded image: avizdock/ones-fm:v3.0.0
d4fc045c9e3a: Loading layer [==================================================>]  7.667MB/7.667MB
b150abefba25: Loading layer [==================================================>]  12.29kB/12.29kB
93cb05de897b: Loading layer [==================================================>]  1.536kB/1.536kB
fb7197bcca0b: Loading layer [==================================================>]  234.3MB/234.3MB
0beddd8d6be2: Loading layer [==================================================>]  61.95kB/61.95kB
8b559dcbd8b1: Loading layer [==================================================>]  2.048kB/2.048kB
ba2a62a232e7: Loading layer [==================================================>]  3.072kB/3.072kB
0087bbc00356: Loading layer [==================================================>]  18.94kB/18.94kB
bec2427aa484: Loading layer [==================================================>]  3.072kB/3.072kB
Loaded image: avizdock/postgres:14
ones-fm-db-data
ones-fm-data
Loaded image: avizdock/docker:v3.0.0
bf63823f8c99: Loading layer [==================================================>]  84.18MB/84.18MB
162b992dedca: Loading layer [==================================================>]  3.395MB/3.395MB
4aa7ea28d987: Loading layer [==================================================>]  43.34MB/43.34MB
dc9851b6350b: Loading layer [==================================================>]  4.608kB/4.608kB
b1b299295e53: Loading layer [==================================================>]  12.08MB/12.08MB
739c25f0a755: Loading layer [==================================================>]  1.536kB/1.536kB
51a99d985dad: Loading layer [==================================================>]  29.31MB/29.31MB
e8605c9dadf3: Loading layer [==================================================>]   2.56kB/2.56kB
e3c514881f8f: Loading layer [==================================================>]  34.07MB/34.07MB
e437f061681a: Loading layer [==================================================>]  8.192kB/8.192kB
Loaded image: avizdock/ones-db-backup:v3.0.0
Loaded image: avizdock/zookeeper:v3.0.0
Loaded image: avizdock/kafka:v3.0.0
Loaded image: avizdock/schemaregistry:v3.0.0
Loaded image: avizdock/kafka-connect:v3.0.0
Loaded image: avizdock/ksqldb-server:v3.0.0
76367d75676f: Loading layer [==================================================>]  7.369MB/7.369MB
a5406ed65f11: Loading layer [==================================================>]  282.7MB/282.7MB
58f70dbfa845: Loading layer [==================================================>]  2.048kB/2.048kB
f757d9533757: Loading layer [==================================================>]  100.4MB/100.4MB
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
Loaded image: avizdock/ones-stream-processor:v3.0.0
5204d88907ef: Loading layer [==================================================>]  68.32MB/68.32MB
920be4d9d898: Loading layer [==================================================>]  2.048kB/2.048kB
ff7ff3cef7fa: Loading layer [==================================================>]  108.9MB/108.9MB
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
Loaded image: avizdock/apiserver:v3.0.0
277a036e29bd: Loading layer [==================================================>]  76.38MB/76.38MB
5f70bf18a086: Loading layer [==================================================>]  1.024kB/1.024kB
Loaded image: avizdock/ones-rule-service:v3.0.0
ones-rule-db-data
046c8b6d5bab6b2c21b5763abebdd37fe58fc215bcd1a961317d6be8d3b59e44
Cleaning up existing containers..
Bringing up ONES app containers
Bringing up ONES-collector-db container in no recreate mode and ONES-fm-db
[+] Running 1/1
 ⠿ Container ones-collector-db  Started                                                                                                                               4.5s
[+] Running 2/2
 ⠿ Container ones-rule-service-db  Started                                                                                                                            0.7s
 ⠿ Container ones-fm-db            Started                                                                                                                            0.7s
[+] Running 1/1
 ⠿ Container zookeeper  Started                                                                                                                                       1.5s
NAME                   COMMAND                  SERVICE             STATUS              PORTS
ones-collector-db      "/docker-entrypoint.…"   collector-db        running             8008/tcp, 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp, 8081/tcp
ones-fm-db             "docker-entrypoint.s…"   fm-db               running             0.0.0.0:2345->5432/tcp, :::2345->5432/tcp
ones-rule-service-db   "docker-entrypoint.s…"   rule-service-db     running             0.0.0.0:2456->5432/tcp, :::2456->5432/tcp
zookeeper              "/etc/confluent/dock…"   zookeeper           running             2888/tcp, 0.0.0.0:2181->2181/tcp, :::2181->2181/tcp, 3888/tcp
please wait for collector-db, rule-service-db and fm-db to initialize
[+] Running 2/2.........................................................................................................
 ⠿ Container zookeeper  Running                                                                                                                                       0.0s
 ⠿ Container broker     Started                                                                                                                                       0.7s

ones-collector-db
...........................................................................................................................................................................[+] Running 5/5......................................................
 ⠿ Container zookeeper        Running                                                                                                                                 0.0s
 ⠿ Container broker           Running                                                                                                                                 0.0s
 ⠿ Container schema-registry  Started                                                                                                                                 0.8s
 ⠿ Container ksqldb-server    Started                                                                                                                                 0.8s
 ⠿ Container kafka-connect    Started                                                                                                                                 1.3s
............................................................
[+] Running 4/4
 ⠿ Container ones-gateway    Started                                                                                                                                  1.9s
 ⠿ Container zookeeper       Running                                                                                                                                  0.0s
 ⠿ Container broker          Running                                                                                                                                  0.0s
 ⠿ Container ones-collector  Started                                                                                                                                  2.5s
[+] Running 17/17...........................................
 ⠿ Container ones-pty-server       Started                                                                                                                            2.0s
 ⠿ Container api-server            Started                                                                                                                            2.4s
 ⠿ Container ones-ui               Started                                                                                                                            2.2s
 ⠿ Container docker                Started                                                                                                                            2.4s
 ⠿ Container ones-rule-service     Started                                                                                                                            1.9s
 ⠿ Container ones-collector-db     Running                                                                                                                            0.0s
 ⠿ Container ones-rule-service-db  Running                                                                                                                            0.0s
 ⠿ Container ones-fm-db            Running                                                                                                                            0.0s
 ⠿ Container zookeeper             Running                                                                                                                            0.0s
 ⠿ Container ones-gateway          Running                                                                                                                            0.0s
 ⠿ Container ones-fm               Started                                                                                                                            2.3s
 ⠿ Container broker                Running                                                                                                                            0.0s
 ⠿ Container ksqldb-server         Running                                                                                                                            0.0s
 ⠿ Container schema-registry       Running                                                                                                                            0.0s
 ⠿ Container stream-processor      Started                                                                                                                            2.1s
 ⠿ Container ones-collector        Running                                                                                                                            0.0s
 ⠿ Container kafka-connect         Running                                                                                                                            0.0s
NAME                   COMMAND                  SERVICE             STATUS              PORTS
api-server             "java -jar /app/apis…"   api-server          running             0.0.0.0:8080->8080/tcp, :::8080->8080/tcp
broker                 "/etc/confluent/dock…"   broker              running             0.0.0.0:9092->9092/tcp, :::9092->9092/tcp, 0.0.0.0:9101->9101/tcp, :::9101->9101/tcp, 0.0.0.0:29092->29092/tcp, :::29092->29092/tcp
docker                 "python3 app.py"         docker              running
kafka-connect          "/etc/confluent/dock…"   kafka-connect       running (healthy)   0.0.0.0:8083->8083/tcp, :::8083->8083/tcp, 9092/tcp
ksqldb-server          "/etc/confluent/dock…"   ksqldb-server       running             0.0.0.0:8088->8088/tcp, :::8088->8088/tcp
ones-collector         "java -jar -XX:MaxGC…"   collector           running             8093/tcp, 0.0.0.0:50053->50053/tcp, :::50053->50053/tcp
ones-collector-db      "/docker-entrypoint.…"   collector-db        running             8008/tcp, 0.0.0.0:5432->5432/tcp, :::5432->5432/tcp, 8081/tcp
ones-fm                "/bin/sh -c '{ gunic…"   fm                  running             0.0.0.0:8787->8080/tcp, :::8787->8080/tcp
ones-fm-db             "docker-entrypoint.s…"   fm-db               running             0.0.0.0:2345->5432/tcp, :::2345->5432/tcp
ones-gateway           "./gnmi-gateway -Tar…"   gateway             running             0.0.0.0:9339->9339/tcp, :::9339->9339/tcp
ones-pty-server        "docker-entrypoint.s…"   pty-server          running             0.0.0.0:8885->8885/tcp, :::8885->8885/tcp
ones-rule-service      "java -jar /app/rule…"   rule-service        running             8080/tcp
ones-rule-service-db   "docker-entrypoint.s…"   rule-service-db     running             0.0.0.0:2456->5432/tcp, :::2456->5432/tcp
ones-ui                "docker-entrypoint.s…"   ui                  running             0.0.0.0:443->443/tcp, :::443->443/tcp, 3002/tcp
schema-registry        "/etc/confluent/dock…"   schema-registry     running             0.0.0.0:8081->8081/tcp, :::8081->8081/tcp
stream-processor       "java -jar /app/stre…"   stream-processor    running             8080/tcp
zookeeper              "/etc/confluent/dock…"   zookeeper           running             2888/tcp, 0.0.0.0:2181->2181/tcp, :::2181->2181/tcp, 3888/tcp
Finishing up ONES Installation...
............................................................Installed ONES application successfully...
....................
Open the ONES application  at https://10.20.0.80

Access ONES Application Web GUI from a supported browser using https://<host-ip/FQDN>

Activation:

For a Trail license, the user needs to reach out to AVIZ Support
For Activation, the user can choose Activate License if the user has an activation key of any subscription

Users can activate the ONES Application first time just after installation(first-time ONES application shows the page to activate the license

After evaluating ONES application, the user will have the option to activate the license anytime from the License Page

1. Activate License

2. Activate Key

Use Default credentials as below;
- Username: superadmin
- Password : Admin@123
Update/Change your password on the first login

Password should contain:-

Minimum Password Length - 8 characters

Maximum Password Length - 24 characters

Character Support - Alpha Numeric

Special Characters - (# @ $ ! & % only)

Character Rule - At least one Upper Case and one special character

After Resetting the password use new credentials to login
You will see the default Monitor Page with a Topology view

1. Upgrade License

After Trail use, if the user wishes to upgrade new Subscription-based license, so user can navigate to the below page.

Account >> License >> Upgrade License

Click Upgrade License & Enter the subscription-based key

If Switches Deployment is large so user needs to enable the large config inside Database Config File

Copy the postgresql.config file outside to do changes

docker cp ones-collector-db:/home/postgres/pgdata/data/postgresql.conf dbconfig.conf

edit the file and uncomment few lines to activate Large config and save the changes

vi dbconfig.conf
    Uncomment the below lines in the above file is the change
#------------------------------------------------------------------------------
# LARGE CONFIGURATION - START
#------------------------------------------------------------------------------
timescaledb.max_background_workers = 16  # Increased for more concurrent background processes
# MEMORY SETTINGS (LARGE)
shared_buffers = 8GB                    # Adjust based on your available system memory
work_mem = 16MB                         # Set based on your workload; adjust as needed
maintenance_work_mem = 1GB              # Important for bulk operations and autovacuum
effective_cache_size = 16GB             # Estimate the cache available for PostgreSQL (usually 50-75% of system memory)
# WAL SETTINGS (LARGE)
wal_level = logical                     # Recommended for logical replication and high-volume streaming
max_wal_size = 8GB                      # Increase to accommodate more WAL data during peak operations
checkpoint_timeout = 15min              # Spread checkpoint operations for better performance
checkpoint_completion_target = 0.9      # Further spreads the checkpoint process
wal_compression = on                    # Reduces WAL size, useful in high-traffic scenarios
# CONNECTION AND PROCESS SETTINGS (LARGE)
max_worker_processes = 16               # Increased to allow more background workers
max_parallel_workers = 16               # More parallel workers for better throughput
max_parallel_workers_per_gather = 4     # Adjust based on the complexity of your queries
# AUTOVACUUM SETTINGS (LARGE)
autovacuum_max_workers = 10             # Handle larger tables or high data churn more effectively
autovacuum_naptime = 10s                # Increase the frequency of autovacuuming
autovacuum_vacuum_cost_limit = 5000     # Handle vacuum operations more aggressively
autovacuum_vacuum_scale_factor = 0.01   # Trigger autovacuum sooner on large tables
# PERFORMANCE SETTINGS (LARGE)
effective_io_concurrency = 500          # For SSDs, this can be set high to optimize I/O
synchronous_commit = off                # Improves throughput at the cost of potential data loss in a crash
random_page_cost = 1.1                  # Optimized for SSDs
seq_page_cost = 1.0                     # Optimized for SSDs
jit = on                                # Enable JIT compilation for performance boosts in complex queries
#------------------------------------------------------------------------------
# LARGE CONFIGURATION - END
#------------------------------------------------------------------------------

Copy the changes to DB config file

docker cp dbconfig.conf ones-collector-db:/home/postgres/pgdata/data/postgresql.conf

Restart the ones-collector-db

docker restart ones-collector-db

ONE-DL cloud Deployment

Using this section user can install ONES-DL backend AWS

Provisioning an EC2 Instance

AWS EC2 Instance Sizing for Event Ingestion

For efficient event ingestion, it's crucial to select the right EC2 instance type based on your event volume:

200K events/sec: Start with a minimum of an m5.4xlarge instance.
Up to 400K events/sec: Scale up to an m5.8xlarge instance.
Up to 600K events/sec: Opt for an m5.12xlarge instance.
For higher volumes: Continue scaling in similar increments.

Install Docker

Install Docker Compose

Install ONE-DL

Copy the ONE-DL package to AWS Instance
Untar the ONE-DL package
Modify the .env file with given input
Run ./one-dl-multitenant-installer.sh

Installing ONES Agents 3.0

Overview

ONES requires user to install the below agents on SONiC NOS to allow Network Orchestration and Visibility

ONES Orchestrator Agent for Network Orchestration
ONES Telemetry Agent for Telemetry Data Streaming (Network Visibility)
ONES Server_Agent for GPU Telemetry Data Streaming

Server_Agent GPU telemetry is only supported on intel Gaudy platform.

ONES Agent 3.0 Version allow the user to add a new controller IP and to change the authentication between controller and agent without doing the complete installation again.

NOTE: for non-SONiC switches,

OpenConfig feature on its NOS needs to be enabled for Network Visibility (Telemetry Data Streaming)
Network Orchestration is not supported

SONiC NOS upgrade scenario - Impact on ONES Agents

SONiC NOS Upgrade could be done either via
- ONES UI (Inventory-->Devices)
  - Instead of using FM - Orchestrator Agent
  - Orchestrator Agent takes a backup of FMCLI, ONES Agents and associated services to the /host folder.
  - After a successful upgrade, Orchestrator Agent restores these files
- Traditional method (ZTP, sonic-installer CLI)
  - The user needs to reinstall ONES Agents again

ONES Telemetry Agent Installation

ONES Agent v3.0 support Agent Auto discovery

ONESv3.0 Agent support auto-discovery feature
ONESv3.0 Agent support to send telemetry on multiple controllers (Max 2)
Restrict IP feature can be enabled/disabled
Only Collector upgrade after Deployment is possible now
Password-based authentication is supported
Using the Restrict IP feature agent will discover the ONES Controller and will update the entry on the ONES App with all the feature metrics
Need to add a few inputs while installing the agent
1. Controller IP //To restrict the telemetry streaming
2. Device Credentials
3. Layer
4. Region
5. type
6. groupid
7. azid
8. brickid
9. rackid

Installation

On the Application machine, go to ONES-3.0/ones_t_agent folder

root@ones-application:~$ cd /ONES-3.0/ones_t_agent

Installation (Agent Install on multiple switches at the same time)

Enter device details (Management IP, Username and Password ) in device_info.csv

root@ones-application/ONES-3.0/ones_t_agent:~$ vi device_info.csv

The user needs to add all the required details in the CSV file, This CSV file will be used to push this information to agent.conf(/etc/sonic/agent.conf) file to every switch and ones-agent on the switch will pick the details from agent.conf file and will register itself to ONES controller with all the given parameters this helps a NetOps engineer to directly add a CSV file containing all the details, The Engineer needs not to add one by one devices on the controller which actually is time-consuming

The user must maintain the layer names exactly as specified above (case-sensitive). If the user inputs names that differ from these, they may encounter issues when using the ONES application.

Save the File

Executing the installation script can be used for installing a telemetry agent on one or more devices in the data centre.

The installer file automatically detects & will process fresh installation or upgrade to the new version

While upgrading, all the previous files will automatically get deleted on the Switch

If users want to use the certificate for GNMI & Auto-Registration, so users need to put the certificate in directory gnmi-certs(for GNMI) & auto-reg-certs(for Agent Auto Registration)

root@ones-application/ONES-3.0/ones_t_agent:~$ ./ones_agent_parallel_installer.sh

Users can use ONES-Agent as an integrated service in SONiC OS or can use it as an independent third-party container.

Users can choose this option to only update one more controller IP without doing the complete agent installation.

Scripts asks to put the Controller IP to use auto-discovery feature

User can only add 2 Controller IP to restrict the telemetry streaming

User can choose the restriction to send telemetry to collector IP only

It's important to restrict collector IP as No in case the running network has NAT translation from private to public IP for ONES server access from the device.

User can enable password based authentication between agnet and collector

Installation Begin

Now Agent will only stream the metrics to the given controller & will autoregister on the ONES-App

The user needs to make sure, The devices have a unique name, otherwise, there will issue while plotting the full topology view(Topology Page).

ONES Server Agent Installation

Server Agent v3.0 support:

Only Intel Guadi platform is supported in ONESv3.0

Supported Platform details

ONESv3.0 Agent support auto-discovery feature
ONESv3.0 Agent support to send telemetry on multiple controllers (Max 2)
Restrict IP feature can be enabled/disabled
Password-based authentication is supported
Using the Restrict IP feature agent will discover the ONES Controller and will update the entry on the ONES App with all the feature metrics
Need to add a few inputs while installing the agent

Installation

On the Application machine, go to ONES-3.0/ones_t_server_agent directory

root@ones-application:~$ cd /ONES-3.0/ones_t_server_agent

Installation (Agent Install on multiple switches at the same time)

Enter device details (Management IP, Username and Password ) in device_info.csv

root@ones-application/ONES-3.0/ones_t_server_agent:~$ vi device_info.csv

The user must maintain the layer names exactly as specified above (case-sensitive). If the user inputs names that differ from these, they may encounter issues when using the ONES application.

Save the File

Executing the installation script can be used for installing a telemetry agent on one or more devices in the data centre.

The installer file automatically detects & will process fresh installation or upgrade to the new version

While upgrading, all the previous files will automatically get deleted on the Switch

If users want to use the certificate for GNMI & Auto-Registration, so users need to put the certificate in directory gnmi-certs(for GNMI) & auto-reg-certs(for Agent Auto Registration)

root@ones-application/ONES-3.0/ones_t_server_agent:~$ ./ones_agent_parallel_installer.sh

Users can update only password in case server is already having agent running.

Users can choose this option to only update one more controller IP without doing the complete agent installation.

Scripts asks to put the Controller IP to use auto-discovery feature

User can only add 2 Controller IP to restrict the telemetry streaming

User can choose the restriction to send telemetry to collector IP only

It's important to restrict collector IP as No in case the running network has NAT translation from private to public IP for ONES server access from the device.

User can enable password based authentication between agnet and collector
user can choose no if user do not want to use password based authentication between agnet and collector.

Installation Begin

Now Server-Agent will only stream the metrics to the given controller & will autoregister on the ONES-App

The user needs to make sure, The devices have a unique name, otherwise, there will issue while plotting the full topology view(Topology Page).

ONES Orchestration Agent Installation

On the ONES Application server, go to ONES-3.0/ones_fm_agent

root@ones-application:~$ cd /ONES-3.0/ones_fm_agent

Installation (Agent Install on multiple switches at the same time)

Enter device details (Management IP, Username, Password ) in device_info.csv

root@ones-application:/ONES-3.0/ones_fm_agent:~$ vi device_info.csv

Save the file
Execute the installation script

Supported Deployment Methods

All these supported methods can be implemented by a single script

Installation: install FMCLI
uninstallation: Uninstall FMCLI
installresetconfig: Install FMCLI and reset the configuration
upgrade: Upgrade FMCLI to the latest version
install_withQOS: Install FMCLI and enable QoS feature
installresetconfig_withQOS: Install FMCLI, reset the configuration, and enable QoS feature

Installation

root@ones-application:/ONES-3.1/ones_fm_agent:~$ ./deploy_fmcli.sh

root@Switch:~$ sudo fmcli

Uninstallation

root@ones-application:/ONES-3.0/ones_fm_agent:~$ ./deploy_fmcli.sh

Installation with a config cleanup

using this process, Script will clear the base config like port--channel related config, IP related config, VXlan related config and more related configuration.

Using the same way user can choose other options to use FM agent

Agent Less Telemetry

Network Device Configuration Interfaces

Cumulus (NVUE API)

Cumulus Networks offers the NVUE (Network Virtualization Utility Engine) API, providing an abstraction layer over traditional configuration mechanisms. This allows for a more intuitive and standardized approach to network configuration and management, echoing modern software development practices.

Arista EOS (OpenConfig)

Arista's EOS platform leverages OpenConfig, a collaborative effort among network operators to define vendor-neutral data models for configuring and managing networks. OpenConfig facilitates simplified, consistent interactions across different network devices.

Cisco NX-OS (gRPC)

Cisco's NX-OS supports gRPC, enabling efficient, scalable, and programmatic network device management. This interface allows for the streaming of telemetry data and the execution of configuration commands.

Cumulus(NVUE API)

Cumulus switch with version >4.4 to start streaming to ONES Controller via NVUE API

Enable gNMI in Cumulus

Enable NVUE API in Cumulus

ONES IS not using NCLU. ONES Application only use NVUE API from OS version 4.4, less than that NCLU code is not enabled for ONES. [For ONES 1.1 testing 4.4 and 5.2 version]

Cumulus 5.x not fully support NCLU, only NVUE.

Arista EOS (OpenConfig)

Introduction

To enable Arista switches running EOS to stream telemetry data to ONES controller, API gNMI and eAPI need to be enabled

Enabling eAPI

Verification eAPI

CISCO NXOS (GRPC)

CISCO NXOS support its own way to stream telemetry data using GRPC, we can enable GRPC and can get offered metrics from the device

Enable GRPC

GRPC Verification

Show run GRPC

GRPC Service Statistics

GRPC Summary

Supported Telemetry

Adding New Controller

ONES Agent configuration file allows user to add new collector(controller) after the agent installation if required

Overview

To redirect agent telemetry data to a different ONES collector without reinstalling the agent, simply re-run the script with the "Only controller IP addition" option enabled. This process automatically registers the device with the new ONES application and starts the telemetry data stream.

Note: The terms "collector" and "controller" are synonymous in this context. It is essential to note that the auto-discovery feature is limited to supporting just two controllers.

Update controller IP without installing agent

Upon upgrading the Controller IP, it will automatically register with the new ONES

Installing ONES Multisite

These steps will guide you on how to install the ONES-Multisite

ONES Multisite Application - Installation Steps

Enable super-user mode

user@ones:~$ sudo su

Extract the contents of the downloaded ONES Installer tar.gz file

root@ones:~$ tar -xvf ones-multisite-v3.0.0.tar.bz2

ones-multisite/
ones-multisite/README.txt
ones-multisite/docker-compose.yml
ones-multisite/ones-multisite.tar

Go to ones-multisite directory on the server machine

root@ones-aplication:~$ cd ones-multisite

Run untar the installer packet to Install the ONES Multisite function

root@ones:~/ones-multisite$ tar -xvf ones-multisite.tar

0b26520cd4bec60d71bb05db9db8bfae8173ef8e0ec1f593bbc8988cb8f16cb7.json
0b3145a235c026e1c52ff0a2607b12e9161c25757b70f5f5574209f9b1d5da2b/
0b3145a235c026e1c52ff0a2607b12e9161c25757b70f5f5574209f9b1d5da2b/VERSION
0b3145a235c026e1c52ff0a2607b12e9161c25757b70f5f5574209f9b1d5da2b/json
0b3145a235c026e1c52ff0a2607b12e9161c25757b70f5f5574209f9b1d5da2b/layer.tar
16b76c7af288dd61a11dd8ce7d816c5aacef7da491d68d2cdcbc084cc7bea859/
16b76c7af288dd61a11dd8ce7d816c5aacef7da491d68d2cdcbc084cc7bea859/VERSION
16b76c7af288dd61a11dd8ce7d816c5aacef7da491d68d2cdcbc084cc7bea859/json
16b76c7af288dd61a11dd8ce7d816c5aacef7da491d68d2cdcbc084cc7bea859/layer.tar
4fc2a9076cc97b2a1dd2aac36adb9fd9c137933c88b7c5e45bf7fd419c4517fc/
4fc2a9076cc97b2a1dd2aac36adb9fd9c137933c88b7c5e45bf7fd419c4517fc/VERSION
4fc2a9076cc97b2a1dd2aac36adb9fd9c137933c88b7c5e45bf7fd419c4517fc/json
4fc2a9076cc97b2a1dd2aac36adb9fd9c137933c88b7c5e45bf7fd419c4517fc/layer.tar
50c8ee7e136f3a930827ba95dfcc17ca381298a5eb491a222346e7494493099a/
50c8ee7e136f3a930827ba95dfcc17ca381298a5eb491a222346e7494493099a/VERSION
50c8ee7e136f3a930827ba95dfcc17ca381298a5eb491a222346e7494493099a/json
50c8ee7e136f3a930827ba95dfcc17ca381298a5eb491a222346e7494493099a/layer.tar
a32bcfc3dbed1878782d95b32ad556b8205d46f9834e00e2c649161d88f556d9/
a32bcfc3dbed1878782d95b32ad556b8205d46f9834e00e2c649161d88f556d9/VERSION
a32bcfc3dbed1878782d95b32ad556b8205d46f9834e00e2c649161d88f556d9/json
a32bcfc3dbed1878782d95b32ad556b8205d46f9834e00e2c649161d88f556d9/layer.tar
ae6eaf728db4f415a92752f49c07f4070f8b45105c5901af8b10ebd5ce9564ec/
ae6eaf728db4f415a92752f49c07f4070f8b45105c5901af8b10ebd5ce9564ec/VERSION
ae6eaf728db4f415a92752f49c07f4070f8b45105c5901af8b10ebd5ce9564ec/json
ae6eaf728db4f415a92752f49c07f4070f8b45105c5901af8b10ebd5ce9564ec/layer.tar
d2eacd088446a54364a9691d26844f707551330d7a712f756c1efef2a468e927/
d2eacd088446a54364a9691d26844f707551330d7a712f756c1efef2a468e927/VERSION
d2eacd088446a54364a9691d26844f707551330d7a712f756c1efef2a468e927/json
d2eacd088446a54364a9691d26844f707551330d7a712f756c1efef2a468e927/layer.tar
d3b5a3f18f6ab12420582150e206fb3426da4e61db12143cf449ee6e806ca328/
d3b5a3f18f6ab12420582150e206fb3426da4e61db12143cf449ee6e806ca328/VERSION
d3b5a3f18f6ab12420582150e206fb3426da4e61db12143cf449ee6e806ca328/json
d3b5a3f18f6ab12420582150e206fb3426da4e61db12143cf449ee6e806ca328/layer.tar
f194d459916db6cadeca2714572218dc53bf03ad031224b71c4bf2d7dfef2991/
f194d459916db6cadeca2714572218dc53bf03ad031224b71c4bf2d7dfef2991/VERSION
f194d459916db6cadeca2714572218dc53bf03ad031224b71c4bf2d7dfef2991/json
f194d459916db6cadeca2714572218dc53bf03ad031224b71c4bf2d7dfef2991/layer.tar
manifest.json
repositories

Load the ONES Multisite docker images

root@ones:~/ones-multisite$ docker load -i ones-multisite.tar

aedc3bda2944: Loading layer [==================================================>]   7.63MB/7.63MB
4e14d5096571: Loading layer [==================================================>]  123.5MB/123.5MB
195af1454385: Loading layer [==================================================>]  7.795MB/7.795MB
3d9615f449be: Loading layer [==================================================>]  3.584kB/3.584kB
9316d3a480e4: Loading layer [==================================================>]  1.536kB/1.536kB
3c7ac698eb08: Loading layer [==================================================>]  44.03kB/44.03kB
3f2a563b3d1c: Loading layer [==================================================>]  10.54MB/10.54MB
503afaa3eafb: Loading layer [==================================================>]  70.14kB/70.14kB
ad6325f75281: Loading layer [==================================================>]  529.4kB/529.4kB
Loaded image: avizdock/ones-multisite:v3.0.0

Run Docker service for ONES-Multisite Application

root@ones:~/ones-multisite$ docker-compose up -d

[+] Running 2/2
 ⠿ Network ones-multisite_default  Created          0.1s
 ⠿ Container ones-multisite        Started          2.9s

After successful deployment of ONES-Multisite installer user can access the server using https://<IP>

VM Deployment

ONES Application can be integrated in the network as a Virtual Machine(VM) Package

VM Packages

QCOW2 Package: Qcow2 can be imported any KVM Hypervisor based application
OVA/OVF Package: OVA can import in
- VMware workstation/Fusion
- ESXI Server
- Virtual-Box

VM Package Upgrade

QCOW2 & OVA, both packages are supported for an upgrade to latest version

VMware ONES Deployment

Download OVA Package

Work with Aviz Sales/Support contact to create an account on Aviz Networks Support Portal
Click on the Downloads section, under ONES, and click to download ONES Release 3.0

VM Compatibility

ONES-3.0.0 OVA support below Versions of VMware Family

Import OVA to ESXI Server

Choose Deploy a virtual machine from an OVF or OVA file >> NEXT

Give it a Valid Name >> Click to select Files or drag/drop (upload from the download folder)

Choose the downloaded OVA package >> NEXT

Choose preferred storage to run ONES-3.0 VM >> NEXT

Choose a Network Adapter to provide DHCP IP to ONES App (Management interface/Eth0) >> NEXT

Verify all the inputs >> FINISH

After the OVA upload to ESXi is complete and the status indicates "Successful," the user will then be able to use ONESVM.

ONES is Ready to use >> Power On the ONES VM

Credentials to access ONES OVA VM

Once logging into the server CLI using below credentials, please continue with the next steps that is Ones Agent Installation

Username: aviz
Password: Aviz@123

Expand HDD

Expanding the HDD

python3 vm-hdd-expand.py

vCPU & RAM can be expended without any dependency

KVM ONES Deployment

QCOW Deployment

Download Qcow2 Package

Work with Aviz Sales/Support contact to create an account on Aviz Networks Support Portal
Click on the Downloads section, under ONES, click to download ONES Release 3.0

Untar the file

tar -I pbzip2 -xf ONES-3.0.0_Full.tar.bz2
aviz_ones/
aviz_ones/aviz_ones.qcow2  
aviz_ones/aviz_ones.xml  
aviz_ones/aviz_ones.xml.back

Navigate to aviz_ones
Copy ONES Release 3.0 package (qcow2) to KVM Hypervisor Server

Create the VM using GUI App virt-manager

If your host server has Ubuntu Desktop and virt-manager installed you can use it to deploy the VM. Make sure you can start the Virtual Machine Manager and that it connects successfully to the local hypervisor.

Creating a VM with virt-manager is very straightforward, Use the following steps to deploy the ONES-Application

File -> New Virtual Machine -> Import existing disk image -> Forward

Now the ONES Application is ready to use

Create the VM using QEMU (XML configuration)

Create an XML configuration file from the following template using vi

vi ones.xml

<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>ONES_VM01</name>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>4</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-1.5'>hvm</type>
    <boot dev='hd'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-x86_64</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='writeback'/>
      <source file='/home/oper/taas_vm/ones.qcow2' />
      <target bus='virtio' dev='vda'/>
    </disk>
    <serial type='pty'>
      <source path='/dev/pts/3'/>
      <target port='0'/>
    </serial>
    <!-- Management interface eth0 -->
    <interface type='network'>
	<model type='e1000' />
        <source network='br0'/>
        <address type='pci' domain='0x0000' bus='0x00' slot='0x00' function='0x0'/>
    </interface>
   <controller type='usb' index='0'/>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </memballoon>
  </devices>
</domain>

User Inputs in XML File

Line #2   The Name of the VM
Line #3   The amount of System Memory for the VM
Line #4   The amount of System Memory for the VM
Line #5   The number of vCPU Core for the VM
Line #25  The Path to the qcow2 VM image file
Line #35  The name of the Linux bridge on the host machine

Start the VM

virsh create <VM XML configuration file>

#sonic@sonic-39:~$ virsh create ones.xml 
#Domain ONES_VM01 created from ones.xml
#sonic@sonic-39:~$

If you see a permission error run the virsh command with sudo may fix the issue

Check the VM status

sonic@sonic-39:~$ virsh list
 Id    Name                           State
----------------------------------------------------
 8     ONES_VM01                      running
sonic@sonic-39:~$

Credentials to access ONES QCOW2 VM

Username: aviz
Password: Aviz@123

Upgrade VM

Upgrade Process

To upgrade any VM (QCOW or OVA)
- Download the ONES installation package
- Follow the Steps to upgrade the ONES to the New Version

VM packages do not support upgrades from one VM to another VM once the VM is deployed in the network, then the ONES tar-ball file can be used to upgrade it.

ONES Web GUI Administration

ONES User Interface - Features

SONiC Devices use auto-discovery
Non-SONiC devices needs to add using YAML editor or using CSV file
Deep Telemetry for ASIC and Switch Hardware
Server_GPU telemetry
Device Inventory details on
- Network Operating System (NOS)
- Firmware versions - ONIE, BIOS, and CPLD
- Hardware SKU, Model, ASIC, and Serial Number
- Platform Components – Fan, PSU, Sensors
- Link/Interface Health – Speed, Connectivity, Transceivers/Cables
Inventory Operations
- Adding/Removing devices using YAML or CSV file
- Agent Status Monitoring
Device Monitoring
- Device Up/Down State based on Agent and Agent-less
- Region and Zone Mapping
- Device Roles – Access, Leaf-Spine, Super-Spine
Device Storage monitoring
- SSD Temperature
- SSD health
- SSD memory
Network Compliance with version checks on
- Telemetry Agent
- Orchestrator Agent
- ONIE, NOS, and Linux Distros versions
Resource Trends
- CPU and Memory Utilization
- PSU and Fan Readings
- ASIC Capacity for Routes and ACLs
- Software and Kernel Route capacity
- Packet Counters – IN/OUT, Errors/Discards
Topology View
- Datacentre and AI-ML Topology
- Device Connectivity view across Roles and Location
- Link/Connectivity Status
- Device or Component failure count
Routing Protocol
- BGP 2 Byte and 4 Byte AS
- BGP Neighbors
- Advertised and Received Prefixes
- Local AS Number
- VXLAN
- MGLAG
- LACP
- RoCE
- QOS
Orchestrator Use Cases
- YAML-based Configuration push
- Image Management via ZTP
- BGP Numbered(IPv4 & IPv6) and Unnumbered Configuration
- BGP Peering with Port-Channel
- NTP, SNMP, SFLOW, and SYSLOG Configuration
- VXLAN
- Symmetric/Asymmetric IRB
- L2/L3 MC-LAG
- EVPN MultiHoming
- Layer2 Leaf-Spine (L2/L3 Mode)
- Leaf only Deployment
- BGP Peering over MC-LAG PeerLink
- BGP Peering using separate Link between MC-LAG Peers
- DHCP Relay
- SAG / SVI
- QOS
Licensing
- Application License
- Telemetry Agent License
- Orchestrator Agent License
User Management
- Add/Edit/Delete User
- Role Management
API Access for configurations originating from External Orchestration Tools
Rule Engine
- Slack Channel for push notification
- Zendesk ticket generation
- Service Now ticket alerts
- Rules status
Cloud Integration for DL
- Splunk
- Amazon S3

ONES allows users to leverage pre-defined templates, and customize them for Ports, IPv4/IPv6 Routes, BGP-Unnumbered, and Switch Services (NTP, SNMP, SYSLOG, ZTP, etc.) functions

Login Page

To access the ONES application, use Server IP/FQDN with HTTPS

https://<host-ip/FQDN>

Use default credentials to login, refer Installing ONES Application page for default credentials

Adding Devices

The user needs to make sure, The devices have a unique name, otherwise, there will issue while plotting the full topology view(Topology Page).

Agent-based devices auto-discover the ONES-App and get registered automatically on the ONES Inventory page
To Onboard the Agent-Less devices user needs to add them manually
- Navigate to Inventory

This page gives the control to onboard the devices with two options
1. Add Devices using the YAML Editor
2. Upload the CSV file containing the device list

The movement user chooses CSV upload, then the YAML Editor will be disabled

1. Add Devices using YAML

Click on Add Devices
Upload Device Inventory using YAML Editor
Navigate to Inventory >> Devices >> Add Devices >> Use YAML
Use the below format to add devices to the application

To Identify the device type user needs to mention the platform

Device Type

Cumulus: cumulus
Arista: arista
Cisco: cisco-nxos
SONiC: sonic

For SONiC-based devices, the user can also leave the type field empty

 inventory:
     - ipAddress: "10.4.4.61"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "cumulus"
       groupid: 1
     - ipAddress: "10.4.4.62"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "arista"
       groupid: 1
     - ipAddress: "10.4.4.63"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: cisco-nxos
       groupid: 1
     - ipAddress: "10.4.4.64"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "sonic"
       groupid: 1

Make sure to use the correct indentation for the YAML files

Click Save & Apply
ONES Application is now ready to manage the added devices

2. Add devices using CSV

Click on Add Devices
Upload Device Inventory using CSV File
Navigate to Inventory >> Devices >> Add Devices >> Use CSV
Use the below format to add devices to the application

Select CVS file to Upload >> Choose CSV file containing devices entry >>

Upload & Add

Monitor

Overview

The monitor widget in ONES:

Shows the complete topology view of the fabric
User can change the topology view by:
- Datacenter
- AI-ML
The Topology view can be categorised by:
- Region
- Platform
- ASICs
- Statuses
  - Not streaming, Faulty Fans, Faulty PSUs, Links Down
- Metrics
  - Bandwidth RX & TX
  - Memory, CPU & ASIC Utilization
This page shows all the links and information connected to each other
Using a right click on device it allow a user to go to specific feature details
- Traffic, Health, Capacity, Protocols
- Allow a user to connect device via SSH, Console Access
- Can get SYSLOGS
Traffic View
- PFC Enabled Device view
- input/output packets in million per sec
- Errors and Discard packets per interface
- And more related metrics
- AI-Fabric metrics
Health of the devices
- CPU & Memory Utilization
- CPU & PSU Temperature
- PSU Voltage & Fan Speed
- SSD Temperature, Health and Memory utilization
- Server GPU Metrics
Capacity of the devices
- IPv6 & IPv6 Routes
  - ASIC/Software/Kernel
  - ASIC ACL capacity
Links Page
- All the connected devices
- Transceivers info
Protocols status
- BGP status
- VXLAN
- MCLAG
- LACP
- QOS

Topology

Navigate to Monitor >> Topology
- Topology Type: DATACENTER
- Topology Type: AI-ML
This shows the complete Topology view, how the devices are connected
Topology can be filtered by Underlay/Overlay/RoCE
We can put the filters to check the customized view of the Topology
Count of devices
- All devices onboarded
- Not streaming
- Faulty Fans & PSUs
- Links Down
We can also check Down Links to check the topology those are having links in the shutdown state
When we hover the cursor over any device and use right click we get few more controls
- Device details/Ports
- Direct Navigation per device
  - Traffic/Health/Capacity/Protocols
- Console connect
- SYSLOG
we can also filter the view by using
- Statuses
  - Not streaming, Faulty Fans, Faulty PSUs, Links Down
- Metrics
  - Bandwidth RX & TX
  - Memory, CPU & ASIC Utilization

Traffic

Using this widget we can check the input and output errors across all the devices
This widget also shows the input and output packet per device
Navigate to Monitor >> Traffic

This page shows the information:
- Device Name & IP
- Roles & Region
- Device details
- Interface speed and ports
- Errors & Utilization of the links
Filter Ribbon can be used to get a customized view
- PFC Enabled Devices
- Operator up/down
- Admin down
- PFC Enable interfaces
When we click on any device it gives more information about the interface traffic
- Errors per interfaces
- Bandwidth Utilisation per interfaces
When we click on any particular interface it gives the timescale of the inputs and output packets with Errors and Discards & all metrics in detail

This page shows the traffic drop rate per interface based and will be very useful while doing any troubleshooting for a traffic drop
Using these details a user can check more details inside to fix the issue of dropping/discarding packets

Health

This page shows the latest utilization of all the devices

CPU & Memory utilization
Temperature & Voltage of PSU
fan speed in % & RPM
SSD Temperature, Health and Memory Usage
Navigate to Monitor >> Health

Health Status

Health Status is reported for the following components

Roles
SKU/ASIC
Ports/Max Speed
CPU Utilization (%)
Memory Utilization (%)
CPU Temperature (℃)
PSU Temperature (℃)
PSU Voltage (V)
Fan Speed (RPM)
SSD
- Temperature(℃)
- Health(%)
- Memory(%)

HOST / IP

Device Name
Device IP

Roles/Region

Device Role
Device Region

SKU/ASIC

SKU (Stock Keeping Unit)
ASIC

Port/Max Speed

Total number of ports available
Speed of ports

CPU Utilization (%)

CPU Utilization reported in 4 states

Normal
Acceptable
Critical - Action needed
Not Streaming - Agent is not up

Click on any device to get the view/status of all the components related to that device

Memory Utilization (%)

Memory Utilization reported in 4 states

Normal
Acceptable
Critical - Action needed
Not Streaming - Agent is not up

Click on any device to get the view/status of all the components related to that device

Average CPU Temperature (C)

Details of the temperature of the CPU across all the devices in degrees celsius

Any device that breaches the configured acceptable or critical value will be shown here
Click on any device to get the view/status of all the components related to that device

Average PSU Temperature (C)

Power Supply Temperature in degrees celsius

Any device that breaches the configured acceptable or critical value will be shown here
Click on any device to get the view/status of all the components related to that device

PSU (Voltage)

Power Supply Voltage readings in volts

Any device that breaches the configured acceptable or critical value will be shown here
Click on any device to get the view/status of all the components related to that device

Average Fan Speed (%)

Fan Speed in % of maximum supported RPM

Any device that breaches the configured acceptable or critical value will be shown here
Click on any device to get the view/status of all the components related to that device

SSD

SSD Status will be shown here

SSD Temperature: will allow a user to track the temperature
SSD Health: will allow a user to check the health utilization in percentage
SSF Memory: this metric will be useful to check the utilization of SSD

Customized View

We can check the health of the device as per some customization
We can filter the devices by:
- Roles
- Region

Role-based Customization

We can choose a role using the available Role-based option
4 Roles available
- Super Spine
- Spine
- Leaf
- ToR
Let’s check it with a Leaf filter
After selecting Leaf input, here is the new view of only devices that belong to the Leaf role

Per Device Status

This Platform Widget also gives the option to check the extended capability view of the device
Apart from this monitoring view, we can also verify/check extended feature sets like:
- PSU Current (A)
- PSU Power (W)
- Services Running
- Services CPU/Memory Consumption (%)
To view per device status with all possible widgets, click on any of the devices present on the list

When we choose a specific device we get an output like this

Device Info Ribbon

Feature

Use

Time Frame: Check Utilization Trends based on Time Range The application has the capacity to store up to 2 weeks of data

Refresh Component Status

Alerts: show all the alerts triggered by rules

Raise a Ticket for Technical Support

Documentation

API Explorer

Device Details

Platform
Number of Ports and Speed
Agent Version
Uptime
CPU Utilization
Memory Utilization
CPU Temperature
Services running on the device

CPU Usage (%)

Here we get the complete status of CPU usage with a time range A complete status What was the usage from starting to end

To check a specific time detail we can hover the cursor to any level

Memory Usage (%)

Now here we get the status of Memory Usage of selected device

To check a specific time detail with memory utilization, we can hover the cursor to any level

Services CPU Consumption (%)

This widget shows us the CPU consumption percentage level of all services / per service.
Here we can see we have the option to check the consumption view of CPU

To check a specific time detail we can hover the cursor on any level

Services Memory Consumption (%)

This widget shows us the Memory consumption percentage level of all services / per service.
Here we can also check the consumption view of only Memory.

To check a specific time detail we can hover the cursor on any level

Services Running

The best widget here for Services
We can also check the total number of count of services running on the platform
This graph shows the red colour bar, red colour show at what time one of the services went down

CPU Temperature (C)

This template shows the status of CPU temperature in degree celsius
Here we get the status of all the CPU and Core running on the device

Components

This page outlines the key metrics for accurately monitoring the performance of various components, specifically focusing on Temperature, Current, Fans, and Power.

SSD

Device Resource Utilization Page

This page allows users to monitor the resource usage of their devices, providing a proactive view of how resources are allocated per switch and the trends in service usage. If you notice any resource usage spiking, you can easily navigate to another utilization page to identify the specific processes contributing to the increased demand. This feature is designed to help users manage their resources more effectively and prevent potential issues before they impact performance.

These metrics can be effectively analyzed through a time series graph.

Capacity

This page shows the view of Capacity and a few more details related to devices

This widget Shows
- Roles/Region per device
- SKU and ASIC details per device
- ASIC ACL Capacity utilization
- IPv4 Routes (ASIC, Software, Kernel)
- IPv6 Routes (ASIC, Software, Kerneel)

Feature

Details

Roles/Region per device

SKU and ASIC details per device

ASIC ACL Capacity utilization

IPv4 Routes (ASIC, Software, Kernel)

IPv6 Routes (ASIC, Software, Kernel)

This Capacity Widget give us the control to get the output per Role and Region basis also

Let's choose Leaf Role to get the customized view

In the same way, we can customize the view by Region & SKUs

This is the extended view of the device capacity for all the IPv4 and IPv6 ASIC routes, ACL utilization, software, and kernel routes

Using this page a user will be able to troubleshoot the protocol or any misbehaviour happening on the devices due to any capacity issue of routes

Per Device Status

This widget gives us the capability to check the extended view of the Routes & ACL usage with a range of time

Click on any of the devices to get the extended view

Feature

Use

When we move the cursor to metrics this gives the usage view of ipv4:
- ASIC
- Kernel
- Software

When we move the cursor to metrics this gives the usage view of ipv6:

ASIC
Kernel
Software

When we move the cursor to metrics this gives the usage view of ACL:

ASIC

Protocols

This Protocol Page shares the metrics of below features

BGP (numbered/ unnumbered)
VXLAN
MGLAG
LACP
QOS

BGP

This BGP section will help a user to know more and accurate number with following details

BGP 2 byte and 4 byte AS
BGP numbered
BGP unnumbered
Total number of neighbors configured
How many neighbors are up and down
total number of prefixes and how many we are advertising
BGP neighbor details

Feature

Here we can get:
- Device name
- Device IP

Here We get the view of:
- Roles and Region

this column shares the details of:
- SKU
- ASIC

This shared the count of total BGP neighbours

This column share the status of
- how many BGP neighbours are UP and running
- How many BGP neighbours are in Down state

This column shares the Total Prefixes Present in BGP

These are the total number of advertised prefixes by the router to other BGP neighbours

This is the Local BGP AS number

Here we have the control to check more details on neighbours

This page gives the best details of the BGP neighbours connected with the devices and possible metrics/values a user can use to troubleshoot a BGP neighbour

Neighbor View

This shows the status of the neighbour's details, the total number of neighbours, received routes, neighbour RID, BGP AS number & much moreWe have the option here to check the neighbour details and status of RoutesWe can click on neighbours to get more details about all neighbours connected

Feature

Here we get the details of connected neighbours
- Neighbour Device Name
- Neighbour IP

Here we get the Neighbour BGP AS number

This shares the neighbour status of uptime, from how long the neighbour is connected

Here we get the detail of the last neighbour reset timer

This share the count of established and dropped connections per neighbour

Here is the view of the Keep Alive timer:
- Tx: how many keepalives have been transmitted
- RX: how many keepalives have been received

Here is the view of the Route Refresh messages count:

Tx: how many Route-Refresh messages have been transmitted
RX: how many Route-Refresh messages have been received

Here is the view of the Updates Count:

Tx: how many times updates have been transmitted
RX: how many times updates have been received

Per device status (Neighbour's & Announcement)

The user can get per-device status by choosing a particular Device

Click on the device name to get the status

This new page shows the status of BGP neighbours about UP and Down status
On the right side it shows the BGP announcements and the local prefixes present in the BGP table

VXLAN

This section is really helpful in finding the devices with active VXLAN features enabled with a few more details

L2 & L3 VXLAN metrics
Local VTEP
Remote VTEP and details on how many are up and down
VLAN to VNI Mapping
VRF to VNI mapping

Below output shows all the possible devices with VXLAN details

VTP Details

By clicking on Local VTEP ID we get the most accurate details on that device for all the remote VTEP connected to this

Users can click on operation status to get the time series graph about the up nd down status, at what time the VTEP was up or down

VLAN to VNI Mapping

Users can get the details on VLAN to VNI mapping using the option on this page

VRF to VNI Mapping

Using the below option user can check all the possible VRF to VNI Mapping

MCLAG

This feature enhances network management by allowing users to access a timescale graph. This graph shows the status of neighbour and peer links over time, indicating periods when they were down or active. Users can further examine the health page to determine whether downtime resulted from process issues or resource utilization problems.

Additionally, the feature provides tools for verifying:

MGLAG (Multi-Chassis Link Aggregation Group) Domain ID
The status of PortChannels associated with Peer Links
MCLAG-L3 (Multi-Chassis Link Aggregation Level 3) status
MCLAG-L2 (Multi-Chassis Link Aggregation Level 2) status

With these capabilities, users can effectively track and diagnose network performance and configuration issues.

Time Series Graph with up and down status

Navigate to Monitor >> Protocols >> <Choose Devcice> >> Click on Active/Passive

LACP

Using this Page metrics user will get the details on the EtherChannel status, it will show per device etherchannel status with member ports and the status with a time series graph

Selecting a port channel on any device allows users to view its time series data. This feature enables the analysis of the device's status, ranging from the latest hour up to two weeks of metrics.

QOS (Quality of Service)

Quality of Service (QoS) in networking is used to prioritize certain types of traffic, ensuring critical applications like video conferencing, VoIP, or online gaming get sufficient bandwidth. It helps reduce latency, minimize jitter, and maintain consistent performance, especially in congested networks, by managing and controlling traffic flows based on importance.

This page allow a user to check the active configuration related to:

QoS Active Queues on interfaces
802.1p and DSCP to TC mapping
PFC enabled queues
TC to PG and Queue mapping
Scheduler and WRED status

Queues status per device

To verify the activated queues, the user can click on "Show Active" This page displays the status of each queue along with the features enabled for each interface.

All Profile

The "Show All" option allows the user to view all activated configurations per widget, providing a detailed overview of QoS-related settings for each device.

Inventory

User can onboard all the devices on the application and can get a complete view of all the populated tables

Agent-Based (Switch and Server) devices will automatically added using the auto discovery feature

Agent-Less devices needs to be added using this inventory page

The Inventory tab has the below-mentioned features:
- Custom OS upgrade: Upgrade the device OS with any customised image. You need to provide the correct path to ensure the OS is updated successfully
- OS upgrade via ZTP: Upgrade the device OS via Zero-touch provisioning
- Reboot devices: Reboot the device from a single click in the UI
- Remove devices from the dashboard: The user can remove the auto-discovered(Agent based) and non-sonic devices
- Add devices from the dashboard:
  - The User can onboard the non-sonic devices using the YAML file upload or via the in-built editor in the UI
  - User will have the option to upload CSV file with the list of devices
- Sub-options
  - Syslog: Using this tab user can easily access all the syslogs and can find out the more relative logs directly in case of some failure of any process or any other module of device
  - Tech Support: User can directly download the techsupport to debug the issue.
  - Export Inventory: A network engg can easily get the inventory in CSV file

Devices

This section explains how users can add/manage/remove the devices using ONES.

Devices

Navigate to Inventory >> Devices

Using this tab, user can:
- Onboard the non-sonic(Agent-Less) device to the application using Add devices
- Syslogs capture
- Upgrade the device using Custom Upgrade
- Upgrade the device using ZTP (Zero Touch Provisioning)
- Reboot individual devices or multiple devices by selecting them in one click
- Remove the devices
- Tech-Support download
- Complete Inventory can be downloaded in CSV format

The user needs to make sure, The devices have a unique name, otherwise, there will issue while plotting the full topology view(Topology Page).

Sonic Devices

Agent-based devices auto-discover the ONES-App and get registered automatically on the ONES Inventory page

Add Non-Sonic Devices

To Onboard the Agent-Less devices user needs to add them manually
- Navigate to Inventory

This page gives the control to onboard the devices with two options
1. Add Devices using the YAML Editor
2. Upload the CSV file containing the device list

The movement user chooses CSV upload, then the YAML Editor will be disabled

1. Add Devices using YAML

Click on Add Devices
Upload Device Inventory using YAML Editor
Navigate to Inventory >> Devices >> Add Devices >> Use YAML
Use the below format to add devices to the application

To Identify the device type user needs to mention the platform

Device Type

Cumulus: cumulus
Arista: arista
Cisco: cisco-nxos
SONiC: sonic
Server: server

For SONiC-based devices, the user can also leave the type field empty

 inventory:
     - ipAddress: "10.4.4.61"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "cumulus"
     - ipAddress: "10.4.4.62"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "arista"
     - ipAddress: "10.4.4.63"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: cisco-nxos
     - ipAddress: "10.4.4.64"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "sonic"
     - ipAddress: "10.10.0.10"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "admin@123"
       type: "server"

Make sure to use the correct indentation for the YAML files
Click Save & Apply
ONES Application is now ready to manage the added devices

2. Add devices using CSV

Click on Add Devices
Upload Device Inventory using CSV File
Navigate to Inventory >> Devices >> Add Devices >> Use CSV
Use the below format to add devices to the application

Select CVS file to Upload >> Choose CSV file containing devices entry >>

Upload & Add

Feature Set

Role / Region: Shows the device roles and regions
SKU / ASIC: Shows the device hardware SKU and ASIC vendor
Port / Max Speed
- Shows the number of ports per device and max port speed on the device
- Click on the number of ports to get a detailed view of all the ports on a particular device

PSUs / Fans: Shows the total number of Power supplies and Fans present on a particular device
NOS Image: Shows the details of the network operating system running on the device and when it was last updated
ONIE Version: Shows which ONIE version is running on the device and when the last reboot time of the device
Agent Version / Network OS: Shows the agent version running on the device and the current active OS version on the device
Agent status / Last contact: Latest status of the Agent and when it was last communicated with that Agent.
Connect: Using this feature we directly get the CLI access of the device
- SSH Connect
- Console Connect
Details: This last option we can again use to get the details of the device

Remove Devices from the ONES Application

Navigate to Inventory >> Devices >> Remove Devices
Choose the devices to be removed & confirm

once the user clicks on confirm, the Inventory page will remove the device

If the devices are agent-based they will get added again after some time, if the user wants to remove the agent-based devices, then the user needs to uninstall the agent from the device

Now the selected devices have been removed from the ONES application

Custom Upgrade

This feature gives the control to upgrade the device to the new version

An HTTP image link is required to use the custom upgrade

Select any of the devices to upgrade to the new version

Click on Custom Upgrade

put the new Image URL and then Submit

It will show the status as In Progress

HTTP image URL should be accessible

This image will be downloaded to the device and configured as the next boot image and devices will be reloaded

Once the device comes up with the new image, the ONES application will install Telemetry and Fabric manager agent

when we upgrade any device that will be locked to do any further changes after a successful upgrade user can again use the same device for another task

Once the image is loaded, the ONES application will show the last image details and time stamp

Upgrade via ZTP

Using this page a user can directly upgrade the box

Select any of the devices to upgrade via ZTP

Click on Upgrade via ZTP

Click on Yes

when we upgrade any device that will be locked to do any further changes, after a successful upgrade user can again use the same device for another task

Reboot Device

Here we will see how we can reboot a device using
We have the option to choose one or multiple devices at a time to reboot
Choose one of the devices that we want to reboot

Click on Reboot
Click on Yes

While rebooting the device, the device will be locked to do any other task, once the reboot is successful, the lock will be removed and the user can take any new action

Sub-options

Syslog

User will have option to choose count of the logs and can filter as per only Error or Only Warning or all the logs

Tech Support

Export Inventory

Configurations

Navigate to Configurations >> Configure Devices
Allows you to configure new devices
Supports valid YAML files
You can download the sample YAML file, edit it, and upload it again with the desired configuration

YAML Config Illustrator

While configuring the topology, users can utilize the "Visualize YAML" feature to preview the structure and layout.

Navigate to Configurations >> Configure Devices >> <Upload Valid YAML> >> Visualize YAML

NOTE: Follow the ONES Orchestration to know more about configuration and all the possible use cases.

Rule Engine

Overview

In data centre operations, a rule engine with alerts for various metrics is essential for proactive monitoring and management of critical components and services. Let's see the different types of rule engine alerts for specific metrics in a data centre environment

CPU and Memory Alerts
Fan and Power Supply Unit Alerts
Traffic Bandwidth
ASIC IPv4 & IPv6 Routes
BGP Neighbour Alerts
Health Services
Device Down Alerts
SSD Health, temperature and memory usage alert
Device Queue counters
PFC counters
Traffic Errors and Discard Counters
frr and syncd services CPU utilization status
Server Agent based metrics
1. CPU Temperature and Utilization
2. Down status
3. FAN Speed
4. Memory Utilization
5. GPU
  1. Memory Utilization
  2. PSU Power Draw
  3. Temperature
  4. Utilization

Push Notification

Rule Engine pushes the configured rule notification in case any device breaches the threshold value configured under the rule to

Slack channel
Zendesk Support ticket
Service Now ticket

To use Rule Engine Alert feature User needs to setup first Slack channel integration, Zendesk Support integration or Service-Now integration

Slack Channel Integration

1. Create a Channel for ONES-App push notification

2. Generate API for Channel

Create an App
Choose From scratch
Provide any App Name and choose the workspace where the user wants to get the push notification & Create App
Choose Incoming Webhook and Activate Incoming Webhooks & Add New Worbhook to workspace
Select the configured Channel & Allow
Copy the newly created webhook link
Open ONES-App and select Integration >> Messaging
Add Channel & Paste the Webhook URL
After saving it will be available to use while creating any rule using Rule Engine feature

Zendesk Support Integration

Login to the Zendesk Support Admin panel & Follow the steps
1. click >> Apps & Integration
2. Choose >> Zendesk API
3. Enable Token Access
4. Give API Token Description (Optional)
5. Copy the API Token
6. Save the Settings
Open ONES-App and select Integration >> Ticketing
Add Channel & Paste the required details
After saving it will be available to use while creating any rule using Rule Engine feature

Service Now Integration

User needs to generate a Instance URL from Service Now developer Account

Integrations >> Ticketing >> ServiceNow

Add Channel
Inputs to sucessfully integrate ServiceNow
1. Instance URL (from serviceNow developer Account)
2. Credentials (from serviceNow developer Account)

Rules Type

There are two types of Rule a user can configure

Entity Based
1. Allow a user to create Rules per device
  1. Allow user to include or exclude the devices from the rule
Entity by Property
1. Allow a user to create Rules by using HwSKU, Role, OS Version across all the managed devices

1. Entity Based explained

Possible Values & Description

Rule Name: The user can choose any related name
For: The user can choose 2 options

Device: Once the user chooses the rule for Devices it will show the below Metrics

ASIC IPv4 Routes
ASIC IPv6 Routes
BGP Neighbours Down
Device CPU Core Temperature
Device CPU Utilization
Device Down
Device Memory Utilization
Device Queue Transmit Counter
FAN Speed
Failed FANs
Failed PSUs
PSU Temperature
SSD Health
SSD Temeperature
SSD Used Memory Percent
frr CPU Utilization
syncd CPU Utilization

Interface: Once the user chooses the rule for Interfaces it will show the below Metrics

Interface flap
Interface PFC Receive Counters
Interface PFC Transmit Counters
Interface Queue Transmit Counters
Traffic InDiscards
Traffic InErrors
Traffic OutDiscards
Traffic OutErrors
Traffic Rx Utilization
Traffic Tx Utilization
Transceiver Rx Power
Transceiver Temperature
Transceiver Tx Power
Transceiver Voltage

Server: The user will be able to get alerts for IntelGaudy

CPU Core Temperature
CPU Utilization
Device Down
FAN Speed
GPU Memory Utilization
GPU PSU 1 Power Draw
GPU PSU 2 Power Draw
GPU Temperature
GPU Utilization
Memory Utilization

Metrics: Metrics depend on the above (For: Device/Interface) condition
Measure: Metrics are measured in three diff ways
1. MIN
2. AVG
3. MAX
Period: Measured metrics can be verified with a buffer of a timer
1. 5 min
2. 10 min
3. 15 min
4. 30 min
5. 1 hour

Conditions

When Measured Value is: This option allows a user to choose what condition has to match when the measured value is
1. EQ: Equal to
2. NEQ: Not Equal to
3. GE: Greater than Equal to
4. LE: Less than Equal to
5. GT: Greater than
6. LT: Less than
Critical Threshold: The user can set a Critical value on which push notification will be triggered
Warning Threshold: The user can set a Warning value on which push notification will be triggered

Notification

Notify: The user can choose the integrated SLACK Channel
Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket
Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket
Weekly Digest: Slack Users can choose this for Weekly Digest to SLACK Channel
Do not notify if the same alert trigger in: 30min, 1hour, 2hours, 10hours, 24hours
Stop notifying after: The user can choose a value of occurrence then it will not trigger the same in the next 24 hours

2. Entity by Property

Possible Values & Description

Rule Name: The user can choose any related name
Filter: user can filter the rule for all managed devices by
1. HWSKU
2. ROLE
3. OS Version
For: The user can choose 2 options

Device: Once the user chooses the rule for Devices it will show the below Metrics

ASIC IPv4 Routes
ASIC IPv6 Routes
BGP Neighbours Down
Device CPU Core Temperature
Device CPU Utilization
Device Down
Device Memory Utilization
Device Queue Counter
FAN Speed
Failed FANs
Failed PSUs
PSU Temperature
SSD Health
SSD Temeperature
SSD Used Memory Percent
frr CPU Utilization
syncd CPU Utilization

Interface: Once the user chooses the rule for Interfaces it will show the below Metrics

Interface Flap
Interface PFC Counters
Interface Queue Counters
Traffic InDiscards
Traffic InErrors
Traffic OutDiscards
Traffic OutErrors
Traffic Rx Utilization
Traffic Tx Utilization
Transceiver Rx Power
Transceiver Temperature
Transceiver Tx Power
Transceiver Voltage

Select: this option depends on the Filter category, possible values are
1. Select HWSKU :
2. Select ROLE :
3. Select OS VERSION :
Metrics: Metrics depend on the above (For: Device/Interface) condition
Measure: Metrics are measured in three diff ways
1. MIN
2. AVG
3. MAX
Period: Measured metrics can be verified with a buffer of a timer
1. 5 min
2. 10 min
3. 15 min
4. 30 min
5. 1 hour

Conditions

When Measured Value is: This option allows a user to choose what condition has to match when the measured value is
1. EQ: Equal to
2. NEQ: Not Equal to
3. GE: Greater than Equal to
4. LE: Less than Equal to
5. GT: Greater than
6. LT: Less than
Critical Threshold: The user can set a Critical value on which push notification will be triggered
Warning Threshold: The user can set a Warning value on which push notification will be triggered

Notification

Notify: The user can choose the integrated SLACK Channel
Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket
Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket
Weekly Digest: Slack Users can choose this for Weekly Digest to SLACK Channel
Do not notify if the same alert trigger in 30min, 1hour, 2hours, 10hours, 24hours
Stop notifying after: The user can choose a value of occurrence then it will not trigger the same in the next 24 hours

Add Rules: Entity

Add Rules

Navigation >> Watcher >> Rules

Create New & Add the required inputs

Preview & Create

Once a user create the rule it will be available in the rule list

Once the device SSD Memory Utilization goes above the threshold value it will start pushing notifications to SLACK & Zendesk Support tickets & also inside the ONES Alert Page

Add Rules: Entity by Properties

Add Rules

Navigation >> Watcher >> Rules

Create New & Add the required inputs

Preview & Create

Once a user creates the rule it will be available in the rule list

Once the device CPU Utilization goes above the threshold value it will start pushing notifications to SLACK & Zendesk Support tickets and the ONES App Alert Page

VXLAN-SVI

MH-VXLAN

MCLAG

ONES Orchestration

This section explains how large data centers can be designed seamlessly using ONES.

Configuring Devices

Most fabric orchestration solutions available today are complex and often difficult to understand. ONES provides simple and effective tools, such as predefined templates (YAML file), to configure data centers at scale. ONES allows a customized way of configuring devices that includes enhancements to the standard configuration.

Configuration Commands:

Save Config:
Copy to File:
Restore Config: //If needed only

Speed config for the Host Facing port should be updated before Orchestration if there is any change in the default speed config.

Ex: Interface speed is 25G, but you can use it with 10G Transceiver. In such cases, user needs to update speed.

Configuration Commands:

Update Speed:

Configuration Commands:

Save Config:
Copy to File:
Restore Config: //If needed only

You need to provide the following inputs to configure the devices:

Device Details

Username - Device User-Name

Management IP - Device IP for management

Device Credentials - Login admin user-name & password with write permission

BGP ASN (Autonomous System Number)

Local AS number - Local BGP AS number a user wants to use

Subnet Details

IPv4 Subnet - IPv4 address range a user wants to use in the domain

IPv4 Loopback - IPv4 address range to use on the devices only for the loopback address

IPv6 Subnet - IPv6 address range a user wants to use in the domain

Connectivity

Link connectivity between (SuperSpine, Spine, Leaf & TOR)

Link Type (Access Trunk)

Layer-2 / Layer3 - interface type

MCLAG Details

VLAN - VLAN to b used for interfaces

PO Group - PortChannel number to be used to bundle the interface

Keepalive VLAN - VLAN a user wants to use to send keepalive messages

VRF number - VRF number to be used for MC-LAG

Host Interface

L2 Access & VLAN - Host facing interface with Access port & VLAN allocation

L2 Trunk & VLAN - Host facing interface with trunk port & VLAN allocation

L3 - Host facing interface with Layer 3 properties

Network Service Address

NTP server - NTP server a user wants to add

Syslog - Syslog server IP address

SNMP - SNMP Server address a user wants to add

VXLAN

VLAN Range - VLAN range a user wants to use for VXLAN Ex. 200-205

VNI Range - VNI range a user wants to use for VXLAN Ex.20000-20005

Any-Cast Gateway - Any-cast Gateway Subnet

Host Per Vlan - Allocation of Host per VLAN

IRB VLAN Range - IRB VLAN is a separate input and should not overlap with VXLAN VNI

IRB VNI Range - IRB VNI is separate input and should not overlap with VXLAN VNI

QoS

dscp_to_tc_map - DSCP to TC mapping a user wants to use Ex. "26:3 | 48:7"

dot1p_to_tc_map - dot1p to TC mapping inputs

tc_to_queue_map - TC to queue mapping inputs Ex. "3:3 | 7:7"

tc_to_pg_map - TC to PG mapping inputs Ex. "3:3 | 7:7"

pfc_enable - PFC value to be enable Ex. "3"

pfcwd - user can choose this feature to be enable disable with below inputs

enable: false

big_red_switch: false

action: "alert"

restoration_time: 400

detection_time: 400

ecn - user can use Explicit congention notification inputs can be added as per infra, below are the inputs can be used

mode: "ecn"

cnp_queue: 7

ecn_gmin: 500000

ecn_gmax: 1500000

ecn_gmark: 10

ecn_rmin: null

ecn_rmax: null

ecn_rmark: null

ecn_ymin: null

ecn_ymax: null

ecn_ymark: null

scheduler:

type: "DWRR"

weight: "0:0 | 1:0 | 2:0 | 3:90 | 4:0 | 5:0 | 6:0"

ONES requires a minimal set of information from the users to configure the devices. The tool is simple to use and allows to configure a large number of devices simultaneously.

Configuration Overview

This section explains the device configuration procedures, that gets applied seamlessly across the entire fabric

Navigate to Configurations >> Devices

Click on the Configure Devices button in the top right corner. This opens a new screen with a sample device configuration. You can edit the configurations directly in the UI to make the desired changes. You can also download the sample YAML file by clicking on Download YAML button, provided at the bottom of the above screen, make new changes and upload the YAML file using Upload YAML button.

A detailed explanation of all the intend fields

Inventory: Specify how many devices you want to add in any particular role - Super Spine, Spine, Leaf, and ToR.

Connectivity: Specify the parameters required to establish link connectivity such as:

Device switch ID: unique ID for every device, required to correctly render the topology
Switch name: hostname of the device
IP address: management address of the device
Autonomous System Number (ASN): BGP AS number to use
Device Credentials: Username & Password.
MCLAG: Multichassis Link Aggregation
Links: links connected with another device

BGP: Specify if you want to enable regular BGP peering or BGP unnumbered peering.

PhysicalIfCfg: Enable or disable FEC and change the MTU settings on all the links being configured.

ASN: Assign a BGP ASN (Autonomous System Number) from the specified pool. Dynamic assigning ASN will be implemented in ONES release 2.0. For release 1.0, you need to specify the ASN under the device configuration, as shown in the sample YAML file.

IPv4Pool: Assign IP pools to different subnets. ONES automatically divides the subnets according to the number of available links.

ONES application uses IPv4 subnets for:

Interfaces
Loopbacks
Host interfaces
To configure BGP neighborship
ONES automatically advertises these subnets in BGP

IPv6Pool: Assign IPv6 subnet.

ONES application uses:

IPv6 subnet for interfaces
Subnets to configure BGP neighborship
Automatically advertise these subnets in BGP

Note* IPv6 loopback is not supported

NTP: Provide the NTP server address, to enable NTP. You can choose your desired timezone.

Supported Time Zone

Africa/Abidjan

Africa/Accra

Africa/Addis_Ababa

Africa/Algiers

Africa/Asmara

Africa/Asmera

Africa/Bamako

Africa/Bangui

Africa/Banjul

Africa/Bissau

Africa/Blantyre

Africa/Brazzaville

Africa/Bujumbura

Africa/Cairo

Africa/Casablanca

Africa/Ceuta

Africa/Conakry

Africa/Dakar

Africa/Dar_es_Salaam

Africa/Djibouti

Africa/Douala

Africa/El_Aaiun

Africa/Freetown

Africa/Gaborone

Africa/Harare

Africa/Johannesburg

Africa/Juba

Africa/Kampala

Africa/Khartoum

Africa/Kigali

Africa/Kinshasa

Africa/Lagos

Africa/Libreville

Africa/Lome

Africa/Luanda

Africa/Lubumbashi

Africa/Lusaka

Africa/Malabo

Africa/Maputo

Africa/Maseru

Africa/Mbabane

Africa/Mogadishu

Africa/Monrovia

Africa/Nairobi

Africa/Ndjamena

Africa/Niamey

Africa/Nouakchott

Africa/Ouagadougou

Africa/Porto-Novo

Africa/Sao_Tome

Africa/Timbuktu

Africa/Tripoli

Africa/Tunis

Africa/Windhoek

America/Adak

America/Anchorage

America/Anguilla

America/Antigua

America/Araguaina

America/Argentina/Buenos_Aires

America/Argentina/Catamarca

America/Argentina/ComodRivadavia

America/Argentina/Cordoba

America/Argentina/Jujuy

America/Argentina/La_Rioja

America/Argentina/Mendoza

America/Argentina/Rio_Gallegos

America/Argentina/Salta

America/Argentina/San_Juan

America/Argentina/San_Luis

America/Argentina/Tucuman

America/Argentina/Ushuaia

America/Aruba

America/Asuncion

America/Atikokan

America/Atka

America/Bahia

America/Bahia_Banderas

America/Barbados

America/Belem

America/Belize

America/Blanc-Sablon

America/Boa_Vista

America/Bogota

America/Boise

America/Buenos_Aires

America/Cambridge_Bay

America/Campo_Grande

America/Cancun

America/Caracas

America/Catamarca

America/Cayenne

America/Cayman

America/Chicago

America/Chihuahua

America/Ciudad_Juarez

America/Coral_Harbour

America/Cordoba

America/Costa_Rica

America/Creston

America/Cuiaba

America/Curacao

America/Danmarkshavn

America/Dawson

America/Dawson_Creek

America/Denver

America/Detroit

America/Dominica

America/Edmonton

America/Eirunepe

America/El_Salvador

America/Ensenada

America/Fort_Nelson

America/Fort_Wayne

America/Fortaleza

America/Glace_Bay

America/Godthab

America/Goose_Bay

America/Grand_Turk

America/Grenada

America/Guadeloupe

America/Guatemala

America/Guayaquil

America/Guyana

America/Halifax

America/Havana

America/Hermosillo

America/Indiana/Indianapolis

America/Indiana/Knox

America/Indiana/Marengo

America/Indiana/Petersburg

America/Indiana/Tell_City

America/Indiana/Vevay

America/Indiana/Vincennes

America/Indiana/Winamac

America/Indianapolis

America/Inuvik

America/Iqaluit

America/Jamaica

America/Jujuy

America/Juneau

America/Kentucky/Louisville

America/Kentucky/Monticello

America/Knox_IN

America/Kralendijk

America/La_Paz

America/Lima

America/Los_Angeles

America/Louisville

America/Lower_Princes

America/Maceio

America/Managua

America/Manaus

America/Marigot

America/Martinique

America/Matamoros

America/Mazatlan

America/Mendoza

America/Menominee

America/Merida

America/Metlakatla

America/Mexico_City

America/Miquelon

America/Moncton

America/Monterrey

America/Montevideo

America/Montreal

America/Montserrat

America/Nassau

America/New_York

America/Nipigon

America/Nome

America/Noronha

America/North_Dakota/Beulah

America/North_Dakota/Center

America/North_Dakota/New_Salem

America/Nuuk

America/Ojinaga

America/Panama

America/Pangnirtung

America/Paramaribo

America/Phoenix

America/Port-au-Prince

America/Port_of_Spain

America/Porto_Acre

America/Porto_Velho

America/Puerto_Rico

America/Punta_Arenas

America/Rainy_River

America/Rankin_Inlet

America/Recife

America/Regina

America/Resolute

America/Rio_Branco

America/Rosario

America/Santa_Isabel

America/Santarem

America/Santiago

America/Santo_Domingo

America/Sao_Paulo

America/Scoresbysund

America/Shiprock

America/Sitka

America/St_Barthelemy

America/St_Johns

America/St_Kitts

America/St_Lucia

America/St_Thomas

America/St_Vincent

America/Swift_Current

America/Tegucigalpa

America/Thule

America/Thunder_Bay

America/Tijuana

America/Toronto

America/Tortola

America/Vancouver

America/Virgin

America/Whitehorse

America/Winnipeg

America/Yakutat

America/Yellowknife

Antarctica/Casey

Antarctica/Davis

Antarctica/DumontDUrville

Antarctica/Macquarie

Antarctica/Mawson

Antarctica/McMurdo

Antarctica/Palmer

Antarctica/Rothera

Antarctica/South_Pole

Antarctica/Syowa

Antarctica/Troll

Antarctica/Vostok

Arctic/Longyearbyen

Asia/Aden

Asia/Almaty

Asia/Amman

Asia/Anadyr

Asia/Aqtau

Asia/Aqtobe

Asia/Ashgabat

Asia/Ashkhabad

Asia/Atyrau

Asia/Baghdad

Asia/Bahrain

Asia/Baku

Asia/Bangkok

Asia/Barnaul

Asia/Beirut

Asia/Bishkek

Asia/Brunei

Asia/Calcutta

Asia/Chita

Asia/Choibalsan

Asia/Chongqing

Asia/Chungking

Asia/Colombo

Asia/Dacca

Asia/Damascus

Asia/Dhaka

Asia/Dili

Asia/Dubai

Asia/Dushanbe

Asia/Famagusta

Asia/Gaza

Asia/Harbin

Asia/Hebron

Asia/Ho_Chi_Minh

Asia/Hong_Kong

Asia/Hovd

Asia/Irkutsk

Asia/Istanbul

Asia/Jakarta

Asia/Jayapura

Asia/Jerusalem

Asia/Kabul

Asia/Kamchatka

Asia/Karachi

Asia/Kashgar

Asia/Kathmandu

Asia/Katmandu

Asia/Khandyga

Asia/Kolkata

Asia/Krasnoyarsk

Asia/Kuala_Lumpur

Asia/Kuching

Asia/Kuwait

Asia/Macao

Asia/Macau

Asia/Magadan

Asia/Makassar

Asia/Manila

Asia/Muscat

Asia/Nicosia

Asia/Novokuznetsk

Asia/Novosibirsk

Asia/Omsk

Asia/Oral

Asia/Phnom_Penh

Asia/Pontianak

Asia/Pyongyang

Asia/Qatar

Asia/Qostanay

Asia/Qyzylorda

Asia/Rangoon

Asia/Riyadh

Asia/Saigon

Asia/Sakhalin

Asia/Samarkand

Asia/Seoul

Asia/Shanghai

Asia/Singapore

Asia/Srednekolymsk

Asia/Taipei

Asia/Tashkent

Asia/Tbilisi

Asia/Tehran

Asia/Tel_Aviv

Asia/Thimbu

Asia/Thimphu

Asia/Tokyo

Asia/Tomsk

Asia/Ujung_Pandang

Asia/Ulaanbaatar

Asia/Ulan_Bator

Asia/Urumqi

Asia/Ust-Nera

Asia/Vientiane

Asia/Vladivostok

Asia/Yakutsk

Asia/Yangon

Asia/Yekaterinburg

Asia/Yerevan

Atlantic/Azores

Atlantic/Bermuda

Atlantic/Canary

Atlantic/Cape_Verde

Atlantic/Faeroe

Atlantic/Faroe

Atlantic/Jan_Mayen

Atlantic/Madeira

Atlantic/Reykjavik

Atlantic/South_Georgia

Atlantic/St_Helena

Atlantic/Stanley

Australia/ACT

Australia/Adelaide

Australia/Brisbane

Australia/Broken_Hill

Australia/Canberra

Australia/Currie

Australia/Darwin

Australia/Eucla

Australia/Hobart

Australia/LHI

Australia/Lindeman

Australia/Lord_Howe

Australia/Melbourne

Australia/NSW

Australia/North

Australia/Perth

Australia/Queensland

Australia/South

Australia/Sydney

Australia/Tasmania

Australia/Victoria

Australia/West

Australia/Yancowinna

Brazil/Acre

Brazil/DeNoronha

Brazil/East

Brazil/West

CET

CST6CDT

Canada/Atlantic

Canada/Central

Canada/Eastern

Canada/Mountain

Canada/Newfoundland

Canada/Pacific

Canada/Saskatchewan

Canada/Yukon

Chile/Continental

Chile/EasterIsland

Cuba

EET

EST

EST5EDT

Egypt

Eire

Etc/GMT

Etc/GMT+0

Etc/GMT+1

Etc/GMT+10

Etc/GMT+11

Etc/GMT+12

Etc/GMT+2

Etc/GMT+3

Etc/GMT+4

Etc/GMT+5

Etc/GMT+6

Etc/GMT+7

Etc/GMT+8

Etc/GMT+9

Etc/GMT-0

Etc/GMT-1

Etc/GMT-10

Etc/GMT-11

Etc/GMT-12

Etc/GMT-13

Etc/GMT-14

Etc/GMT-2

Etc/GMT-3

Etc/GMT-4

Etc/GMT-5

Etc/GMT-6

Etc/GMT-7

Etc/GMT-8

Etc/GMT-9

Etc/GMT0

Etc/Greenwich

Etc/UCT

Etc/UTC

Etc/Universal

Etc/Zulu

Europe/Amsterdam

Europe/Andorra

Europe/Astrakhan

Europe/Athens

Europe/Belfast

Europe/Belgrade

Europe/Berlin

Europe/Bratislava

Europe/Brussels

Europe/Bucharest

Europe/Budapest

Europe/Busingen

Europe/Chisinau

Europe/Copenhagen

Europe/Dublin

Europe/Gibraltar

Europe/Guernsey

Europe/Helsinki

Europe/Isle_of_Man

Europe/Istanbul

Europe/Jersey

Europe/Kaliningrad

Europe/Kiev

Europe/Kirov

Europe/Kyiv

Europe/Lisbon

Europe/Ljubljana

Europe/London

Europe/Luxembourg

Europe/Madrid

Europe/Malta

Europe/Mariehamn

Europe/Minsk

Europe/Monaco

Europe/Moscow

Europe/Nicosia

Europe/Oslo

Europe/Paris

Europe/Podgorica

Europe/Prague

Europe/Riga

Europe/Rome

Europe/Samara

Europe/San_Marino

Europe/Sarajevo

Europe/Saratov

Europe/Simferopol

Europe/Skopje

Europe/Sofia

Europe/Stockholm

Europe/Tallinn

Europe/Tirane

Europe/Tiraspol

Europe/Ulyanovsk

Europe/Uzhgorod

Europe/Vaduz

Europe/Vatican

Europe/Vienna

Europe/Vilnius

Europe/Volgograd

Europe/Warsaw

Europe/Zagreb

Europe/Zaporozhye

Europe/Zurich

Factory

GB-Eire

GMT

GMT+0

GMT-0

GMT0

Greenwich

HST

Hongkong

Iceland

Indian/Antananarivo

Indian/Chagos

Indian/Christmas

Indian/Cocos

Indian/Comoro

Indian/Kerguelen

Indian/Mahe

Indian/Maldives

Indian/Mauritius

Indian/Mayotte

Indian/Reunion

Iran

Israel

Jamaica

Japan

Kwajalein

Libya

MET

MST

MST7MDT

Mexico/BajaNorte

Mexico/BajaSur

Mexico/General

NZ-CHAT

Navajo

PRC

PST8PDT

Pacific/Apia

Pacific/Auckland

Pacific/Bougainville

Pacific/Chatham

Pacific/Chuuk

Pacific/Easter

Pacific/Efate

Pacific/Enderbury

Pacific/Fakaofo

Pacific/Fiji

Pacific/Funafuti

Pacific/Galapagos

Pacific/Gambier

Pacific/Guadalcanal

Pacific/Guam

Pacific/Honolulu

Pacific/Johnston

Pacific/Kanton

Pacific/Kiritimati

Pacific/Kosrae

Pacific/Kwajalein

Pacific/Majuro

Pacific/Marquesas

Pacific/Midway

Pacific/Nauru

Pacific/Niue

Pacific/Norfolk

Pacific/Noumea

Pacific/Pago_Pago

Pacific/Palau

Pacific/Pitcairn

Pacific/Pohnpei

Pacific/Ponape

Pacific/Port_Moresby

Pacific/Rarotonga

Pacific/Saipan

Pacific/Samoa

Pacific/Tahiti

Pacific/Tarawa

Pacific/Tongatapu

Pacific/Truk

Pacific/Wake

Pacific/Wallis

Pacific/Yap

Poland

Portugal

ROC

ROK

Singapore

SystemV/AST4

SystemV/AST4ADT

SystemV/CST6

SystemV/CST6CDT

SystemV/EST5

SystemV/EST5EDT

SystemV/HST10

SystemV/MST7

SystemV/MST7MDT

SystemV/PST8

SystemV/PST8PDT

SystemV/YST9

SystemV/YST9YDT

Turkey

UCT

US/Alaska

US/Aleutian

US/Arizona

US/Central

US/East-Indiana

US/Eastern

US/Hawaii

US/Indiana-Starke

US/Michigan

US/Mountain

US/Pacific

US/Samoa

UTC

Universal

W-SU

WET

Zulu

SYSLOG: Provide the SYSLOG server address, to enable SYSLOG.

SNMP: Provide the SNMP server address, to enable SNMP.

Parameters: Provide user the ability to enable VXLAN and related Parameters.

QoS: Provide user the ability to enable RoCE related configuration.

Creating Configuration

Navigate to Configurations >> Devices >> Configure Devices

Applying Configuration

Click on Apply Configs button in the bottom right corner of the above screen, to push the configs across the entire fabric.

ONES provides real-time updates when the devices are being configured and validates the configurations automatically to ensure the network is ready to use.

You will see the below screen, after the configurations are successfully verified:

FRR config Issue

With Few versions of FRR, when user gives reboot, existing config is erased and default config is pushed to FRR. This will lead to missing the configuration for users. below is the workaround config in this situation

Go inside BGP Container & Open docker_init.sh
Look for "Split" Keyword & Comment out the statemets inside that with if conditions
Add a new line which writes Service integrated in vtysh.conf
Comment rm -f /etc/frr/frr.conf & save the changes
Commit the docker Changes

Various fields shown in the top right corner of the above slide are explained below:

Connect

Configuration Page allows a user to connect to the device using console access or using SSH method too.

Navigate >> Configurations >> Devices >> Connect

User can choose SSH or console option to access the device.

Console Logs

Console Logs show the exact configuration loaded on the device and the overview of the config loaded as per YAML & Derived Host IP Range can be viewed from the "Derived_Config:" section

Navigate >> Configurations >> Devices >> Console Logs

Click on the Console Log of the device

Config

This section describes the configuration feature of ONES using which you can check the applied and running configurations.

Navigate >> Configurations >> Devices >> Config

Click on Config

Compare Configuration

This section describes the compare configuration feature of ONES using which you can compare the applied and running configurations.

Navigate >> Configurations >> Devices >> Compare Configs

Compare Config

This page allows the user to compare applied configurations to the running configuration of a selected device.

The user should select only one device from the list and perform 'Compare Config' on this page, it may take several minutes to fetch the running configuration from the device

YAML Editor will appear with two windows comparing applied and running configurations as depicted in the below picture

The difference in configuration is highlighted with colour coding in the respective window of the configuration

Backup & Configuration

This Section describe the use of Backup & Restore Configuration across all the managed devices

Navigate >> Configurations >> Devices >> Backup & Restore Configs

Using this feature, a user will be able to take multiple backups and will be able to restore the backup at any time.

Taking a Backup

Select Backup & Restore Configs

Give a Tag Name to the device & Select the device, the device you want to take a backup config
Submit the task

Once submitted the config will backup with the given name & can be used to restore the config at any time in future

Restoring a Backup

Select Backup & Restore Configs
Select Restore Config

Click on the drop-down button of the device on which the user wants to restore the config

Select the backup a user wants to restore from the Backups Available list
Then Submit the backup & Click on Yes to confirm

VXLAN-SVI-no-mclag-ebgp-IPv4-Underlay

If devices are already holding V1.3 orchestrated configuration, then V2.0 configuration would not be integrated along, the user needs to use the V2.0 template only while using GA2.0

Template Details: VXLAN-SVI-no-mclag-ebgp-IPv4-Underlay

Devices used
- 2- Spine Devices
- 4- Leaf Devices
- 4- End Host

VXLAN-SVI-no-mclag-ebgp-IPv4-Underlay Standard Template

Inventory:
  SSpines: 0
  Spines: 2
  Leafs: 4
  Tors: 0
Connectivity:
  SSpine: []
  Spine:
    - switchId: 1
      switchName: "Spine-1"
      ipAddress: "100.100.10.11"
      ASN: 2001
      Credentials:
        user: "admin"
        password: "admin"
      mclag: 
      Links:
        - link: "S1_Ethernet0 | L1_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet4 | L2_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet8 | L3_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet12 | L4_Ethernet48"
          staticLink: true
          properties: 
    - switchId: 2
      switchName: "Spine-2"
      ipAddress: "100.100.10.12"
      ASN: 2002
      Credentials:
        user: "admin"
        password: "admin"
      mclag: 
      Links:
        - link: "S2_Ethernet0 | L1_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet4 | L2_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet8 | L3_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet12 | L4_Ethernet52"
          staticLink: true
          properties: 
  Leaf:
    - switchId: 1
      switchName: "Leaf-1"
      ipAddress: "100.100.10.13"
      ASN: 1001
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
      Links:
        - link: "L1_Ethernet48 | S1_Ethernet0"
          staticLink: true
          properties: 
        - link: "L1_Ethernet52 | S2_Ethernet0"
          staticLink: true
          properties: 
        - link: "L1_Ethernet0 |  H1_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 201
    - switchId: 2
      switchName: "Leaf-2"
      ipAddress: "100.100.10.14"
      ASN: 1002
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
      Links:
        - link: "L2_Ethernet48 | S1_Ethernet4"
          staticLink: true
          properties: 
        - link: "L2_Ethernet52 | S2_Ethernet4"
          staticLink: true
          properties: 
        - link: "L2_Ethernet4 |  H2_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 202
    - switchId: 3
      switchName: "Leaf-3"
      ipAddress: "100.100.10.15"
      ASN: 1003
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
      Links:
        - link: "L3_Ethernet48 | S1_Ethernet8"
          staticLink: true
          properties: 
        - link: "L3_Ethernet52 | S2_Ethernet8"
          staticLink: true
          properties: 
        - link: "L3_Ethernet0 |  H3_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 203
    - switchId: 4
      switchName: "Leaf-4"
      ipAddress: "100.100.10.16"
      ASN: 1004
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
      Links:
        - link: "L4_Ethernet48 | S1_Ethernet12"
          staticLink: true
          properties: 
        - link: "L4_Ethernet52 | S2_Ethernet12"
          staticLink: true
          properties: 
        - link: "L4_Ethernet4 |  H4_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 204
  Tor: []
BGP:
  BGP_U: false
  ND_RA: 30
PhysicalIfCfg:
  FEC: "Off"
  MTU: 9000
  AdminStatus: "Up"
ASN:
  SSpine: "10000-20000"
  Spine: "21000-50000"
  Leaf: "51000-60000"
  Tor: "61000-70000"
IPv4Pool:
  Loopback: "10.10.10.0/24"
  LeafSpine: "49.0.0.0/24"
  LeafTor: "40.0.0.0/24"
  Host: "39.0.0.0/24"
IPv6Pool:
  LeafSpine: 
  LeafTor: 
  Host: 
NTP:
  server: "100.100.10.10"
  timezone: "Asia/Kolkata"
SYSLOG:
  server: "100.100.10.10"
SNMP:
  trapserver: "100.100.10.10"
Parameters:
  vlan: "200-205"
  vni: "20000-20005"
  anycast_gateway: "106.10.0.0/23"
  anycast_mac: "00:11:22:33:55:44"
  hosts_per_vlan: 10
  routing_symmetric: false
  sag: False

Supported Time Zone

Africa/Abidjan

Africa/Accra

Africa/Addis_Ababa

Africa/Algiers

Africa/Asmara

Africa/Asmera

Africa/Bamako

Africa/Bangui

Africa/Banjul

Africa/Bissau

Africa/Blantyre

Africa/Brazzaville

Africa/Bujumbura

Africa/Cairo

Africa/Casablanca

Africa/Ceuta

Africa/Conakry

Africa/Dakar

Africa/Dar_es_Salaam

Africa/Djibouti

Africa/Douala

Africa/El_Aaiun

Africa/Freetown

Africa/Gaborone

Africa/Harare

Africa/Johannesburg

Africa/Juba

Africa/Kampala

Africa/Khartoum

Africa/Kigali

Africa/Kinshasa

Africa/Lagos

Africa/Libreville

Africa/Lome

Africa/Luanda

Africa/Lubumbashi

Africa/Lusaka

Africa/Malabo

Africa/Maputo

Africa/Maseru

Africa/Mbabane

Africa/Mogadishu

Africa/Monrovia

Africa/Nairobi

Africa/Ndjamena

Africa/Niamey

Africa/Nouakchott

Africa/Ouagadougou

Africa/Porto-Novo

Africa/Sao_Tome

Africa/Timbuktu

Africa/Tripoli

Africa/Tunis

Africa/Windhoek

America/Adak

America/Anchorage

America/Anguilla

America/Antigua

America/Araguaina

America/Argentina/Buenos_Aires

America/Argentina/Catamarca

America/Argentina/ComodRivadavia

America/Argentina/Cordoba

America/Argentina/Jujuy

America/Argentina/La_Rioja

America/Argentina/Mendoza

America/Argentina/Rio_Gallegos

America/Argentina/Salta

America/Argentina/San_Juan

America/Argentina/San_Luis

America/Argentina/Tucuman

America/Argentina/Ushuaia

America/Aruba

America/Asuncion

America/Atikokan

America/Atka

America/Bahia

America/Bahia_Banderas

America/Barbados

America/Belem

America/Belize

America/Blanc-Sablon

America/Boa_Vista

America/Bogota

America/Boise

America/Buenos_Aires

America/Cambridge_Bay

America/Campo_Grande

America/Cancun

America/Caracas

America/Catamarca

America/Cayenne

America/Cayman

America/Chicago

America/Chihuahua

America/Ciudad_Juarez

America/Coral_Harbour

America/Cordoba

America/Costa_Rica

America/Creston

America/Cuiaba

America/Curacao

America/Danmarkshavn

America/Dawson

America/Dawson_Creek

America/Denver

America/Detroit

America/Dominica

America/Edmonton

America/Eirunepe

America/El_Salvador

America/Ensenada

America/Fort_Nelson

America/Fort_Wayne

America/Fortaleza

America/Glace_Bay

America/Godthab

America/Goose_Bay

America/Grand_Turk

America/Grenada

America/Guadeloupe

America/Guatemala

America/Guayaquil

America/Guyana

America/Halifax

America/Havana

America/Hermosillo

America/Indiana/Indianapolis

America/Indiana/Knox

America/Indiana/Marengo

America/Indiana/Petersburg

America/Indiana/Tell_City

America/Indiana/Vevay

America/Indiana/Vincennes

America/Indiana/Winamac

America/Indianapolis

America/Inuvik

America/Iqaluit

America/Jamaica

America/Jujuy

America/Juneau

America/Kentucky/Louisville

America/Kentucky/Monticello

America/Knox_IN

America/Kralendijk

America/La_Paz

America/Lima

America/Los_Angeles

America/Louisville

America/Lower_Princes

America/Maceio

America/Managua

America/Manaus

America/Marigot

America/Martinique

America/Matamoros

America/Mazatlan

America/Mendoza

America/Menominee

America/Merida

America/Metlakatla

America/Mexico_City

America/Miquelon

America/Moncton

America/Monterrey

America/Montevideo

America/Montreal

America/Montserrat

America/Nassau

America/New_York

America/Nipigon

America/Nome

America/Noronha

America/North_Dakota/Beulah

America/North_Dakota/Center

America/North_Dakota/New_Salem

America/Nuuk

America/Ojinaga

America/Panama

America/Pangnirtung

America/Paramaribo

America/Phoenix

America/Port-au-Prince

America/Port_of_Spain

America/Porto_Acre

America/Porto_Velho

America/Puerto_Rico

America/Punta_Arenas

America/Rainy_River

America/Rankin_Inlet

America/Recife

America/Regina

America/Resolute

America/Rio_Branco

America/Rosario

America/Santa_Isabel

America/Santarem

America/Santiago

America/Santo_Domingo

America/Sao_Paulo

America/Scoresbysund

America/Shiprock

America/Sitka

America/St_Barthelemy

America/St_Johns

America/St_Kitts

America/St_Lucia

America/St_Thomas

America/St_Vincent

America/Swift_Current

America/Tegucigalpa

America/Thule

America/Thunder_Bay

America/Tijuana

America/Toronto

America/Tortola

America/Vancouver

America/Virgin

America/Whitehorse

America/Winnipeg

America/Yakutat

America/Yellowknife

Antarctica/Casey

Antarctica/Davis

Antarctica/DumontDUrville

Antarctica/Macquarie

Antarctica/Mawson

Antarctica/McMurdo

Antarctica/Palmer

Antarctica/Rothera

Antarctica/South_Pole

Antarctica/Syowa

Antarctica/Troll

Antarctica/Vostok

Arctic/Longyearbyen

Asia/Aden

Asia/Almaty

Asia/Amman

Asia/Anadyr

Asia/Aqtau

Asia/Aqtobe

Asia/Ashgabat

Asia/Ashkhabad

Asia/Atyrau

Asia/Baghdad

Asia/Bahrain

Asia/Baku

Asia/Bangkok

Asia/Barnaul

Asia/Beirut

Asia/Bishkek

Asia/Brunei

Asia/Calcutta

Asia/Chita

Asia/Choibalsan

Asia/Chongqing

Asia/Chungking

Asia/Colombo

Asia/Dacca

Asia/Damascus

Asia/Dhaka

Asia/Dili

Asia/Dubai

Asia/Dushanbe

Asia/Famagusta

Asia/Gaza

Asia/Harbin

Asia/Hebron

Asia/Ho_Chi_Minh

Asia/Hong_Kong

Asia/Hovd

Asia/Irkutsk

Asia/Istanbul

Asia/Jakarta

Asia/Jayapura

Asia/Jerusalem

Asia/Kabul

Asia/Kamchatka

Asia/Karachi

Asia/Kashgar

Asia/Kathmandu

Asia/Katmandu

Asia/Khandyga

Asia/Kolkata

Asia/Krasnoyarsk

Asia/Kuala_Lumpur

Asia/Kuching

Asia/Kuwait

Asia/Macao

Asia/Macau

Asia/Magadan

Asia/Makassar

Asia/Manila

Asia/Muscat

Asia/Nicosia

Asia/Novokuznetsk

Asia/Novosibirsk

Asia/Omsk

Asia/Oral

Asia/Phnom_Penh

Asia/Pontianak

Asia/Pyongyang

Asia/Qatar

Asia/Qostanay

Asia/Qyzylorda

Asia/Rangoon

Asia/Riyadh

Asia/Saigon

Asia/Sakhalin

Asia/Samarkand

Asia/Seoul

Asia/Shanghai

Asia/Singapore

Asia/Srednekolymsk

Asia/Taipei

Asia/Tashkent

Asia/Tbilisi

Asia/Tehran

Asia/Tel_Aviv

Asia/Thimbu

Asia/Thimphu

Asia/Tokyo

Asia/Tomsk

Asia/Ujung_Pandang

Asia/Ulaanbaatar

Asia/Ulan_Bator

Asia/Urumqi

Asia/Ust-Nera

Asia/Vientiane

Asia/Vladivostok

Asia/Yakutsk

Asia/Yangon

Asia/Yekaterinburg

Asia/Yerevan

Atlantic/Azores

Atlantic/Bermuda

Atlantic/Canary

Atlantic/Cape_Verde

Atlantic/Faeroe

Atlantic/Faroe

Atlantic/Jan_Mayen

Atlantic/Madeira

Atlantic/Reykjavik

Atlantic/South_Georgia

Atlantic/St_Helena

Atlantic/Stanley

Australia/ACT

Australia/Adelaide

Australia/Brisbane

Australia/Broken_Hill

Australia/Canberra

Australia/Currie

Australia/Darwin

Australia/Eucla

Australia/Hobart

Australia/LHI

Australia/Lindeman

Australia/Lord_Howe

Australia/Melbourne

Australia/NSW

Australia/North

Australia/Perth

Australia/Queensland

Australia/South

Australia/Sydney

Australia/Tasmania

Australia/Victoria

Australia/West

Australia/Yancowinna

Brazil/Acre

Brazil/DeNoronha

Brazil/East

Brazil/West

CET

CST6CDT

Canada/Atlantic

Canada/Central

Canada/Eastern

Canada/Mountain

Canada/Newfoundland

Canada/Pacific

Canada/Saskatchewan

Canada/Yukon

Chile/Continental

Chile/EasterIsland

Cuba

EET

EST

EST5EDT

Egypt

Eire

Etc/GMT

Etc/GMT+0

Etc/GMT+1

Etc/GMT+10

Etc/GMT+11

Etc/GMT+12

Etc/GMT+2

Etc/GMT+3

Etc/GMT+4

Etc/GMT+5

Etc/GMT+6

Etc/GMT+7

Etc/GMT+8

Etc/GMT+9

Etc/GMT-0

Etc/GMT-1

Etc/GMT-10

Etc/GMT-11

Etc/GMT-12

Etc/GMT-13

Etc/GMT-14

Etc/GMT-2

Etc/GMT-3

Etc/GMT-4

Etc/GMT-5

Etc/GMT-6

Etc/GMT-7

Etc/GMT-8

Etc/GMT-9

Etc/GMT0

Etc/Greenwich

Etc/UCT

Etc/UTC

Etc/Universal

Etc/Zulu

Europe/Amsterdam

Europe/Andorra

Europe/Astrakhan

Europe/Athens

Europe/Belfast

Europe/Belgrade

Europe/Berlin

Europe/Bratislava

Europe/Brussels

Europe/Bucharest

Europe/Budapest

Europe/Busingen

Europe/Chisinau

Europe/Copenhagen

Europe/Dublin

Europe/Gibraltar

Europe/Guernsey

Europe/Helsinki

Europe/Isle_of_Man

Europe/Istanbul

Europe/Jersey

Europe/Kaliningrad

Europe/Kiev

Europe/Kirov

Europe/Kyiv

Europe/Lisbon

Europe/Ljubljana

Europe/London

Europe/Luxembourg

Europe/Madrid

Europe/Malta

Europe/Mariehamn

Europe/Minsk

Europe/Monaco

Europe/Moscow

Europe/Nicosia

Europe/Oslo

Europe/Paris

Europe/Podgorica

Europe/Prague

Europe/Riga

Europe/Rome

Europe/Samara

Europe/San_Marino

Europe/Sarajevo

Europe/Saratov

Europe/Simferopol

Europe/Skopje

Europe/Sofia

Europe/Stockholm

Europe/Tallinn

Europe/Tirane

Europe/Tiraspol

Europe/Ulyanovsk

Europe/Uzhgorod

Europe/Vaduz

Europe/Vatican

Europe/Vienna

Europe/Vilnius

Europe/Volgograd

Europe/Warsaw

Europe/Zagreb

Europe/Zaporozhye

Europe/Zurich

Factory

GB-Eire

GMT

GMT+0

GMT-0

GMT0

Greenwich

HST

Hongkong

Iceland

Indian/Antananarivo

Indian/Chagos

Indian/Christmas

Indian/Cocos

Indian/Comoro

Indian/Kerguelen

Indian/Mahe

Indian/Maldives

Indian/Mauritius

Indian/Mayotte

Indian/Reunion

Iran

Israel

Jamaica

Japan

Kwajalein

Libya

MET

MST

MST7MDT

Mexico/BajaNorte

Mexico/BajaSur

Mexico/General

NZ-CHAT

Navajo

PRC

PST8PDT

Pacific/Apia

Pacific/Auckland

Pacific/Bougainville

Pacific/Chatham

Pacific/Chuuk

Pacific/Easter

Pacific/Efate

Pacific/Enderbury

Pacific/Fakaofo

Pacific/Fiji

Pacific/Funafuti

Pacific/Galapagos

Pacific/Gambier

Pacific/Guadalcanal

Pacific/Guam

Pacific/Honolulu

Pacific/Johnston

Pacific/Kanton

Pacific/Kiritimati

Pacific/Kosrae

Pacific/Kwajalein

Pacific/Majuro

Pacific/Marquesas

Pacific/Midway

Pacific/Nauru

Pacific/Niue

Pacific/Norfolk

Pacific/Noumea

Pacific/Pago_Pago

Pacific/Palau

Pacific/Pitcairn

Pacific/Pohnpei

Pacific/Ponape

Pacific/Port_Moresby

Pacific/Rarotonga

Pacific/Saipan

Pacific/Samoa

Pacific/Tahiti

Pacific/Tarawa

Pacific/Tongatapu

Pacific/Truk

Pacific/Wake

Pacific/Wallis

Pacific/Yap

Poland

Portugal

ROC

ROK

Singapore

SystemV/AST4

SystemV/AST4ADT

SystemV/CST6

SystemV/CST6CDT

SystemV/EST5

SystemV/EST5EDT

SystemV/HST10

SystemV/MST7

SystemV/MST7MDT

SystemV/PST8

SystemV/PST8PDT

SystemV/YST9

SystemV/YST9YDT

Turkey

UCT

US/Alaska

US/Aleutian

US/Arizona

US/Central

US/East-Indiana

US/Eastern

US/Hawaii

US/Indiana-Starke

US/Michigan

US/Mountain

US/Pacific

US/Samoa

UTC

Universal

W-SU

WET

Zulu

VXLAN-Symmetric-SAG-mclag-vrf

If devices are already holding V1.3 orchestrated configuration, then V2.0 configuration would not be integrated along, the user needs to use the V2.0 template only while using GA2.0

Template Details: VXLAN-Symmetric-SAG-no-mclag-vrf

Devices used
- 2- Spine Devices
- 4- Leaf Devices
- 4- End Host

VXLAN-Symmetric-SAG-no-mclag-vrf Standard Template

Inventory:
  SSpines: 0
  Spines: 2
  Leafs: 4
  Tors: 0
Connectivity:
  SSpine: []
  Spine:
    - switchId: 1
      switchName: "Spine-1"
      ipAddress: "100.100.10.11"
      ASN: 2001
      Credentials:
        user: "admin"
        password: "admin"
      mclag: 
      Links:
        - link: "S1_Ethernet0 | L1_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet4 | L2_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet8 | L3_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet12 | L4_Ethernet48"
          staticLink: true
          properties: 
    - switchId: 2
      switchName: "Spine-2"
      ipAddress: "100.100.10.12"
      ASN: 2002
      Credentials:
        user: "admin"
        password: "admin"
      mclag: 
      Links:
        - link: "S2_Ethernet0 | L1_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet4 | L2_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet8 | L3_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet12 | L4_Ethernet52"
          staticLink: true
          properties: 
  Leaf:
    - switchId: 1
      switchName: "Leaf-1"
      ipAddress: "100.100.10.13"
      ASN: 1001
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L2"
        keepalive_vlan: 998
      Links:
        - link: "L1_Ethernet48 | S1_Ethernet0"
          staticLink: true
          properties: 
        - link: "L1_Ethernet52 | S2_Ethernet0"
          staticLink: true
          properties: 
        - link: "L1_Ethernet56 |  L2_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L1_Ethernet0 |  H1_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 300
            mc_po_group: 300
            vrf: "evpn"
        - link: "L1_Ethernet4 |  H2_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 301
            mc_po_group: 301
            vrf: "evpn"
    - switchId: 2
      switchName: "Leaf-2"
      ipAddress: "100.100.10.14"
      ASN: 1001
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L1"
        keepalive_vlan: 998
      Links:
        - link: "L2_Ethernet48 | S1_Ethernet4"
          staticLink: true
          properties: 
        - link: "L2_Ethernet52 | S2_Ethernet4"
          staticLink: true
          properties: 
        - link: "L2_Ethernet56 | L1_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L2_Ethernet0 |  H1_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 300
            mc_po_group: 300
            vrf: "evpn"
        - link: "L2_Ethernet4 |  H2_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 301
            mc_po_group: 301
            vrf: "evpn"
    - switchId: 3
      switchName: "Leaf-3"
      ipAddress: "100.100.10.15"
      ASN: 1002
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L4"
        keepalive_vlan: 998
      Links:
        - link: "L3_Ethernet48 | S1_Ethernet8"
          staticLink: true
          properties: 
        - link: "L3_Ethernet52 | S2_Ethernet8"
          staticLink: true
          properties: 
        - link: "L3_Ethernet56 | L4_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L3_Ethernet0 |  H3_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 300
            mc_po_group: 300
            vrf: "evpn"
        - link: "L3_Ethernet4 |  H4_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 301
            mc_po_group: 301
            vrf: "evpn"
    - switchId: 4
      switchName: "Leaf-4"
      ipAddress: "100.100.10.16"
      ASN: 1002
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L3"
        keepalive_vlan: 998
      Links:
        - link: "L4_Ethernet48 | S1_Ethernet12"
          staticLink: true
          properties: 
        - link: "L4_Ethernet52 | S2_Ethernet12"
          staticLink: true
          properties: 
        - link: "L4_Ethernet56 | L3_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L4_Ethernet0 |  H3_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 300
            mc_po_group: 300
            vrf: "evpn"
        - link: "L4_Ethernet4 |  H4_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 301
            mc_po_group: 301
            vrf: "evpn"
  Tor: []
BGP:
  BGP_U: true
  ND_RA: 30
PhysicalIfCfg:
  FEC: "Off"
  MTU: 9000
  AdminStatus: "Up"
ASN:
  SSpine: "10000-20000"
  Spine: "21000-50000"
  Leaf: "51000-60000"
  Tor: "61000-70000"
IPv4Pool:
  Loopback: "10.10.200.0/24"
  LeafSpine: "40.0.0.0/24"
  LeafTor: "39.0.0.0/24"
  Host: "49.0.0.0/24"
IPv6Pool:
  LeafSpine: 
  LeafTor: 
  Host: 
NTP:
  server: "100.100.10.10"
  timezone: "Asia/Kolkata"
SYSLOG:
  server: "100.100.10.10"
SNMP:
  trapserver: "100.100.10.10"
Parameters:
  vlan: "300-310"
  vni: "10300-10310"
  anycast_gateway: "208.64.160.0/23"
  anycast_mac: "00:11:22:33:44:55"
  hosts_per_vlan: 10
  routing_symmetric: true
  irb_vlan: "800-805"
  irb_vni: "10800-10805"
  sag: true

Supported Time Zone

Africa/Abidjan

Africa/Accra

Africa/Addis_Ababa

Africa/Algiers

Africa/Asmara

Africa/Asmera

Africa/Bamako

Africa/Bangui

Africa/Banjul

Africa/Bissau

Africa/Blantyre

Africa/Brazzaville

Africa/Bujumbura

Africa/Cairo

Africa/Casablanca

Africa/Ceuta

Africa/Conakry

Africa/Dakar

Africa/Dar_es_Salaam

Africa/Djibouti

Africa/Douala

Africa/El_Aaiun

Africa/Freetown

Africa/Gaborone

Africa/Harare

Africa/Johannesburg

Africa/Juba

Africa/Kampala

Africa/Khartoum

Africa/Kigali

Africa/Kinshasa

Africa/Lagos

Africa/Libreville

Africa/Lome

Africa/Luanda

Africa/Lubumbashi

Africa/Lusaka

Africa/Malabo

Africa/Maputo

Africa/Maseru

Africa/Mbabane

Africa/Mogadishu

Africa/Monrovia

Africa/Nairobi

Africa/Ndjamena

Africa/Niamey

Africa/Nouakchott

Africa/Ouagadougou

Africa/Porto-Novo

Africa/Sao_Tome

Africa/Timbuktu

Africa/Tripoli

Africa/Tunis

Africa/Windhoek

America/Adak

America/Anchorage

America/Anguilla

America/Antigua

America/Araguaina

America/Argentina/Buenos_Aires

America/Argentina/Catamarca

America/Argentina/ComodRivadavia

America/Argentina/Cordoba

America/Argentina/Jujuy

America/Argentina/La_Rioja

America/Argentina/Mendoza

America/Argentina/Rio_Gallegos

America/Argentina/Salta

America/Argentina/San_Juan

America/Argentina/San_Luis

America/Argentina/Tucuman

America/Argentina/Ushuaia

America/Aruba

America/Asuncion

America/Atikokan

America/Atka

America/Bahia

America/Bahia_Banderas

America/Barbados

America/Belem

America/Belize

America/Blanc-Sablon

America/Boa_Vista

America/Bogota

America/Boise

America/Buenos_Aires

America/Cambridge_Bay

America/Campo_Grande

America/Cancun

America/Caracas

America/Catamarca

America/Cayenne

America/Cayman

America/Chicago

America/Chihuahua

America/Ciudad_Juarez

America/Coral_Harbour

America/Cordoba

America/Costa_Rica

America/Creston

America/Cuiaba

America/Curacao

America/Danmarkshavn

America/Dawson

America/Dawson_Creek

America/Denver

America/Detroit

America/Dominica

America/Edmonton

America/Eirunepe

America/El_Salvador

America/Ensenada

America/Fort_Nelson

America/Fort_Wayne

America/Fortaleza

America/Glace_Bay

America/Godthab

America/Goose_Bay

America/Grand_Turk

America/Grenada

America/Guadeloupe

America/Guatemala

America/Guayaquil

America/Guyana

America/Halifax

America/Havana

America/Hermosillo

America/Indiana/Indianapolis

America/Indiana/Knox

America/Indiana/Marengo

America/Indiana/Petersburg

America/Indiana/Tell_City

America/Indiana/Vevay

America/Indiana/Vincennes

America/Indiana/Winamac

America/Indianapolis

America/Inuvik

America/Iqaluit

America/Jamaica

America/Jujuy

America/Juneau

America/Kentucky/Louisville

America/Kentucky/Monticello

America/Knox_IN

America/Kralendijk

America/La_Paz

America/Lima

America/Los_Angeles

America/Louisville

America/Lower_Princes

America/Maceio

America/Managua

America/Manaus

America/Marigot

America/Martinique

America/Matamoros

America/Mazatlan

America/Mendoza

America/Menominee

America/Merida

America/Metlakatla

America/Mexico_City

America/Miquelon

America/Moncton

America/Monterrey

America/Montevideo

America/Montreal

America/Montserrat

America/Nassau

America/New_York

America/Nipigon

America/Nome

America/Noronha

America/North_Dakota/Beulah

America/North_Dakota/Center

America/North_Dakota/New_Salem

America/Nuuk

America/Ojinaga

America/Panama

America/Pangnirtung

America/Paramaribo

America/Phoenix

America/Port-au-Prince

America/Port_of_Spain

America/Porto_Acre

America/Porto_Velho

America/Puerto_Rico

America/Punta_Arenas

America/Rainy_River

America/Rankin_Inlet

America/Recife

America/Regina

America/Resolute

America/Rio_Branco

America/Rosario

America/Santa_Isabel

America/Santarem

America/Santiago

America/Santo_Domingo

America/Sao_Paulo

America/Scoresbysund

America/Shiprock

America/Sitka

America/St_Barthelemy

America/St_Johns

America/St_Kitts

America/St_Lucia

America/St_Thomas

America/St_Vincent

America/Swift_Current

America/Tegucigalpa

America/Thule

America/Thunder_Bay

America/Tijuana

America/Toronto

America/Tortola

America/Vancouver

America/Virgin

America/Whitehorse

America/Winnipeg

America/Yakutat

America/Yellowknife

Antarctica/Casey

Antarctica/Davis

Antarctica/DumontDUrville

Antarctica/Macquarie

Antarctica/Mawson

Antarctica/McMurdo

Antarctica/Palmer

Antarctica/Rothera

Antarctica/South_Pole

Antarctica/Syowa

Antarctica/Troll

Antarctica/Vostok

Arctic/Longyearbyen

Asia/Aden

Asia/Almaty

Asia/Amman

Asia/Anadyr

Asia/Aqtau

Asia/Aqtobe

Asia/Ashgabat

Asia/Ashkhabad

Asia/Atyrau

Asia/Baghdad

Asia/Bahrain

Asia/Baku

Asia/Bangkok

Asia/Barnaul

Asia/Beirut

Asia/Bishkek

Asia/Brunei

Asia/Calcutta

Asia/Chita

Asia/Choibalsan

Asia/Chongqing

Asia/Chungking

Asia/Colombo

Asia/Dacca

Asia/Damascus

Asia/Dhaka

Asia/Dili

Asia/Dubai

Asia/Dushanbe

Asia/Famagusta

Asia/Gaza

Asia/Harbin

Asia/Hebron

Asia/Ho_Chi_Minh

Asia/Hong_Kong

Asia/Hovd

Asia/Irkutsk

Asia/Istanbul

Asia/Jakarta

Asia/Jayapura

Asia/Jerusalem

Asia/Kabul

Asia/Kamchatka

Asia/Karachi

Asia/Kashgar

Asia/Kathmandu

Asia/Katmandu

Asia/Khandyga

Asia/Kolkata

Asia/Krasnoyarsk

Asia/Kuala_Lumpur

Asia/Kuching

Asia/Kuwait

Asia/Macao

Asia/Macau

Asia/Magadan

Asia/Makassar

Asia/Manila

Asia/Muscat

Asia/Nicosia

Asia/Novokuznetsk

Asia/Novosibirsk

Asia/Omsk

Asia/Oral

Asia/Phnom_Penh

Asia/Pontianak

Asia/Pyongyang

Asia/Qatar

Asia/Qostanay

Asia/Qyzylorda

Asia/Rangoon

Asia/Riyadh

Asia/Saigon

Asia/Sakhalin

Asia/Samarkand

Asia/Seoul

Asia/Shanghai

Asia/Singapore

Asia/Srednekolymsk

Asia/Taipei

Asia/Tashkent

Asia/Tbilisi

Asia/Tehran

Asia/Tel_Aviv

Asia/Thimbu

Asia/Thimphu

Asia/Tokyo

Asia/Tomsk

Asia/Ujung_Pandang

Asia/Ulaanbaatar

Asia/Ulan_Bator

Asia/Urumqi

Asia/Ust-Nera

Asia/Vientiane

Asia/Vladivostok

Asia/Yakutsk

Asia/Yangon

Asia/Yekaterinburg

Asia/Yerevan

Atlantic/Azores

Atlantic/Bermuda

Atlantic/Canary

Atlantic/Cape_Verde

Atlantic/Faeroe

Atlantic/Faroe

Atlantic/Jan_Mayen

Atlantic/Madeira

Atlantic/Reykjavik

Atlantic/South_Georgia

Atlantic/St_Helena

Atlantic/Stanley

Australia/ACT

Australia/Adelaide

Australia/Brisbane

Australia/Broken_Hill

Australia/Canberra

Australia/Currie

Australia/Darwin

Australia/Eucla

Australia/Hobart

Australia/LHI

Australia/Lindeman

Australia/Lord_Howe

Australia/Melbourne

Australia/NSW

Australia/North

Australia/Perth

Australia/Queensland

Australia/South

Australia/Sydney

Australia/Tasmania

Australia/Victoria

Australia/West

Australia/Yancowinna

Brazil/Acre

Brazil/DeNoronha

Brazil/East

Brazil/West

CET

CST6CDT

Canada/Atlantic

Canada/Central

Canada/Eastern

Canada/Mountain

Canada/Newfoundland

Canada/Pacific

Canada/Saskatchewan

Canada/Yukon

Chile/Continental

Chile/EasterIsland

Cuba

EET

EST

EST5EDT

Egypt

Eire

Etc/GMT

Etc/GMT+0

Etc/GMT+1

Etc/GMT+10

Etc/GMT+11

Etc/GMT+12

Etc/GMT+2

Etc/GMT+3

Etc/GMT+4

Etc/GMT+5

Etc/GMT+6

Etc/GMT+7

Etc/GMT+8

Etc/GMT+9

Etc/GMT-0

Etc/GMT-1

Etc/GMT-10

Etc/GMT-11

Etc/GMT-12

Etc/GMT-13

Etc/GMT-14

Etc/GMT-2

Etc/GMT-3

Etc/GMT-4

Etc/GMT-5

Etc/GMT-6

Etc/GMT-7

Etc/GMT-8

Etc/GMT-9

Etc/GMT0

Etc/Greenwich

Etc/UCT

Etc/UTC

Etc/Universal

Etc/Zulu

Europe/Amsterdam

Europe/Andorra

Europe/Astrakhan

Europe/Athens

Europe/Belfast

Europe/Belgrade

Europe/Berlin

Europe/Bratislava

Europe/Brussels

Europe/Bucharest

Europe/Budapest

Europe/Busingen

Europe/Chisinau

Europe/Copenhagen

Europe/Dublin

Europe/Gibraltar

Europe/Guernsey

Europe/Helsinki

Europe/Isle_of_Man

Europe/Istanbul

Europe/Jersey

Europe/Kaliningrad

Europe/Kiev

Europe/Kirov

Europe/Kyiv

Europe/Lisbon

Europe/Ljubljana

Europe/London

Europe/Luxembourg

Europe/Madrid

Europe/Malta

Europe/Mariehamn

Europe/Minsk

Europe/Monaco

Europe/Moscow

Europe/Nicosia

Europe/Oslo

Europe/Paris

Europe/Podgorica

Europe/Prague

Europe/Riga

Europe/Rome

Europe/Samara

Europe/San_Marino

Europe/Sarajevo

Europe/Saratov

Europe/Simferopol

Europe/Skopje

Europe/Sofia

Europe/Stockholm

Europe/Tallinn

Europe/Tirane

Europe/Tiraspol

Europe/Ulyanovsk

Europe/Uzhgorod

Europe/Vaduz

Europe/Vatican

Europe/Vienna

Europe/Vilnius

Europe/Volgograd

Europe/Warsaw

Europe/Zagreb

Europe/Zaporozhye

Europe/Zurich

Factory

GB-Eire

GMT

GMT+0

GMT-0

GMT0

Greenwich

HST

Hongkong

Iceland

Indian/Antananarivo

Indian/Chagos

Indian/Christmas

Indian/Cocos

Indian/Comoro

Indian/Kerguelen

Indian/Mahe

Indian/Maldives

Indian/Mauritius

Indian/Mayotte

Indian/Reunion

Iran

Israel

Jamaica

Japan

Kwajalein

Libya

MET

MST

MST7MDT

Mexico/BajaNorte

Mexico/BajaSur

Mexico/General

NZ-CHAT

Navajo

PRC

PST8PDT

Pacific/Apia

Pacific/Auckland

Pacific/Bougainville

Pacific/Chatham

Pacific/Chuuk

Pacific/Easter

Pacific/Efate

Pacific/Enderbury

Pacific/Fakaofo

Pacific/Fiji

Pacific/Funafuti

Pacific/Galapagos

Pacific/Gambier

Pacific/Guadalcanal

Pacific/Guam

Pacific/Honolulu

Pacific/Johnston

Pacific/Kanton

Pacific/Kiritimati

Pacific/Kosrae

Pacific/Kwajalein

Pacific/Majuro

Pacific/Marquesas

Pacific/Midway

Pacific/Nauru

Pacific/Niue

Pacific/Norfolk

Pacific/Noumea

Pacific/Pago_Pago

Pacific/Palau

Pacific/Pitcairn

Pacific/Pohnpei

Pacific/Ponape

Pacific/Port_Moresby

Pacific/Rarotonga

Pacific/Saipan

Pacific/Samoa

Pacific/Tahiti

Pacific/Tarawa

Pacific/Tongatapu

Pacific/Truk

Pacific/Wake

Pacific/Wallis

Pacific/Yap

Poland

Portugal

ROC

ROK

Singapore

SystemV/AST4

SystemV/AST4ADT

SystemV/CST6

SystemV/CST6CDT

SystemV/EST5

SystemV/EST5EDT

SystemV/HST10

SystemV/MST7

SystemV/MST7MDT

SystemV/PST8

SystemV/PST8PDT

SystemV/YST9

SystemV/YST9YDT

Turkey

UCT

US/Alaska

US/Aleutian

US/Arizona

US/Central

US/East-Indiana

US/Eastern

US/Hawaii

US/Indiana-Starke

US/Michigan

US/Mountain

US/Pacific

US/Samoa

UTC

Universal

W-SU

WET

Zulu

VXLAN-Symmetric-SVI-mclag-vrf

If devices are already holding V1.3 orchestrated configuration, then V2.0 configuration would not be integrated along, the user needs to use the V2.0 template only while using GA2.0

Template Details: VXLAN-Symmetric-SVI-no-mclag-vrf

Devices used
- 2- Spine Devices
- 4- Leaf Devices
- 4- End Host

VXLAN-Symmetric-SVI-mclag-vrf Standard Template

Inventory:
  SSpines: 0
  Spines: 2
  Leafs: 4
  Tors: 0
Connectivity:
  SSpine: []
  Spine:
    - switchId: 1
      switchName: "Spine-1"
      ipAddress: "100.100.10.11"
      ASN: 21001
      Credentials:
        user: "admin"
        password: "admin"
      mclag: 
      Links:
        - link: "S1_Ethernet0 | L1_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet4 | L2_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet8 | L3_Ethernet48"
          staticLink: true
          properties: 
        - link: "S1_Ethernet12 | L4_Ethernet48"
          staticLink: true
          properties: 
    - switchId: 2
      switchName: "Spine-2"
      ipAddress: "100.100.10.12"
      ASN: 21002
      Credentials:
        user: "admin"
        password: "admin"
      mclag: 
      Links:
        - link: "S2_Ethernet0 | L1_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet4 | L2_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet8 | L3_Ethernet52"
          staticLink: true
          properties: 
        - link: "S2_Ethernet12 | L4_Ethernet52"
          staticLink: true
          properties: 
  Leaf:
    - switchId: 1
      switchName: "Leaf-1"
      ipAddress: "100.100.10.13"
      ASN: 31001
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L2"
        keepalive_vlan: 10
      Links:
        - link: "L1_Ethernet48 | S1_Ethernet0"
          staticLink: true
          properties: 
        - link: "L1_Ethernet52 | S2_Ethernet0"
          staticLink: true
          properties: 
        - link: "L1_Ethernet56 |  L2_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L1_Ethernet0 |  H1_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 500
            mc_po_group: 500
            vrf: 1
        - link: "L1_Ethernet4 |  H2_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 501
            mc_po_group: 501
            vrf: 1
    - switchId: 2
      switchName: "Leaf-2"
      ipAddress: "100.100.10.14"
      ASN: 31001
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L1"
        keepalive_vlan: 10
      Links:
        - link: "L2_Ethernet48 | S1_Ethernet4"
          staticLink: true
          properties: 
        - link: "L2_Ethernet52 | S2_Ethernet4"
          staticLink: true
          properties: 
        - link: "L2_Ethernet56 | L1_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L2_Ethernet0 |  H1_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 500
            mc_po_group: 500
            vrf: 1
        - link: "L2_Ethernet4 |  H2_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 501
            mc_po_group: 501
            vrf: 1
    - switchId: 3
      switchName: "Leaf-3"
      ipAddress: "100.100.10.15"
      ASN: 31002
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L4"
        keepalive_vlan: 10
      Links:
        - link: "L3_Ethernet48 | S1_Ethernet8"
          staticLink: true
          properties: 
        - link: "L3_Ethernet52 | S2_Ethernet8"
          staticLink: true
          properties: 
        - link: "L3_Ethernet56 | L4_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L3_Ethernet0 |  H3_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 500
            mc_po_group: 500
            vrf: 1
        - link: "L3_Ethernet4 |  H4_Ethernet0"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 501
            mc_po_group: 501
            vrf: 1
    - switchId: 4
      switchName: "Leaf-4"
      ipAddress: "100.100.10.16"
      ASN: 31002
      Credentials:
        user: "admin"
        password: "admin"
      mclag:
        enabled: true
        peer: "L3"
        keepalive_vlan: 10
      Links:
        - link: "L4_Ethernet48 | S1_Ethernet12"
          staticLink: true
          properties: 
        - link: "L4_Ethernet52 | S2_Ethernet12"
          staticLink: true
          properties: 
        - link: "L4_Ethernet56 | L3_Ethernet56"
          staticLink: true
          properties:
            mode: "MC-LAG" 
        - link: "L4_Ethernet0 |  H3_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 500
            mc_po_group: 500
            vrf: 1
        - link: "L4_Ethernet4 |  H4_Ethernet1"
          staticLink: true
          properties:
            mode: "L2-Trunk"
            vlan: 501
            mc_po_group: 501
            vrf: 1
  Tor: []
BGP:
  BGP_U: false
  ND_RA: 30
PhysicalIfCfg:
  FEC: "Off"
  MTU: 9000
  AdminStatus: "Up"
ASN:
  SSpine: "10000-20000"
  Spine: "21000-50000"
  Leaf: "51000-60000"
  Tor: "61000-70000"
IPv4Pool:
  Loopback: "49.10.10.0/24"
  LeafSpine: "39.0.0.0/24"
  LeafTor: "29.0.0.0/24"
  Host: "19.0.0.0/24"
IPv6Pool:
  LeafSpine: 
  LeafTor: 
  Host: 
NTP:
  server: "100.100.10.10"
  timezone: "Asia/Kolkata"
SYSLOG:
  server: "100.100.10.10"
SNMP:
  trapserver: "100.100.10.10"
Parameters:
  vlan: "500-505"
  vni: "50000-50005"
  anycast_gateway: "200.10.0.0/23"
  anycast_mac: "00:11:22:33:44:55"
  hosts_per_vlan: 10
  routing_symmetric: true
  irb_vlan: "400-405"
  irb_vni: "40000-40005"
  sag: False

Supported Time Zone

Africa/Abidjan

Africa/Accra

Africa/Addis_Ababa

Africa/Algiers

Africa/Asmara

Africa/Asmera

Africa/Bamako

Africa/Bangui

Africa/Banjul

Africa/Bissau

Africa/Blantyre

Africa/Brazzaville

Africa/Bujumbura

Africa/Cairo

Africa/Casablanca

Africa/Ceuta

Africa/Conakry

Africa/Dakar

Africa/Dar_es_Salaam

Africa/Djibouti

Africa/Douala

Africa/El_Aaiun

Africa/Freetown

Africa/Gaborone

Africa/Harare

Africa/Johannesburg

Africa/Juba

Africa/Kampala

Africa/Khartoum

Africa/Kigali

Africa/Kinshasa

Africa/Lagos

Africa/Libreville

Africa/Lome

Africa/Luanda

Africa/Lubumbashi

Africa/Lusaka

Africa/Malabo

Africa/Maputo

Africa/Maseru

Africa/Mbabane

Africa/Mogadishu

Africa/Monrovia

Africa/Nairobi

Africa/Ndjamena

Africa/Niamey

Africa/Nouakchott

Africa/Ouagadougou

Africa/Porto-Novo

Africa/Sao_Tome

Africa/Timbuktu

Africa/Tripoli

Africa/Tunis

Africa/Windhoek

America/Adak

America/Anchorage

America/Anguilla

America/Antigua

America/Araguaina

America/Argentina/Buenos_Aires

America/Argentina/Catamarca

America/Argentina/ComodRivadavia

America/Argentina/Cordoba

America/Argentina/Jujuy

America/Argentina/La_Rioja

America/Argentina/Mendoza

America/Argentina/Rio_Gallegos

America/Argentina/Salta

America/Argentina/San_Juan

America/Argentina/San_Luis

America/Argentina/Tucuman

America/Argentina/Ushuaia

America/Aruba

America/Asuncion

America/Atikokan

America/Atka

America/Bahia

America/Bahia_Banderas

America/Barbados

America/Belem

America/Belize

America/Blanc-Sablon

America/Boa_Vista

America/Bogota

America/Boise

America/Buenos_Aires

America/Cambridge_Bay

America/Campo_Grande

America/Cancun

America/Caracas

America/Catamarca

America/Cayenne

America/Cayman

America/Chicago

America/Chihuahua

America/Ciudad_Juarez

America/Coral_Harbour

America/Cordoba

America/Costa_Rica

America/Creston

America/Cuiaba

America/Curacao

America/Danmarkshavn

America/Dawson

America/Dawson_Creek

America/Denver

America/Detroit

America/Dominica

America/Edmonton

America/Eirunepe

America/El_Salvador

America/Ensenada

America/Fort_Nelson

America/Fort_Wayne

America/Fortaleza

America/Glace_Bay

America/Godthab

America/Goose_Bay

America/Grand_Turk

America/Grenada

America/Guadeloupe

America/Guatemala

America/Guayaquil

America/Guyana

America/Halifax

America/Havana

America/Hermosillo

America/Indiana/Indianapolis

America/Indiana/Knox

America/Indiana/Marengo

America/Indiana/Petersburg

America/Indiana/Tell_City

America/Indiana/Vevay

America/Indiana/Vincennes

America/Indiana/Winamac

America/Indianapolis

America/Inuvik

America/Iqaluit

America/Jamaica

America/Jujuy

America/Juneau

America/Kentucky/Louisville

America/Kentucky/Monticello

America/Knox_IN

America/Kralendijk

America/La_Paz

America/Lima

America/Los_Angeles

America/Louisville

America/Lower_Princes

America/Maceio

America/Managua

America/Manaus

America/Marigot

America/Martinique

America/Matamoros

America/Mazatlan

America/Mendoza

America/Menominee

America/Merida

America/Metlakatla

America/Mexico_City

America/Miquelon

America/Moncton

America/Monterrey

America/Montevideo

America/Montreal

America/Montserrat

America/Nassau

America/New_York

America/Nipigon

America/Nome

America/Noronha

America/North_Dakota/Beulah

America/North_Dakota/Center

America/North_Dakota/New_Salem

America/Nuuk

America/Ojinaga

America/Panama

America/Pangnirtung

America/Paramaribo

America/Phoenix

America/Port-au-Prince

America/Port_of_Spain

America/Porto_Acre

America/Porto_Velho

America/Puerto_Rico

America/Punta_Arenas

America/Rainy_River

America/Rankin_Inlet

America/Recife

America/Regina

America/Resolute

America/Rio_Branco

America/Rosario

America/Santa_Isabel

America/Santarem

America/Santiago

America/Santo_Domingo

America/Sao_Paulo

America/Scoresbysund

America/Shiprock

America/Sitka

America/St_Barthelemy

America/St_Johns

America/St_Kitts

America/St_Lucia

America/St_Thomas

America/St_Vincent

America/Swift_Current

America/Tegucigalpa

America/Thule

America/Thunder_Bay

America/Tijuana

America/Toronto

America/Tortola

America/Vancouver

America/Virgin

America/Whitehorse

America/Winnipeg

America/Yakutat

America/Yellowknife

Antarctica/Casey

Antarctica/Davis

Antarctica/DumontDUrville

Antarctica/Macquarie

Antarctica/Mawson

Antarctica/McMurdo

Antarctica/Palmer

Antarctica/Rothera

Antarctica/South_Pole

Antarctica/Syowa

Antarctica/Troll

Antarctica/Vostok

Arctic/Longyearbyen

Asia/Aden

Asia/Almaty

Asia/Amman

Asia/Anadyr

Asia/Aqtau

Asia/Aqtobe

Asia/Ashgabat

Asia/Ashkhabad

Asia/Atyrau

Asia/Baghdad

Asia/Bahrain

Asia/Baku

Asia/Bangkok

Asia/Barnaul

Asia/Beirut

Asia/Bishkek

Asia/Brunei

Asia/Calcutta

Asia/Chita

Asia/Choibalsan

Asia/Chongqing

Asia/Chungking

Asia/Colombo

Asia/Dacca

Asia/Damascus

Asia/Dhaka

Asia/Dili

Asia/Dubai

Asia/Dushanbe

Asia/Famagusta

Asia/Gaza

Asia/Harbin

Asia/Hebron

Asia/Ho_Chi_Minh

Asia/Hong_Kong

Asia/Hovd

Asia/Irkutsk

Asia/Istanbul

Asia/Jakarta

Asia/Jayapura

Asia/Jerusalem

Asia/Kabul

Asia/Kamchatka

Asia/Karachi

Asia/Kashgar

Asia/Kathmandu

Asia/Katmandu

Asia/Khandyga

Asia/Kolkata

Asia/Krasnoyarsk

Asia/Kuala_Lumpur

Asia/Kuching

Asia/Kuwait

Asia/Macao

Asia/Macau

Asia/Magadan

Asia/Makassar

Asia/Manila

Asia/Muscat

Asia/Nicosia

Asia/Novokuznetsk

Asia/Novosibirsk

Asia/Omsk

Asia/Oral

Asia/Phnom_Penh

Asia/Pontianak

Asia/Pyongyang

Asia/Qatar

Asia/Qostanay

Asia/Qyzylorda

Asia/Rangoon

Asia/Riyadh

Asia/Saigon

Asia/Sakhalin

Asia/Samarkand

Asia/Seoul

Asia/Shanghai

Asia/Singapore

Asia/Srednekolymsk

Asia/Taipei

Asia/Tashkent

Asia/Tbilisi

Asia/Tehran

Asia/Tel_Aviv

Asia/Thimbu

Asia/Thimphu

Asia/Tokyo

Asia/Tomsk

Asia/Ujung_Pandang

Asia/Ulaanbaatar

Asia/Ulan_Bator

Asia/Urumqi

Asia/Ust-Nera

Asia/Vientiane

Asia/Vladivostok

Asia/Yakutsk

Asia/Yangon

Asia/Yekaterinburg

Asia/Yerevan

Atlantic/Azores

Atlantic/Bermuda

Atlantic/Canary

Atlantic/Cape_Verde

Atlantic/Faeroe

Atlantic/Faroe

Atlantic/Jan_Mayen

Atlantic/Madeira

Atlantic/Reykjavik

Atlantic/South_Georgia

Atlantic/St_Helena

Atlantic/Stanley

Australia/ACT

Australia/Adelaide

Australia/Brisbane

Australia/Broken_Hill

Australia/Canberra

Australia/Currie

Australia/Darwin

Australia/Eucla

Australia/Hobart

Australia/LHI

Australia/Lindeman

Australia/Lord_Howe

Australia/Melbourne

Australia/NSW

Australia/North

Australia/Perth

Australia/Queensland

Australia/South

Australia/Sydney

Australia/Tasmania

Australia/Victoria

Australia/West

Australia/Yancowinna

Brazil/Acre

Brazil/DeNoronha

Brazil/East

Brazil/West

CET

CST6CDT

Canada/Atlantic

Canada/Central

Canada/Eastern

Canada/Mountain

Canada/Newfoundland

Canada/Pacific

Canada/Saskatchewan

Canada/Yukon

Chile/Continental

Chile/EasterIsland

Cuba

EET

EST

EST5EDT

Egypt

Eire

Etc/GMT

Etc/GMT+0

Etc/GMT+1

Etc/GMT+10

Etc/GMT+11

Etc/GMT+12

Etc/GMT+2

Etc/GMT+3

Etc/GMT+4

Etc/GMT+5

Etc/GMT+6

Etc/GMT+7

Etc/GMT+8

Etc/GMT+9

Etc/GMT-0

Etc/GMT-1

Etc/GMT-10

Etc/GMT-11

Etc/GMT-12

Etc/GMT-13

Etc/GMT-14

Etc/GMT-2

Etc/GMT-3

Etc/GMT-4

Etc/GMT-5

Etc/GMT-6

Etc/GMT-7

Etc/GMT-8

Etc/GMT-9

Etc/GMT0

Etc/Greenwich

Etc/UCT

Etc/UTC

Etc/Universal

Etc/Zulu

Europe/Amsterdam

Europe/Andorra

Europe/Astrakhan

Europe/Athens

Europe/Belfast

Europe/Belgrade

Europe/Berlin

Europe/Bratislava

Europe/Brussels

Europe/Bucharest

Europe/Budapest

Europe/Busingen

Europe/Chisinau

Europe/Copenhagen

Europe/Dublin

Europe/Gibraltar

Europe/Guernsey

Europe/Helsinki

Europe/Isle_of_Man

Europe/Istanbul

Europe/Jersey

Europe/Kaliningrad

Europe/Kiev

Europe/Kirov

Europe/Kyiv

Europe/Lisbon

Europe/Ljubljana

Europe/London

Europe/Luxembourg

Europe/Madrid

Europe/Malta

Europe/Mariehamn

Europe/Minsk

Europe/Monaco

Europe/Moscow

Europe/Nicosia

Europe/Oslo

Europe/Paris

Europe/Podgorica

Europe/Prague

Europe/Riga

Europe/Rome

Europe/Samara

Europe/San_Marino

Europe/Sarajevo

Europe/Saratov

Europe/Simferopol

Europe/Skopje

Europe/Sofia

Europe/Stockholm

Europe/Tallinn

Europe/Tirane

Europe/Tiraspol

Europe/Ulyanovsk

Europe/Uzhgorod

Europe/Vaduz

Europe/Vatican

Europe/Vienna

Europe/Vilnius

Europe/Volgograd

Europe/Warsaw

Europe/Zagreb

Europe/Zaporozhye

Europe/Zurich

Factory

GB-Eire

GMT

GMT+0

GMT-0

GMT0

Greenwich

HST

Hongkong

Iceland

Indian/Antananarivo

Indian/Chagos

Indian/Christmas

Indian/Cocos

Indian/Comoro

Indian/Kerguelen

Indian/Mahe

Indian/Maldives

Indian/Mauritius

Indian/Mayotte

Indian/Reunion

Iran

Israel

Jamaica

Japan

Kwajalein

Libya

MET

MST

MST7MDT

Mexico/BajaNorte

Mexico/BajaSur

Mexico/General

NZ-CHAT

Navajo

PRC

PST8PDT

Pacific/Apia

Pacific/Auckland

Pacific/Bougainville

Pacific/Chatham

Pacific/Chuuk

Pacific/Easter

Pacific/Efate

Pacific/Enderbury

Pacific/Fakaofo

Pacific/Fiji

Pacific/Funafuti

Pacific/Galapagos

Pacific/Gambier

Pacific/Guadalcanal

Pacific/Guam

Pacific/Honolulu

Pacific/Johnston

Pacific/Kanton

Pacific/Kiritimati

Pacific/Kosrae

Pacific/Kwajalein

Pacific/Majuro

Pacific/Marquesas

Pacific/Midway

Pacific/Nauru

Pacific/Niue

Pacific/Norfolk

Pacific/Noumea

Pacific/Pago_Pago

Pacific/Palau

Pacific/Pitcairn

Pacific/Pohnpei

Pacific/Ponape

Pacific/Port_Moresby

Pacific/Rarotonga

Pacific/Saipan

Pacific/Samoa

Pacific/Tahiti

Pacific/Tarawa

Pacific/Tongatapu

Pacific/Truk

Pacific/Wake

Pacific/Wallis

Pacific/Yap

Poland

Portugal

ROC

ROK

Singapore

SystemV/AST4

SystemV/AST4ADT

SystemV/CST6

SystemV/CST6CDT

SystemV/EST5

SystemV/EST5EDT

SystemV/HST10

SystemV/MST7

SystemV/MST7MDT

SystemV/PST8

SystemV/PST8PDT

SystemV/YST9

SystemV/YST9YDT

Turkey

UCT

US/Alaska

US/Aleutian

US/Arizona

US/Central

US/East-Indiana

US/Eastern

US/Hawaii

US/Indiana-Starke

US/Michigan

US/Mountain

US/Pacific

US/Samoa

UTC

Universal

W-SU

WET

Zulu