Overview

Below are the primary components of ONES Application

• ONES Telemetry Collector(s) for Network Visibility

• ONES Orchestrator for Fabric Configuration

• ONES Supportability

• ONES Security

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), L3 EVPN Symmetric IRB, L3EVPN symmetric IRB with MCLAG.

• 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

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
...
...

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

Refer to the "How to contact Aviz Networks Support?" section of this document for more details

ONES Supportability

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

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 a Auto-discovery for SONiC and YAML-based Non-SONiC Device Discovery Template for adding switches 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 utilization

• Traffic Utilization

• Software Compliance

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

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, system services including NTP, SNMP, SYSLOG etc. 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.

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, Nvidia ASICs

• View the topology of the entire fabric across multiple hardware platforms, and network operating systems

• Monitor traffic, system health, bandwidth utilization, & more

• 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

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

• Click to get more details on RBAC

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, ONESv1.3 support Certificate based communication between switches and ONES Controller, and all the metrics will be streamed using the certificate-based encryption

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

Supported Matrix

Cumulus & Arista platforms are considered by ONES as Agent-less and supports metrics available using NVUE and eOS APIs

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

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

• 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 1.3

  • File to install on Ubuntu

    • ONES 1.3 Installation package

  • File to install on VMware, ESXI, vSphere, and vCenter setup

    • ONES 1.3 OVA

  • File to install on Hypervisor, KVM, LibVirt Manager

    • ONES 1.3 QCOW2

To install ONES Package on Ubuntu or Linux

• Copy ONES Release 1.3 package (tar.gz) to ONES Application machine

• Follow the next page to execute a successful installation

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

The installer allows a default capability for managing 8 devices without a license. Beyond this, the following license key is required for proceeding with the Installation;

• ONES Application License (As per device count)

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

• License Duration - In Years (1-5)

• Devices Count - 8, 32, 64, 128, 256, 512 or 1024

• ONES installation ID

• Email ID: (For Account creation)

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;

System Software Requirements - ONES Application

Customer Firewall Configuration (Ports to be opened)

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

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)

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 means (ZTP, sonic-installer CLI)

    • The user needs to reinstall ONES Agents again

ONES Agent v1.3 support Agent Auto discovery

1. ONESv1.3 Agent support auto-discovery feature

2. ONESv1.3 Agent support to send telemetry on multiple controllers

3. Restrict IP is enabled by default in ONESv1.3

4. Using this feature agent will discover the ONES Controller and will update the entry on ONES App with all the feature metrics

5. Need to add a few inputs while installing agent

   1. Controller IP //To restrict the telemetry streaming

   2. Device Credentials

   3. Layer

   4. Region

   5. azid

   6. brickid

   7. rackid

Installation

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

root@ones-application:~$ cd /ONES-1.3/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-1.3/ones_t_agent:~$ vi device_info.csv

ip,user,passwd,layer,region,azid,brickid,rackid
10.4.4.77,admin,YourPaSsWoRd,Spine,SanJose,1,1,1
10.4.4.78,admin,YourPaSsWoRd,Leaf,SanJose,1,1,1
...
...
...

• Save the File

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

root@ones-application/ONES-1.3/ones_t_agent:~$ python3 ones_agent_parallel_installer.py

1. Script asks to to put the Controller IP to use auto-discovery feature

Enter the ip address of collectors to auto-discover. Do not enter more than 2. Eg - 10.1.1.10, 10.2.2.5 : 10.4.4.11

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

Do you want to restrict access only to provided collector ip?
Note: Providing Yes will restrict access to agent only with the provided collector IP Address
Enter Yes/No : Yes

Installation Begin

root@ones-application/ONES-1.3/ones_t_agent:~$ python3 ones_agent_parallel_installer.py
Enter the ip address of collectors to auto-discover. Do not enter more than 2. Eg - 10.1.1.10, 10.2.2.5 : 10.4.4.11
Note: Providing Yes will restrict access to agent only with the provided collector IP Address
Enter Yes/No : Yes
[{'ip': '10.4.4.77', 'user': 'admin', 'passwd': 'YourPaSsWoRd', 'layer': 'Spine', 'region': 'SanJose', 'azid': '1', 'brickid': '1', 'rackid': '1', 'installation_instance': 1, 'agentip': '10.4.4.77', 'collectorip': '10.4.4.11'}, {'ip': '10.4.4.78', 'user': 'admin', 'passwd': 'YourPaSsWoRd', 'layer': 'Leaf', 'region': 'SanJose', 'azid': '1', 'brickid': '1', 'rackid': '1', 'installation_instance': 1, 'agentip': '10.4.4.78', 'collectorip': '10.4.4.11'}]
###############Connecting to switch###############
###############Connecting to switch###############
Connection to switch 10.4.4.77 successful.....................
Looking for previous installation........................
avizdock/ones-agent:v1.3.0

...
...
...
...
ones-agent.service file copied successfully on the device 10.4.4.77........
##################################################################
ones-agent.service file copied successfully on the device 10.4.4.78........
##################################################################
Deployment of ones-agent to switch 10.4.4.77 is successful
Deployment of ones-agent to switch 10.4.4.78 is successful

ONES Application support Agent Less devices telemetry for

>Cumulus (NVUE API)

>Arista EOS (OpenConfig)

Enable gNMI in Cumulus

netq config add agent gnmi-enable true
netq config add agent opta-enable false
netq config add agent gnmi-port 9339
netq config restart agent
netq config status agent

netq config add agent gnmi-port 50052
netq config restart agent
netq config status agent

cumulus@cumulus:mgmt:~$ cat /etc/netq/netq.yml
netq-agent:
is-gnmi-enabled: true
is-opta-enabled: false
netq-gnmi:
gnmi_port: 9339

Enable NVUE API in Cumulus

sudo ln -s /etc/nginx/sites-{available,enabled}/nvue.conf
sudo sed -i 's/listen localhost:8765 ssl;/listen \[::\]:8765 ipv6only=off ssl;/g' /etc/nginx/sites-available/nvue.conf
sudo systemctl restart nginx

Introduction

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

Enable API gNMI

Arista-DCS-7010T(config)#management api gnmi
Arista-DCS-7010T(config-mgmt-api-gnmi)#transport grpc default
Arista-DCS-7010T(config-gnmi-transport-default)#provider eos-native
Arista-DCS-7010T(config-mgmt-api-gnmi)#end

Arista-DCS-7010T#show management api gnmi
Octa: enabled
Transport: GRPC
Enabled: yes
Server: running on port 50052, in default VRF
SSL profile: SELFSIGNED
QoS DSCP: none
Authorization required: no
Accounting requests: no
Certificate username authentication: no
Notification timestamp: last change time
Listen addresses: ::

Transport: default
Enabled: yes
Server: running on port 6030, in default VRF
SSL profile: none
QoS DSCP: none
Authorization required: no
Accounting requests: no
Certificate username authentication: no
Notification timestamp: last change time
Listen addresses: ::

Enabling eAPI

bash$ ssh username@myswitch
   Password: <passw0rd>
   myswitch> enable
   myswitch# configure terminal
   myswitch(config)# management api http-commands
   myswitch(config-mgmt-api-http-cmds)# no shutdown
   myswitch(config-mgmt-api-http-cmds)# show management api http-commands
   Enabled:            Yes
   HTTPS server:       running, set to use port 443
   HTTP server:        shutdown, set to use port 80
   Local HTTP server:  shutdown, no authentication, set to use port 8080
   Unix Socket server: shutdown, no authentication
   VRFs:               default

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

QCOW Integration

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 1.3

• Copy ONES Release 1.3 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

Credentials to access ONES QCOW2 VM

Username: root
Password: Admin@123

OVA Integration

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, click to download ONES Release 1.3

• Copy ONES Release 1.3 package (OVA/OVF) to VMware or ESXI Server

Credentials to access ONES OVA VM

Username: ones
Password: Admin@123

Upgrade Process

• To upgrade any VM (QCOW or OVA)

  • Download the ONES installation package

To access the ONES application, use Server IP with HTTPS

https://<host-ip>

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

ONES User Interface - Features

• SONiC Devices use auto-discovery

• Non-SONiC devices needs to add using YAML editor

• Deep Telemetry for ASIC and Switch Hardware

• 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

  • 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

• 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

  • Device Connectivity view across Roles and Location

  • Link/Connectivity Status

• Routing Protocol

  • BGP Neighbors

  • Advertised and Received Prefixes

  • Local AS Number

• Orchestrator Use Cases

  • YAML-based Configuration push

  • Image Management via ZTP

  • BGP Numbered and Unnumbered Configuration

  • NTP, SNMP, and SYSLOG Configuration

• 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

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

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

root@ones-application:~$ cd /ONES-1.3/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-1.3/ones_fm_agent:~$ vi device_info.csv

ip,user,passwd
10.4.4.75,admin,YourPaSsWoRd
10.4.4.76,admin,YourPaSsWoRd
10.4.4.77,admin,YourPaSsWoRd 
...
...
...

• Save the file

• Execute the installation script

root@ones-application/ONES-1.3/ones_fm_agent:~$ python3 deploy_fmcli.py "install"

[{'ip': '10.4.4.61', 'passwd': 'YourPaSsWoRd', 'user': 'admin'}]
Operation = install
##### params = {'ip': '10.4.4.61', 'passwd': 'YourPaSsWoRd', 'user': 'admin'} #####
###############Connecting to switch###############
<paramiko.client.SSHClient object at 0x7f44742fda90>
Connection to switch 10.4.4.61 successfull.....................
/home/neeraj.kamboj/ONES/ones_fm_agent
Creating work directory  on the device 10.4.4.61........
...
#################### Installing FMCLI ######################
...
...
FM-Agent installed successfully on the device 10.4.4.61........

• Verify the Installation success by running the fmcli command on individual devices

root@Switch:~$ sudo fmcli

root@Switch:~$ sudo fmcli 
fmcli# 

Hardware (Default)

The dashboard provides the NetOps with an overview of the data centre. It contains the entire hardware inventory of the network and shows the status whether these switches are streaming or not streaming.

• After the Installation of ONES Application for the first time, the Dashboard is empty and Devices need to be onboarded for them to reflect

• Dashboard will be used to

  • monitor the status of an agent running on all the devices present

  • Device Roles and associated Regions and

  • Details of Switch Hardware SKU and ASICs

Components

• Navigate to Dashboard >> Components

Software

• Navigate to Dashboard >> Software

Interfaces

• Navigate to Dashboard >> Interfaces

• Using this page a user gets the status of

  • the cables utilized in the network

  • how many pairs of cable can be used for future topology (helps the admins in capacity planning)

  • interface to identify if any power failure is happening over the interface

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

• To Onboard the Agent-Less devices user need to add manualy

  • Navigate to Inventory

• This page gives the control to onboard the devices with two options

  • Add/Remove Devices using the YAML Editor

  • Upload the YAML file containing the device list

• Click on Add/Remove Devices

• Upload Device Inventory using YAML Editor

• Navigate to Inventory >> Devices >> Add/Remove Devices

• Use the below format to add devices to the application

• Make sure to use the correct indentation for the YAML files

• Make sure the Switch Name matches to Hostname of the switch

• Click Save & Apply

• ONES Application is now ready to manage the added devices

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

Agent-Based 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

  • 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

  • Remove devices from the dashboard: The user can remove the auto-discovered(Agent based) and non-sonic devices

Devices

• Navigate to Inventory >> Devices

• Using this tab, user can:

  • Onboard the non-sonic(Agent-Less) device to the application using Add devices

  • 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

Add Non-Sonic Devices

• Upload Device Inventory using YAML editor

• Navigate to Inventory >> Devices >> Add Devices

• Use the below sample format to add devices to the application

• Make sure to use the correct indentation for the YAML files

• Make sure the Switch Name matches to Hostname of the device

• Click Save & Apply

• ONES Application is now ready to manage the added devices

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 ports 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, so we can use this if we need some tuning or need to push some extra config

• Details: This last option we can again use to get the details of the device

Remove Devices from the 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

• Now the selected devices have been removed from the ONES application

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

Upgrade via ZTP

• Select any of the devices to upgrade via ZTP

• Click on Upgrade via ZTP

• Click on Yes

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

Overview

Using this feature setting we can set the acceptable and critical percentage level for the following device components

This page gives the control over the widget refresh timer and user idle state

Users can set the manual timer to refresh all the widgets after a time interval (default is 30sec)

Users can set the timer after how many minutes of idle state the ONES-UI should be logout

• Thresholds we can set for Components

• CPU Utilization

• Memory Utilization

• Fan Speed

• PSU Temperature

• PSU Voltage

• As per requirement, we can set different lower and higher threshold values for each component

• User can see the acceptable and critical number of devices in the Monitor Health tab view

• Navigate to Monitor >> Platform when any component breach the higher value

Thresholds

• Navigate to Settings >> Thresholds

• Change the values as per your requirements

• Update it to get these new settings live, after Save Changes, all these metrics will be reflected on devices metric pages under Inventory

