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

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 on the application 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

• Yaml-based config for VXLAN, MCLAG, BGP IP CLOS & EVPN(L2VPN)

• 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

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

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

Overview

There are three primary components of ONES Application

• ONES Telemetry Collector(s) for Network Visibility

• ONES Orchestrator for Fabric Configuration

• ONES Supportability

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

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 on managing 8 devices without a license. Beyond this, the following license keys are 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 Type - Evaluation Trial or Full

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

NOTE: 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

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

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

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

ONES User Interface - Features

• 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

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

• 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

inventory:
  - switchName: "SN2100-Spine"
    layer: "Spine"
    ipAddress: "10.4.4.61"
    region: "SJC"
    azId: 1
    brickId: 1
    rackId: null
    user: "admin"
    password: "YourPaSsWoRd"
  - switchName: "SN2100-Leaf3"
    layer: "Leaf"
    ipAddress: "10.4.4.62"
    region: "SJC"
    azId: 1
    brickId: 1
    rackId: null
    user: "admin"
    password: "YourPaSsWoRd"

• 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

On the Application machine, go to GAv1.1/ones_t_agent folder

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

• Save the File

• Verify and Clean up old versions of Agents running

root@ones-application/GAv1.1/ones_t_agent:~$ python3 ones_agent_uninstaller.py

• Execute the installation script can be used for installing telemetry agent on one or more devices in the data center.

root@ones-application/GAv1.1/ones_t_agent:~$ python3 ones_agent_installer.py

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

On the ONES Application server, go to GAv1.1/ones_fm_agent

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

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/GAv1.1/ones_fm_agent:~$ python3 deploy_fmcli.py "install"

###########Connecting to Switch############ 
###########Connecting to Switch############ 
###########Connecting to Switch############ 
###########Connecting to Switch############ 
Connection to switch 10.4.4.75 successful………… 
Installing agent on 10.4.4.75……………………….. 
Installation of agent on 10.4.4.75 successful…………………. 
Connection to switch 10.4.4.76 successful………… 
Installing agent on 10.4.4.76……………………….. 
Installation of agent on 10.4.4.76 successful…………………. 
...
...
...

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

root@Switch:~$ sudo fmcli

FMCLI: System Initialization in progress......
fmcli# 

Supported Matrix

Cumulus support limited to available Open Config models, is considered by ONES as Agent-less

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 version beyond 202012 or 202111 are supported

• Only x86 intel-based architectures are supported

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

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

• 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/Remove devices from the dashboard: You can onboard the devices using the YAML file upload or via in-built editor in the UI

Devices

• Navigate to Inventory >> Devices

• Using this tab, user can:

  • Onboard the device to the application using ADD/Remove 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

Add Devices

• Upload Device Inventory using YAML editor

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

• Use the below format to add devices to the application

inventory:
  - switchName: "SN2100-Spine"
    layer: "Spine"
    ipAddress: "10.4.4.61"
    region: "SJC"
    azId: 1
    brickId: 1
    rackId: null
    user: "admin"
    password: "YourPaSsWoRd"
  - switchName: "SN2100-Leaf3"
    layer: "Leaf"
    ipAddress: "10.4.4.62"
    region: "SJC"
    azId: 1
    brickId: 1
    rackId: null
    user: "admin"
    password: "YourPaSsWoRd"

• 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 >> Add/Remove Devices

• Remove all the inputs entered by the user

• Click Save and Apply

• Once the application detects, a user is trying to remove devices it shows one confirmation dialogue box to cross-check the status

• Now all the 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

• 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

Overview

The monitor widget in ONES:

• Shows the complete topology view of the fabric

• The Topology view can be filtered by:

  • Region

  • Brick

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

• Low and high utilization 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, we get the device status and device details popup

• 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: ToR

  • Region: San Jose

Platform

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

Platform Status

Platform 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 ToR filter

• After selecting ToR input, here is the new view of only devices that belong to the ToR Role

Region-based Customization

• We can choose a role using the available Region-based option

• Two roles available

  • San Jose

  • Asia Pacific

• Let’s check it with Asia Pacific Region

• After selecting Asia Pacific input, here is the new view of only devices that belongs to the Asia Pacific Region

Role / Region based Customization

• We have the liberty to do the filtering by both combination Role-based and Region based at the same time

• As of now, we have two Region available

  • San Jose

  • Asia Pacific

• 3 Roles available

  • Super Spine

  • Spine

  • Leaf

  • ToR

• Let’s check it with a combination of Asia Pacific & Spine Role

• After selecting both Roles and Region-based filter, here is the new view of the device that belongs to the Spine role and parallel belongs to Asia Pacific Region

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 Utilization (%)

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

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

Memory Utilization (%)

• Now here we get the status of memory utilization 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

• To check a specific time detail for all the CPU/Cores, we can hover the cursor on any level

• We can also check Per CPU Core details

• We can see here the customized view per CPU Core

Fan Speed (%)

• Here we get the status of the FAN speed percentage level across all fans available on the device

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

• We can choose to view the customized view of a few fans at once

• Here we can see the output of fan1 and fan7 in this customized view

• When we move the cursor to check the exact status of fans at a particular time

PSU Temperature (C)

• This widget provides the status of the Power Supply Unit (PSU) temperature (in degree celsius) across all power supplies available on a particular device.

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

• We can choose to view the customized view of a few PSUs at once

• In our case, we have 2 PSUs, so now let's choose one of them and check the output

