TNDL Messages

TNDL-1000

Message: TunnelMgr initialized successfully.

Message Type: LOG

Severity: INFO

Probable Cause: Indicates that the Data Center Ethernet (DCE) tunnel manager has been initialized.

Recommended Action: None

TNDL-1001

Message:Failed to allocate memory: (<function name>).

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that the specified function has failed to allocate memory.

Recommended Action: Check the memory usage on the switch using the show process memory command.

Restart or power cycle the switch.

TNDL-1005

Message: TunnelMgr startup failed.

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that the Data Center Ethernet (DCE) tunnel manager encountered an unexpected severe error during basic startup and initialization.

Recommended Action: Restart or power cycle the switch.

If the problem persists, download a new firmware version using the firmware download command.

TNDL-1006

Message: Tunnel <tunnel ID> creation failed.

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that the tunnel creation was unsuccessful.

Recommended Action: Technical support is required.

TNDL-1007

Message: Tunnel <tunnel ID> deletion failed.

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that the tunnel deletion was unsuccessful.

Recommended Action: Technical support is required.

TNDL-2001

Message: NSX controller pushed more than <Safe Ucast_Macs_Remote limit> Ucast_Macs_Remote objects. This may result in unexpected traffic behavior.

Message Type: LOG

Severity: WARNING

Probable Cause: Indicates that the switch may be connecting to NSX controllers having huge number of configurations which are beyond scale capacity of the switch. There could be traffic loss or unexpected behavior.

Recommended Action:Update configurations in NSX controller accordingly.

TNDL-2011

Message: Delete duplicate Mcast_Macs_Remote entry; MAC=\"<Multicast MAC>\", logical_switch=\"<Logical_Switch name>\".

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates an unexpected error while communicating to the VMware NSX controller.

Recommended Action:Undo all operations and try again.

TNDL-2012

Message: Local MAC \"<MAC address>\" already exists in Ucast_Macs_Remote table; skipping write to Ucast_Macs_Local.

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that Layer 2 system (L2SYS) has notified a MAC entry that was learned from the VMware NSX controller.

Recommended Action:Undo all operations and try again.

TNDL-2013

Message: Failed to cleanup Overlay Gateway Configuration during reconcile.

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that cleanup of tunnels or local MAC entries has failed in the back-end.

Recommended Action:Undo all operations and try again.

TNDL-2014

Message: Tunnel id conflict detected for one or more tunnels. Automatic recovery initiated.

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that tunnel ID conflict is detected for one or more tunnels.

Recommended Action:The system initiates automatic recovery.

TNDL-2015

Message: Tunnel creation failed (source <> destination <>) due to max number of tunnels reached(<>).

Message Type: LOG

Severity: ERROR

Probable Cause: Indicates that tunnel creation failed as max supported number of tunnels reached.

Recommended Action:Delete some other tunnels and retry.

TNLD-2016

Message: Tunnel resource has reached user configured high threshold limit.

Message Type: LOG

Severity: INFO

Probable Cause: Indicates that the number of active tunnels has crossed the user configured high threshold level.

Recommended Action: Close some active tunnels.

TNDL-2017

Message: Tunnel resource dropped below user configured low threshold limit.

Message Type: LOG

Severity: INFO

Probable Cause: Indicates that the number of active tunnels has dropped below the user configured low threshold level.

Recommended Action: No action is required.