System Control

• Navigate to Settings >> System

• Using this page, users can change the refresh interval in seconds for all the widget

  • In the dropdown menu, available intervals are:

    • 30 Seconds

    • 60 Seconds

    • 90 Seconds

    • 120 Seconds

• Users can set the timeout in minutes for the ONES-UI

• Navigate to Configurations >> 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

New Features Added

Multi-Homing

Restore Config

Version 1.3 give the capability to the user to take a backup of the entire config and later in the future user can restore the config

Restore config works in a way it replaces the current config and loads all the config as per user input.

Day-2 Orchestration

It Provides the difference between golden configuration and running configure and accordingly does require configuring replacement operations through ONES API call also called as soft provisioning in Day2 Operations

Overview

The monitor widget in ONES:

• Shows the complete topology view of the fabric

• The Topology view can be categorised by:

  • Region

  • Brick

  • Link Bandwidth

  • ASIC Route Utilisation

  • CPU & Memory utilisation

• This page shows all the links and information connected to each other

• Low and high utilisation of all components

• Input / Output errors on links

• ASIC detailed view of all managed devices

• BGP status

  • Neighbour Count

  • Neighbor status (Up/Down)

  • Prefixes (Total/Advertised)

  • ASN

• Traffic View

  • input/output packets in million per sec

  • Errors and Discard packets per interface

NOTE: If all the managed devices have the same Region/Brick ID, we do not get any filter ribbon

Topology

• Navigate to Monitor >> Topology

• This shows the complete Topology view, how the devices are connected and to which role they belong to

• We can put the filters to check the customized view of the Diagram by: Region Availability Zone Brick ID

NOTE: we do not get filter ribbon if all devices belong to the same Region/Availability Zone/Brick ID

• We can also check Down Links to check the topology those are having links in the shutdown state as per Role

  • Super Spine

  • Spine

  • Leaf

  • ToR

• When we hover the cursor over any device and use right click we can connect to the device and get the details of the device

• we can also filter the view by using

  • Link utilization

  • ASIC Route utilization

  • CPU & RAM Utilization

• Users can easily filter the view as per the Region, Availability zone and Brick ID

Links

This page gives a view to the user for all the possible connected links between devices with a few more capabilities

• Navigate to Monitor >> Links

• This page helps a user to get the best view of the number of connections between devices with speed and other manufacturer details

• This page gives the exact view of the interface name, interface speed, transceivers and admin & operator status

Links View with Filter Ribbon

• We can also have a filtered view of links

• Choose a specific Role and Region to filter

• let's choose:

  • Role: Leaf

Health

This page shows the latest utilization of the devices with CPU & Memory utilization, Temperature & Voltage of PSU, and fan speed in RPM

• 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)

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 ToR input, here is the new view of only devices that belong to the ToR 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 including these new widgets, click on any of the device statuses present on the Platform tab

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

Device Info Ribbon

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

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

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

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

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)

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

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

Protocols

This Protocol Page shares the data of BGP neighbours present across managed devices

Neighbor View

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

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 right side it shows the BGP announcements and the local prefixes present in BGP table

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

  • Input packets

  • Output packets

• When we click on any device it give 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

ONES Application system - Installation Steps

• Enable super-user mode

user@ones-application:~$ sudo su

• Create a directory for ONESv1.3

user@ones-application:~$ mkdir ONES-1.3

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

root@ones-application:~$ tar -xvzf ONES-1.3.tar.gz -C ONES-1.3

• Go to ONES-1.3 folder on the server machine

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

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

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

1. By default, the installer has a license for 8 devices upto 30days

2. ONESv1.3 support SSL certificate integration

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

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

3. 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 application creates a database backup in every 86400 seconds(1 day), but user can modify it as per the requirement

3. Local & 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

1. ONESv1.3 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.

NOTE: The system might have multiple IP addresses, so the user can use any one IP to access ONES-UI.

• Installation begins

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

Activation:

• For Trail, user can choose Start A Trial (valid for 30days)

• For Activation, user can choose Activate License if the user has an activation key of any subscription

Start A Trail

• Use Default credentials as below;

  • Username: superadmin

  • Password : Admin@123

• Update/Change your password on the first login

Login To ONES

• After Resetting the password use new credentials to login

• You will see the default Dashboard → Hardware view

Activate License

Get the Activation key

• Share ONES installation ID to the AVIZ support team

