Skip to content

rConfig Vector – Upgrade V7 Pro to Vector Server

8 mins Vector

Introduction

rConfig Vector Server is an enhanced version of rConfig V7 Pro, offering advanced features and capabilities for managing network configurations and devices. Upgrading from V7 Pro to Vector Server provides access to new functionalities, improved performance, and enhanced security features. The process to upgrade from V7 Pro to Vector Server is straightforward and involves acquiring a new license, running an in place upgrade, and configuring the Vector Server to work with your existing agents.

Updating the Vector Agent by OS Type


Steps to Upgrade rConfig v7 Pro to Vector Server

  1. Login to the server using SSH, and change to root user

    Terminal window
    ssh user@your-server-ip

  2. Change to the rConfig application directory

    Terminal window
    cd /var/www/html/rconfig7/

  3. Download the latest deployment script. This script will only work if you have the correct license key as assigned by support.

    Terminal window
    cd /var/www/html/rconfig7/
    wget https://dl.rconfig.com/downloads/rconfig7-vector-envoy.blade.php?$(date +%s) -O /var/www/html/rconfig7/Envoy.blade.php

  4. Run the deployment script Replace <someCode> with your API token.

    Terminal window
    envoy run deploy --apitoken=<someCode>

  5. Verify the upgrade

    • Check the version of rConfig to ensure it reflects the Vector Server update.
    • Navigate to the Agents menu under Settings.
    • When adding or editing a device, confirm that the Agent option is available.
    • Verify that the top left logo has changed to the Vector logo.

That’s it! 🎉 You’ve successfully upgraded to the Vector Server on CentOS, Rocky, RHEL, Alma, and AWS.

Action Unauthorized Error after update

If you encounter an Action Unauthorized error after updating to Vector Server, you may need to clear out some cached RBAC related data.

The error may look like this when opening the Settings > Agents page for example:

To do this, run the following command:

Terminal window
#This error is typically caused by cached data from the previous version of rConfig.


redis-cli
select 1
keys *
del KEYNAME #(anything with permisssions in it)


exit
cd /var/www/html/rconfig7/current && php artisan rconfig:clear-all

Heres a video example of the process:

Clear Redis RBAC Cache

Clearing Redis RBAC Cache