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
  • 1. Add Devices using YAML
  • Device Type
  • 2. Add devices using CSV

Was this helpful?

  1. ONES Web GUI Administration

Adding Devices

PreviousLogin PageNextAI Asistance

Last updated 2 months ago

Was this helpful?

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

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

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

    • Navigate to Inventory

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

    1. Add Devices using the YAML Editor

    2. Upload the CSV file containing the device list

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

1. Add Devices using YAML

  • Click on Add Devices

  • Upload Device Inventory using YAML Editor

  • Navigate to Inventory >> Devices >> Add Devices >> Use YAML

  • Use the below format to add devices to the application

To Identify the device type user needs to mention the platform

Device Type

  1. Cumulus: cumulus

  2. Arista: arista

  3. Cisco: cisco-nxos

  4. SONiC: sonic

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

 inventory:
     - ipAddress: "10.4.4.61"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "cumulus"
       groupid: 1
     - ipAddress: "10.4.4.62"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "arista"
       groupid: 1
     - ipAddress: "10.4.4.63"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: cisco-nxos
       groupid: 1
     - ipAddress: "10.4.4.64"
       layer: "Spine"
       region: "San Jose"
       azId: 1
       brickId: 1
       user: "admin"
       password: "YourPaSsWoRd"
       type: "sonic"
       groupid: 1
  • Make sure to use the correct indentation for the YAML files

  • Click Save & Apply

  • ONES Application is now ready to manage the added devices

2. Add devices using CSV

  • Click on Add Devices

  • Upload Device Inventory using CSV File

  • Navigate to Inventory >> Devices >> Add Devices >> Use CSV

  • Use the below format to add devices to the application

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

  • Upload & Add