Deploy VCF Operations for Networks with Fleet Management

HOMELAB JOURNAL

Deploy VCF Operations for Networks with Fleet Management

Follow VCF Operations for Networks deployment through Fleet Management, including platform and collector settings, certificates and prechecks.

Overview

This VCF Operations for Networks deployment walkthrough uses Fleet Management to add the platform and collector to my lab. It covers certificate creation, infrastructure and network inputs, and the deployment prechecks before I begin configuring collection.

Start the deployment

Start by logging in to the VCF Operations web gui.

Expand Fleet Management and click on Lifecycle

Click Add underneath operations-networks

At the Deployment screen, select New Install. I selected the Standard deployment type shown here because it was the smallest profile offered by this VCF 9.0 Fleet Management workflow and this is a homelab. That is a lab resource decision, not a sizing recommendation for another environment. Click Next to continue.

Operations for Networks deployment screen selects a new installation of version 9.0.0 with the Standard deployment type.

Configure the certificate

Click the Plus sign and select Generate Certificate to create a self-signed certificate for this deployment

Enter in the required information to create the certificate, for VCF Operations for Networks there are going to be 2 appliances deployed so be sure to include both of those FQDNs in your certificate. Click Generate

Generate Certificate dialog uses netops.jtec.local for the alias and common name and includes both netops.jtec.local and netops-collector.jtec.local in the server-domain field, with a 2048-bit key.

In the drop down, select the newly created certificate and click Next

Certificate step shows the generated netops.jtec.local certificate selected and displays its validity period, Fleet Management issuer, subject, SAN entries, SHA-256 signature, and 2048-bit RSA key.

Configure infrastructure and networking

Enter in the infrastructure settings to tell VCF Operations where to deploy the appliances. Click Next

Infrastructure step selects vcm.jtec.local, the management cluster and network, and the deployment folder and resource-pool choices for Operations for Networks.

Provide the domain name, DNS and NTP servers for the appliance deployment along with the default gateway and subnet mask. Once you have entered in the network configuration settings, click Next

Network step configures the jtec.local domain and search path, VCF DNS servers at 172.16.0.50 and 172.16.0.51, and NTP server synchronization.

Enter in the default password and appliance details for the platform and collector appliances. Click Next to continue.

Components step selects FIPS compliance mode Off, the generated certificate, anti-affinity disabled, a default component password, and integration with Identity Manager.

Validate and deploy

Click Run Precheck to validate the information entered.

After the prechecks pass, click Next to continue to the summary page.

Precheck page reports all validations passed; Infrastructure and Operations for Networks are marked Passed while Data validation also displays one warning.

Review the settings at the summary page and click Submit to deploy. If any changes need to be made to the deployment you can go back and re-run the precheck.

Deployment summary shows Operations for Networks 9.0.0 with the generated certificate, two NTP servers, DRS anti-affinity rules enabled, and FIPS compliance mode enabled.

The deployment will start with re-running the validations.

Once the deployment has completed, we have all the components installed for VCF Operations.

Fleet Management task view reports the Operations for Networks deployment succeeded in 43 minutes 35 seconds with all 14 stages completed.

You can return to my main VCF Lab page to follow along with this deployment.

Related lab guides

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.