Remediate or update incorrect Fleet, Platform or Instance Virtual IP (VIP) addresses in VCF Services Runtime

Products

• VCF Automation

Issue/Introduction

This article provides the technical procedure for utilizing a utility script to remediate or update an incorrect Virtual IP (VIP) address assigned to the Fleet, Platform or Instance Fully Qualified Domain Name (FQDN) within VCF services runtime or VCF Automation in VCF 9.1

Environment

VCF services runtime 9.1
VCF Automation 9.1

Cause

During configuration or post-deployment lifecycle modifications, an incorrect or an undesired VIP may inadvertently be associated with the Fleet, Platform or Instance FQDN within the VCF Services Runtime platform. This document acts as an operational guide to manually remediate the error.

Resolution

1. Download the attached script.

2. Change the permission of the file. 

chmod +x ./patch-vsp-vip.sh

3. Locate the IP address of any VCF Services Runtime platform VM from the SDDC Manager UI. If the UI is inaccessible, locate the VMs in vCenter and note the IP address of one of them.

4. Export ADMIN_PASSWORD setting it to the APPLIANCE_ROOT_PASSWORD used during the deployment of the component. If you are unsure of the VCF services runtime password, refer KB reset-password

export ADMIN_PASSWORD='..'

5. Run --help to identify all the options. 

/patch-vsp-vip.sh --help

6. Run the script 

./patch-vsp-vip.sh --node-ip <vm-ip-address> --username vmware-system-user --fleet-vip <vip1>[,<vip2>] --fleet-vip-ipv6 <vip6>[,<vip6-2>] --instance-vip <vip1>[,<vip2>] --instance-vip-ipv6 <vip6>[,<vip6-2>] --platform-vip <vip1>[,<vip2>] --platform-vip-ipv6 <vip6>[,<vip6-2>] --dry-run