AVIZ Networks
HomeRelease
  • Open Networking Enterprise Suite (ONES)
    • ONES Application
      • ONES Telemetry Collector(s) and Visibility
      • ONES Time Scale Metric Calculation
      • ONES Rule Engine
      • ONES Orchestration
      • ONE DL
      • ONES AVIZ Support
      • ONES Security
      • ONES Multisite
    • Licensing
  • What's new?
  • Getting Started
    • Supported Switch Platforms and NOS
    • Scalability
    • Subscription
    • ONES Installation
      • Installation Pre-requisites
      • Download ONES Package
      • Installing ONES Application
      • Upgrade ONES Application
      • ONE-DL cloud Deployment
      • Installing ONES Agents 3.1.0
        • ONES Telemetry Agent Installation
        • ONES Server Agent Installation
        • ONES Orchestration Agent Installation
        • Agent Less Telemetry
          • Cumulus(NVUE API)
          • Arista EOS (eAPI)
          • CISCO NXOS (GRPC)
      • Adding New Controller
      • Installing ONES Multisite
    • VM Deployment
      • VMware ONES Deployment
      • KVM ONES Deployment
      • Upgrade VM
  • ONES Web GUI Administration
    • Login Page
    • Adding Devices
    • AI Asistance
    • Monitor
    • Inventory
      • Devices
      • Configurations
        • YAML Based Configuration
          • VXLAN-Symmetric
            • VXLAN-Symmetric-SAG-no-mclag-vrf
            • VXLAN-Symmetric-SAG-mclag-vrf
            • VXLAN-Symmetric-SVI-no-mclag-vrf
            • VXLAN-Symmetric-SVI-mclag-vrf
            • VXLAN-Symmetric-SAG-vrf-RoCE
          • VXLAN-SVI
            • VXLAN-SVI-no-mclag-IPv6-eBGP-IPv6-SVI
            • VXLAN-SVI-no-mclag-iBGP-IPv4-Underlay
            • VXLAN-SVI-no-mclag-eBGP-IPv6-SAG
            • VXLAN-SVI-no-mclag-eBGP-IPv4-Underlay
            • VXLAN-svi-no-mclag-eBGP-BGPU-Underlay
          • VXLAN-SAG
            • VXLAN-SAG-no-mclag-iBGP-no-host
            • VXLAN-SAG-no-mclag-iBGP-BGPU-Underlay
            • VXLAN-SAG-no-mclag-iBGP-BGPU-Underlay-HostPO
            • VXLAN-SAG-no-mclag-ebgp-no-host
          • VXLAN-MGLAG
            • VXLAN-MCLAG-ibgp-sag
            • VXLAN-MCLAG-ebgp-svi.yaml
            • VXLAN-MCLAG-ipv6-ibgp-sag
            • VXLAN-MCLAG-ebgp-BGPU-IPv6SAG
            • VXLAN-MCLAG-ibgp-BGPU-IPv6svi
            • VXLAN-MCLAG-ipv4-ibgp-svi
            • VXLAN-MCLAG-ipv6-ebgp-sag
          • VXLAN-Asymmetric
            • VXLAN-Asymmetric-SAG-no-mclag
            • VXLAN-Asymmetric-SAG-mclag
            • VXLAN-Asymmetric-SVI-no-mclag
            • VXLAN-Asymmetric-SVI-mclag
          • MH-VXLAN
            • MH-VXLAN-ibgp-sag
            • MH-VXLAN-ipv6-ibgp-sag
            • MH-VXLAN-Asymmetric-SAG
            • MH-VXLAN-ebgp-BGPU-IPv6SAG
            • MH-VXLAN-ipv6-ebgp-sag
            • MH-VXLAN-Symmetric-2-SAG-vrf
          • MCLAG
            • MCLAG-IPv4-SVI-AccessHosts
            • MCLAG-ibgp-BGPU-Underlay-IPv4SVI-AccessHosts
            • MCLAG-ibgp-IPv6-Underlay-IPv6SVI-AccessHosts
            • MCLAG-IPv4-Underlay-IPv6SVI-AccessHosts
            • MCLAG-IPv6-Underlay-IPv6SVI-AccessHosts
          • L3-MCLAG
            • L3-MCLAG
            • L3-MCLAG-bgpU-combinedLink
            • L3-MCLAG-bgp-combinedLink
          • L2-LS
            • L2LS-EC-L2
            • L2LS-EC-L3-ipv4
            • L2LS-EC-L3-ipv6
          • iBGP
            • i-BGP-IPv6-CLOS-IPv6-host
            • i-BGP-IPv6-CLOS-IPv4-svi
            • i-BGP-IPv4-CLOS-L2PO-host
            • i-BGP-IPv4-CLOS-L2-host
            • i-BGP-IPv4-CLOS-IPv6-svi
            • i-BGP-IPv4-CLOS-IPv4-PO-host
            • i-BGP-BGP-U-CLOS-IPv4-svi
            • i-BGP-BGP-U-CLOS-IPv4-host
          • e-BGP
            • e-BGP-IPv6-CLOS-IPv6-host
            • e-BGP-IPv6-CLOS-IPv4-svi
            • e-BGP-IPv4-CLOS-L2-host
            • e-BGP-IPv4-CLOS-IPv6-svi
            • e-BGP-BGP-U-CLOS-IPv6-svi
            • e-BGP-BGP-U-CLOS-IPv6-host
          • BGP-PO
            • BGP-PO-SLFOW-LeafOnly-EC
            • BGP-PO-SLFOW-LeafOnly-EC-incr1
            • BGP-PO-MCLAG-SLFOW-LeafOnly-EC
          • LeafOnly-EC
          • IPCLOS-1-IPv4-SVI-AccessHosts
          • DHCP-IPCLOS-IPv4-SVI-AccessHosts
          • VXLAN-Symmetric-SAG-vrf-RoCE
        • GUI Based Configuration
        • NetOps Based Configuration
    • Rule Engine
      • Rules Type
        • Add Rules: Entity
        • Add Rules: Entity by Properties
      • Alerts
    • Analytics
    • Settings
    • Integrations
      • Slack Channel Integration
      • Zendesk Support Integration
      • Service Now Integration
      • Cloud Services
        • Splunk
        • Amazon S3
    • Accounts
  • Support
    • How to contact Aviz Networks Support?
    • Backup and Recovery
