Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 148 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

ONES-3.0

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

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

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

  1. CPU and Memory Utilisation

  2. Fan and PSU LED status

  3. Traffic Bandwidth

  4. ASIC Routes

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

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.

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

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

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

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.

Traffic Utilisation

  • Software Compliance

  • AI Fabric

  • Underlay and Overlay protocols view

  • 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

  • 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

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

  • 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

    1. CPU and Memory Utilisation

    2. Fan and PSU LED status

    3. SSD Memory Utilization, Health and Temperature Status

    4. Traffic Bandwidth

    5. ASIC Routes

    6. Health Services

    7. Device Down alerts

    8. BGP Neighbour Down alter

    9. Component failure

    10. Interface Flap Alerts

    11. Traffic Errors and Discard Counters

    12. PFC Counters

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

    1. Device Level

    2. Interface Level

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

    12Hours

    5Minutes

    144

    1Day

    10Minutes

    144

    1Week

    1Hour 10Minutes

    144

    2Weeks

    2Hours 20Minutes

    144

    Time Series

    Average between 2 data points

    Data Points

    Reference

    1Hour

    30sec

    120

    2Hours

    40sec

    180

    4Hours

    1Minute 20sec

    180

    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

    NA

    NA

    NA

    Device

    Queue Counter

    Count()

    AVG/MIN/MAX

    Count

    Device

    SSD Health

    Percentage(%)

    Percentage(%)

    0/100

    Device

    SSD Temperature

    Celsius ()

    AVG/MIN/MAX

    Celsius

    Device

    SSD Memory

    Percentage(%)

    Percentage(%)

    0/100

    Interface

    Int Flap

    NA

    NA

    NA

    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

    Hierarchy

    Metrics

    Unit

    Measure

    Value

    Device

    CPU Utilization

    Percentage (%)

    AVG/MIN/MAX

    0/100

    Device

    Memory Utilization

    Percentage (%)

    AVG/MIN/MAX

    0/100

    ONE DL

    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 1.0.0

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

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

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

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

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

  • 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

    Users can reach out to customer support on

    Supports Options are available:

    • Integrated Chat

    • Submit a Ticket

    • Send an email to support@aviznetworks.com

    Refer to the "" section of this document for more details

    ONES Supportability

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

    www.support.aviznetworks.com
    How to contact Aviz Networks Support?
    https://www.support.aviznetworks.com

    Supported Switch Platforms and NOS

    SONiC Supported Broadcom Platforms:

    Speed
    Vendor (Models)

    1G

    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)

    SONiC Supported Cisco Platforms:

    Speed
    Models

    SONiC Supported Marvell Platforms:

    Speed
    Vendor (Models)

    SONiC Supported NVIDIA Platforms:

    Speed
    Models

    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

    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

    Proprietary NOS like Arista EOS, Cumulus, and Cisco NX-OS does not require an ONES Agent and instead leverage the (Agent-less) feature. OpenConfig extends APIs that provide Network Telemetry information about the resources being monitored via (gRPC Network Management Interface) protocol to the ONES Application

    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

    100G

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

    400G

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

    800G

    Celestica (DS4101)

    100G

    8101-32H, 8102-64H

    400G

    8101-32FH

    1G

    Wistron (ES1227, ES2227)

    400G

    Wistron (6512)

    1G

    SN2201

    10/25G

    SN2010, SN2410, SN3420

    100G

    SN2100, SN2700, SN3700C, SN3800, SN4600C

    400G

    SN4410, SN4700

    800G

    SN5600

    Arista

    EOS

    4.x

    Cisco

    NXOS

    9.x

    NVIDIA

    Cumulus Linux

    5.9, 5.11

    OpenConfig
    gNMI

    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

    System Software Requirements - ONES Application

    OS
    Libraries
    Task
    Command
    Validation

    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

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

    These ports has to be enable on Device(Switch)

    ONES Service
    Port Numbers

    Ports to be open on ONES Server for ONES Services

    ONES Service
    Port Numbers

    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

    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.

    128GB

    640GB or more

    64

    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

    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

    8080

    stream-processer

    8093

    ksqldb-server

    8088

    kafka-connect

    8083

    schema-registry

    8081

    broker

    29092, 9101, 9092

    Zookeeper

    2181

    ONES Collector

    50053

    8

    x86/x64 based,

    16-core CPU

    32GB

    160GB or more

    16

    x86/x64 based,

    16-core CPU

    64GB

    320GB or more

    32

    Ubuntu 18.0 or later

    docker, docker-compose

    python3, python3-pip

    paramiko

    scp

    Ubuntu Server

    Installer file (Version 18 or higher)

    lsb_release -a

    Update to latest packages

    sudo apt-get update

    NA​

    Install Docker

    sudo apt-get install docker.io

    ​docker ps​

    ONES Collector

    50053

    Switch Access over SSH

    22

    ONES Monitoring

    50052

    gNMI Gateway (Telemetry)

    9339

    ONES Telemetry Database

    5432

    ONES Orchestrator

    8787

    ONES Orchestrator Database

    2345

    pty-server

    8885

    ONES Web GUI

    443

    x86/x64 based,

    16-core CPU

    Install Docker-compose

    API-Server

    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

    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

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

    2. ONESv3.0 support SSL certificate integration

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

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

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

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

    1. ONES Application support IP-based Access & FQDN Access

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

    IP based

    FQDN based

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

      2. User can choose no if there no requirement of authentication

    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

    • 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

    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

    Login To ONES

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

    1. Account >> License >> Upgrade License

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

    1. Copy the postgresql.config file outside to do changes

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

    1. Copy the changes to DB config file

    1. Restart the ones-collector-db

    Download ONES Package

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

    Please refer to the link https://support.aviznetworks.com/hc/en-us/articles/10268234313997-ONES-Image-Download for downloading latest version of ONES Application

    NOTE: You are required to sign-up on https://support.aviznetworks.com/hc/en-us for getting access to the download page.

    • Work with Aviz Sales/Support contact to create an account on Aviz Networks Support Portal

    • Login to with your account credentials

    • Click on the Downloads section, under ONES, click to download ONES Release 3.0

      • File to install on Ubuntu

        • ONES 3.0 Installation package

    ONES Telemetry Agent Installation

    ONES Agent v3.0 support Agent Auto discovery

    1. ONESv3.0 Agent support auto-discovery feature

    2. ONESv3.0 Agent support to send telemetry on multiple controllers (Max 2)

    3. Restrict IP feature can be enabled/disabled

    4. Only Collector upgrade after Deployment is possible now

    5. Password-based authentication is supported

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

    7. Need to add a few inputs while installing the agent

      1. Controller IP //To restrict the telemetry streaming

      2. Device Credentials

      3. Layer

    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

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

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

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

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

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

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

    Cumulus(NVUE API)

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

    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

    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.

    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.

    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

    ONES Server Agent Installation

    Server Agent v3.0 support:

    Only Intel Guadi platform is supported in ONESv3.0

    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.

    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)

    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.

    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

    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

    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

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

    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

    For higher volumes: Continue scaling in similar increments.

  • Run ./one-dl-multitenant-installer.sh

  • 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

    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

    1. Installation: install FMCLI

    2. uninstallation: Uninstall FMCLI

    3. installresetconfig: Install FMCLI and reset the configuration

    4. upgrade: Upgrade FMCLI to the latest version

    5. install_withQOS: Install FMCLI and enable QoS feature

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

    Show run GRPC

    GRPC Service Statistics

    GRPC Summary

    Supported Telemetry

    switch-1# configure terminal
    switch-1(config)#
    switch-1# feature grpc
    switch-1(config)#
    switch(config)# grpc use-vrf default
    ZOOKEEPER_SERVER_VALUE=    //Public DNS
    KAFKA_SERVER_VALUE=        //Public DNS
    SCHEMA_REGISTRY_SERVER_VALUE=    
    INSTANCE_ID=               //Instance ID
    VPC_ID=                    //VPC ID
    REGION=                    //REGION ID
    SG_ID=                     //SG ID
    Document the `instance_id`, `vpc_id`, `region`, and `security_group_id` of the provisioned instance.
    sudo apt update
    
    sudo apt install apt-transport-https ca-certificates curl software-properties-common
    
    curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /usr/share/keyrings/docker-archive-keyring.gpg
    
    echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
    
    sudo apt update
    
    apt-cache policy docker-ce
    
    sudo apt install docker-ce
    
    mkdir -p ~/.docker/cli-plugins/
    curl -SL https://github.com/docker/compose/releases/download/v2.3.3/docker-compose-linux-x86_64 -o ~/.docker/cli-plugins/docker-compose
    
    chmod +x ~/.docker/cli-plugins/docker-compose
    
    docker compose version
    
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ tar -xvf one-dl.tar.gz
    docker-compose.yml
    one-dl-multitenant-installer.sh
    .env
    aviz@aviz % ssh -i ones-dl-qa.pem ubuntu@34.215.5.89
    Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 6.2.0-1018-aws x86_64)
    
     * Documentation:  https://help.ubuntu.com
     * Management:     https://landscape.canonical.com
     * Support:        https://ubuntu.com/pro
    
      System information as of Thu Mar  7 06:17:12 UTC 2024
    
      System load:  0.01513671875      Processes:                224
      Usage of /:   1.0% of 247.92GB   Users logged in:          1
    ZOOKEEPER_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    KAFKA_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    SCHEMA_REGISTRY_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    INSTANCE_ID=i-06e36f82c35173cc9
    VPC_ID=vpc-09a64a3439e9c1022
    REGION=us-west-2
    SG_ID=sg-0057cdb5b97e1d218
    ~
    ".env" 7L, 323B                                                                                                                                     1,1           All
      Memory usage: 0%                 IPv4 address for docker0: 172.17.0.1
      Swap usage:   0%                 IPv4 address for ens5:    172.31.28.5
    
    
    Expanded Security Maintenance for Applications is not enabled.
    
    39 updates can be applied immediately.
    25 of these updates are standard security updates.
    To see these additional updates run: apt list --upgradable
    
    7 additional security updates can be applied with ESM Apps.
    Learn more about enabling ESM Apps service at https://ubuntu.com/esm
    
    
    Last login: Thu Mar  7 06:10:37 2024 from 18.237.140.163
    ubuntu@ip-172-31-28-5:~$
    ubuntu@ip-172-31-28-5:~$ pwd
    /home/ubuntu
    ubuntu@ip-172-31-28-5:~$ cd ONES-DL-CLOUD/
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ pwd
    /home/ubuntu/ONES-DL-CLOUD
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ ls
    one-dl.tar.gz
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ tar -xvf one-dl.tar.gz
    docker-compose.yml
    one-dl-multitenant-installer.sh
    .env
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ vi .env
    ZOOKEEPER_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    KAFKA_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    SCHEMA_REGISTRY_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    INSTANCE_ID=i-06e36f82c35173cc9
    VPC_ID=vpc-09a64a3439e9c1022
    REGION=us-west-2
    SG_ID=sg-0057cdb5b97e1d218
    
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ cat .env
    ZOOKEEPER_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    KAFKA_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    SCHEMA_REGISTRY_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    INSTANCE_ID=i-06e36f82c35173cc9
    VPC_ID=vpc-09a64a3439e9c1022
    REGION=us-west-2
    SG_ID=sg-0057cdb5b97e1d218
    
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ cp .env .env-backup
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ cat .env-backup
    ZOOKEEPER_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    KAFKA_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    SCHEMA_REGISTRY_SERVER_VALUE=ec2-35-93-19-159.us-west-2.compute.amazonaws.com
    INSTANCE_ID=i-06e36f82c35173cc9
    VPC_ID=vpc-09a64a3439e9c1022
    REGION=us-west-2
    SG_ID=sg-0057cdb5b97e1d218
    
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ ls
    docker-compose.yml  one-dl-multitenant-installer.sh  one-dl.tar.gz
    
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ ./one-dl-multitenant-installer.sh
    SHELL=/bin/bash
    REGION=us-west-2
    KAFKA_SERVER_VALUE=ec2-34-215-5-89.us-west-2.compute.amazonaws.com
    PWD=/home/ubuntu/ONES-DL-CLOUD
    LOGNAME=ubuntu
    XDG_SESSION_TYPE=tty
    SCHEMA_REGISTRY_SERVER_VALUE=ec2-34-215-5-89.us-west-2.compute.amazonaws.com
    MOTD_SHOWN=pam
    HOME=/home/ubuntu
    LANG=C.UTF-8
    LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.zst=01;31:*.tzst=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.wim=01;31:*.swm=01;31:*.dwm=01;31:*.esd=01;31:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.webp=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36:
    VPC_ID=vpc-09a64a3439e9c1022
    LC_TERMINAL=iTerm2
    SSH_CONNECTION=43.224.130.156 61180 172.31.28.5 22
    LESSCLOSE=/usr/bin/lesspipe %s %s
    XDG_SESSION_CLASS=user
    TERM=xterm-256color
    LESSOPEN=| /usr/bin/lesspipe %s
    USER=ubuntu
    SG_ID=sg-04c3752b777d8f77e
    LC_TERMINAL_VERSION=3.4.16
    SHLVL=2
    XDG_SESSION_ID=5
    LC_CTYPE=C.UTF-8
    XDG_RUNTIME_DIR=/run/user/1000
    SSH_CLIENT=43.224.130.156 61180 22
    XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop
    ZOOKEEPER_SERVER_VALUE=ec2-34-215-5-89.us-west-2.compute.amazonaws.com
    PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
    INSTANCE_ID=i-01300eb6edb18273b
    DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
    SSH_TTY=/dev/pts/1
    OLDPWD=/home/ubuntu
    _=/usr/bin/env
    us-west-2 i-01300eb6edb18273b vpc-09a64a3439e9c1022 sg-04c3752b777d8f77e
    Error response from daemon: No such container: zookeeper
    Error response from daemon: No such container: kafka
    Error response from daemon: No such container: schema-registry
    Error response from daemon: No such container: kafka-connect
    Error response from daemon: No such container: zookeeper
    Error response from daemon: No such container: kafka
    Error response from daemon: No such container: schema-registry
    Error response from daemon: No such container: kafka-connect
    {
        "Return": true,
        "SecurityGroupRules": [
            {
                "SecurityGroupRuleId": "sgr-07f887d736a7c773c",
                "GroupId": "sg-04c3752b777d8f77e",
                "GroupOwnerId": "259789323334",
                "IsEgress": false,
                "IpProtocol": "tcp",
                "FromPort": 29092,
                "ToPort": 29092,
                "CidrIpv4": "0.0.0.0/0"
            }
        ]
    }
    {
        "Return": true,
        "SecurityGroupRules": [
            {
                "SecurityGroupRuleId": "sgr-0d446cf43dbf8c55a",
                "GroupId": "sg-04c3752b777d8f77e",
                "GroupOwnerId": "259789323334",
                "IsEgress": false,
                "IpProtocol": "tcp",
                "FromPort": 9092,
                "ToPort": 9092,
                "CidrIpv4": "0.0.0.0/0"
            }
        ]
    }
    {
        "Return": true,
        "SecurityGroupRules": [
            {
                "SecurityGroupRuleId": "sgr-08d752b5cbfea8b1c",
                "GroupId": "sg-04c3752b777d8f77e",
                "GroupOwnerId": "259789323334",
                "IsEgress": false,
                "IpProtocol": "tcp",
                "FromPort": 2181,
                "ToPort": 2181,
                "CidrIpv4": "0.0.0.0/0"
            }
        ]
    }
    {
        "Return": true,
        "SecurityGroupRules": [
            {
                "SecurityGroupRuleId": "sgr-058962812f2650b4e",
                "GroupId": "sg-04c3752b777d8f77e",
                "GroupOwnerId": "259789323334",
                "IsEgress": false,
                "IpProtocol": "tcp",
                "FromPort": 8083,
                "ToPort": 8083,
                "CidrIpv4": "0.0.0.0/0"
            }
        ]
    }
    {
        "Return": true,
        "SecurityGroupRules": [
            {
                "SecurityGroupRuleId": "sgr-03a801549ac17a74d",
                "GroupId": "sg-04c3752b777d8f77e",
                "GroupOwnerId": "259789323334",
                "IsEgress": false,
                "IpProtocol": "tcp",
                "FromPort": 8081,
                "ToPort": 8081,
                "CidrIpv4": "0.0.0.0/0"
            }
        ]
    }
    {
        "Return": true,
        "SecurityGroupRules": [
            {
                "SecurityGroupRuleId": "sgr-01ae4abe9d99c0086",
                "GroupId": "sg-04c3752b777d8f77e",
                "GroupOwnerId": "259789323334",
                "IsEgress": false,
                "IpProtocol": "tcp",
                "FromPort": 8181,
                "ToPort": 8181,
                "CidrIpv4": "0.0.0.0/0"
            }
        ]
    }
    [+] Running 10/10
     ✔ zookeeper 9 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                                         5.1s
       ✔ 23828d760c7b Pull complete                                                                                                                                  0.6s
       ✔ e2670537dceb Pull complete                                                                                                                                  0.5s
       ✔ 3c059ccfa418 Pull complete                                                                                                                                  0.6s
       ✔ a23d33d59f2a Pull complete                                                                                                                                  0.7s
       ✔ 842a648f5439 Pull complete                                                                                                                                  0.9s
       ✔ 278244c5561f Pull complete                                                                                                                                  0.9s
       ✔ 0ab51e87b8dc Pull complete                                                                                                                                  1.0s
       ✔ 26ff518a75d1 Pull complete                                                                                                                                  1.4s
       ✔ 050c7bc3a5c4 Pull complete                                                                                                                                  1.1s
    [+] Running 1/1
     ✔ Container zookeeper  Started                                                                                                                                  4.2s
    [+] Running 12/12
     ✔ kafka 11 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                                          9.4s
       ✔ fe36fc382320 Pull complete                                                                                                                                  0.7s
       ✔ 4250354b4fb7 Pull complete                                                                                                                                  2.1s
       ✔ c4c5f447179d Pull complete                                                                                                                                  0.3s
       ✔ 17fe3a92262f Pull complete                                                                                                                                  0.6s
       ✔ 5420596c14ab Pull complete                                                                                                                                  1.1s
       ✔ 0e55377ebe37 Pull complete                                                                                                                                  0.9s
       ✔ da7039bb2113 Pull complete                                                                                                                                  1.1s
       ✔ d389b3791c2e Pull complete                                                                                                                                  1.4s
       ✔ c24709eccb2a Pull complete                                                                                                                                  1.4s
       ✔ ad79ffd84e00 Pull complete                                                                                                                                  2.4s
       ✔ 218229bf30d9 Pull complete                                                                                                                                  1.7s
    [+] Running 1/1
     ✔ Container kafka  Started                                                                                                                                      5.7s
    [+] Running 12/12
     ✔ schema-registry 11 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                               17.9s
       ✔ fe36fc382320 Already exists                                                                                                                                 0.0s
       ✔ 4250354b4fb7 Already exists                                                                                                                                 0.0s
       ✔ c4c5f447179d Already exists                                                                                                                                 0.0s
       ✔ 17fe3a92262f Already exists                                                                                                                                 0.0s
       ✔ 5420596c14ab Already exists                                                                                                                                 0.0s
       ✔ 0e55377ebe37 Already exists                                                                                                                                 0.0s
       ✔ da7039bb2113 Already exists                                                                                                                                 0.0s
       ✔ d389b3791c2e Already exists                                                                                                                                 0.0s
       ✔ c24709eccb2a Already exists                                                                                                                                 0.0s
       ✔ e69ded016b1a Pull complete                                                                                                                                  8.9s
       ✔ 83e8ec805f43 Pull complete                                                                                                                                  0.3s
    [+] Running 1/1
     ✔ Container schema-registry  Started                                                                                                                           18.7s
    [+] Running 21/21
     ✔ kafka-connect 20 layers [⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿]      0B/0B      Pulled                                                                                        18.1s
       ✔ a49367d57626 Pull complete                                                                                                                                  0.7s
       ✔ eeec2f37f4a0 Pull complete                                                                                                                                  2.8s
       ✔ ae805807db54 Pull complete                                                                                                                                  1.4s
       ✔ c553584e96cc Pull complete                                                                                                                                  1.1s
       ✔ 28769e081b94 Pull complete                                                                                                                                  2.4s
       ✔ 151cf144f79d Pull complete                                                                                                                                  1.9s
       ✔ 04292bb11042 Pull complete                                                                                                                                  2.3s
       ✔ c2e0c70921ea Pull complete                                                                                                                                  2.7s
       ✔ e8d7f71a6ca4 Pull complete                                                                                                                                  2.9s
       ✔ eb27eb7b8f05 Pull complete                                                                                                                                  4.7s
       ✔ 9bb8b7d5f6a0 Pull complete                                                                                                                                  3.3s
       ✔ 302eaef771e0 Pull complete                                                                                                                                 11.7s
       ✔ 1d0d5b44b6f1 Pull complete                                                                                                                                  3.8s
       ✔ 22df7873ee50 Pull complete                                                                                                                                  4.4s
       ✔ 4f4fb700ef54 Pull complete                                                                                                                                  4.7s
       ✔ 972adc085ab6 Pull complete                                                                                                                                  7.0s
       ✔ c4f994822767 Pull complete                                                                                                                                  6.1s
       ✔ 70547799762d Pull complete                                                                                                                                  7.0s
       ✔ 3f0c034e271c Pull complete                                                                                                                                  7.5s
       ✔ b6195a937e7b Pull complete                                                                                                                                  7.7s
    [+] Running 1/1
     ✔ Container kafka-connect  Started                                                                                                                              4.6s
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$
    ubuntu@ip-172-31-28-5:~/ONES-DL-CLOUD$ sudo su
    root@ip-172-31-28-5:/home/ubuntu/ONES-DL-CLOUD# docker ps
    CONTAINER ID   IMAGE                             COMMAND                  CREATED              STATUS                             PORTS     NAMES
    ab8aa46cc746   avizdock/kafka-connect:latest     "/etc/confluent/dock…"   28 seconds ago       Up 23 seconds (health: starting)             kafka-connect
    346522f4baf5   confluentinc/cp-schema-registry   "/etc/confluent/dock…"   About a minute ago   Up About a minute                            schema-registry
    23c50c44bc5b   confluentinc/cp-kafka:latest      "/etc/confluent/dock…"   2 minutes ago        Up 2 minutes                                 kafka
    633eba10034d   zookeeper                         "/docker-entrypoint.…"   3 minutes ago        Up 3 minutes                                 zookeeper
    root@ip-172-31-28-5:/home/ubuntu/ONES-DL-CLOUD#
    ./ones_agent_parallel_installer.sh
    Do you want to update the username/password for password authentication? (yes/no): no
    Does the ONES-agent is integrated with SONiC NOS? (yes/no): no
    Do you want to add only Collector IP for auto-discovery and skip the agent installation? (yes/no): yes
    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.20.0.80
    Do you want to restrict access only to the provided collector IP?
    Note: Providing Yes will restrict access to agent only with the provided collector IP Address
    Enter yes/no: No
    Do you want to enable password authentication? (yes/no): no
    e2ef8a51359d: Loading layer [==================================================>]  72.54MB/72.54MB
    ae2d55769c5e: Loading layer [==================================================>]  7.401MB/7.401MB
    3054512b6f71: Loading layer [==================================================>]  31.35MB/31.35MB
    997b8e79e84f: Loading layer [==================================================>]   5.12kB/5.12kB
    e6c5004ee77f: Loading layer [==================================================>]   11.7MB/11.7MB
    867f2af1b281: Loading layer [==================================================>]   2.56kB/2.56kB
    86fee8a2d43f: Loading layer [==================================================>]  31.45MB/31.45MB
    4a2339f45f2a: Loading layer [==================================================>]   42.7MB/42.7MB
    274d02d0f011: Loading layer [==================================================>]  1.421MB/1.421MB
    Loaded image: avizdock/agent_installer:latest
    Docker image 'avizdock/agent_installer' is loaded.
    fc82d440ded45cb5002c6539c62daaeac6435c82a41078a356e943dad1ca6fc4
    Docker container 'agent_installer' is running.
    Selecting ‘Yes’ will exclusively initiate the day-2 deployment of the Ones-Agent,
    involving a reconfiguration of the existing agent to establish communication with the specified collector(s).
    Choosing ‘No’ will initiate the deployment of the Ones-Agent as an independent third-party container.
    The default values for rackid, brickid, and azid are all set to 0.
    [{'ip': '10.20.2.12', 'user': 'admin', 'passwd': 'YourPaSsWoRd', 'layer': 'Leaf', 'region': 'San_Jose_Lab', 'type': ackid': '1', 'installation_instance': 1, 'agentip': '10.20.2.12', 'collectorip': '10.20.0.80', 'restrict_collector_i
    
    Agent installation skipped successfully........
    Adding Collector IP for auto-discovery...........
    ###############Connecting to switch###############
    Connection to switch 10.20.2.12 successful.....................
    Copying conf file to tmp directory on the device 10.20.2.12 .............
    Copying conf file to tmp directory successful on the device 10.20.2.12 .............
    Collector ip successfully added to agent.conf on the device 10.20.2.12........
    Docker container is up. Proceeding with collector registration.......
    ╒══════════════╤══════════╕
    │ IP Address   │ Result   │
    ╞══════════════╪══════════╡
    ╘══════════════╧══════════╛
    agent_installer
    
    Docker agent_installer has been stopped
    agent_installer
    
    Docker agent_installer has been removed
    Untagged: avizdock/agent_installer:latest
    Deleted: sha256:180765aed1eba26b8d30d3bef983682a2b36a3507b7655c6e614f22dbbf80007
    Deleted: sha256:7912382f54799a2f35358528c441af6bb745ba6fe6cb040a7be48347ff7e80a3
    Deleted: sha256:fe33139b53a0b2b401d44f57a74ff789beb4a3a38792f80a793cc01611bab9e7
    Deleted: sha256:38e2eba240dfe04c6d027aafc1954c84fc1eadeb3e4fd9d1e9a8ad7100686d7f
    Deleted: sha256:53fdc4ec83b42d7060b4143da9ffbf9dd55e3bfa6fb4843bfacec19dcbd80e4b
    Deleted: sha256:11b1633cb703032b065434387b48194f3e97a57aaddc61a31aa2918a1fd32780
    Deleted: sha256:aa353210edce17d0370066fc6184cff9e2a9197884e6f43a0ad1fd32b630f8de
    Deleted: sha256:b23b2f4af61d8cc745c6bea66be93bd59b97c3971c36466ae4ea345f52fdfc67
    Deleted: sha256:b55ff4d1eb4dd15edbc9ffc15b1bd5771cd09c371b0e7c44cbcbd5c5f62ec76a
    Deleted: sha256:e2ef8a51359d088511d34c725305c220294a1fcd5fe5e5dbe4d698c7239ce2c9
    
    Docker avizdock/agent_installer image has been removed
    
    ip,user,passwd
    10.4.4.61,admin,YourPaSsWoRd
    10.4.4.62,admin,YourPaSsWoRd
    ...
    ...
    ...
    root@ones-application:/ONES-3.1/ones_fm_agent# ./deploy_fmcli.sh
    
    Available options for FMCLI installation:
    1) install
       - Install FMCLI
    2) uninstall
       - Uninstall FMCLI
    3) installresetconfig
       - Install FMCLI and reset the configuration
    4) upgrade
       - Upgrade FMCLI to the latest version
    5) install_withQOS
       - Install FMCLI and enable QoS feature
    6) installresetconfig_withQOS
       - Install FMCLI, reset the configuration, and enable QoS feature
    
    Please enter your choice (1-6) to proceed with the FMCLI installation: 1
    
    Installer will proceed with FMCLI-install ...
    
    e2ef8a51359d: Loading layer [==================================================>]  72.54MB/72.54MB
    ae2d55769c5e: Loading layer [==================================================>]  7.401MB/7.401MB
    3054512b6f71: Loading layer [==================================================>]  31.35MB/31.35MB
    997b8e79e84f: Loading layer [==================================================>]   5.12kB/5.12kB
    e6c5004ee77f: Loading layer [==================================================>]   11.7MB/11.7MB
    867f2af1b281: Loading layer [==================================================>]   2.56kB/2.56kB
    86fee8a2d43f: Loading layer [==================================================>]  31.45MB/31.45MB
    4a2339f45f2a: Loading layer [==================================================>]   42.7MB/42.7MB
    274d02d0f011: Loading layer [==================================================>]  1.421MB/1.421MB
    Loaded image: avizdock/agent_installer:latest
    Docker image 'avizdock/agent_installer:latest' is loaded.
    469077cbff8b9f424c6ec6e46272788451c4714cf742eb42ee94771b0f8bd944
    
    Docker container 'agent_installer' is running.
    CONTAINER ID   IMAGE                             COMMAND     CREATED         STATUS                  PORTS     NAMES
    469077cbff8b   avizdock/agent_installer:latest   "python3"   2 seconds ago   Up Less than a second             agent_installer
    
    Docker container 'ones-fm' is running.
    Update success for 10.20.3.14
    Update success for 10.20.3.16
    Ignore below Error if Installing Agent via docker installer
    
    ones-fm container is not running
    
    Operation = install
    ##### params = {'ip': '10.20.3.14', 'passwd': 'YourPaSsWoRd', 'user': 'admin', 'server_ip': '172.17.0.2', 'fm_port': None} #####
    ##### params = {'ip': '10.20.3.16', 'passwd': 'YourPaSsWoRd', 'user': 'admin', 'server_ip': '172.17.0.2', 'fm_port': None} #####
    ###############Connecting to switch###############
    ###############Connecting to switch###############
    <paramiko.client.SSHClient object at 0x7e52a08862b0>
    Connection to switch 10.20.3.14 successfull.....................
    /home/ones_fm_agent
    <paramiko.client.SSHClient object at 0x7e52a0886670>
    Connection to switch 10.20.3.16 successfull.....................
    /home/ones_fm_agent
    Creating work directory  on the device 10.20.3.14........
    Work Directory ones-fm_1726039311_4128287 created successfully on the device 10.20.3.14 .............
    Copying FMCLI_Installer.py to directory ones-fm_1726039311_4128287 on the device 10.20.3.14 .............
    Creating work directory  on the device 10.20.3.16........
    Work Directory ones-fm_1726039311_510445 created successfully on the device 10.20.3.16 .............
    Copying FMCLI_Installer.py to directory ones-fm_1726039311_510445 on the device 10.20.3.16 .............
    Debug command used:: sudo ls ones-fm_1726039311_4128287/FMCLI_Installer.py
    The file 'ones-fm_1726039311_4128287/FMCLI_Installer.py' copy success on the device.
    Copying FMCLI_Installer.py to directory ones-fm_1726039311_4128287 successful on the device 10.20.3.14 .............
    Copying fmcli-app.tgz to directory ones-fm_1726039311_4128287 on the device 10.20.3.14 .............
    Debug command used:: sudo ls ones-fm_1726039311_510445/FMCLI_Installer.py
    The file 'ones-fm_1726039311_510445/FMCLI_Installer.py' copy success on the device.
    Copying FMCLI_Installer.py to directory ones-fm_1726039311_510445 successful on the device 10.20.3.16 .............
    Copying fmcli-app.tgz to directory ones-fm_1726039311_510445 on the device 10.20.3.16 .............
    Debug command used:: sudo ls ones-fm_1726039311_4128287/fmcli-app.tgz
    The file 'ones-fm_1726039311_4128287/fmcli-app.tgz' copy success on the device.
    Copying fmcli-app.tgz to directory ones-fm_1726039311_4128287 successful on the device 10.20.3.14 .............
    Debug command used:: sudo ls ones-fm_1726039311_510445/fmcli-app.tgz
    The file 'ones-fm_1726039311_510445/fmcli-app.tgz' copy success on the device.
    Copying fmcli-app.tgz to directory ones-fm_1726039311_510445 successful on the device 10.20.3.16 .............
    File '/usr/lib/frr/frr-reload.py' exists in container 'bgp'
    Skip scp as File: /usr/lib/frr/frr-reload.py exits inside bgp container
    File '/usr/lib/frr/frr-reload.py' exists in container 'bgp'
    Skip scp as File: /usr/lib/frr/frr-reload.py exits inside bgp container
    
    #################### Installing FMCLI on the device 10.20.3.14 ######################
    
    #################### Installing FMCLI on the device 10.20.3.16 ######################
    ####### Debug LOGS on the device 10.20.3.14 #######
    fmcli-app/
    fmcli-app/libhiredis.so.1.1.0
    fmcli-app/fmcli.sh
    fmcli-app/fmcli
    fmcli-app/ip_validate
    fmcli-app/fmcli.cli
    fmcli-app/fmcli.version
    fmcli-app/fmcli_read_db_schema
    fmcli-app/fmclimain.service
    fmcli-app/fmcli_composer_mapping.cfg
    fmcli-app/fmcli_composer.py
    fmcli-app/libcligen.so.6.2
    cli
    cli/fmcli-app-arm.tgz
    cli/fmcli-app-amd.tgz
    Extracting cli/fmcli-app-amd.tgz...
    Installing Aviz-FMCLI ..........
    Aviz-FMCLI installation successful........
    
    Created symlink /etc/systemd/system/multi-user.target.wants/fmclimain.service → /etc/systemd/system/fmclimain.service.
    /tmp/fmcliStartup.init
    
    FM-Agent installed successfully on the device 10.20.3.14........
    ####### Deleting ones-fm_1726039311_4128287 dir on the device 10.20.3.14 #######
    Deployment of FM-Agent to switch 10.20.3.14 is Completed
    ####### Debug LOGS on the device 10.20.3.16 #######
    fmcli-app/
    fmcli-app/libhiredis.so.1.1.0
    fmcli-app/fmcli.sh
    fmcli-app/fmcli
    fmcli-app/ip_validate
    fmcli-app/fmcli.cli
    fmcli-app/fmcli.version
    fmcli-app/fmcli_read_db_schema
    fmcli-app/fmclimain.service
    fmcli-app/fmcli_composer_mapping.cfg
    fmcli-app/fmcli_composer.py
    fmcli-app/libcligen.so.6.2
    cli
    cli/fmcli-app-arm.tgz
    cli/fmcli-app-amd.tgz
    Extracting cli/fmcli-app-amd.tgz...
    Installing Aviz-FMCLI ..........
    Aviz-FMCLI installation successful........
    
    Created symlink /etc/systemd/system/multi-user.target.wants/fmclimain.service → /etc/systemd/system/fmclimain.service.
    /tmp/fmcliStartup.init
    
    FM-Agent installed successfully on the device 10.20.3.16........
    ####### Deleting ones-fm_1726039311_510445 dir on the device 10.20.3.16 #######
    Deployment of FM-Agent to switch 10.20.3.16 is Completed
    FMCLI install Result
    {'10.20.3.14': 'PASS', '10.20.3.16': 'PASS'}
    ╒═════════╤════════════╤══════════════════╕
    │   SL.No │ Device     │ install Result   │
    ╞═════════╪════════════╪══════════════════╡
    │       1 │ 10.20.3.14 │ PASS             │
    ├─────────┼────────────┼──────────────────┤
    │       2 │ 10.20.3.16 │ PASS             │
    ╘═════════╧════════════╧══════════════════╛
    agent_installer
    Docker agent_installer has been stopped
    agent_installer
    Docker agent_installer has been removed
    Untagged: avizdock/agent_installer:latest
    Deleted: sha256:180765aed1eba26b8d30d3bef983682a2b36a3507b7655c6e614f22dbbf80007
    Deleted: sha256:7912382f54799a2f35358528c441af6bb745ba6fe6cb040a7be48347ff7e80a3
    Deleted: sha256:fe33139b53a0b2b401d44f57a74ff789beb4a3a38792f80a793cc01611bab9e7
    Deleted: sha256:38e2eba240dfe04c6d027aafc1954c84fc1eadeb3e4fd9d1e9a8ad7100686d7f
    Deleted: sha256:53fdc4ec83b42d7060b4143da9ffbf9dd55e3bfa6fb4843bfacec19dcbd80e4b
    Deleted: sha256:11b1633cb703032b065434387b48194f3e97a57aaddc61a31aa2918a1fd32780
    Deleted: sha256:aa353210edce17d0370066fc6184cff9e2a9197884e6f43a0ad1fd32b630f8de
    Deleted: sha256:b23b2f4af61d8cc745c6bea66be93bd59b97c3971c36466ae4ea345f52fdfc67
    Deleted: sha256:b55ff4d1eb4dd15edbc9ffc15b1bd5771cd09c371b0e7c44cbcbd5c5f62ec76a
    Deleted: sha256:e2ef8a51359d088511d34c725305c220294a1fcd5fe5e5dbe4d698c7239ce2c9
    Docker avizdock/agent_installer:latest image has been removed
    
    root@Switch:~$ sudo fmcli 
    fmcli# 
    Available options for FMCLI installation:
    1) install
       - Install FMCLI
    2) uninstall
       - Uninstall FMCLI
    3) installresetconfig
       - Install FMCLI and reset the configuration
    4) upgrade
       - Upgrade FMCLI to the latest version
    5) install_withQOS
       - Install FMCLI and enable QoS feature
    6) installresetconfig_withQOS
       - Install FMCLI, reset the configuration, and enable QoS feature
    
    Please enter your choice (1-6) to proceed with the FMCLI installation: 2
    
    Installer will proceed with FMCLI-uninstall ...
    
    e2ef8a51359d: Loading layer [==================================================>]  72.54MB/72.54MB
    ae2d55769c5e: Loading layer [==================================================>]  7.401MB/7.401MB
    3054512b6f71: Loading layer [==================================================>]  31.35MB/31.35MB
    997b8e79e84f: Loading layer [==================================================>]   5.12kB/5.12kB
    e6c5004ee77f: Loading layer [==================================================>]   11.7MB/11.7MB
    867f2af1b281: Loading layer [==================================================>]   2.56kB/2.56kB
    86fee8a2d43f: Loading layer [==================================================>]  31.45MB/31.45MB
    4a2339f45f2a: Loading layer [==================================================>]   42.7MB/42.7MB
    274d02d0f011: Loading layer [==================================================>]  1.421MB/1.421MB
    Loaded image: avizdock/agent_installer:latest
    Docker image 'avizdock/agent_installer:latest' is loaded.
    f5922322cecfe27405c0dc2d62201b2145695eac1eeedd8e6d9acf20e6e55541
    
    Docker container 'agent_installer' is running.
    CONTAINER ID   IMAGE                             COMMAND     CREATED         STATUS                  PORTS     NAMES
    f5922322cecf   avizdock/agent_installer:latest   "python3"   2 seconds ago   Up Less than a second             agent_installer
    
    Docker container 'ones-fm' is running.
    Update success for 10.20.3.14
    Update success for 10.20.3.16
    Ignore below Error if Installing Agent via docker installer
    
    ones-fm container is not running
    
    Operation = uninstall
    ##### params = {'ip': '10.20.3.14', 'passwd': 'YourPaSsWoRd', 'user': 'admin', 'server_ip': '172.17.0.2', 'fm_port': None} #####
    ###############Connecting to switch###############
    ##### params = {'ip': '10.20.3.16', 'passwd': 'YourPaSsWoRd', 'user': 'admin', 'server_ip': '172.17.0.2', 'fm_port': None} #####
    ###############Connecting to switch###############
    <paramiko.client.SSHClient object at 0x73c327c662b0>
    Connection to switch 10.20.3.14 successfull.....................
    /home/ones_fm_agent
    ############### Uninstalling FM Agent ###############
    <paramiko.client.SSHClient object at 0x73c327c66670>
    Connection to switch 10.20.3.16 successfull.....................
    /home/ones_fm_agent
    ############### Uninstalling FM Agent ###############
    FMCLI uninstall Result
    {'10.20.3.14': 'PASS', '10.20.3.16': 'PASS'}
    ╒═════════╤════════════╤════════════════════╕
    │   SL.No │ Device     │ uninstall Result   │
    ╞═════════╪════════════╪════════════════════╡
    │       1 │ 10.20.3.14 │ PASS               │
    ├─────────┼────────────┼────────────────────┤
    │       2 │ 10.20.3.16 │ PASS               │
    ╘═════════╧════════════╧════════════════════╛
    agent_installer
    Docker agent_installer has been stopped
    agent_installer
    Docker agent_installer has been removed
    Untagged: avizdock/agent_installer:latest
    Deleted: sha256:180765aed1eba26b8d30d3bef983682a2b36a3507b7655c6e614f22dbbf80007
    Deleted: sha256:7912382f54799a2f35358528c441af6bb745ba6fe6cb040a7be48347ff7e80a3
    Deleted: sha256:fe33139b53a0b2b401d44f57a74ff789beb4a3a38792f80a793cc01611bab9e7
    Deleted: sha256:38e2eba240dfe04c6d027aafc1954c84fc1eadeb3e4fd9d1e9a8ad7100686d7f
    Deleted: sha256:53fdc4ec83b42d7060b4143da9ffbf9dd55e3bfa6fb4843bfacec19dcbd80e4b
    Deleted: sha256:11b1633cb703032b065434387b48194f3e97a57aaddc61a31aa2918a1fd32780
    Deleted: sha256:aa353210edce17d0370066fc6184cff9e2a9197884e6f43a0ad1fd32b630f8de
    Deleted: sha256:b23b2f4af61d8cc745c6bea66be93bd59b97c3971c36466ae4ea345f52fdfc67
    Deleted: sha256:b55ff4d1eb4dd15edbc9ffc15b1bd5771cd09c371b0e7c44cbcbd5c5f62ec76a
    Deleted: sha256:e2ef8a51359d088511d34c725305c220294a1fcd5fe5e5dbe4d698c7239ce2c9
    Docker avizdock/agent_installer:latest image has been removed
    
    switch# show run grpc
    !Command: show running-config grpc
    !Running configuration last done at: Mon Jan 29 13:59:36 2024
    !Time: Mon Jan 29 14:06:27 2024
    version 9.3(9) Bios:version 04.18
    feature grpc
    grpc use-vrf default
    switch# show grpc gnmi service statistics
    =============
    gRPC Endpoint
    =============
    Vrf            : management
    Server address : [::]:50051
    Status         : Running - certificate expired
    Cert notBefore : Jan 10 07:07:03 2024 GMT
    Cert notAfter  : Jan 11 07:07:03 2024 GMT
    Max concurrent calls            :  8
    Listen calls                    :  1
    Active calls                    :  0
    Number of created calls         :  32
    Number of bad calls             :  29
    Subscription stream/once/poll   :  15/0/0
    Max gNMI::Get concurrent        :  5
    Max grpc message size           :  8388608
    gNMI Synchronous calls          :  20496
    gNMI Synchronous errors         :  0
    gNMI Adapter errors             :  0
    gNMI Dtx errors                 :  0
    =============
    gRPC Endpoint
    =============
    Vrf            : default
    Server address : [::]:50051
    Status         : Running - certificate expired
    Cert notBefore : Jan 10 07:07:03 2024 GMT
    Cert notAfter  : Jan 11 07:07:03 2024 GMT
    Max concurrent calls            :  8
    Listen calls                    :  1
    Active calls                    :  0
    Number of created calls         :  1
    Number of bad calls             :  0
    Subscription stream/once/poll   :  0/0/0
    Max gNMI::Get concurrent        :  5
    Max grpc message size           :  8388608
    gNMI Synchronous calls          :  0
    gNMI Synchronous errors         :  0
    gNMI Adapter errors             :  0
    gNMI Dtx errors                 :  0
    
    switch# show grpc gnmi rpc summary
    =============
    gRPC Endpoint
    =============
    Vrf            : management
    Server address : [::]:50051
    Status         : Running - certificate expired
    Cert notBefore : Jan 10 07:07:03 2024 GMT
    Cert notAfter  : Jan 11 07:07:03 2024 GMT
    Capability rpcs    : 20474
    Capability errors  : 0
    Get rpcs           : 22
    Get errors         : 0
    Set rpcs           : 0
    Set errors         : 0
    Resource Exhausted : 0
    Option Unsupported : 0
    Invalid Argument   : 0
    Operation Aborted  : 0
    Internal Error     : 0
    Unknown Error      : 0
    RPC Type        State      Last Activity  Cnt Req    Cnt Resp   Client
    --------------- ---------- -------------- ---------- ---------- ----------------------------------------
    Subscribe       Listen     01/29 08:42:41          0          0
    =============
    gRPC Endpoint
    =============
    Vrf            : default
    Server address : [::]:50051
    Status         : Running - certificate expired
    Cert notBefore : Jan 10 07:07:03 2024 GMT
    Cert notAfter  : Jan 11 07:07:03 2024 GMT
    Capability rpcs    : 0
    Capability errors  : 0
    Get rpcs           : 0
    Get errors         : 0
    Set rpcs           : 0
    Set errors         : 0
    Resource Exhausted : 0
    Option Unsupported : 0
    Invalid Argument   : 0
    Operation Aborted  : 0
    Internal Error     : 0
    Unknown Error      : 0
    RPC Type        State      Last Activity  Cnt Req    Cnt Resp   Client
    --------------- ---------- -------------- ---------- ---------- ----------------------------------------
    Subscribe       Listen     01/10 08:12:32          0          0
    switch#
    switch# show grpc gnmi transactions
    =============
    gRPC Endpoint
    =============
    Vrf            : management
    Server address : [::]:50051
    Status         : Running - certificate expired
    Cert notBefore : Jan 10 07:07:03 2024 GMT
    Cert notAfter  : Jan 11 07:07:03 2024 GMT
    RPC          DataType   Session         Time In              Duration(ms) Status
    ------------ ---------- --------------- -------------------- ------------ ------
    Capabilities -          0               01/29 12:04:07       0            0
    Capabilities -          0               01/29 12:03:47       0            0
    Capabilities -          0               01/29 12:03:35       0            0
    Get          ALL        3698131864      01/29 08:43:34       1186         0
    ...
    ...
    ...
    
    switch# show telemetry yang direct-path cisco-nxos-device
    1) Cisco-NX-OS-device:System/lldp-items
    2) Cisco-NX-OS-device:System/mac-items
    3) Cisco-NX-OS-device:System/intf-items
    4) Cisco-NX-OS-device:System/procsys-items
    5) Cisco-NX-OS-device:System/ipqos-items/queuing-items/policy-items/out-items
    6) Cisco-NX-OS-device:System/ch-items

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

  • Enable or disable the ONE DL feature

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

    2. User can choose No if need not to enable ONES DataLake feature

  • 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

  • Update/Change your password on the first login

    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

  • https://support.aviznetworks.com

    Region

  • type

  • groupid

  • azid

  • brickid

  • rackid

  • Supported Platform details
    Device
    GPU
    GPU VENDOR ID
    GPU DEVICE ID
    NIC VENDOR ID

    Device

    GPU

    GPU VENDOR ID

    GPU DEVICE ID

    NIC VENDOR ID

    Intel Gaudi

    GAUDI2

    HABANALABS (0x1DA3)

    GAUDI2 (1020)

    HABANALABS (0x1da3)

    1. ONESv3.0 Agent support auto-discovery feature

    2. ONESv3.0 Agent support to send telemetry on multiple controllers (Max 2)

    3. Restrict IP feature can be enabled/disabled

    4. Password-based authentication is supported

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

    6. 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 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_server_agent:~$ ./ones_agent_parallel_installer.sh

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

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

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

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

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

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

    root@ones:~$ tar -xvf ones-multisite-v3.0.0.tar.bz2
    • 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

    • Load the ONES Multisite docker images

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

    • Run Docker service for ONES-Multisite Application

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

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

    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

    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

    Verification eAPI

    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

    1. CPU and Memory Alerts

    Login Page

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

    https://<host-ip/FQDN>

    Use default credentials to login, refer page for default credentials

    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...
    
    
    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>
    Do you want to enable ONE-DL feature? [y/n]: n
    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
    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 
    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 
    
    Enter the ONES App URL: https://192.168.1.1
    Enter the ONES App URL: https://ones.aviznetworks.com
    Do you want to enable agent authentication ? [y/n]: y
    Enter the ones-agent username: admin
    Enter the ones-agent password: YourPaSsWoRd
    Do you want to enable agent authentication ? [y/n]: n
    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
    
    docker cp ones-collector-db:/home/postgres/pgdata/data/postgresql.conf dbconfig.conf
    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
    #------------------------------------------------------------------------------
    docker cp dbconfig.conf ones-collector-db:/home/postgres/pgdata/data/postgresql.conf 
    docker restart ones-collector-db
    ip,user,passwd,layer,region,type,groupid,azid,brickid,rackid
    "10.20.2.12","admin","YourPaSsWoRd","Spine","San_Jose_Lab","sonic",1,1,1,1
    ...
    ...
    ...
    Does the ONES-agent is integrated with SONiC NOS? (yes/no): no
    Do you want to add only Collector IP for auto-discovery and skip the agent installation ?(yes/no): no 
    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
    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
    Do you want to enable password authentication? (yes/no): yes
    Enter the new username: admin
    Enter the new password: YourPaSsWoRd
    Do you want to update the username/password for password authentication? (yes/no): no
    Does the ONES-agent is integrated with SONiC NOS? (yes/no): no
    Do you want to add only Collector IP for auto-discovery and skip the agent installation? (yes/no): no
    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.20.0.87
    Do you want to restrict access only to the provided collector IP?
    Note: Providing Yes will restrict access to agent only with the provided collector IP Address
    Enter yes/no: Yes
    Do you want to enable password authentication? (yes/no): yes
    Enter the new username: admin
    Enter the new password: YourPaSsWoRd
    e2ef8a51359d: Loading layer [==================================================>]  72.54MB/72.54MB
    ae2d55769c5e: Loading layer [==================================================>]  7.401MB/7.401MB
    3054512b6f71: Loading layer [==================================================>]  31.35MB/31.35MB
    997b8e79e84f: Loading layer [==================================================>]   5.12kB/5.12kB
    e6c5004ee77f: Loading layer [==================================================>]   11.7MB/11.7MB
    867f2af1b281: Loading layer [==================================================>]   2.56kB/2.56kB
    86fee8a2d43f: Loading layer [==================================================>]  31.45MB/31.45MB
    4a2339f45f2a: Loading layer [==================================================>]   42.7MB/42.7MB
    274d02d0f011: Loading layer [==================================================>]  1.421MB/1.421MB
    Loaded image: avizdock/agent_installer:latest
    Docker image 'avizdock/agent_installer' is loaded.
    06275757da6600fb25d31f1e4c195116d52729e0d80db1aa8064474c5e858ae5
    Docker container 'agent_installer' is running.
    Selecting ‘Yes’ will exclusively initiate the day-2 deployment of the Ones-Agent,
    involving a reconfiguration of the existing agent to establish communication with the specified collector(s).
    Choosing ‘No’ will initiate the deployment of the Ones-Agent as an independent third-party container.
    The default values for rackid, brickid, and azid are all set to 0.
    [{'ip': '10.20.2.12', 'user': 'admin', 'passwd': 'YourPaSsWoRd', 'layer': 'Leaf', 'region': 'San_Jose_Lab', 'type': 'Sonic', 'groupid': '', 'azid': '1', 'brickid': '1', 'rackid': '1', 'installation_instance': 1, 'agentip': '10.20.2.12', 'collectorip': '10.20.0.80', 'restrict_collector_ip': 'no', 'password_authentication': 'yes', 'username': 'admin', 'encpass': 'e08d855d42cc2e488592731e', 'enciv': '5b3e16bb25581d5e0934683617dbc445'}]
    ###############Connecting to switch###############
    Connection to switch 10.20.2.12 successful.....................
    Looking for previous installation........................
    avizdock/ones-agent:v3.0.0
    Previous installation found commencing uninstallation on the device 10.20.2.12........
    stop ones-agent docker on the device 10.20.2.12........
    docker stopped successfully on the device 10.20.2.12........
    remove ones-agent docker on the device 10.20.2.12........
    docker removed successfully on the device 10.20.2.12........
    remove redundant ones-agent docker container on the device 10.20.2.12........
    No redundant ones-agent container found on the device 10.20.2.12........
    remove docker ones-agent images from DUT on the device 10.20.2.12........
    docker image removed successfully on the device 10.20.2.12........
    Removing work directory on the device 10.20.2.12........
    removed work directory successfully on the device 10.20.2.12........
    #####ones-agent uninstalltion completed from device=########## 10.20.2.12
    
    Creating work directory  on the device 10.20.2.12........
    Work Directory ones-agent_1725877821_191873 created successfully on the device 10.20.2.12 .............
    Copying ones_agent_start.sh to directory ones-agent_1725877821_191873 on the device 10.20.2.12 .............
    Copying ones_agent_start.sh to directory ones-agent_1725877821_191873 successful on the device 10.20.2.12 .............
    ones_agent_start.sh file copied to /usr/bin successfully on the device 10.20.2.12........
    Copying ones_agent_ip_rule.sh to directory ones-agent_1725877821_191873 on the device 10.20.2.12 .............
    Copying ones_agent_ip_rule.sh to directory ones-agent_1725877821_191873 successful on the device 10.20.2.12 .............
    ones_agent_ip_rule.sh file copied to /usr/bin successfully on the device 10.20.2.12........
    Copying ones-agent.service to directory ones-agent_1725877821_191873 on the device 10.20.2.12 .............
    Copying ones-agent.service to directory ones-agent_1725877821_191873 successful on the device 10.20.2.12 .............
    
    Installation proceeding with NoTls mode
    Copying agent.conf to directory ones-agent_1725877821_191873 successful on the device 10.20.2.12 .............
    agent.conf copied to /etc/sonic successfully on the device 10.20.2.12........
    Copying ones-agent.tar to directory ones-agent_1725877821_191873 on the device 10.20.2.12 .............
    Copying ones-agent.tar to directory ones-agent_1725877821_191873 on the device 10.20.2.12 .............
    Loading Docker image on the device 10.20.2.12 ###########################################
    Docker image loaded successfully on the device 10.20.2.12........
    Getting name of the loaded image
    image = ##avizdock/ones-agent:v3.0.0##
    Running docker.....................
    docker run -it -v /var/run/docker.sock:/var/run/docker.sock -v /host/reboot-cause:/host/reboot-cause -v /etc/sonic:/etc/sonic -v /var/run/redis:/var/run/redis -v /var/run:/var/hostrun --log-driver local --log-opt max-size=5m --log-opt max-file=3 --cpu-period=100000 --cpu-quota=50000 --net=host --privileged -dt --name ones-agent avizdock/ones-agent:v3.0.0
    b'969e2e65db674b594c7ced6f789b2b44ef7a8b556d28499a90c94ba4125b5c00\n'
    Loading Service file on the device 10.20.2.12........
    Service file loaded successfully on the device 10.20.2.12##################
    Enabling ones-agent.service 10.20.2.12 ##################
    Enabled ones-agent as service successfully on the device 10.20.2.12 ##################
    Starting ones-agent service on the device 10.20.2.12........
    Made ones-agent immune to booting on the device 10.20.2.12########################
    Copying ones-agent.tar file
    ones-agent.tar file copied successfully on the device 10.20.2.12........
    Copying agent.conf file
    agent.conf file copied successfully on the device 10.20.2.12........
    Copying ones-agent.service file
    ones-agent.service file copied successfully on the device 10.20.2.12........
    Copying ones_agent_ip_rule.sh file
    ones_agent_ip_rule.sh file copied successfully on the device 10.20.2.12........
    Copying ones_agent_start.sh file
    ones_agent_start.sh file copied successfully on the device 10.20.2.12........
    ##################################################################
    Status of ones-agent.service is -      Active: active (running) since Mon 2024-09-09 16:03:52 IST; 1min 35s ago
    
    removing backup files
    removed backup directory successfully on the device 10.20.2.12........
    Deployment of ones-agent to switch 10.20.2.12 is successful
    ╒══════════════╤══════════╕
    │ IP Address   │ Result   │
    ╞══════════════╪══════════╡
    │ 10.20.2.12   │ Pass     │
    ╘══════════════╧══════════╛
    agent_installer
    
    Docker agent_installer has been stopped
    agent_installer
    
    Docker agent_installer has been removed
    Untagged: avizdock/agent_installer:latest
    Deleted: sha256:180765aed1eba26b8d30d3bef983682a2b36a3507b7655c6e614f22dbbf80007
    Deleted: sha256:7912382f54799a2f35358528c441af6bb745ba6fe6cb040a7be48347ff7e80a3
    Deleted: sha256:fe33139b53a0b2b401d44f57a74ff789beb4a3a38792f80a793cc01611bab9e7
    Deleted: sha256:38e2eba240dfe04c6d027aafc1954c84fc1eadeb3e4fd9d1e9a8ad7100686d7f
    Deleted: sha256:53fdc4ec83b42d7060b4143da9ffbf9dd55e3bfa6fb4843bfacec19dcbd80e4b
    Deleted: sha256:11b1633cb703032b065434387b48194f3e97a57aaddc61a31aa2918a1fd32780
    Deleted: sha256:aa353210edce17d0370066fc6184cff9e2a9197884e6f43a0ad1fd32b630f8de
    Deleted: sha256:b23b2f4af61d8cc745c6bea66be93bd59b97c3971c36466ae4ea345f52fdfc67
    Deleted: sha256:b55ff4d1eb4dd15edbc9ffc15b1bd5771cd09c371b0e7c44cbcbd5c5f62ec76a
    Deleted: sha256:e2ef8a51359d088511d34c725305c220294a1fcd5fe5e5dbe4d698c7239ce2c9
    
    Docker avizdock/agent_installer image has been removed
    
    
    Do you want to enable password authentication? (yes/no): yes
    Enter the new username: admin
    Enter the new password: YourPaSsWoRd
    Do you want to enable password authentication? (yes/no): no
    ip,user,passwd,layer,region,type,groupid,azid,brickid,rackid
    "10.20.0.80","admin","YourPaSsWoRd","Server","San_Jose_Lab","Server",1,1,1,1
    ...
    ...
    ...
    Do you want to update the username/password for password authentication? (Yes/No): no
    Do you want to add only Collector IP for auto-discovery and skip the agent installation ?(yes/no): no 
    Enter the IP addresses of collectors to auto-discover (max 2, comma-separated, e.g., 10.1.1.10,10.2.2.5):10.20.0.93
    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
    Do you want to update the username/password for password authentication? (Yes/No): no
    Do you want to add only Collector IP for auto-discovery and skip the agent installation? (yes/no): no
    Enter the IP addresses of collectors to auto-discover (max 2, comma-separated, e.g., 10.1.1.10,10.2.2.5): 10.20.0.93
    Do you want to restrict access only to the provided collector IP?
    Note: Providing Yes will restrict access to agent only with the provided collector IP Address
    Enter Yes/No: no
    Do you want to enable password authentication? (Yes/No): no
    f58d795dfab9: Loading layer [==================================================>]   2.56kB/2.56kB
    ed46ea0f4e17: Loading layer [==================================================>]  31.74MB/31.74MB
    1c38a701a3d6: Loading layer [==================================================>]   42.7MB/42.7MB
    c4456c24c820: Loading layer [==================================================>]  1.421MB/1.421MB
    Loaded image: avizdock/agent_installer:latest
    Docker image 'avizdock/agent_installer' is loaded.
    b17757c75cda3c71ff4d1311c116c6143893726ddce7dead02b0d77cc926fc5c
    Docker container 'agent_installer' is running.
    /usr/local/lib/python3.8/site-packages/paramiko/pkey.py:82: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from this module in 48.0.0.
      "cipher": algorithms.TripleDES,
    /usr/local/lib/python3.8/site-packages/paramiko/transport.py:253: CryptographyDeprecationWarning: TripleDES has been moved to cryptography.hazmat.decrepit.ciphers.algorithms.TripleDES and will be removed from this module in 48.0.0.
      "class": algorithms.TripleDES,
    Selecting ‘Yes’ will exclusively initiate the day-2 deployment of the Ones-Agent,
    involving a reconfiguration of the existing agent to establish communication with the specified collector(s).
    Choosing ‘No’ will initiate the deployment of the Ones-Agent as an independent third-party container.
    [{'ip': '10.20.0.80', 'user': 'aviz', 'passwd': 'Aviz@123', 'layer': 'Server', 'region': 'San Jose', 'azid': '1', 'brickid': '1', 'rackid': '1', 'groupid': '8', 'type': 'Server', 'installation_instance': 1, 'agentip': '10.20.0.80', 'collectorip': '10.20.0.93', 'restrict_collector_ip': 'no', 'password_authentication': 'no'}]
    ###############Connecting to switch###############
    Connection to switch 10.20.0.80 successful.....................
    Looking for previous installation........................
    Copying files to the switch........................
    Verifying files on the remote switch........................
    File /home/aviz/docker_packages.tar.gz exists on the remote server.
    File /home/aviz/prerequisites.sh exists on the remote server.
    File verification completed.
    Untarring docker_packages.tar.gz on the remote server...
    Successfully untarred docker_packages.tar.gz.
    Setting execute permissions on prerequisites.sh...
    Successfully set execute permissions on prerequisites.sh.
    Executing prerequisites.sh on the remote server...
    
    ....................
    ....................
    ....................
    ....................
    ....................
    (Reading database ... 116661 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) ...
    No previous installation found  on the device 10.20.0.80........
    Creating work directory  on the device 10.20.0.80........
    Work Directory ones-agent_1727157788_9940367 created successfully on the device 10.20.0.80 .............
    Copying ones_agent_start.sh to directory ones-agent_1727157788_9940367 on the device 10.20.0.80 .............
    Copying ones_agent_start.sh to directory ones-agent_1727157788_9940367 successful on the device 10.20.0.80 .............
    ones_agent_start.sh file copied to /usr/bin successfully on the device 10.20.0.80........
    
    Copying ones_agent_ip_rule.sh to directory ones-agent_1727157788_9940367 on the device 10.20.0.80 .............
    Copying ones_agent_ip_rule.sh to directory ones-agent_1727157788_9940367 successful on the device 10.20.0.80 .............
    ones_agent_ip_rule.sh file copied to /usr/bin successfully on the device 10.20.0.80........
    Copying ones-agent.service to directory ones-agent_1727157788_9940367 on the device 10.20.0.80 .............
    Copying ones-agent.service to directory ones-agent_1727157788_9940367 successful on the device 10.20.0.80 .............
    
    Installation proceeding with NoTls mode
    Copying agent.conf to directory ones-agent_1727157788_9940367 successful on the device 10.20.0.80 .............
    agent.conf copied to /etc/ones successfully on the device 10.20.0.80........
    Copying ones-agent.tar to directory ones-agent_1727157788_9940367 on the device 10.20.0.80 .............
    Copying ones-agent.tar to directory ones-agent_1727157788_9940367 on the device 10.20.0.80 .............
    Loading Docker image on the device 10.20.0.80 ###########################################
    Docker image loaded successfully on the device 10.20.0.80........
    Getting name of the loaded image
    image = ##avizdock/ones-server-agent:v3.0.0##
    Running docker.....................
    docker run -it -v /usr/bin/hl-smi:/usr/bin/hl-smi -v /etc/ones:/etc/ones -v /etc/os-release:/etc/os-release-origin --cpu-period=100000 --cpu-quota=50000 --net=host --privileged -dt --name ones-agent avizdock/ones-server-agent:v3.0.0
    b'8435e8edc34c90c3d378a89769dc5167e020095818ede8178ac675c96d37ecd3\n'
    Service file loaded successfully on the device 10.20.0.80##################
    Enabling ones-agent.service 10.20.0.80 ##################
    Enabled ones-agent as service successfully on the device 10.20.0.80 ##################
    Starting ones-agent service on the device 10.20.0.80........
    Made ones-agent immune to booting on the device 10.20.0.80########################
    Copying ones-agent.tar file
    ones-agent.tar file copied successfully on the device 10.20.0.80........
    Copying agent.conf file
    agent.conf file copied successfully on the device 10.20.0.80........
    Copying ones-agent.service file
    ones-agent.service file copied successfully on the device 10.20.0.80........
    Copying ones_agent_ip_rule.sh file
    ones_agent_ip_rule.sh file copied successfully on the device 10.20.0.80........
    Copying ones_agent_start.sh file
    ones_agent_start.sh file copied successfully on the device 10.20.0.80........
    ##################################################################
    Status of ones-agent.service is -      Active: active (running) since Tue 2024-09-24 06:06:03 UTC; 2min 34s ago
    
    Deployment of ones-agent to switch 10.20.0.80 is successful
    ╒══════════════╤══════════╕
    │ IP Address   │ Result   │
    ╞══════════════╪══════════╡
    │ 10.20.0.80   │ Pass     │
    ╘══════════════╧══════════╛
    agent_installer
    
    Docker agent_installer has been stopped
    agent_installer
    
    Docker agent_installer has been removed
    Untagged: avizdock/agent_installer:latest
    Deleted: sha256:b115eb21a63518b47079a0f9b25ed56e8dd807a4aa054dc18efb1d5635b9728d
    Deleted: sha256:a2052350dbedd8d19d573f1f81a333af50d33c157dd565c6fb3ea19ff32d7869
    Deleted: sha256:403906165705c1c4c263865c7d2e8560424306ef76cc7dfd319565e1036a4b49
    Deleted: sha256:71d4c516421d0cd5b08b0c7f7ddff68182ca799815c621e1bf1d7c2a247820f2
    Deleted: sha256:ed5221ab4eb63334a3121c173d4b6e0fb882b13eb0de6f1daa781908da91a464
    
    Docker avizdock/agent_installer image has been removed
    
    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
    ones-multisite/
    ones-multisite/README.txt
    ones-multisite/docker-compose.yml
    ones-multisite/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

    Intel Gaudi

    GAUDI2_HL2000

    HABANALABS (0x1DA3)

    GAUDI2_HL2000 (1010)

    MELLANOX TECHNOLOGIES(0x15b3)

       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

    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

  • Push Notification

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

    1. Slack channel

    2. Zendesk Support ticket

    3. Service Now ticket

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

    Installing ONES Application

    Service Now Integration

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

    1. Integrations >> Ticketing >> ServiceNow

    1. Add Channel

      Inputs to sucessfully integrate ServiceNow

      1. Instance URL (from serviceNow developer Account)

      2. Credentials (from serviceNow developer Account)

    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

    Slack Channel Integration

    1. Create a Channel for ONES-App push notification

    2. Generate API for Channel

    login to api.slack.com & choose Your apps

    1. Create an App

    2. Choose From scratch

    3. Provide any App Name and choose the workspace where the user wants to get the push notification & Create App

    4. Choose Incoming Webhook and Activate Incoming Webhooks & Add New Worbhook to workspace

    5. Select the configured Channel & Allow

    6. Copy the newly created webhook link

    7. Open ONES-App and select Integration >> Messaging

    8. Add Channel & Paste the Webhook URL

    9. After saving it will be available to use while creating any rule using Rule Engine feature

    Zendesk Support Integration

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

    2. Open ONES-App and select Integration >> Ticketing

    3. Add Channel & Paste the required details

    4. After saving it will be available to use while creating any rule using Rule Engine feature

    Rules Type

    Rules Type

    There are two types of Rule a user can configure

    1. Entity Based

      1. Allow a user to create Rules per device

        1. Allow user to include or exclude the devices from the rule

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

    1. Rule Name: The user can choose any related name

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

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

    • Interface PFC Receive Counters

    Server: The user will be able to get alerts for IntelGaudy
    • CPU Core Temperature

    • CPU Utilization

    • Device Down

    1. Metrics: Metrics depend on the above (For: Device/Interface) condition

    2. Measure: Metrics are measured in three diff ways

      1. MIN

    Conditions

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

    Notification

    1. Notify: The user can choose the integrated SLACK Channel

    2. Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket

    3. Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket

    2. Entity by Property

    Possible Values & Description

    1. Rule Name: The user can choose any related name

    2. Filter: user can filter the rule for all managed devices by

      1. HWSKU

    Device: Once the user chooses the rule for Devices it will show the below Metrics
    • ASIC IPv4 Routes

    • ASIC IPv6 Routes

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

    • Interface PFC Counters

    1. Select: this option depends on the Filter category, possible values are

      1. Select HWSKU :

      2. Select ROLE :

    Conditions

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

    Notification

    1. Notify: The user can choose the integrated SLACK Channel

    2. Create Ticker: Zendesk Users can choose this to raise the Zendesk support ticket

    3. Create Ticker: ServiceNow Users can choose this to raise the ServiceNow support ticket

    Alerts

    Overview

    When a user creates a rule, and the threshold value is exceeded, alerts will be generated. These alerts will also be displayed on this page.

    Alerts

    Notifications from the Alerts Page are always sent to:

    [+] Running 2/2
     ⠿ Network ones-multisite_default  Created          0.1s
     ⠿ Container ones-multisite        Started          2.9s
    Utilization
    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 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

  • FAN Speed

  • GPU Memory Utilization

  • GPU PSU 1 Power Draw

  • GPU PSU 2 Power Draw

  • GPU Temperature

  • GPU Utilization

  • Memory Utilization

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

  • GE: Greater than Equal to
  • LE: Less than Equal to

  • GT: Greater than

  • 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

  • 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

  • ROLE
  • OS Version

  • For: The user can choose 2 options

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

  • GE: Greater than Equal to
  • LE: Less than Equal to

  • GT: Greater than

  • 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

  • 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

    • ServiceNow Support: Integrated ServiceNow Support will get all the alerts triggered by ONES.

    • Zendesk Support: Integrated Zendesk Support systems will receive all push notifications.

    • SLACK Channel: If integrated, notifications will also be sent to the configured SLACK channel.

    • Alert Page: It will always display the alerts on ONES Alert page

    At a time one single Support Ticket can work, While using Zendesk Support User wont be able to use ServiceNow Ticket Support

    Alert Management

    1. Count of alerts related to feature

    2. Alert Name

    3. First seen of the alert

    4. Last seen of the alert

    5. Option to delete the alerts

    Expand Option is used to check the payload and total alerts

    Time Scale Alert Updates

    Users can choose the time range to check the more alerts

    Alert Page allows a user to download the report in CSV format with a time range

    Enable the Service

    Analytics

    Hardware

    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.

    Feature
    Use

    Status of Switch

    • Not Streaming: The device is Inactive/Unreachable

    • Streaming: The device is in a Working state

    • Non-Licensed: The device is added out of licensed devices

    Regions

    Status of Regions, their Location and Device Mappings

    Switch SKUs

    Switch Hardware Vendor, Model Number and SKU

    ASICs

    ASIC Vendor, Model and Hardware version details

    Roles

    Device Roles in Customer Environment

    • Super-Spine

    • Spine

    • Leaf

    • 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

    Feature
    Use

    PSUs

    Shows the list of

    • all faulty Power Supplies across managed switches

    • LED status of managed switches

    Fans

    Show the list of

    • all faulty fans across managed switches

    • airflow direction of faulty fans for troubleshooting

    Transceivers Temperature

    Temperature readings and alerts for Optics

    Transceivers Voltage

    Voltage readings and alerts for Optics

    Interfaces

    • Navigate to Dashboard >> Interfaces

    Feature
    Use

    Interfaces

    • Total number of ports available across devices

    • Status of Up interfaces across devices

    • Unused interfaces across the devices

    Cabling

    • Total number of cables used across devices

    • Cable type used across device

      • Fiber

    Interface Down

    • Information on Down Interfaces

    • Agent Status of a Device for a Down

    • Interface Historical Flaps starting with 5, 15, 30 minutes and 1 hours interval

    • Provides two types of Status:

    • 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

    Software

    • Navigate to Dashboard >> Software

    Feature
    Use

    Telemetry Agent version

    • version across all managed switches

    • distribution of Agent-based vs Agent-less switches

    • Device Status (Up/Down) based on Distro

    Orchestrator Agent version

    • version across all managed switches

    • Agent Health - Up and Down

    Network OS

    • NOS status and version across all managed switches

    • Distribution based on NOS versions

    • Device Status (Up/Down) based on NOS versions

    Firmware Version

    • This widget shows the BIOS & ONIE version running on all managed devices

    Linux Distro

    • version across all managed switches

    • Distribution based on Linux Distros

    • Devices Status (Up/Down) based on Linux Distro

    Devices

    ToR
    Copper
  • Count of cables required for unused ports

    • Device Name with interface details

    • At what time the interface went down

    Accounts

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

    "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

    • 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

    Roles - Add User Roles

    • Navigate to Accounts >> Roles

    • Now let's add few extra permissions

      • Add/Remove Devices

    After giving permissions, the user can be added to this role in the user section.

  • 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

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

    Vendor Staff

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

  • Configure Devices