Requirement of Access Token During VCF Usage Meter In-Place Upgrade 9.0 to 9.x

Products

• VMware Usage Meter

Issue/Introduction

This article explains whether obtaining a new access token from the VCF Business Services console is required when performing an in-place upgrade from VCF Usage Meter 9.0 to 9.1, and clarifies the conditions under which the token prompt appears.

Environment

VCF Usage Meter 9.0

VCF Usage Meter 9.1

Resolution

Generating and entering a new access token is NOT required for an in-place upgrade from VCF Usage Meter 9.0 to 9.1.

When you run the upgrade script (upgrade-um.sh), the existing configuration settings (including the access token) already configured in version 9.0 are automatically carried over.
Therefore, the console will not prompt you to enter an access token, and the upgrade process will proceed seamlessly.

Additional Information

Entering an access token primarily for the following scenarios:

1. Major Upgrades (e.g., 4.8 to 9.x)
   When upgrading from legacy versions such as VCF Usage Meter 4.8 to the 9.x series, entering an access token is mandatory to establish the initial integration with the VCF Business Services console.
2. Expired Access Token
   If the existing token has expired, data uploads to the console will fail, and a new token must be generated and registered.

Reference: Usage Meter fails data upload to VCF Business Console due to expired access token

 

VCF Usage Meter 9.x のインプレースアップグレード（9.0から9.x）におけるアクセストークンの要件