close
keyboard_arrow_left
Table of Contents
- play_arrow Introduction
- play_arrow System Requirements
- play_arrow Install Paragon Automation On Ubuntu
- play_arrow Install Paragon Automation on RHEL
- play_arrow Upgrade and Update Paragon Automation
- play_arrow Backup and Restore
- play_arrow Troubleshooting
- play_arrow Migrate Data
list Table of Contents
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.
Verification
- Verify that information federation between the two deployment clusters is operational,
using the
kubectl exec -it -n northstar rabbitmq-0 – rabbitmqctl list_parameterscommand. The output of the command must be similar to:content_copy zoom_out_mapListing runtime parameters for vhost "/" … component name federation-upstream my-upstream {"expires":30000,"uri":"amqps://northstar:BJitYWROJ5@10.54.239.02?cacertfile=/opt/bitnami/rabbitmq/certs/ca_certificate.pem&verify=verify_none"} Federation link is automatically created once there is an exchange with matching name created.
Log in into one of the rabbitmq pods.
kubectl exec -it -n northstar rabbitmq-0 -- bashRun 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; doneThe output of the command must be similar to:
content_copy zoom_out_mapI have no name!@rabbitmq-0:/$ for i in 0 1 2; do rabbitmqctl federation_status -n rabbit@rabbitmq-$i.rabbitmq-headless.northstar.svc.cluster.local; done Listing federation links on node rabbit@rabbitmq-0.rabbitmq-headless.northstar.svc.cluster.local... [#{error => <<>>,exchange => <<"controller.federated.topo">>, id => <<"f0e7320f">>,last_changed => <<"2023-04-18 09:19:14">>, local_connection => <<"<rabbit@rabbitmq-0.rabbitmq-headless.northstar.svc.cluster.local.3.24866.9>">>, queue => <<>>,status => running,type => exchange, upstream => <<"my-upstream">>, upstream_exchange => <<"controller.federated.topo">>, upstream_queue => <<>>,uri => <<"amqps://10.54.239.100">>,vhost => <<"/">>}] Listing federation links on node rabbit@rabbitmq-1.rabbitmq-headless.northstar.svc.cluster.local... [] Listing federation links on node rabbit@rabbitmq-2.rabbitmq-headless.northstar.svc.cluster.local... []
