Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3289

Interface name blank on PPP interface on Mikrotik device

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller, Ports
    • None
    • Linux CentOS 7.7.1908
      PHP Version 7.1.33
      php-fpm enabled
      Opcache enabled

    Description

      Hi support,

      we started to move our PPP sessions from our customer from a old Cisco device to a couple of brand new Mikrotik CCR with the LAC-LNS configuration, so every PPP sessione is generated as an l2tp interface with the username included. Everything is fine except on the web interface, the PPP interfaces on the mikrotik device have the name blank.

      So if You go on the device and watch the Port menu, what you can see is a long list of interfaces without name, and if You click on one of those, You can see the graph populated but the interface name is blank.

      If You search on those interface, it's listed in the search box, but when You click on the interface, it will show the graph page of that interface, correctly graphed but the name is blank.

      I've tried to run the discovery and the poller manually on those mikrotik device, and the ppp interface name are reported correctly.

      It's just an hypothesis, but the interface name is like  <l2tp-tartufi.fioriti@wireless.fibering.it> ,

      the <> is included in the interface name, is it possibile that this break the generation of the html page ?

      Attachments

        1. observium_blank_interface_name.png
          observium_blank_interface_name.png
          74 kB
        2. observium_blank_interface_name2.png
          observium_blank_interface_name2.png
          70 kB
        3. discovery_debug.log
          414 kB
        4. myagent.snmpwalk
          6.49 MB

        Activity

          [OBS-3289] Interface name blank on PPP interface on Mikrotik device
          landy Mike Stupalov added a comment -

          SUre, incorrect escaping for port labels,
          fixed in r10440.

          landy Mike Stupalov added a comment - SUre, incorrect escaping for port labels, fixed in r10440.
          fibering Fibering System Administrator added a comment -

          Attached

          discovery_debug.log

          myagent.snmpwalk

          fibering Fibering System Administrator added a comment - Attached discovery_debug.log myagent.snmpwalk
          fibering Fibering System Administrator added a comment -

          Sorry for the delay, here the files You asked for.

          fibering Fibering System Administrator added a comment - Sorry for the delay, here the files You asked for.
          landy Mike Stupalov added a comment -

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • Additionally please do and attach these debug: 

            ./discovery.php -d -h <device>

          landy Mike Stupalov added a comment - Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. Additionally please do and attach these debug: ./discovery.php -d -h <device>

          People

            landy Mike Stupalov
            fibering Fibering System Administrator
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: