ONES Telemetry Agent Installation
ONES Agent v2.1 support Agent Auto discovery
ONESv2.1 Agent support auto-discovery feature
ONESv2.1 Agent support to send telemetry on multiple controllers (Max 2)
Restrict IP feature can be enabled/disabled
Only Collector upgrade after Deployment is possible now
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
Need to add a few inputs while installing the agent
Controller IP //To restrict the telemetry streaming
Device Credentials
Layer
Region
azid
brickid
rackid
Installation
On the Application machine, go to ONES-2.1/ones_t_agent folder
root@ones-application:~$ cd /ONES-2.1/ones_t_agent
Installation (Agent Install on multiple switches at the same time)
Enter device details (Management IP, Username and Password ) in device_info.csv
root@ones-application/ONES-2.1/ones_t_agent:~$ vi device_info.csv
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.
root@ones-application/ONES-2.1/ones_t_agent:~$ ./ones_agent_parallel_installer.sh
Users can use ONES-Agent as an integrated service in SONiC OS or can use it as an independent third-party container.
Users can choose this option to only update one more controller IP without doing the complete agent installation.
Scripts asks to put the Controller IP to use auto-discovery feature
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.
Installation Begin
The user needs to make sure, The devices have a unique name, otherwise, there will issue while plotting the full topology view(Topology Page).
