NSX Configuration Change from multi uplink to single uplink LAG shows "in progress" state

Products

• VMware NSX

Issue/Introduction

Symptoms:

• NSX Configuration Change from multi uplink to single uplink LAG  shows "in progress" state  after changing the uplink profile 

 

• API Call GET /api/v1/transport-nodes/<BME_TN_UUID>/state] , on Bare Metal EDGE may show a a Configuration edit failed with error. Failed to update syslog node configuration edit failed with error. failed to update syslog exporter servers failure_code:16042

 

• Transport node Sync may be stuck with an error log in NSX Manager /var/log/proton/nsxapi

------------------------------------------

2024-03-20T14:50:12.846Z INFO L2HostConfigTaskExecutor1 IPAMUtils 4464 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Releasing the ip [10.235.129.8] from the ip pool [IpPool/########-####-####-####-########a42c].

2024-03-20T14:50:12.847Z INFO L2HostConfigTaskExecutor1 AddressManagementServiceImpl 4464 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Attempting release of id 10.235.129.8 into pool ########-####-####-####-########e598 with delay 120000

2024-03-20T14:50:12.848Z INFO L2HostConfigTaskExecutor1 RangeServiceImpl 4464 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] No Temporary, Permanent or deletion marker found but id 183206152 is allocated. Id must be allocated in older version-HL/GC

2024-03-20T14:50:12.848Z INFO L2HostConfigTaskExecutor1 AddressManagementServiceImpl 4464 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Id 10.235.129.8released into pool ########-####-####-####-########e598

2024-03-20T14:50:12.848Z INFO L2HostConfigTaskExecutor1 IPAMServiceImpl 4464 POOL-MGMT [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Ip Address 10.235.129.8 is released from the range with start 10.235.129.1 and end 10.235.129.125 in the pool IpPool/########-####-####-####-########a42c.

2024-03-20T14:50:12.848Z ERROR L2HostConfigTaskExecutor1 TransportNodeAsyncRequestHandler 4464 FABRIC [nsx@6876 comp="nsx-manager" errorCode="MP100" level="ERROR" subcomp="manager"] TransportNodeConfigTask on host [########-####-####-####-########909e] failed. Abort all unprocessed stages.

org.corfudb.runtime.exceptions.TransactionAlreadyStartedException: An existing transaction is still in progress. TX[ae56]

        at org.corfudb.runtime.collections.TxnContext.txBeginInternal(TxnContext.java:90) ~[?:?]

        at org.corfudb.runtime.collections.TxnContext.<init>(TxnContext.java:79) ~[?:?]

        at com.vmware.nsx.persistence.UfoStore.tx(UfoStore.java:202) ~[?:?]

        at com.vmware.nsx.persistence.UfoStore.tx(UfoStore.java:186) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.MACAMUtils.getUfoDefaultMACAMPool(MACAMUtils.java:219) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.VtepPopulator.releaseVtepResources(VtepPopulator.java:1094) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.VtepPopulator.releaseExistingVteResources(VtepPopulator.java:1032) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.VtepPopulator.releaseAllResources(VtepPopulator.java:1043) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.VtepPopulator.releaseAllResources(VtepPopulator.java:1011) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.TransportNodeAsyncServiceImpl.releaseUnusedVtepResourcesAndSaveTnStateInTransaction(TransportNodeAsyncServiceImpl.java:2447) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.TransportNodeAsyncServiceImpl.releaseUnusedVtepResourcesAndSaveTnStateWithRetry(TransportNodeAsyncServiceImpl.java:2504) ~[?:?]

        at com.vmware.nsx.management.switching.sync.host.TransportNodeAsyncServiceImpl.releaseUnusedVtepResourcesAndSaveTnState(TransportNodeAsyncServiceImpl.java:2407) ~[?:?]

---------------------------

Environment

VMware NSX-T Data Center 3.x

Resolution

• This issue is resolved in VMware NSX-T Data Center 3.2.4
• This issue is resolved in VMware NSX-T Data Center 4.1.2

Additional Information

Impact/Risks:

• Previous VTEP is not removed from the bond created by LAG and may cause data forwarding issue