Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-10258

enlinkd prints bridge forwarding table debug messages in output.log

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Major
    • Resolution: Fixed
    • Meridian-2018.1.0, 23.0.0
    • 23.0.0
    • None
    • Security Level: Default (Default Security Scheme)
    • None
    • Horizon - July 11th 2018

    Description

       On a system running 23.0.0-SNAPSHOT, I found the following messages in output.log:

      bft:nodeid:[539], bridgeport:[68], ifindex:[68], vlan:[null] macs:[00c0]
      bft:nodeid:[539], bridgeport:[7], ifindex:[7], vlan:[null] macs:[b41]
      bft:nodeid:[539], bridgeport:[9], ifindex:[9], vlan:[null] macs:[00e]
      bft:nodeid:[539], bridgeport:[14], ifindex:[14], vlan:[null] macs:[00c]
      bft:nodeid:[539], bridgeport:[22], ifindex:[22], vlan:[null] macs:[b41]
      bft:nodeid:[539], bridgeport:[23], ifindex:[23], vlan:[null] macs:[00c]
      bft:nodeid:[539], bridgeport:[55], ifindex:[55], vlan:[null] macs:[00c]
      bft:nodeid:[539], bridgeport:[24], ifindex:[24], vlan:[null] macs:[1cdf]
      bft:nodeid:[539], bridgeport:[56], ifindex:[56], vlan:[null] macs:[00c]
      bft:nodeid:[539], bridgeport:[57], ifindex:[57], vlan:[null] macs:[00c0]
      

      These messages should be removed or logged via a logger rather than using stdout/stderr.

      Attachments

        Activity

          People

            rssntn67 Antonio Russo
            j-white Jesse White
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: