Transport Nodes Briefly Report Failed Configuration State During Transport Node Realization in VMware NSX
search cancel

Transport Nodes Briefly Report Failed Configuration State During Transport Node Realization in VMware NSX

book

Article ID: 447452

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Multiple Transport Nodes (TNs) briefly report a Failed configuration state during transport node realization. This occurs due to conflicting Logical Switch state updates during full synchronization of the logical switches to vCenter Server (VC)
  • Multiple Transport Nodes show hostConfigStatus as FAILED with the following message:
    LogicalSwitch full-sync: Failed to execute the LogicalSwitch full-sync to VC.
  • The Logical Switch (LS) state for discovered logical switches may be marked as Failed.
  • The issue auto-rectifies without manual intervention within subsequent realization retries (typically 5–10 minutes).

Relevant Log Entries (proton / nsxapi.log):

2026-06-14T00:07:11.906Z  INFO L2HostConfigTaskExecutor3 TransportNodeAsyncUtils 77434 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Found TZs have changed for TN TransportNode/########-d98f-####-a9e5-c6########## HostSwitch ## ## 9d ## 8c ## a8 58-## ba ## 8c 32 ## ea ##. DesiredState TZs [########-7792-####-a922-c7##########] , RealizedState TZs [########-9ae5-####-adab-4b##########, ########-7792-####-a922-c7##########, ########-9ae5-####-adab-4b##########]
...
2026-06-14T00:07:14.155Z  INFO L2HostConfigTaskExecutor3 TransportNodeAsyncServiceImpl 77434 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Performing LogicalSwitch full-sync to VC
2026-06-14T00:07:14.155Z  INFO L2HostConfigTaskExecutor3 LogicalSwitchStateServiceImpl 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Start to sync all logicalswitches to VC.
2026-06-14T00:07:14.155Z  INFO L2HostConfigTaskExecutor3 LogicalSwitchStateServiceImpl 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] syncAllLogicalSwitchesToVc #addedVDSLogicalSwitch : 0
2026-06-14T00:07:14.155Z  INFO L2HostConfigTaskExecutor3 LogicalSwitchStateServiceImpl 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] no issue exsits during creation
2026-06-14T00:07:14.155Z  INFO L2HostConfigTaskExecutor3 LogicalSwitchStateServiceImpl 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] syncAllLogicalSwitchesToVc #removedVDSLogicalSwitch : 1
2026-06-14T00:07:14.155Z  INFO L2HostConfigTaskExecutor3 NsxPortgroupExecuteVcUtils 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] dvsId ## ## 9d ## 8c ## a8 58-## ba ## 8c 32 ## ea ## found 7 security only LSs

2026-06-14T00:07:14.162Z  INFO L2HostConfigTaskExecutor3 LogicalSwitchStateServiceImpl 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated LogicalSwitchState to : failed for Discovered LS

2026-06-14T00:07:14.172Z  INFO L2HostConfigTaskExecutor3 LogicalSwitchStateServiceImpl 77434 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated LogicalSwitchState to : failed for Discovered LS

...
2026-06-14T00:07:14.257Z  WARN L2HostConfigTaskExecutor3 ObjectsView 77434 TXEnd[TX[4c69]] Aborted Exception
org.corfudb.runtime.exceptions.TransactionAbortedException: TX ABORT  | Snapshot Time = Token(epoch=376, sequence=3832995976) | Failed Transaction ID = ########-549c-####-8b03-cd########## | Offending Address = 3832995986 | Conflict Key = 6248A8946E7BA0DF | Conflict Stream = nsx$LogicalSwitchState | Cause = CONFLICT | Time = 102 ms
        at org.corfudb.runtime.view.StreamsView.append(StreamsView.java:180) ~[?:?]
        at org.corfudb.runtime.view.StreamsView.append(StreamsView.java:233) ~[?:?]
        at org.corfudb.runtime.view.StreamsView.append(StreamsView.java:244) ~[?:?]
        at org.corfudb.runtime.object.transactions.OptimisticTransactionalContext.getConflictSetAndCommit(OptimisticTransactionalContext.java:223) ~[?:?]
        at org.corfudb.runtime.object.transactions.WriteAfterWriteTransactionalContext.commitTransaction(WriteAfterWriteTransactionalContext.java:34) ~[?:?]
        at org.corfudb.runtime.view.ObjectsView.TXEnd(ObjectsView.java:162) ~[?:?]
        at org.corfudb.runtime.collections.TxnContext.commit(TxnContext.java:793) ~[?:?]

Environment

VMware NSX

Cause

During Transport Node realization, NSX Manager incorrectly identifies the internal, system-created security Transport Zone (TZ) which is automatically generated for Distributed Firewall (DFW) configurations as being removed.

As a result, the manager attempts to update the discovered Logical Switches associated with this TZ to a failed status. When multiple Transport Nodes concurrently attempt to modify the state of the exact same Logical Switch, it causes write conflicts in the Corfu database, culminating in TransactionAbortedException or StaleRevisionUpdateException errors.

Resolution

This issue is resolved in VMware NSX 4.2.5.

Workaround:
No manual workaround or database remediation is required. The configuration failure is transient and automatically self-resolves within 5 to 10 minutes during subsequent scheduled Transport Node realization retry loops.

Powered by Wolken Software