Error “file name does not conform to the expected format” encountered during NSX upgrade from 3.2.2.0 to 4.2.2.1 when uploading the precheck file
search cancel

Error “file name does not conform to the expected format” encountered during NSX upgrade from 3.2.2.0 to 4.2.2.1 when uploading the precheck file

book

Article ID: 407822

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Below error will be noticed in the Upgrade page:

Error: File name does not conform to the expected format.Please remove extra characters such as brackets and try again

 

 

Environment

VMware NSX-T

Cause

The incorrect upgrade bundle was used for the precheck.

In this case the customer did the .PUB which completed, the next step is to upload the .MUB. Its a workflow error on the customers part.

Resolution

This issue occurs because the precheck was run using a PUB file for the version 3.2.X , which is not valid for the upgrade process. For upgrading NSX, a MUB file must be used for the versions 3.2.x and lower.

  1. Download the correct MUB upgrade bundle from the Broadcom Customer Support Portal.

  2. Upload and use the MUB file, as it contains both the upgrade prechecks and the upgrade software.

 

Example:

Required upgrade bundle:

  • Product: NSX 4.2.2.1 Upgrade Bundle

  • File: VMware-NSX-upgrade-bundle-4.2.2.1.0.24765084.mub (9.13 GB)

  • Build Number: 24765084

For future upgrades beyond NSX 4.2.2.1, the PUB file can be used for prechecks.

 

Please refer the Support Portal to download the right upgrade bundle:

NOTE: MUB will not  include the PUB. It is a separate process 

https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/upgrade-guide/preparing-to-upgrade-nsx-t/run-the-upgrade-precheck-bundle.html