Deploying VLAN AVNs fails in SDDC Manager fails at Attach transport zone with NSX Transport Node Profile

Products

• VMware SDDC Manager

Issue/Introduction

Deployment of vLAN Application Virtual Network fails at the below subtask - 

domainmanager.log: 

yyyy-mm-ddThh:mm:ss ERROR [vcf_dm,68302356f6cc505f94d7a9e3f8a49f63,5af3] [c.v.e.s.c.c.i.BundleLocalizationTools,dm-exec-13] Problem handling Error code [ATTACH_TZ_WITH_TNP_FAILED] with message [Error wile attaching transport zone {} with transport node profile in NSX {}]. Arguments: [avn-vlan-tz] [nsxt-fqdn]
java.lang.IllegalArgumentException: can't parse argument number:
        at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1454)
        at java.base/java.text.MessageFormat.applyPattern(MessageFormat.java:492)
        at java.base/java.text.MessageFormat.<init>(MessageFormat.java:371)
        at com.vmware.evo.sddc.common.core.i18n.BundleLocalizationTools.getLocalizedMessage(BundleLocalizationTools.java:80)
        at com.vmware.evo.sddc.common.core.i18n.BundleLocalizationTools.getLocalizedMessage(BundleLocalizationTools.java:34)
        at com.vmware.evo.sddc.common.core.i18n.LocalizationTools.getDefaultMessage(LocalizationTools.java:156)
        at com.vmware.evo.sddc.common.core.error.ErrorLocalizationTools.getDefaultMessage(ErrorLocalizationTools.java:195)
        at com.vmware.evo.sddc.common.core.error.ErrorCodePackImpl.buildDefaultMessage(ErrorCodePackImpl.java:88)
        at com.vmware.evo.sddc.common.core.error.LocalizableRuntimeException.getInternalErrorMessage(LocalizableRuntimeException.java:222)
Caused by: java.lang.NumberFormatException: For input string: ""
        at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:67)
        at java.base/java.lang.Integer.parseInt(Integer.java:678)
        at java.base/java.lang.Integer.parseInt(Integer.java:786)
        at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1452)
        ... 30 common frames omitted

yyyy-mm-ddThh:mm:ss ERROR [vcf_dm,68302356f6cc505f94d7a9e3f8a49f63,5af3] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-13]  [3P55C2] ATTACH_TZ_WITH_TNP_FAILED Error code [ATTACH_TZ_WITH_TNP_FAILED] with message [Error wile attaching transport zone {} with transport node profile in NSX {}]. Arguments: [avn-vlan-tz] [nsxm-fqdn]
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Error code [ATTACH_TZ_WITH_TNP_FAILED] with message [Error wile attaching transport zone {} with transport node profile in NSX {}]. Arguments: [avn-vlan-tz] [nsxt-fqdn]
        at com.vmware.vcf.common.fsm.plugins.nsxt.policy.action.AttachTransportZoneWithTransportNodeProfileAction.execute(AttachTransportZoneWithTransportNodeProfileAction.java:123)
        at com.vmware.vcf.common.fsm.plugins.nsxt.policy.action.AttachTransportZoneWithTransportNodeProfileAction.execute(AttachTransportZoneWithTransportNodeProfileAction.java:36)
Caused by: java.lang.NullPointerException: Cannot invoke "com.vmware.vcf.common.nsxt.sdk.client.model.TransportNodeCollection.getTransportNodeProfileId()" because "transportNodeCollection" is null

Environment

VMware Cloud Foundation 5.x

Cause

Transport Node collection is not present for the cluster in the NSX-t manager, indicating there is no active Transport Node Profile Applied on the cluster. To validate the Applied Profile is empty for the cluster:

• NSX Manager UI, System > Fabric > Hosts > Clusters > Applied profile is empty. 

• NSX Manager UI, System > Fabric > Hosts > Transport Node Profile > Applied clusters value is 0.

 

Resolution

The Task: AttachTransportZoneWithTransportNodeProfileAction, finds the active Transport Node Collection which contains the active TNP applied on the cluster. And then updates the Vlan Transport Zone in the Transport Node Profile. There should be Overlay Transport Zone which was created by VCF orchestration should be present on the system.

If there TNP is not applied on the cluster, follow the below steps to perform it manually from the NSX UI.

1. Make sure all the cluster Transport Node State is Healthy. (Login to NSX Manager UI, System > Fabric > Hosts > Clusters > Check the Node Status)

2. Make sure all the cluster NSX configuration is a Success. (NSX Manager UI, System > Fabric > Hosts > Clusters > NSX Configuration Column)

3. Verify if Applied Profile is empty. If this is the case, then Go to Transport Node Profile and look for the transport node profile, the name of the profile should match vcenter name + cluster name (vcf inventory names).

Note - If it does not exists, then we may have to re-create one which should be exactly same as transport node configuration. 

4. Apply this profile on to the cluster 

• Select the Cluster > Configure NSX.

• In the NSX Installation, Drop down the list and select the TNP.

• Once the configuration is complete, go back System > Fabric > Hosts > Clusters > Applied profile. You should see the TNP there -

6. Retry the failed workflow.