Getting Started with Paragon Automation
This section describes the high-level steps that you can perform after logging in to the Paragon Automation GUI.
To get started with Paragon Pathfinder:
- Onboard your devices.
Select Configuration > Devices. On the Device page, click Add Device (+).
- Configure Path Computation Element Protocol (PCEP) for
each device either by using the GUI or through the CLI.
If you are using the GUI, on the Devices page, select the device that you have onboarded and click the Edit icon. Modify the fields in the Protocols > PCEP section.
- Enable NETCONF for each device.
On the Device page, select the device that you onboarded and click the Edit icon. Enable the toggle button in the Protocols > Netconf section.
Note Ensure that you configure BGP-Link State (BGP-LS), and Junos telemetry tnterface (JTI) for the devices.
- Add your devices to the controller device group.
- Run device collection.
If you want to test telemetry use cases, you can set the JTI System ID and ensure that it matches the settings on the device. To save time, you can create a configuration template and push these configurations to the device. For example:
set services analytics streaming-server hb remote-address {{Paragon_web_UI_IP}}} set services analytics streaming-server hb remote-port 4000 set services analytics export-profile ns local-address {{System_ID}}} set services analytics export-profile ns local-port 4001 set services analytics export-profile ns reporting-rate 30 set services analytics export-profile ns format gpb set services analytics export-profile ns transport udp set services analytics sensor ifd server-name hb set services analytics sensor ifd export-name ns set services analytics sensor ifd resource /junos/system/linecard/interface/ set services analytics sensor ifd export-to-routing-engine set services analytics sensor ifl server-name hb set services analytics sensor ifl export-name ns set services analytics sensor ifl resource /junos/system/linecard/interface/logical/usage/ set services analytics sensor ifl export-to-routing-engine set services analytics sensor lsp server-name hb set services analytics sensor lsp export-name ns set services analytics sensor lsp resource /junos/services/label-switched-path/usage/ set services analytics sensor lsp export-to-routing-engine set services analytics sensor sr-te-color server-name hb set services analytics sensor sr-te-color export-name ns set services analytics sensor sr-te-color resource /junos/services/segment-routing/traffic-engineering/ingress/usage/ set services analytics sensor sr-te-color export-to-routing-engine set services analytics sensor sid server-name hb set services analytics sensor sid export-name ns set services analytics sensor sid resource /junos/services/segment-routing/sid/usage/ set services analytics sensor sid export-to-routing-engine set services analytics sensor sr-te-tunnels server-name hb set services analytics sensor sr-te-tunnels export-name ns set services analytics sensor sr-te-tunnels resource /junos/services/segment-routing/traffic-engineering/tunnel/ingress/usage/ set services analytics sensor sr-te-tunnels export-to-routing-engine {% if interfaces and interfaces | length > 0 %} {% for interface in interfaces %} set services rpm probe northstar-ifl test {{interface.name}} probe-type icmp-ping-timestamp set services rpm probe northstar-ifl test {{interface.name}} target address {{interface.peer_IP}} set services rpm probe northstar-ifl test {{interface.name}} probe-count 15 set services rpm probe northstar-ifl test {{interface.name}} probe-interval 1 set services rpm probe northstar-ifl test {{interface.name}} test-interval 20 set services rpm probe northstar-ifl test {{interface.name}} source-address {{interface.source_IP}} set services rpm probe northstar-ifl test {{interface.name}} history-size 512 set services rpm probe northstar-ifl test {{interface.name}} moving-average-size 60 set services rpm probe northstar-ifl test {{interface.name}} traps test-completion set services rpm probe northstar-ifl test {{interface.name}} destination-interface {{interface.name}} set services rpm probe northstar-ifl test {{interface.name}} one-way-hardware-timestamp {% endfor %} {% endif %}
- Test your use cases.
To get started with Paragon Insights:
- Add your device.
Select Configuration > Device. On the Device page, click Add Device (+).
- Create a device group and add your device to the device
group.
To create a device group, select Configuration > Device Group. On the Device Group page, click Add Device Group (+). In the Devices field, you must select the device that you added in Step 1.
- Push the OpenConfig-gRPC configuration to your devices.
For example:
set system services extension-service request-response grpc clear-text address 0.0.0.0 set system services extension-service request-response grpc max-connections 30 set system services extension-service request-response grpc skip-authentication set system services extension-service notification allow-clients address 0.0.0.0/0
- Upload predefined rules and playbooks.
To upload rules, select Configuration > Rules, and click the ↑ Upload Rule Files icon.
To upload playbooks (if applicable), select Configuration > Playbook, and click the ↑ Upload Playbook Files icon.
- Apply the playbook for your device group.
- Test your use cases.