ʻIkepili huna
1 Juniper NETWORKS Paragon Automation
2 Nā kikoʻī
3 Nā kuhikuhi hoʻohana
4 Hoʻolauna
5 Hoʻouka a hoʻonui
6 FAQs
7 Palapala / Punawai
7.1 Nā kuhikuhi

Juniper-LOGO

Juniper NETWORKS Paragon Automation

Juniper-NETWORKS-Paragon-Automation-PRODUCT1

Nā kikoʻī

  • Inoa Huahana: Juniper Paragon Automation
  • Hoʻokuʻu ʻia: 2.4.1
  • Ka lā i hoʻopuka ʻia: 2025-07-22

Hoʻolauna
Juniper Paragon Automation is designed to assist service providers, cloud providers, and enterprises in managing network operations efficiently. It offers a modern microservices architecture with open APIs and an intuitive user interface.

Nā mea nui

  • Hoʻokaʻawale i ka hoʻouka ʻana a me ka hoʻolako ʻana i nā mea hana
  • E hoʻomaʻamaʻa a hoʻolōʻihi i ka lawelawe ʻana
  • E noʻonoʻo i ka hana o ka mea hana a me ka lawelawe
  • E ho'ēmi i ka hana lima a me ka manawa

Laikini
Product entitlements are honour-based for Paragon Automation Release 2.4.1. To purchase a license, contact your Juniper Networks sales representative. Once purchased, manage licenses using the Juniper Agile Licensing (JAL) portal.

Kākoʻo ʻia ʻo Junos OS Releases, Devices, and Browsers
Refer to Table 1 for a list of supported Junos OS releases, devices, and browsers in Juniper Paragon Automation.

Hoʻouka a hoʻonui
To install or upgrade Juniper Paragon Automation, follow these steps:

  1. Download the installation package from the official Juniper Networks webpaena.
  2. Holo i ka wizard hoʻonohonoho a hahai i nā ʻōlelo kuhikuhi ma ka pale.
  3. For upgrades, ensure compatibility with existing configurations.

Nā kuhikuhi hoʻohana

Hoʻopaʻa ʻana a me ka hoʻolako ʻana
To onboard a device and provision services: Log in to the Paragon Automation GUI.

  1. E hoʻokele i ka ʻāpana Onboarding.
  2. E hahai i nā ʻanuʻu i alakaʻi ʻia e hoʻohui i kahi mea hana hou.
  3. E hoʻonohonoho i nā ʻāpana lawelawe e like me ka mea e pono ai.
  4. E hōʻoia i ka holomua ma ka ʻāpana Inventory.

ʻO ka hoʻokō ʻana i ka lawelawe
No ka hoʻokō ʻana i ka lawelawe:

  1. Select the desired service from the Service Catalogue.
  2. E hahai i nā kuhikuhi e hoʻonohonoho i nā kikoʻī lawelawe.
  3. Submit the provisioning request.
  4. E nānā i ka holomua ma ka Papa Hana Hana.

Hoʻolauna

  • Ke kū nei nā mea lawelawe, nā mea hoʻolako kapua, a me nā ʻoihana i ka piʻi ʻana o ka nui, ka wikiwiki, a me nā ʻano o ke kaʻa. Hoʻokumu kēia i nā luʻi kūʻokoʻa (hoʻonui i ka manaʻolana o nā mea hoʻohana a hoʻonui i nā hoʻoweliweli palekana) a me nā manawa hou (he hanauna hou o 5G, IoT, nā lawelawe ʻaoʻao i hāʻawi ʻia) no nā mea hoʻohana pūnaewele.
  • To accommodate rapid changes in traffic patterns, service providers and enterprises need to quickly detect and troubleshoot devices and service issues, and make changes to service configurations in real-time. Any misconfiguration due to human errors can lead to service outages. ʻO ka noiʻi ʻana a me ka hoʻoponopono ʻana i kēia mau pilikia hiki ke hana i ka manawa.
  • Juniper® Paragon Automation is a WAN automation solution that enables service providers and enterprise networks to meet these challenges. Juniper’s solution delivers an experience-first and automation-driven network that provides a high-quality experience to network operators.
  • Paragon Automation is based on a modern microservices architecture with open APIs. Paragon Automation is designed with an easy-to-use UI that provides a superior operational and user experience. For exampa, hoʻohana ʻo Paragon Automation i nā persona pro like ʻolefiles (such as network architect, network planner, field technician, and Network Operations Centre [NOC] engineer) to enable operators to understand and perform the different activities in the device life-cycle management (LCM) process.
  • Paragon Automation takes a use case-based approach to network operations. When you execute a use case, Paragon Automation invokes all the required capabilities of that use case, runs a workflow (if necessary) and presents you with a completed set of tasks that implement the use case.

