rConfig V8 Pro to Vector Server Upgrade: Enterprise Platform Migration

rConfig Vector Server represents an enhanced edition of rConfig V8 Professional, delivering advanced capabilities for network configuration and device management. Migration from V8 Professional to Vector Server provides access to expanded functionality, enhanced performance characteristics, and strengthened security features. The upgrade procedure follows an in-place migration approach, requiring license acquisition, script execution, and Vector Server configuration for existing agent infrastructure.

Vector Server Upgrade Procedures by Operating System

CentOS, Rocky, RHEL, Alma / AWS
Ubuntu

rConfig V8 Professional to Vector Server Upgrade Procedures

Establish SSH connection to the server and elevate to root user privileges
Terminal window
```
ssh user@your-server-ip
```
Navigate to the rConfig application directory
Terminal window
```
cd /var/www/html/rconfig8/
```

Download the current deployment script. This script requires valid licensing as provisioned by support services.

cd /var/www/html/rconfig8/
wget https://dl.rconfig.com/downloads/rconfig8-vector-deploy.sh -O rconfig8-vector-deploy.sh
chmod +x rconfig8-vector-deploy.sh

Execute the deployment script Replace <someCode> with your API authentication token.
Terminal window
```
./rconfig8-vector-deploy.sh --mode=deploy --apitoken=<someCode>
```
Verify upgrade completion
- Following deployment script completion, update legacy directory path references in the database for rconfig5, rconfig6, or rconfig7 directories:
  Terminal window
```
    cd /var/www/html/rconfig8/current
    php artisan rconfig:updatedb8
```
- Verify the rConfig version reflects the Vector Server update.
- Navigate to the Agents menu under Settings.
- When adding or modifying device configurations, verify that the Agent option is available.
- Verify that the application logo has updated to the Vector branding.

Vector Server upgrade on CentOS, Rocky, RHEL, Alma, and AWS is complete. Continue with Vector agent installation to register managed endpoints.

rConfig V8 Professional to Vector Server Upgrade Procedures

Establish SSH connection to the server and elevate to root user privileges
Terminal window
```
ssh user@your-server-ip
```
Navigate to the rConfig application directory
Terminal window
```
cd /var/www/html/rconfig8/
```

Download the current deployment script. This script requires valid licensing as provisioned by support services.

cd /var/www/html/rconfig8/
sudo wget https://dl.rconfig.com/downloads/rconfig8-vector-deploy-ubuntu.sh -O rconfig8-vector-deploy-ubuntu.sh
sudo chmod +x rconfig8-vector-deploy-ubuntu.sh

Execute the deployment script Replace <someCode> with your API authentication token.
Terminal window
```
sudo ./rconfig8-vector-deploy-ubuntu.sh --mode=deploy --apitoken=yourApiToken
```
Verify upgrade completion
- Following deployment script completion, update legacy directory path references in the database for rconfig5, rconfig6, or rconfig7 directories:
Terminal window
```
    cd /var/www/html/rconfig8/current
    php artisan rconfig:updatedb8
```
- Verify the rConfig version reflects the Vector Server update.
- Navigate to the Agents menu under Settings.
- When adding or modifying device configurations, verify that the Agent option is available.
- Verify that the application logo has updated to the Vector branding.

Vector Server upgrade on Ubuntu is complete. Continue with Vector agent installation to register managed endpoints.

HTTP 403 Access Forbidden Error Resolution

If encountering HTTP 403 Access Forbidden errors following Vector Server upgrade, cached RBAC data may require clearing.

The error may appear as follows when accessing Settings > Agents:

rConfig Vector network management platform showing RBAC permissions error after V8 Professional upgrade

To resolve, execute the following commands:

# This error typically results from cached data from previous rConfig versions

redis-cli
select 1
keys *
del KEYNAME # (any key containing "permissions")

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

Video demonstration of the resolution process:

Clear Redis RBAC Cache