Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Post Installation Tasks

date_range 29-Jan-25

After you install the Paragon Automation cluster, you can use Paragon Shell to perform the following additional optional tasks:

  • Ensure that the installed cluster is healthy and operational.

    Execute the request paragon health-check command. The Overall Cluster Status must be GREEN. For example:

    content_copy zoom_out_map
    root@primary1> request paragon health-check 
    Health status checking...
    
    =======================================================
    Get node count of Kubernetes cluster.
    =======================================================
    
    OK
    There are 4 nodes in the cluster.
    ...
    <output snipped>
    ...
    ======================================================
    Verifying Elasticsearch
    ======================================================
    
    OK
    Opensearch test...
    Checking health status at opensearch-cluster-master.common:9200...
    Opensearch is healthy (green).
    OPENSEARCH VERIFICATION PASS
    
    =======================================================
    Overall cluster status
    =======================================================
    
    GREEN
    
  • Configure the PCE server. See Configure PCE Server.

  • Configure SMTP-based user management. See Configure SMTP Settings in Paragon Shell.

  • Install custom user certificates. See Install User Certificates.

  • Back up your Paragon Automation cluster configuration. See Back Up Using Paragon Shell.

  • Configure monitoring in Paragon Automation to collect metrics from different types of sources and forward the collected data to designated sinks. See Configure Monitoring.

  • Update the Victoria Metrics cluster configuration parameters. See Update Victoria Metrics.

Update Victoria Metrics

Update the Victoria Metrics cluster configuration parameters. Victoria-metrics is a time series database. Different microservices populate the database and query data using the APIs provided by Victoria metrics.

  1. Log in to the node from which you deployed the Paragon Automation cluster.
  2. Type configure to enter configuration mode.
  3. Update the Victoria Metrics parameters. Use the following commands.
    • content_copy zoom_out_map
      root@primary1# set paragon cluster insights victoria-metrics vm-cluster-replication-factor replication_factor
    • content_copy zoom_out_map
      root@primary1# set paragon cluster insights victoria-metrics vm-cluster-retention-period retention_period
    • content_copy zoom_out_map
      root@primary1# set paragon cluster insights victoria-metrics vm-cluster-storage-instances number_of_pods

    For more information on vm-cluster-replication-factor, vm-cluster-retention-period, and vm-cluster-storage-instances, see set paragon cluster insights victoria-metrics.

  4. Type commit and-quit to commit the configuration and exit configuration mode.
  5. Regenerate the configuration files.
    content_copy zoom_out_map
    root@primary1> request paragon config
    Paragon inventory file saved at /epic/config/inventory
    Paragon config file saved at /epic/config/config.yml
  6. Deploy the updated configuration.
    content_copy zoom_out_map
    root@primary1> request paragon deploy cluster input "-v -t victoriametrics-cluster"
    Process running with PID: 23xx022
    To track progress, run 'monitor start /epic/config/log'
footer-navigation