Kākoʻo ʻo Paragon Automation i kēia mau hihia hoʻohana:

  • Device life-cycle management (LCM)—Allows you to onboard, provision, and then manage a device. Paragon Automation automates the device onboarding experience, from shipment through service provisioning, thus enabling the device to be ready to accept production traffic.
  • Observability—Allows you to visualise the network topology, provision tunnels, view nā mea hou topology i ka manawa maoli, a nānā i nā polokalamu a me ka pūnaewele. Hiki nō iā ʻoe view ke olakino a me ka ʻoihana pūnaewele a ʻike i nā kikoʻī. Eia kekahi, hōʻike ʻo Paragon Automation iā ʻoe e pili ana i nā pilikia pūnaewele me ka hoʻohana ʻana i nā mākaʻikaʻi, nā ala ala a me nā hanana, hiki iā ʻoe ke hoʻohana e hoʻoponopono i nā pilikia e pili ana i kāu pūnaewele. Hāʻawi pū ʻo Paragon Automation i kahi dashboard routing a me kahi palapala topology routing interactive kahi e hiki ai iā ʻoe ke nānā ikaika i ke olakino holo holoʻokoʻa o kāu pūnaewele i ka manawa maoli.
  • Trust and compliance—Automatically checks whether the device complies with the rules defined in the Centre for Internet Security (CIS) benchmarks document. In addition, Paragon Automation also checks the configuration, integrity, and performance of the device and then generates a trust score that determines the device’s trustworthiness.
  • Service Orchestration—Enables you to streamline and optimise the delivery of network services, thereby improving efficiency and reducing the risk of errors. A service can be any point-to-point, point-to-multipoint or multipoint-to-multipoint connection. For example, Layer 3 VPNs a i ʻole EVPNs.
  • Active Assurance—Enables you to actively monitor and test the network’s data plane by generating synthetic traffic using Test Agents. Test Agents are measurement points deployed in certain routers in your network. These Test Agents are capable of generating, receiving, and analysing network traffic and therefore enable you to continuously view a nānā i nā ana hopena i ka manawa maoli a i hui pū ʻia.
  • Network Optimisation—Enables you to optimise the utilisation of network resources, enhance network performance, and ensure reliable and efficient delivery of data across the network. Paragon Automation optimises the network by managing the life-cycle of label-switched paths (LSPs) or segment routing policies through an intent-based approach.

In summary, Paragon Automation helps operators automate the onboarding and provisioning of devices, simplify and accelerate service delivery, evaluate device and service performance, and reduce manual effort and timelines.

  • Use these release notes to know about features, supported Junos OS and Junos OS Evolved releases, supported devices, and open issues in Paragon Automation.

Laikini

To use Paragon Automation and its features, you need:

  • Product Entitlement—To use Paragon Automation and its use cases.

MANAʻO: Product entitlements are honour-based and not enforced for Paragon Automation Release 2.4.1.

  • Laikini Mea Hana—To use the features on a device that you onboarded.

No ke kūʻai ʻana i laikini, e kelepona i kāu luna kūʻai Juniper Networks. No ka ʻike hou aku e pili ana i ke kūʻai ʻana i nā laikini, e ʻike iā Juniper Licensing User Guide. Ma hope o ke kūʻai ʻana i kahi laikini, hiki iā ʻoe ke hoʻoiho i ka laikini file a mālama i nā laikini ma ka hoʻohana ʻana i ka puka puka Juniper Agile Licensing (JAL). Hiki iā ʻoe ke koho e loaʻa ka laikini file via e-mail. The license file aia ke kī laikini. Hoʻoholo ke kī laikini inā ʻae ʻoe e hoʻohana i nā hiʻohiʻona laikini.

  • Ma hope o ka paʻa ʻana o ka hāmeʻa, hiki i ka Mea Hoʻohana Nui a me ka Pūnaewele Pūnaewele ke hoʻohui i kahi laikini hāmeʻa mai ka pā laikini (Observability> Health> Troubleshoot Devices> Device-Name> Inventory> Licenses) o ka Paragon Automation GUI. No ka 'ike hou aku, e nānā i ka Manage Device Licenses.

Kākoʻo ʻia ʻo Junos OS Releases, Devices, and Browsers
Hōʻike ka papa 1 ma ka ʻaoʻao 3 i nā mea hoʻopuka Junos OS i kākoʻo ʻia, nā polokalamu, a me nā polokalamu kele pūnaewele ma Juniper Paragon Automation.

Papa 1: Kākoʻo ʻia nā hoʻokuʻu ʻana o Junos OS, nā polokalamu, a me nā polokalamu kele pūnaewele

Kākoʻo ʻia ʻo Junos OS

  • Junos OS Evolved releases 24.4R1, 24.2R2, 24.2R1, 23.4R2, 23.2R2, 22.4R2, and 22.2R3,
  • Junos OS releases 24.4R1, 24.2R2, 24.2R1, 23.4R2, 23.2R2, 22.4R2, and 22.2R3.

Kākoʻo ʻia nā ʻenehana Juniper

  • ACX2200 (EMS functionality and topology-related information only)
  • ACX7024
  • ACX7024-X
  • ACX7100-32C
  • ACX7100-48L
  • ACX7348
  • ACX7332
  • ACX7509
  • PTX10001-36MR
  • PTX10002-36QDD
  • PTX10004
  • PTX10008
  • PTX10016
  • MX204
  • MX240
  • MX304
  • MX480
  • MX960
  • MX10003
  • MX10004
  • MX10008
  • vMX
  • EX3400
  • EX4300-32F (EMS functionality only)
  • EX4300-48MP
  • EX9200
  • QFX5110
  • QFX5120

Supported third-party devices

  • Cisco Network Convergence System 57C3 (Cisco NCS57C3)
  • Cisco Network Convergence System 5504 (Cisco NCS5504)
  • Cisco 8202 Alaula
  • Cisco IOS XRv Router
  • Cisco Aggregation Services Routers 9902 (Cisco ASR9902)
  • MANAʻO: For third-party devices:
  • Only basic device management functions (such as basic device adoption, simple gNOI commands (reboot) and configuration templates) and onboarding using APIs are supported.
  • You cannot enable routing protocol analytics and data collection.

Nā polokalamu kele pūnaewele i kākoʻo ʻia

  • The latest versions of Google Chrome, Mozilla Firefox, and Safari.

Hoʻouka a hoʻonui

  • Juniper Paragon Automation Release 2.4.1 is a maintenance release of Release 2.4.0. Release 2.4.0 is no longer available for download from the software download site. To install and utilise features available in release 2.4.0, you must install release 2.4.1 or upgrade to release 2.4.1 from an older release.
  • To install Juniper Paragon Automation Release 2.4.1 afresh, download the paragon-2.4.1-builddate OVA file from the Juniper Paragon Automation software download site. Perform the steps described in the Installation and Upgrade  Guide to install release 2.4.1 and log in to the Web GUI. See Install Paragon Automation for information.
  • If you have already installed Juniper Paragon Automation Release 2.4.0 or an older release of Paragon Automation, upgrade to release 2.4.1 by downloading the upgrade_paragon-release-2.4.1.build-id.tgz available on the software download site. See Upgrade Paragon Automation for information.
  • You can upgrade to release 2.4.1 from the following releases.
    • Hoʻokuʻu 2.4.0
    • Hoʻokuʻu 2.3.0
    • Hoʻokuʻu 2.2.0
  • We do not support upgrading directly from Juniper Paragon Automation releases 2.0.0 and 2.1.0 to release 2.4.1. If you have a release 2.1.0 installation, you can upgrade to release 2.2.0, and then subsequently upgrade to release 2.4.1.

Nā mea hou

  • ʻAʻohe mea hou ma Juniper Paragon Automation Release 2.4.1.

Nā pilikia i ʻike ʻia

MA KEIA PAUKU

  • Device Life-Cycle Management | 7
  • Observability | 7
  • Service Orchestration | 14 Active Assurance | 16
  • Network Optimization | 18 Trust | 18
  • Administration | 18
  • Installation and Upgrade | 18

Hōʻike kēia ʻāpana i nā pilikia i ʻike ʻia ma Juniper Paragon Automation.

Hoʻoponopono Pūkino Ola-Poʻo

  • If you have onboarded a Cisco device, but later changed the TLS settings on the device (either turned it on or off), the status of the device will show as Disconnected on the Inventory page.
  • Workaround: Delete the device and onboard the device again by setting Insecure to False and Skip Verify to True accordingly based on whether you turned TLS off or on previously.
  • Onboarding a QFX device to Paragon Automation fails if Trust is enabled in a device profile applied to the QFX device.
    Workaround: Disable Trust in the device profile a laila e hoʻāʻo e kau i ka mea QFX.
  • Paragon Automation triggers the configuration templates included in a device profile a me interface profile i ka wā o ka hoʻomaka mua ʻana o ka hāmeʻa. ʻAʻole hiki iā ʻoe ke hoʻohana i nā hiʻohiʻona hoʻonohonoho i hoʻokomo ʻia i ka polokalamu profiles a me interface profiles to apply additional configuration to a device after the device is onboarded.
  • Workaround: If you need to apply additional configuration on a device after the device is onboarded, you need to manually apply the configuration using the CLI or by executing the configuration templates through the Paragon Automation GUI.
  • ʻO ka View Network Resources page (Inventory > Device Onboarding > Network Implementation Plan > More) doesn’t display AE interface-related details.
  • Hoʻoponopono: Hiki iā ʻoe view nā kikoʻī pili pili i nā AE ma ka View loulou config hoʻoikaika o ka Configuration accordion (Observability> Troubleshoot Devices> Device-Name).

ʻIke ʻia

  • Due to changes in XML Path Language (XPath), some custom rules cannot collect KPI information from the device.
    • Hoʻoponopono: ʻAʻohe.
  • During heavy ingest scenarios, such as onboarding of routers for the first time or router maintenance windows, it takes some time for the total number of routes to be reflected on the Routing Status graph (Observability > Routing >  Routing Explorer Routing Status tab).
  • If there are any events in the network, the Routing Status graph or the Routing Updates table (Observability > Routing > Route Explorer > Routing Updates) might display the data with substantial latency. We expect that the latency is reasonable during steady-state operation of the network.
  • Eia kekahi, ʻo nā helu helu ma ka ʻaoʻao Device (Observability > Routing > Route Explorer > Routing Status) a i ʻole ma ka Adjacencies tab (Observability > Routing > Route Explorer) e hōʻano hou ʻia me ka latency haʻahaʻa (1 a 5 mau minuke).
    • Hoʻoponopono: ʻAʻohe.
  • In a rare case of running multi-level ISIS protocols on a link, the topology map might not be updated or might not reflect the latest live operation status.
  • Hoʻoponopono: Hoʻopili i ke kau BGP LS, ma kahi o ka hoʻomaka hou ʻana i ke kikowaena topology.

Log in to the organisation-specific CRPD.
kubectl -n $(kubectl get namespaces -o jsonpath='{.items}’ | jq -r ‘.[]|select(.metadata.name |startswith(“pf-“))|.metadata.name’) exec -it $(kubectl -n $(kubectl get namespaces -o jsonpath='{.items}’ |jq -r ‘.[]|select(.metadata.name | startswith(“pf-“))|.metadata.name’) get pods -l northstar=bmp -o jsonpath='{.items[0].metadata.name}’) -c crpd — cli

Clear the BGP session.

  • Clear BGP from the neighbour all

If you try to create an LSP using the REST API and if you are reusing an existing LSP name, then the REST API server does not return an error.
Hoʻoponopono: ʻAʻohe.

  • Due to the changes in telemetry paths, you cannot view IS-IS data for ACX7020 devices on the Routing and MPLS accordion (Observability > Health > Troubleshoot > Devices > Device-Name). Workaround: None.
  • The Route Explorer page (Observability > Routing) displays data only if you have installed Junos OS or Junos OS Evolved Release 23.2 or earlier.
  • While adding a device profile for a network implementation plan, if you enable Routing Protocol Analytics,s then the routing data is collected for the devices listed in the device profile. When you publish the network implementation plan, even though the onboarding workflow appears to be successful, there might be errors related to the collection of routing data for these devices. Because of these errors, the devices will not be configured to send data to Paragon Automation and therefore, the routing data will not be displayed on the Route Explorer page of the Paragon Automation GUI. This issue occurs while offboarding devices as well, where the offboarded devices continue to send data to Paragon Automation.

Hiki mai kēia pilikia inā ʻaʻole ʻoe i hoʻonohonoho i ka ASN a i ʻole Router ID ma nā polokalamu, a i ʻole i ka wā i laka ʻia ai ka hoʻonohonoho ʻana o ka hāmeʻa no ka hoʻoponopono kūʻokoʻa.

Hoʻoponopono: To fix this issue:

  1. E hana i kekahi o kēia mau mea:
    Check the service logs by running the request paragon debug logs namespace routingbot app routingbot service routingbot-apiserver Shell command. Take the necessary action based on the error messages that you see in No Link Title.
    Papa 2: Nā memo Hapa
    Nā memo hewa Puka
    ʻAʻole i loaʻa ka polokalamu profile info for dev_id

    {dev_id}: {res.status_code} – {res.text}

     

    ʻAʻole i loaʻa ka ʻike mea hana no dev_id {dev['dev_id']}. Mea hoolele.

    		 Ua hāʻule ka API kelepona iā PAPI no ka loaʻa ʻana o ka ʻike.
    No results found in the response for dev_id

    {dev_id}

     

    ʻAʻole i loaʻa ka ʻike mea hana no dev_id {dev['dev_id']}. Mea hoolele.

    		 Hoʻihoʻi ka API kelepona iā PAPI i kahi pane me ka ʻike ʻole.
    Complete device info not found in the response for dev_id {dev_id}: {device_info} Hoʻihoʻi ka API kelepona iā PAPI i kahi pane me ka ʻikepili piha ʻole.
    ʻAʻohe ʻikepili i loaʻa no dev_id {dev_id} mai PF Ua hāʻule ka API kelepona iā Pathfinder no ka loaʻa ʻana o ka ʻike.
    ʻAʻole i loaʻa ka ʻikepili i koi ʻia no dev_id {dev_id} mai ka ʻikepili PF:{node_data} Hoʻihoʻi ka API i ka Pathfinder no ka loaʻa ʻana o ka ʻike mea hana i kahi pane me ka ʻikepili piha ʻole.
    EMS config failed with error, for config: {cfg_data} or EMS Config push error {res} {res.text} | try:

    {retries}. Failed to configure BMP on device

    {mac_id}

    		 Ua hāʻule ka hoʻonohonoho BGP.
    Nā memo hewa Puka
    Invalid format for major, minor, or release version: {os_version} The device’s OS version is not supported.
    Ua hewa POST {self.config_server_path}/api/v2/ config/device/{dev_id}/ {data} {res.json()} PThe laybook application has failed.
    Hapa PUT:{self.config_server_path}/api/v2/ config/device/{dev_id}/ {data} {res_put.json()} ʻAʻole hiki ke wehe ʻia ka puke pāʻani.
    Hapa PUT:{self.config_server_path}/api/v2/ config/device/{dev_id}/ {data} {res_put.json()} The device or playbook application to the device group has failed.
    Error PUT {self.config_server_path}/api/v2/ config/device-group/{site_id}/ {data}

    {res_put.json()}

    		 Device or playbook removal from the device group has failed.
    Nā memo hewa Puka
    Invalid format for major, minor, or release version {os_version} The device’s OS version is not supported.
    Ua hewa POST {self.config_server_path}/api/v2/ config/device/{dev_id}/ {data} {res.json()} Ua hāʻule ka polokalamu Playbook.
    Hapa PUT:{self.config_server_path}/api/v2/ config/device/{dev_id}/ {data} {res_put.json()} ʻAʻole hiki ke wehe ʻia ka puke pāʻani.
    Hapa PUT:{self.config_server_path}/api/v2/ config/device/{dev_id}/ {data} {res_put.json()} The device or playbook application to the device group has failed.
    Error PUT {self.config_server_path}/api/v2/ config/device-group/{site_id}/ {data}

    {res_put.json()}

    		 Device or playbook removal from the device group has failed.

    Examine the device configuration to check whether the device shows unexpected absence or presence of the configuration. For example, hiki iā ʻoe,

    • View aia nā hoʻonohonoho ma lalo o nā pūʻulu hoʻonohonoho paragon-routing-bgp-analytics routing-options bmp.
    • Check the device configuration in the JTIMON pod.
  2. After resolving the above issues, edit the device profile of the network implementation plan that you have applied to the device. Based on whether you are onboarding or offboarding devices, enable or disable the Routing Protocol Analytics option in the device profile.
  3. Publish the network implementation plan.
  4. Verify whether the required results are seen based on the data that is displayed on the Route Explorer page of the Paragon Automation GUI.

After you upgrade to Juniper Paragon Automation Release 2.4.1, you need to configure the cRPD VIP address to enable Routing Observability features.

No ka hoʻohana ʻana i nā hiʻohiʻona Routing Observability, e holo i kēia mau kauoha:

  • set paragon cluster applications routingbot routingbot-crpd-vip <vip-address> commit and exit
  • Request Paragon config
  • request paragon deploy cluster input “-t metallb,routingbot-crpd,addon-apps -e target_components=routingbot-api-server
  • kubectl -n routingbot rollout restart deployment routingbot-apiserver

On the Interfaces accordion, FEC uncorrected errors charts are available only on interfaces that support speeds equal to or greater than 100-Gbps.

  • After you apply a new configuration for a device, the Active Configuration for Device-Name page
    (Observability> Troubleshoot Device > Device-Name > Configuration accordion > View ʻaʻole hōʻike koke ʻia ka hoʻonohonoho hoʻonohonoho hou. He mau minuke e ʻike ʻia ai nā loli hou loa ma ka ʻaoʻao Active Configuration for Device-Name.
  • Hoʻoponopono: Hiki iā ʻoe ke hōʻoia inā pili nā hoʻonohonoho hou i ka hāmeʻa ma ke komo ʻana i ka hāmeʻa me ka hoʻohana ʻana iā CLI.
  • If a device is discovered through a BGP-LS peering session, even before you onboard the device, then duplicate LSPs are created when a PCEP session is established with the device. In rare cases, the duplicate LSPs that are created will continue to remain.
  • Workaround: If you see duplicate LSPs, rerun the configuration parsing after ensuring that
  • TopoServer has received a profile no ke poʻo LSP mai edgeAdapter. Hoʻomaka ʻia ka parsing hoʻonohonoho ʻana inā loaʻa kahi hanana commit ma ka hāmeʻa. No ka hoʻomaka lima ʻana i ka hoʻonohonoho ʻana:
    1. Log in to the airflow scheduler pod.
      kubectl -n airflow exec -it $(kubectl -n airflow get pods -l component=airflow-scheduler -o
      jsonpath='{.items[0].metadata.name}’) -c scheduler — bash
    2. Run configuration parsing.
      cd /opt/airflow/mount /opt/airflow/mount/utils/getipconf -northstar -noVT -noASNodeLink -topo_id 10 -dir /opt/airflow/mount/collection/<org id>/<topo id>/config/config -i /opt/airflow/mount/collection/<org id>/<topo id>/config/interface -geo /opt/airflow/mount/collection/<org id>/<topo id>/config/geo_file.json
  • The number of unhealthy devices listed on the Troubleshoot Devices and Health Dashboard pages (Observability > Health) does not match.
    Hoʻoponopono: ʻAʻohe.
  • You cannot delete unwanted nodes and links from the Paragon Automation GUI.
    Workaround: Use the following REST APIs to delete nodes and links:
  • REST API to delete a link:
    [DELETE] https://{{server-ip}}/topology/api/v1/orgs/{{org-id}}/{{topo-id}}/links/{{link-id}}

MANAʻO: You can follow the steps described here to get the actual URL.

No example,

MANAʻO: You can follow the steps described here to get the actual URL.

No example,

E hoʻohana i kēia kaʻina hana e kiʻi i ka mea maoli URL āu e hoʻohana ai ma CURL for deleting a link or a node:

  1. Navigate to the Topology page (Observability > Topology).
  2. Open the developer tool in the browser by using the CTRL + Shift + I buttons on the keyboard.
  3. In the developer’s tool, select Network and select the XHR filter option.
  4. Identify the link index number or node number. To identify the link index number to the node number:
    • On the Topology page of the Paragon Automation GUI, double-click the link or the node that you want to delete. The Link Link-Name page or the Node Node-Name page appears.
    • Navigate to the Details tab and note the link index number or the node number that is displayed.
  5. In the developer’s tool, select and click the row based on the link index number or the node number that is related to the link or the node that you want to delete.
  6. E kope i ka URL pono ʻoe e hoʻohana e holoi i ka loulou a i ʻole node ma CURL.

Not all optics modules support all the optics-related KPIs. See No Link Title for more information. Workaround: None.

Table 3: KPIs Supported for Optics Modules

Module Rx nalo o ka hōʻailona KPI Tx Pohō o ka hōʻailona KPI KPI Hoʻopaʻa Laser
SFP optics ʻAʻole ʻAʻole ʻAʻole
CFP optics ʻAe ʻAʻole ʻAʻole
CFP_LH_ACO optics ʻAe ʻAʻole ʻAʻole
QSFP optics ʻAe ʻAe ʻAe
CXP optics ʻAe ʻAe ʻAʻole
XFP optics ʻAʻole ʻAʻole ʻAʻole
  • For PTX100002 devices, the following issues are observed on the Interface accordion (Observability > Health > Troubleshoot Devices > Device-Name > Overview):
    • On the Pluggables Details for Device-Name page (Interfaces accordion > Pluggables data-link), the Optical Tx Power and Optical Rx Power graphs do not display any data.
    • On the Input Traffic Details for Device-Name page (Interfaces accordion > Input Traffic data-link), the Signal Functionality graph does not display any data.

ʻO ka hoʻonohonoho lawelawe

  • If different L3VPN services are running on the same IFD using different MTU values, then service provisioning fails.
    Workaround: Ensure that the MTU values are the same for L3VPN services that share the same IFD.
  • The following accordions on the Passive Assurance tab (Orchestration > Instances > Service-Order-Name Details) display incorrect or no data:
  • BGP accordion—The VPN State column displays incorrect data for customer edge (CE) or provider edge (PE) devices with IPv4 or IPv6 neighbours.
  • OSPF accordion—There are no IPv6 entries in the Neighbour Address column for CE or PE devices with IPv6 neighbours.
  • L3VPN accordion—The VPN State column displays incorrect data for OSPF and BGP protocols. The Neighbourr Session and VPN State columns are blank for CE or PE devices with static IPv4 or IPv6 addresses.
  • This issue occurs only for an L3VPN service.
  • Hoʻoponopono: ʻAʻohe.
  • If no valid interface option is available for a CE and PE device combination, then the Interface drop-down will be empty.
    Workaround: You can do one of the following:
    • Select a different CE and PE combination.
    • Unselect the CE device before selecting the PE device and its interface. In this scenario, the system automatically assigns the CE device.
  • If you upgrade Paragon Automation from Release 2.3.0 to 2.4.1, then you might not be able to modify VLANs for Site Network Accesses on the existing L3VPN service instances.
    Workaround: You need to upgrade the service instances to Release 2.4.1 to use the interactive placement functionality.
  • The device name is not displayed when you hover over the View Details hyperlink in the Relevant Events section of the L3VPN accordion (Orchestration > Instances > Service Instances > Service-Instance-Name hyperlink > Service-Instance-Name Details > Passive Assurance tab).
  • Hoʻoponopono: ʻAʻohe.
  • If you have upgraded the topology resource from Release 2.2.0 or Release 2.3.0 to Release 2.4.1 and if you later edit and provision a service instance (L3VPN or EVPN) that was created in an older release (Release 2.3.0 or Release 2.2.0), then the provisioning of the service instance fails. Workaround: Before you start editing the service instance, ensure that the topology resource and the service instance are in the same version. You can choose to upgrade the topology resource first and then the service, or vice versa.
  • When you onboard devices in batches, due to Kubernetes’ horizontal pod autoscaling of airflow-worker pods, the onboarding might fail for the devices that are in the middle of the onboarding process.
  • Workaround: Use the Resume Onboarding option on the Paragon Automation GUI to re-initiate onboarding.
  • After you upgrade Paragon Automation from Release 2.2.0 to Release 2.4.1, ensure that you upgrade the L3VPN service instance before you upgrade the topology resource instance; otherwise, you might encounter issues.
  • Hoʻoponopono: E hoʻomaikaʻi mua i nā manawa lawelawe āpau a laila e hoʻomaikaʻi i ke kumu kumu topology.
  • The “vpn_svc_type” service type is displayed as “pbb-evpn” instead of “evpn-mpls” on the Paragon Automation GUI and through the REST API.
  • Hoʻoponopono: ʻAʻohe.
  • For an MX 240 device, the OSPF-related data is not populated on the Passive Assurance tab (Orchestration > Instances > Service-Order-Name Details).
  • Hoʻoponopono: E hoʻonohonoho i ka OSPF ma ka mea kūʻai aku (CE).
  • While creating or modifying an EVPN service order, you cannot configure multiple VLAN IDs on the Aggregated Ethernet (AE) interface. The EVPN considers the AE port as a single resource, and therefore, an AE interface cannot be reused across service instances even when the VLAN IDs on the AE IFL differ.
  • Hoʻoponopono: ʻAʻohe.
  • When you click the Refresh icon on the Service-Instance-Name Details page (Orchestration > Instances > Service-Instance-Name), you may not see the latest events in the Relevant Events section.
  • Hoʻoponopono: To view the latest events, instead of using the Refresh icon, go to the Service Instance page (Orchestration > Instances) and select the service instance for which you need to see the latest events.
  • While modifying an existing L3VPN service instance, if you try to remove a device that is already a part of a network implementation pla, then the modify workflow fails.
  • Workaround: On the Monitors page, stop all the monitors associated with the device that has to be deleted in the service instance. After the relevant monitors are stopped, you can proceed with modifying the L3VPN service instance.
  • The Order History tab on the L3VPN-Name Details page (Orchestration > Instances > Service-
  • Instance-Name hyperlink) lists all the order history if you deprovision a service instance and later provision a service using the same details as those of the deprovisioned service.
  • Hoʻoponopono: ʻAʻohe.
  • In a scaled setup, you cannot upgrade service designs in bulk.
  • Workaround: We recommend that you upgrade only one service design at a time.
  • The Output Traffic rate column on the Logical Interface accordion (Orchestration > Instances > Service Instances page > service-instance-name hyperlink > Service-Instance-Name Details) displays some data even when there is no traffic through the devices.
  • Hoʻoponopono: ʻAʻohe.

Hoʻoikaika ikaika

  • You might not be able to view the Tests page (Observability > Active Assurance) if your role type is Observer.
  • Hoʻoponopono: ʻAʻohe.
  • If you had installed Test Agent on a router while using Juniper Paragon Automation Release 2.3.0 or earlier releases, and later, if you upgrade to Paragon Automation Release 2.4.1 and reboot the router, then there will be a mismatch between the Test Agent version that is installed on the router and the Test Agent version that is available in Paragon Automation. Due to this issue, you cannot run Tests or Monitors on the router that is rebooted.
  • Workaround: After you upgrade Paragon Automation to 2.4.1, log in to the router and remove the Test Agent version information from the Test Agent Config by running the delete services paa test-agent ta-version command.
  • The status of a Test Agent is shown as offline after the device’s Routing Engine switches over from the primary Routing Engine to the backup Routing Engine, or vice versa. This issue occurs only if you are using a Junos OS version that is older than 23.4R2.
  • Hoʻoponopono: E hoʻouka hou i ka mea ho'āʻo ma hope o ka hoʻololi ʻana i ka ʻenekini ala.
  • You cannot run multiple versions of plug-ins on a Test Agent.
  • Hoʻoponopono: Ke hoʻomaikaʻi ʻoe i ka Paragon Automation, e hoʻomaka hou i nā ana āpau ma mua o ka hana ʻana i nā ana hou.
  • When you click a Monitor on the Monitors page (Observability > Active Assurance), the Monitor-Name page takes approximately a minute to load the data. This issue occurs only when there is a larger number of events in the system.
  • Hoʻoponopono: ʻAʻohe.
  • The streams are not generated when you create a Test with a DNS plug-in, and the following event is raised:
    • Could not get nameserver from resolv.conf
  • This issue occurs when the Test is associated with a Test Agent that runs on a Juniper Networks router with Junos OS EVO installed, and you don’t specify the Name Server field while configuring a Test.
  • Hoʻoponopono: E hōʻoia ʻoe e kuhikuhi i kahi waiwai no ke kahua Name Server i ka wā e hoʻonohonoho ana i kahi hōʻike.
  • After you update a Monitor or a Test Template that is created by another user, the Updated By column on the Monitors (Observability > Active Assurance) and Test Template (Inventory > Active Assurance) pages do not reflect the name of the user who modified the Monitor or the Test Template. Workaround: None.
  • When you add a new host to the existing Monitor, the new measurements are not reflected in the Active Assurance tab of the Health Dashboard (Observability > Health).
  • Hoʻoponopono: ʻAʻohe.
  • The devices table on the Devices tab (Observability > Health > Health Dashboard > Active Assurance (Tab) > Click any accordion > View Details > Affected Items tab) ʻaʻole i papa inoa i nā mea i loaʻa nā ana maikaʻi ʻole.
    Hoʻoponopono: ʻAʻohe.

Hoʻopono pūnaewele

  • Segment Routing (SR) LSPs are not created when you publish a path intent with an SR tunnel profile. This issue occurs because the broadcast link is not supported due to the dynamic election nature of the designated router (DR) in OSPF or designated intermediate system (DIS) in IS-IS.
  • Hoʻoponopono: ʻAʻohe.

hilinai

  • ʻAʻohe pilikia i ʻike ʻia ma kēia hoʻokuʻu.

Hooponopono

  • The maximum size of a configuration template supported is 1 MB, and not 10 MB as indicated in the error message on the GUI.
  • Hoʻoponopono: ʻAʻohe.
  • Occasionally, there is a noticeable delay of up to 10 minutes between when an alert is triggered and when it appears on the GUI.
  • Hoʻoponopono: ʻAʻohe.

Hoʻouka a hoʻonui

  • When you run the request paragon deploy cluster or request paragon service start commands, sometimes the commands may fail because the config.yml is empty. In such cases, the log file hiki ke hōʻike i kahi hewa e like me kēia:

hoʻohana: ansible-playbook [-h] [–version] [-v] [–private-key PRIVATE_KEY_FILE] [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT][–ssh-common-args SSH_COMMON_ARGS]

  • [–sftp-extra-args SFTP_EXTRA_ARGS]
  • [–scp-extra-args SCP_EXTRA_ARGS]
  • [–ssh-extra-args SSH_EXTRA_ARGS]
  • [-k | –connection-password-file CONNECTION_PASSWORD_FILE]
  • [–force-handlers] [–flush-cache] [-b]
  • [–become-method BECOME_METHOD]
  • [–become-user BECOME_USER]
  • [-K | –become-password-file ALOHA_PASSWORD_FILE]
  • [-t TAGS] [–hoʻokuʻu-tags SKIP_TAGS] [-C]
  • [–syntax-check] [-D] [-i INVENTORY] [–list-hosts]
  • [-l SUBSET] [-e EXTRA_VARS] [–vault-id VAULT_IDS]
  • [–ask-vault-password | –vault-password-file VAULT_PASSWORD_FILES][-f FORKS] [-M MODULE_PATH] [–list-tasks]
  • [–list-tags] [–step] [–start-at-task START_AT_TASK]
  • playbook [playbook …]

Runs Ansible playbooks, executing the defined tasks on the targeted hosts.

< hoʻopuka ʻia >

  • –become-metho BECOME_METHOD
    • privilege escalation method to use (default=sudo), use `ansible-doc -t become -l` to list valid choices.
  • – lilo i mea hoʻohana BECOME_USER
    • Run operations as this user (default=root)
  • -b, – lilo
    • run operations with become (does not imply password prompting)

Workaround: Perform the following steps before rerunning either of the commands.

  1. Verify that the config.yml file ua hakahaka ma ka hoohana ana i ka file show /epic/config/config.yml command. If the config.yml file is empty, perform the following steps.
  2. Regenerate the configuration files using the request paragon config command.
  3. Type exit to exit to the Linux root shell.
  4. E hoʻokō i kēia mau kauoha:
    • # chattr +i /root//epic/config/inventory
    • # chattr +i /root//epic/config/config.yml
  5. Type cli to enter Paragon Shell.
  6. Execute the request paragon deploy cluster or request paragon service start commands (as the case may be).
  7. Immediately type exit to exit to the Linux root shell.
  8. E hoʻokō i kēia mau kauoha:
    • # chattr -i /root//epic/config/inventory
    • # chattr -i /root//epic/config/config.yml
  9. Type cli to re-enter Paragon Shell.
  10. Monitor the progress of deployment using the monitor start /epic/config/log command.

The vmrestore tool restores data into vmstorage pods. While performing a restore, the tool creates a lock file ka mea e pale ai i kekahi noi ʻē aʻe mai ke komo ʻana i ka ʻikepili i ka wā hoʻihoʻi. Eia naʻe, i kekahi manawa ʻaʻole hiki i ka mea hana vmrestore ke holoi i ka laka file, and the vmstorage pods cannot access data. Workaround: The lock can be released by rerunning the restore operation using the same backup files. For information on restoring your Paragon Automation cluster, see Back Up and Restore Paragon Automation.

  • When the worker node is down, there might be issues if you create an organisation or onboard a device.
  • Workaround: Do not create an organisation or onboard a device when a worker node is down. You must wait until the cluster recovers and then create an organisation or onboard a device. A recovered state is when all the pods are either in Running or Pending states and are not in any intermediate states like Terminating, CrashloopbackOff, and so on.

Nā pilikia i hoʻoholo ʻia
ʻAʻohe pilikia i hoʻoholo ʻia ma Juniper Paragon Automation Release 2.4.1

  • ʻO Juniper Networks, ka logo Juniper Networks, Juniper, a me Junos he mau hōʻailona inoa inoa o Juniper Networks, Inc. ma ʻAmelika Hui Pū ʻIa a me nā ʻāina ʻē aʻe. ʻO nā hōʻailona ʻē aʻe a pau, nā hōʻailona lawelawe, nā hōʻailona i hoʻopaʻa ʻia, a i ʻole nā ​​​​hōʻailona lawelawe i hoʻopaʻa inoa ʻia ka waiwai o ko lākou mau mea nona. ʻAʻole kuleana ʻo Juniper Networks no nā hemahema o kēia palapala. Hiki iā Juniper Networks ke hoʻololi, hoʻololi, hoʻololi, a i ʻole e hoʻoponopono hou i kēia puke me ka ʻole o ka hoʻolaha. Kuleana kope © 2025 Juniper Networks, Inc. Ua mālama ʻia nā kuleana āpau.

FAQs

Nīnau: Pehea wau e hoʻoponopono ai i nā pilikia pilikia ma Paragon Automation?

A: To troubleshoot device issues, navigate to Observability > Health > Troubleshoot Devices in the Paragon Automation GUI. Select the specific device and follow the troubleshooting guides provided.

Nīnau: Hiki iaʻu ke hoʻohana i ka Paragon Automation me ka ʻole o ka laikini?

A: While product entitlements are honor-based, it is recommended to purchase a license for full access to all features and support services.

Palapala / Punawai

Juniper NETWORKS Paragon Automation [pdf] Ke alakaʻi hoʻohana
Hoʻokuʻu 2.4.1, Paragon Automation, Paragon, Automation

Nā kuhikuhi

Waiho i kahi manaʻo

ʻAʻole e paʻi ʻia kāu leka uila. Hōʻailona ʻia nā kahua i makemake ʻia *