Powered by GitBook

Copyright © Aviz Networks, Inc.

On this page
  • ONES YAML Based Configuration
  • YAML Config Illustrator
  • ONES-UI Based Configuration
  • Config Status (Available in YAML & UI Based configuration)
  • Admin Features: (Available in YAML & UI Based configuration)
  • Connect
  • Console Logs
  • Config
  • NetOps
  • Compare Configuration
  • Backup & Configuration

Was this helpful?

  1. ONES Web GUI Administration
  2. Inventory

Configurations

PreviousDevicesNextYAML Based Configuration

Last updated 1 month ago

Was this helpful?

ONES YAML Based Configuration

Navigate to Configurations >> Configure >> YAML

  • Allows you to configure new devices

  • Supports valid YAML files

  • You can download the sample YAML file, edit it, and upload it again with the desired configuration

YAML Config Illustrator

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

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

ONES-UI Based Configuration

Navigate to Configurations >> Configure >> GUI

This option can be used in case user wants to bring a very basic topology with Vlan, SVI, BGP and few more configuration

Config Status (Available in YAML & UI Based configuration)

  • Device configuration is not yet started

  • In case of the user has not applied any feature like (VXLAN, MCLAG and so on..)

Device configuration is in progress

The device configuration has failed. Move the cursor to the failed option to see the Error message.

Device configuration is completed successfully

is used to configure or modify a configuration when we need to add several other devices with the same file

Backup & Restore Configs: using this user can take device config backup and can use later to restore the configuration

Admin Features: (Available in YAML & UI Based configuration)

Sub Options
Details

Allow user to connect via SSH and Console

Allow user to collect the console logs

Used to get the view of Config Intent and Applied Config and user can copy the complete config

Allow user to Manually modify and apply specific configurations directly from the UI

Allow users to Compare device configurations or track changes using backups from different timestamps

Connect

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

Navigate >> Configurations >> Devices >> Connect

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

Console Logs

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

Navigate >> Configurations >> Devices >> Console Logs

  • Click on the Console Log of the device

Config

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

Navigate >> Configurations >> Devices >> Config

  • Click on Config

NetOps

This section can be used to do manual config, instead of complete infra config, user can do individual changes per device

Navigate >> Configurations >> Devices >> NetOps

Compare Configuration

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

Navigate >> Configurations >> Devices >> Compare Configs

  • Compare Config

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

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

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

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

Backup & Configuration

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

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

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

Taking a Backup

  • Select Backup & Restore Configs

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

  • Submit the task

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

Restoring a Backup

  • Select Backup & Restore Configs

  • Select Restore Config

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

  • Select the backup a user wants to restore from the Backups Available list

  • Then Submit the backup & Click on Yes to confirm

NOTE: Follow theto know more about configuration and all the possible use cases.

​​

​​

​​

​​

​​

ONES Configuration
It will open in new window