ONES Server Agent Installation

Server Agent v3.0 support:

Only Intel Guadi platform is supported in ONESv3.0

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)

Intel Gaudi

GAUDI2_HL2000

HABANALABS (0x1DA3)

GAUDI2_HL2000 (1010)

MELLANOX TECHNOLOGIES(0x15b3)

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

PreviousONES Telemetry Agent InstallationNextONES Orchestration Agent Installation