Upgrading from NSX-T 3.0.x to NSX-T 3.2.0 or 3.2.1 causes nonconfig disk to grow for environments where IDS/IPS is utilized
search cancel

Upgrading from NSX-T 3.0.x to NSX-T 3.2.0 or 3.2.1 causes nonconfig disk to grow for environments where IDS/IPS is utilized

book

Article ID: 317756

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Symptoms:
  • /nonconfig partition size keeps growing on the NSX-T Manager appliance.
  • /nonconfig disk becomes too full and alarms are raised on the NSX-T Manager appliance.
  • In the NSX-T Manager log bundle, entries similar to the below will be present in var/log/corfu-nonconfig/nonconfig-corfu-compactor-audit.log:

2022-04-06T04:39:09.944Z ERROR main KeyDynamicProtobufSerializer - messagesFdProtoNameMap doesn't contain the message type com.vmware.nsx.securitydataservice.LogicalRouterToEdgeClusterMappingKeyMsg of payload type_url: "type.googleapis.com/com.vmware.nsx.securitydataservice.LogicalRouterToEdgeClusterMappingKeyMsg"

.

.

2022-04-06T04:39:09.958Z ERROR main CorfuCompileProxy - abortTransaction[CorfuTable[79cf]] Abort Transaction with Exception java.lang.NullPointerException

 


Environment

VMware NSX-T Data Center

Cause

The root cause has been confirmed due to be attributed to the addition of new types to an existing file in the DB.

Since the types were added to the existing file, the new changes are not captured and since one of those types happens to be the key, the upgrade fails.

Resolution

Currently there is no resolution to this issue


Attachments

corfudb-tools-3.2.20211207164848.664.1-shaded get_app