Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure Disaster Recovery for Paragon Pathfinder

You can deploy Paragon Automation at two different geographical locations so that when the Paragon Pathfinder component is down at one location, the Paragon Pathfinder component at the other location can continue managing Path Computation Client (PCC)-delegated LSPs in your network. You can configure a federated exchange of information to synchronize the two deployments so that you can manage the topologies and modify and optimize LSPs from either one of the instances of Paragon Pathfinder.
To configure a disaster recovery setup of Paragon Pathfinder instances in dual Paragon Automation deployments, perform the following steps.
  1. Prepare the deployments to configure disaster recovery for Paragon Pathfinder.

    • For new deployments of Paragon Automation:

      Edit the config.yml file for both deployments as follows:

      prepare_multi_cluster: true

      Proceed with installing both Paragon Automation clusters as usual.

    • For existing deployments of Paragon Automation:

      1. Edit the config.yml file for both deployments as follows:

        prepare_multi_cluster: true

      2. Rerun the following deploy command for both deployments.

        ./run -c config-dir deploy -t rabbitmq,ambassador

      3. Verify that both the deployments are functioning normally.

        Now you have prepared two active Paragon Automation deployment clusters to configure disaster recovery for Paragon Pathfinder.

  2. Configure federated exchange of information between the two active deployments.

    • Through the cmgd CLI.

    • Through the Paragon Automation UI.

      Navigate to Configuration > Network Settings > Pathfinder Setting > Topology Server > Messaging Bus and enable the use-federated-exchange flag on both clusters.

  3. Restart the toposerver pod.
  4. Create an inventory_ha inventory file to activate the information federation. Create the file in the same config-dir directory as the inventory and config.yml files of one Paragon Automation deployment. If the two deployment have different Ansible control hosts, create the file in the config-dir directory of any one of the control hosts.

    Sample inventory_ha file:

    For example:

  5. Activate the information federation using the deploy-federated-exchange command.

    ./run -c config-dir deploy-federated-exchange

Verification
  1. Verify that information federation between the two deployment clusters is operational, using the kubectl exec -it -n northstar rabbitmq-0 – rabbitmqctl list_parameters command. The output of the command must be similar to:

  2. Federation link is automatically created once there is an exchange with matching name created.

    1. Log in into one of the rabbitmq pods.

      kubectl exec -it -n northstar rabbitmq-0 -- bash

    2. Run the following command in the rabbitmq pod.

      for i in 0 1 2; do rabbitmqctl federation_status -n rabbit@rabbitmq-$i.rabbitmq-headless.northstar.svc.cluster.local; done

      The output of the command must be similar to:

Related Documentation