Post upgrading to NSX version 4.0.x, in ESXi 8.0 transport node's nsx-syslog.log, we see excessive loglines of payload-type data.
search cancel

Post upgrading to NSX version 4.0.x, in ESXi 8.0 transport node's nsx-syslog.log, we see excessive loglines of payload-type data.

book

Article ID: 376965

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • Post upgrading to NSX version 4.0.x, in ESXi 8.0 transport node's nsx-syslog.log, we see excessive loglines of payload-type data, identifiable by the [+] sign.|

  • In the nsx-syslog.log file, the payload-type data is logged similar to as shown below:

    2024-07-30T17:12:43.981Z In(182) cfgAgent[2788014]: NSX 2788014 - [nsx@6876 comp="nsx-controller" subcomp="cfgAgent" tid="C0FC9C80" level="info"] Decoder: Received LOG_SWITCH_FIB VTEP old msg ########-####-####-####-########7743: vtep {
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: vtep_ip {
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: ipv4: ##.##.##.##
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: }
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: vtep_label {
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: label: 88065
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: }
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: segment_id {
    2024-07-30T17:12:43.981Z In(182)[+] cfgAgent[2788014]: ipv4: ##.##.##.##

    2024-07-30T17:12:44.399Z In(182) nestdb-server[2788056]: NSX 2788056 - [nsx@6876 comp="nsx-esx" subcomp="nsx-nestdb" tid="2788056" level="INFO"] ExtractRepeatedDelta (Patch Op): vtep {
    2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: self {
    2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: op: APPEND
    2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: }
    2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: }
    2024-07-30T17:12:44.399Z In(182)[+] nestdb-server[2788056]: mac {

  • The nsx-syslog.log rotation now happens every 3-4 minutes instead of every 4-5 hours in the previous versions:

    4.0.x version:

    2024-07-30T15:19:35.959Z -> 2024-07-30T15:22:01.918Z -> ./var/run/log/nsx-syslog.27 -> 4.0M -> 424134 lines
    2024-07-30T15:22:01.918Z -> 2024-07-30T15:25:17.970Z -> ./var/run/log/nsx-syslog.26 -> 4.3M -> 417892 lines
    2024-07-30T15:25:17.970Z -> 2024-07-30T15:28:42.212Z -> ./var/run/log/nsx-syslog.25 -> 4.2M -> 416079 lines

    Previous versions:

    2024-07-24T05:14:13.076Z -> 2024-07-24T10:47:20.571Z -> ./var/run/log/nsx-syslog.27 -> 4.8M -> 146620 lines
    2024-07-24T10:47:20.571Z -> 2024-07-24T16:29:46.935Z -> ./var/run/log/nsx-syslog.26 -> 4.7M -> 147576 lines
    2024-07-24T16:29:46.954Z -> 2024-07-24T22:09:03.958Z -> ./var/run/log/nsx-syslog.25 -> 4.7M -> 147528 lines

  • Such excessive logging affects the data retention period and utilizes more space, especially when the logs are being forwarded to a syslog collector.

Environment

VMware NSX 4.x

Cause

In ESXi 8.0, the log line has embedded newline character which, results in logging in multiple lines.

Resolution

This issue will be resolved in the future product release.
Currently, there is no workaround.