ONES GA-2.1
Release
  • ONES GA v2.1
    • 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 Supportability
        • ONES Security
    • What's new?
    • Getting Started
      • Supported Switch Platforms and NOS
      • Scalability
      • Subscription
      • ONES Installation
        • Installation Pre-requisites
        • Download ONES Package
        • Installing ONES Application
        • ONE-DL cloud Deployment
        • Installing ONES Agents 2.1
          • ONES Telemetry Agent Installation
          • ONES Orchestration Agent Installation
          • Agent Less Telemetry
            • Cumulus(NVUE API)
            • Arista EOS (OpenConfig)
            • CISCO NXOS (GRPC)
        • Adding New Controller
      • VM Deployment
        • VMware ONES Deployment
        • KVM ONES Deployment
        • Upgrade VM
    • ONES Web GUI Administration
      • Login Page
      • Adding Devices
      • Monitor
      • Inventory
        • Devices
        • Configurations
      • Rule Engine
        • Slack Channel Integration
        • Zendesk Support Integration
        • Rules Type
          • Add Rules: Entity
          • Add Rules: Entity by Properties
        • Alerts
      • Analytics
      • Settings
      • Integrations
        • Slack Channel Integration
        • Zendesk Support Integration
        • Cloud Services
          • Splunk
          • Amazon S3
      • Accounts
      • ONES Orchestration
        • 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-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
    • Common Issues and Troubleshooting Steps
      • ONES Installation
        • Storage issue
      • ONES Uninstallation
        • ONES-Application
        • Telemetry Agent
        • Orchestration Agent
      • Permission Issues
        • Application Installation
      • gNMI Troubleshooting on non-SONiC Switches
    • How to contact Aviz Networks Support?
    • Backup and Recovery
Powered by GitBook
On this page
  • Overview
  • Update controller IP without installing agent
Export as PDF
  1. ONES GA v2.1
  2. Getting Started
  3. ONES Installation

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.

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

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.4.5.254
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: No
468025bd9c12: Loading layer [==================================================>]   2.56kB/2.56kB
1961412d5783: Loading layer [==================================================>]  36.56MB/36.56MB
de3513fa22d1: Loading layer [==================================================>]  42.69MB/42.69MB
ca3343e443b5: Loading layer [==================================================>]  1.421MB/1.421MB
Loaded image: avizdock/agent_installer:latest
Docker image 'avizdock/agent_installer:latest' is loaded.
6466655d5e7dc2631ea51df49e41d75661547603aaa0ddd4615778170fa33a70
Docker container 'agent_installer' is running.
CONTAINER ID   IMAGE                             COMMAND     CREATED        STATUS                  PORTS     NAMES
6466655d5e7d   avizdock/agent_installer:latest   "python3"   1 second ago   Up Less than a second             agent_installer
10.4.5.254
no
no
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.4.4.61', 'user': 'admin', 'passwd': 'YourPaSsWoRd', 'layer': 'Leaf', 'region': 'Nyk', 'azid': '1', 'brickid': '1', 'rackid': '1', 'installation_instance': 1, 'agentip': '10.4.4.61', 'collectorip': '10.4.5.254', 'restrict_collector_ip': 'no'}]

Agent installation skipped successfully........
Adding Collector IP for auto-discovery...........
###############Connecting to switch###############
Connection to switch 10.4.4.61 successful.....................
...
...
...
Docker agent_installer has been stopped
agent_installer

Docker agent_installer has been removed
Untagged: avizdock/agent_installer:latest
Deleted: sha256:6604bbec1feedd9169ea6cca598650bf2f1fe659ae587e9637f80adabe877eeb
Deleted: sha256:4754441bc1128ca32bd0085e2a366e111b4882359cdebc92560d243a671f33e3
Deleted: sha256:c803c23f2ec84e2601fa5e5d954b1cbf406167ae057d7200e9d2f61ba1f402fa
Deleted: sha256:f9279b9fbc87fee822c69ea9cacc2f9d9a10d9c54bbc21732205684ea3bcf0b1
Deleted: sha256:27ea50b3cb2914caa5f99e5268ba0b47e15fb7c490275f560c54e400162e2cc3

Docker  image has been removed

Upon upgrading the Controller IP, it will automatically register with the new ONES

PreviousCISCO NXOS (GRPC)NextVM Deployment