• As per PO, the AVIZ team will share the Activation key

• Paste the activation key and Activate

Overview

Use this feature to

• Create new users and roles

• Remove and suspend existing user one by one

• Remove and suspend multiple users at the same time

• Password reset of existing users

Only super admin or Enterprise admin can perform these actions

Users

• Navigate to User Management >> Accounts >> Users

• Initially, we get one default Admin User Credential

• In this view, we get the User status and Role given to it and the Last login time by the user.

• On this User tab, we can Add new users and can remove or suspend any existing users

Users - Add New

• Navigate to Accounts >> Users >> Add

• Admin can add

  • Profile picture

  • Username

  • Password

    • 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

  • First and Last Name

  • Role

• Enter all the required details

• Click Save

"on the first login by the user with given details, ONES application prompt with a screen to rest the password

• Now User is ready to login with valid credentials

Users - Reset Password

• Navigate to Accounts >> Users >> Edit User >> Reset Password >> Yes

• Using Admin credentials you can reset the user password

• Click on Reset Password

• Submit & Save

• After this user can try login with the temporary password, on the first login, ONES application actively asks to change the password

Users - Remove User

• Navigate to Accounts >> Users >> ((Select Users you want to remove)) >> remove >> Yes

• We can remove multiple users at a time

• After this, the user will be removed from the database and cannot use credentials to login again

Users - Suspend User

• Instead of removing any user, we can also suspend the user

• Once we suspend a user it will not be removed from the database but it will be in an Inactive state in the database

• Later if we need we can restore the user to its active state

• Navigate to Accounts >> Users >> ((Select Users you want to suspend)) >> Suspend >> Yes

• Choose users & click on Suspend

Users - Restore User

• Navigate to Accounts >> Users >> ((Select Users you want to restore)) >> Restore >> Yes

Roles

• Navigate to Account >> Roles

• By default, the device comes with these 4 Roles

  • Super Admin

  • Enterprise Admin

  • Enterprise Staff

  • Vendor Staff

• As per the new user access requirement, we can assign limited access to user roles

Roles - Add User Roles

• Navigate to Accounts >> Roles

• Now let's add few extra permissions

  • Add/Remove Devices

  • Configure Devices

Template Details: BGP IP-CLOS Config with 3-Stage in the given topology

• Devices used

  • 2- Spine Devices

  • 3- Leaf Devices

  • 3- End Host

Topology

BGP-IP-CLOS Standard Template

Inventory:
 SSpines: 0
 Spines: 2
 Leafs: 3
 Tors: 0
Connectivity:
 SSpine: []
 Spine:
   - switchId: 1
     switchName: Spine-1
     ipAddress: 190.10.10.11
     ASN: 2001
     Credentials:
      user: admin
      password: YourPaSsWoRd
     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:
   - switchId: 2
     switchName: Spine-2
     ipAddress: 190.10.10.12
     ASN: 2002
     Credentials:
      user: admin
      password: YourPaSsWoRd
     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: 
 Leaf:
   - switchId: 1
     switchName: Leaf1
     ipAddress: 190.10.10.13
     ASN: 1001 
     Credentials:
      user: admin
      password: YourPaSsWoRd
     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: L3
   - switchId: 2
     switchName: Leaf-2
     ipAddress: 190.10.10.14
     ASN: 1002  
     Credentials:
      user: admin
      password: YourPaSsWoRd
     mclag:    
     Links:
       - link: L2_Ethernet48 | S1_Ethernet4
         staticLink: True
         properties:
       - link: L2_Ethernet52 | S2_Ethernet4
         staticLink: True
         properties:
       - link: L2_Ethernet0 |  H2_Ethernet0
         staticLink: True
         properties:  
          mode: L3
   - switchId: 3
     switchName: Leaf-3
     ipAddress: 190.10.10.15
     ASN: 1003 
     Credentials:
      user: admin
      password: YourPaSsWoRd
     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_Ethernet0 |  H3_Ethernet0
         staticLink: True
         properties: 
          mode: L3
 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: 40.0.0.0/24
 LeafTor: 39.0.0.0/24
 Host: 49.0.0.0/24
IPv6Pool: 
 LeafSpine: 
 LeafTor:
 Host:
NTP:
 server: 128.138.141.172
 timezone: Asia/Kolkata
SYSLOG:
 server: 128.138.141.172
SNMP:
 trapserver: 128.138.141.172
Parameters: