Validate MC and UC installation

Validate MC and UC installation

UC is installed along with MC. Validate your MC installation and verify that all required services are running correctly. Begin by identifying where MC is hosted and then perform the applicable validation steps for UC.

Validate Management Console and Unified Console Installation

After installing or upgrading Management Console, validate the deployment to ensure that both MC and UC are operating correctly and are accessible to users.

This validation procedure helps you confirm that:

  • MC is accessible from a browser.
  • UC loads successfully.
  • Required services are running.
  • Required certificates are trusted.
  • Network connectivity is configured correctly.
  • No installation or startup failures have occured.

Perform this validation:

  • After a new installation
  • After an upgrade
  • After changing the UC port
  • After updating CA certificates
  • After troubleshooting connectivity issues
  • After troubleshooting sign-in issues

Before you begin, identify whether your deployment is On-premises or Cloud.

Validation workflow

Perform validation in the following order:

  1. Verify that users can access MC and UC.
  2. Verify the installed MC version.
  3. Verify that MC services are running.
  4. Verify that UC processes are running.
  5. Verify network connectivity.
  6. Review logs only if any validation fails.

On-premises deployment

Step 1: Verify browser access

  1. Open the MC URL in your browser: https://<MC_HOSTNAME>:8433
  2. Verify the following:
    • The login page loads successfully.
    • The browser does not display certificate warnings.
    • You can sign in successfully.
    • UC opens after login.

If MC and UC are accessible, basic installation and service startup have completed successfully.

Step 2: Determine the installed MC version

The validation steps differ slightly between MC versions.

Run:

rpm -qa | grep vertica-console

Example output:

vertica-console-26.3.0-1.x86_6

Record the installed version before proceeding.

Step 3: Verify the MC service

Run:

sudo /opt/vconsole/shared/vertica-consoled status

Expected output:

Vertica Console: Running
status OK

Verify:

  • Service status is displayed as Running.
  • No startup or service errors are reported.

Step 4: Perform version-specific validation

MC version 26.2

Verify browser certificates

Confirm that all required CA certificates are imported into the browser.

Verify that:

  • No certificate warnings appear.
  • HTTPS connections are trusted.
Verify UC runtime files

Run:

ls -ltr /opt/vconsole/uc/run

Verify that:

  • PID files exist.
  • Runtime files are present.
  • Runtime files are being updated.
  • No stale lock files exist.

MC Version 26.3

Verify UC runtime components

Run:

ls -ltr /opt/vconsole/uc/run

Verify that:

  • UC processes are running.
  • PID files exist.
  • Runtime files are present.

Cloud deployment

Step 1: Verify browser access

Open the MC URL.

https://<MC_HOSTNAME>:8433

Verify the following:

  • The login page appears.
  • Authentication succeeds.
  • UC loads correctly.

Step 2: Determine the installed MC version

Run:

rpm -qa | grep -i console

Example output:

vertica-console-26.3.0-1.x86_64

Step 3: Verify the MC service

Run:

sudo /opt/vconsole/shared/vertica-consoled status

Expected output:

Vertica Console: Running
status OK

Verify:

  • MC service is running.
  • No startup errors are reported.

Step 4: Perform version-specific validation

MC version 26.2

Verify CA certificates

Confirm that the required CA certificates are imported into your browser.

Verify that:

  • HTTPS connections are trusted.
  • Certificate warnings do not appear.
Verify UC runtime files

Run:

ls -ltr /opt/vconsole/uc/run

Verify that:

  • Runtime files exist.
  • PID files are present.
  • No startup failures are reported.
Verify security group configuration

Ensure that the cloud security group allows the following ports:

  • TCP 8090
  • TCP 8433
Verify connectivity

Run:

nc -zv <MC_HOSTNAME> 8090
nc -zv <MC_HOSTNAME> 8433

Expected result:

  • Both connection tests succeed.

MC version 26.3

Verify UC runtime components

Run:

ls -ltr /opt/vconsole/uc/run

Verify that:

  • UC processes are running.
  • PID files exist.
  • No startup failures are reported.
Verify security group configuration

Ensure that the cloud security group allows TCP 8433.

Verify connectivity

Run:

nc -zv <MC_HOSTNAME> 8433

Expected result:

  • The connection test succeeds.

Troubleshooting installation validation failures

If any validation step fails, collect diagnostic information before contacting support.

Check MC service logs

Collect the recent MC service log entries:

journalctl -u vertica-consoled -n 200

Review:

  • Service startup failures
  • Port binding issues
  • SSL errors
  • Certificate validation errors

Locate UC log files

Find all UC log files:

find /opt/vconsole -name "*.log"

Common locations include:

  • /opt/vconsole/log/
  • /opt/vconsole/uc/logs/

Review:

  • Startup failures
  • Process crashes
  • Certificate-related errors
  • Connectivity errors

Verify endpoint reachability

Run one of the following commands:

telnet <MC_HOSTNAME> 8433
curl -vk https://<MC_HOSTNAME>:8433
nc -zv <MC_HOSTNAME> 8433

Expected result:

  • The endpoint accepts incoming connections.

Validate a custom UC port configuration

By default, UC uses port 8433. If you configured UC to use a different port:

  • Verify that the new port is reachable.
  • Verify that firewall rules allow access to the configured port.
  • Verify that cloud security groups allow access to the configured port.
  • Confirm that users access MC using the updated port.

Example:

https://<MC_HOSTNAME>:<CUSTOM_PORT>

Verify connectivity:

nc -zv <MC_HOSTNAME> <CUSTOM_PORT>

Validation complete

The installation is considered successful when the following conditions are met:

  • MC is accessible from a browser.
  • Users can sign in successfully.
  • Unified console loads correctly.
  • MC service status is Running.
  • The required UC processes are running.
  • The required network ports are reachable.
  • No startup failures or certificate-related errors are reported.

The MC and UC deployment are ready for use.