Skip to content
rConfig Documentation

rConfig Vector V7 to V8 Upgrade Guide

rConfig Vector V7 to V8 Upgrade: Enterprise Network Management Platform Migration

Section titled “rConfig Vector V7 to V8 Upgrade: Enterprise Network Management Platform Migration”

Upgrading from rConfig Vector V7 to Vector V8 utilizes a streamlined automated migration process. Fully automated upgrade scripts are provided for CentOS, RHEL, Rocky Linux, and Ubuntu-based systems, managing all required migration procedures. For new deployments, compare this workflow with the Vector server installation guide.

When to use this

Section titled “When to use this”

Follow this guide when you have a working rConfig Vector V7 installation and want to migrate to Vector V8 using the automated upgrade script. If deploying a fresh Vector V8 environment without an existing V7 installation, use the Vector server installation guide instead.

Prerequisites

Section titled “Prerequisites”
  • rConfig Vector V7 installed at the default path
  • Root or sudo SSH access to the server
  • API authentication token from the rConfig customer portal
  • Complete system and database backups taken, verified, and stored off-server
  • Active internet connection for package downloads during the upgrade script

Upgrade Procedures

Section titled “Upgrade Procedures”
Terminal window
cd /home
wget https://dl.rconfig.com/downloads/upgrade-to-rconfig8.sh -O upgrade-to-v8.sh
chmod +x upgrade-to-v8.sh
sudo ./upgrade-to-v8.sh YourSecureToken1234 vector

Database Path Update Procedure

Section titled “Database Path Update Procedure”

Following upgrade script completion, update legacy directory path references in the database that reference rconfig5, rconfig6, or rconfig7 directories:

Terminal window
cd /var/www/html/rconfig8/current
php artisan rconfig:updatedb8

Web Server Configuration

Section titled “Web Server Configuration”

For Apache deployments, verify DocumentRoot references /var/www/html/rconfig8/current/public. For Nginx deployments, update the root directive accordingly.

Verify current configuration:

Terminal window
# Apache Ubuntu
apache2ctl -S


# Apache RHEL/CentOS/Rocky
httpd -S


# Example output:
# VirtualHost configuration. Verify each VirtualHost for correct path configuration:
10.1.1.2:443           vega.rconfig.com (/etc/httpd/sites-enabled/vega.rconfig.com-le-ssl.conf:3)
*:443                  vega.rconfig.com (/etc/httpd/conf.d/ssl.conf:40)
*:80                   vega.rconfig.com (/etc/httpd/sites-enabled/vega.rconfig.com.conf:2)

For each virtual host configuration, update the DocumentRoot directive:

# Update rconfig7 references to rconfig8


RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
<IfModule mod_ssl.c>
<VirtualHost v8demo.rconfig.com:443>
        ServerName v8demo.rconfig.com
        ServerAlias v8demo.rconfig.com
        DocumentRoot /var/www/html/rconfig8/public
        <Directory "/var/www/html/rconfig8/public">
                Options Indexes FollowSymLinks MultiViews
                Order allow,deny
                Allow from all
                AllowOverride All
                Require all granted
                Satisfy Any
        </Directory>


    SSLEngine on
    SSLCertificateFile  /etc/pki/tls/certs/cert.crt
    SSLCertificateKeyFile /etc/pki/tls/private/key.key


    SSLProtocol             all -SSLv3 -TLSv1 -TLSv1.1
    SSLCipherSuite          PROFILE=SYSTEM


</VirtualHost>
</IfModule>

Upgrade Completion

Section titled “Upgrade Completion”

Upon successful completion of upgrade procedures:

  • Your rConfig system is now operating on Vector V8
  • Access the system using your existing rConfig URL
  • Execute a hard browser refresh (CTRL+SHIFT+R or CMD+SHIFT+R) following the upgrade to clear cached assets
rConfig Vector V8 authentication login interface after successful upgrade from V7 enterprise network management platform rConfig V8 Authentication Interface

What’s next

Section titled “What’s next”