NSX Manager - Multiple and constant LspInterVtep messages.
Article ID: 434946
Updated On:
Products
Issue/Introduction
After upgrading to VMware NSX 4.2.3.x, you observe a high frequency of the following entries in the NSX Manager /var/log/syslog.log:
info <> NSX 77732 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] logicalSwitch is LogicalSwitch [id=LogicalSwitch/<LS_ID>, name=<SEG_NAME>, segmentPath=/infra/segments/<SEG_NAME>, switchType=DEFAULT, transportZoneId=TransportZone/<TZ_ID>, vlan=100, adminState=UP, switchingProfileIds=null, switchMode=STANDARD, switchType=DEFAULT, uplinkTeamingPolicyName=null, extraConfigs=[ ], originId=null, originType=null, org=null, project=null, vpc=null, skipDefaultProfile=[]] or No EdgeTNs [] found. Skipping logicalPort update.info <> NSX 77732 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] LspInterVtep flag true logicalPort LogicalPort [id=<ID>, intentPath=/infra/segments/<SEG_NAME>/ports/default:<ID>, logicalPortState=UP, ephemeral=true, logicalSwitchId=LogicalSwitch/<LS_ID>, transportZoneId=TransportZone/<TZ_ID>, transportZoneType=VLAN, attachmentId=<ATTACHMENT_ID>, attachmentType=vif, internalPortAttachment=null, switchingProfileIds=[], switchMode=STANDARD, extraConfigs=null, systemExtraConfigs=null, internalId=, initState=null, tags=null, pendingConfigFromHostd=true, addressBindings=null, ignoreAddressBindings=null, isIndependentVifPort=false, context=null, isEsxVmk=false, isDvport=false, skipDefaultProfiles=[]], logicalSwitch LogicalSwitch [id=LogicalSwitch/<LS_ID>, name=damm-vl-net-servicio-datacenter, segmentPath=/infra/segments/<SEG_NAME>, switchType=DEFAULT, transportZoneId=TransportZone/<TZ_ID>, vlan=100, adminState=UP, switchingProfileIds=null, switchMode=STANDARD, switchType=DEFAULT, uplinkTeamingPolicyName=null, extraConfigs=[ ], originId=null, originType=null, org=null, project=null, vpc=null, skipDefaultProfile=[]], edgeTransportNodes []
- The logs are marked with level="INFO".
- These messages appear in pairs for logical ports and logical switch containers.
- There is no reported impact on the data plane or control plane functionality.
Environment
VMware NSX 4.2.3.x and higher
Cause
This behavior is expected in NSX 4.2.3 and later versions. These messages are informational only and do not indicate a failure or misconfiguration.
INFO messages are generated each time the Discovery Agent is triggered to re-report all VNIs for the VM at 3–5 minute intervals, even when no changes have occurred on the other interfaces.
In some cases, the guest OS sees failure in getting DHCP IP address. Depending on the setting, the NetworkManager may continuously retry getting the DHCP IP address. This causes the Discovery Agent to see multiple messages.
Resolution
These logs can be safely ignored as they have no impact on system performance or network traffic.
Broadcom Engineering is aware of the high frequency of these logs and is tracking a request to lower the log level or reduce the frequency of these specific entries in a future release to reduce log noise.
Workaround:
No workaround is required, as there is no functional impact. Ensure that VM interfaces are either properly configured or disabled if they are not in use.
Feedback