• When we move the cursor to check the exact status of the PSU at a particular time

PSU Voltage (V)

• This widget provides the status of the Power Supply Unit (PSU) voltage across all power supplies available on a particular device.

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

• Same we can check the customized view by choosing one or two PSUs

• Let us choose one of the PSU to check individual Voltage, so here we have taken PSU2 to check individual Voltage

PSU Current (A)

• This widget provides the status of the Power Supply Unit (PSU) current in Amperes, across all PSUs available on a particular device.

• To check a specific time detail, hover the cursor on any level

• Same here as per other power supply customized views we can also check the customized view here by choosing specific PSUs

PSU Power (W)

• Here we get the status of Power supply power in Watt across all power supply present on the device

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

• We can also check the customized view of this

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

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

• Here we get the name and count of all the services running on the platform

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

• When we get this output we get a clear view of both CPU Utilization per service based

• We can also customise the view of this widget by choosing some specific application

• We have all the services button here to choose

• Again we can check the view of all the services we need

• So here is the view of only the BGP service

• We can see the CPU and Memory consumption for these 2 services

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

• Here we get a clear view of Memory Utilization per service based

• We can also customise the view of this widget by choosing some specific application

• We have all the services button here to choose

• So here is the view of only the BGP service

ASIC

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

• This widget Shows

  • Roles/Region per device

  • SKU and ASIC details per device

  • ASIC Route Capacity in IPv4 & current utilization

  • ASIC Route Capacity in IPv6 & current utilization

  • ASCI ACL capacity & utilization

  • Software routes for IPv4 and IPv6

  • Kernel Routes for IPv4 and IPv6

This ASIC 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

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

BGP

This BGP 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 neighbour

• 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

Customized view

• This page gives us the power to check neighbours as per Roles and Region-based

• Let's check how we can filter as per Role-based

• Here is the global view of all the Devices with BGP status

• Choose Leaf Role to check customized view

• After having only Leaf Roles here is the modified output

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:

  • Bandwidth utilization in percentage

  • Input packets per second in millions

  • Output packets per second in millions

  • Input packets

  • Output packets

  • Input and Output discards

• 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

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

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

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 to this folder

root@ones-application:~$ tar -xvf ONES-GAv1.1.tar.gz

• Go to GAv1.1 folder on the server machine

root@ones-aplication:~$ cd GAv1.1

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

root@ones-application:~/GAv1.1$ ./ones-installer.sh

Fresh install
Installing ONES application...

Do you want to install SSL certificates? [y/n]n
Using self signed certificates.

NOTE:

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

2. ONESv1.1 support SSL certificate integration

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

   2. Choose NO, if the user does not have their own SSL certificate and wants to use the certificate provided by AVIZ

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 backup interval in seconds : 86400    #Enter the time in seconds to take backup after every interval
Enter the number of backups to retain (Older backups will be deleted): 5 #Enter the number of backup user wants to create

Remote backup:
Do you want to enable DB backups? [y/n]y
Where do you want to store the backups? [local/remote]: remote    #remote keyword trigger remote database on server
Enter the remote machine IP: 10.4.4.11    #Enter the Database Sever IP
Enter the remote machine username: dbserver    #Enter the Database server username with write permission
Enter the remote machine password:     #Enter the Database Server password
Enter the backup directory: ~/dbserver/backups    #Enter the Database server directory in which user wants to take backup
Enter the backup interval in seconds : 86400    #Enter the time in seconds to take backup after every interval
Enter the number of backups to retain (Older backups will be deleted): 5 #Enter the number of backup user wants to create

1. 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. By-Default application creates 5 backups and once it will add one more it will remove the first copy of the database, User can modify the number of backup files at the time of installation

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

• Installation begins

Fresh install
Installing ONES application...

Do you want to install SSL certificates? [y/n]n
Using self signed certificates.
Do you want to enable DB backups? [y/n]y
Where do you want to store the backups? [local/remote]: local
Enter the backup directory: ./backups
Enter the backup interval in seconds : 86400
Enter the number of backups to retain (Older backups will be deleted): 5
Loading docker images..
Loading Collector..
92a4e8a3140f: Loading layer  83.87MB/83.87MB
... 
... 
... 
Creating default user accounts

Aviz S3 Apps tables [AccessToken,ACL,RoleMapping,S3Role,S3User,S3Acl,S3RoleAclMapping,Setting,S3ComponentAcl,S3RoleComponentAclMapping,RedundancySetting] created in  postgresql
Total roles created:  1
Total s3acl created:  5
Total s3Componentacl created:  9
Total settings created:  5
User created!! username:  superadmin
Installed ONES application successfully.
Open browser at https://<host-ip>

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

Activation:

• For Trail, user can choose Start A Trial

• Then user can choose Activate License if user has activated key to supporting more then 8 devices

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

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 Device

  • Run ZTP

Template Details: BGP IP-CLOS with MCLAG in the given topology

• Devices used

  • 2- Spine Devices

  • 4- Leaf Devices

  • 2- End Host

Topology

BGP-IP-CLOS-MCLAG Standard Template

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

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

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

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:

1. Device switch ID: unique ID for every device, required to correctly render the topology

2. Switch name: hostname of the device

3. IP address: management address of the device

4. Autonomous System Number (ASN): BGP AS number to use

5. Device Credentials: Username & Password.

6. MCLAG: Multichassis Link Aggregation

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