Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Import Network Models from Paragon Automation and NorthStar Controller

You can import offline network models into Routing Director for comprehensive data analysis and reuse.

Note: You can import network model only from Paragon Automation (Pathfinder, Planner, Insights) and NorthStar Controller.

To ensure compatibility with Routing Director, you need to first convert the network model to JSON format using a script (spec2json.sh), and later import the network model using the Routing Director GUI.

This feature enables you to manage and analyze network data, and leverage the capabilities of Routing Director for improved operational insights.

To import a network model from Paragon Automation or NorthStar Controller:

  1. Archive the network model by logging in to Paragon Automation or NorthStar Controller GUI.

    For more information on archiving the network model, see Collection Tasks to Create Network Archives (NorthStar Controller) or Add a Network Archive Task (Paragon Automation).

  2. Log in to the primary node of Paragon Automation or NorthStar Controller.
  3. Navigate to the Network Archive file in Paragon Automation or NorthStar Controller. The network archive file is the archived network model that describes the network topology and is available at the following location:

    • NorthStar—/opt/northstar/data/.network

    • Paragon Automation—dcscheduler-UUID:/opt/northstar/data/

  4. Copy the Network Archive file.
    Note: Ensure that you compress the Network Archive file as the Network Archive file size is large. It might take a couple of minutes to create the compressed file.
  5. Exit from the primary node of Paragon Automation or NorthStar Controller.
  6. Log in to the primary node of Routing Director.
  7. Copy the compressed network archive file to the Routing Director primary node.
  8. Run the script to convert the network archive file to a format (JSON) that can be reused in Routing director.
    Note:

    Before you run the spec2json.sh script,:

    • Ensure that you set KUBECONFIG to:

    • Ensure that the network archive file is in the tar.gz format

    The generated JSON file will always be named as topology-out.json and will be saved in the /root/topology.out.json folder. If you try to convert another network archive, then this file will be overwritten.

  9. Save the JSON file to your local system.
  10. Import the saved JSON file to create an offline network in Routing Director. For more information, see Create a Network Model.

    The network model that you imported from Paragon Automation or NorthStar Controller will be listed on the Working Models page (Planning > Networks > Offline Models) of the Routing Director GUI.

Related Documentation