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

Incorrect interface vlan information on Cisco Small Business devices

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • None
    • Poller
    • None
    • Cisco Small Business 2.5.0.90 (SG350-10-K9)

    Description

      This looks related to ticket OBS-4391 - which is closed as "resolved" but appears to be still an issue. 

      What version of Observium: 23.8.12912 (2nd August 2023)

      When did this start:
      This was working before an update to Observium sometime in Q1 of 2023, after that time this issue appeared. 

      Issue description:

      On all of our 200+ Cisco Small Business switches the port vlan information is incorrectly reporting as "VLAN1".  This is visible when viewing port details. When viewing VLANs details the vlans are correctly discovered, but ports with vlan configuration are visible  twice - once in vlan1 and once in their correct vlan. 

      Attached documentation:
      I've attached the output of 

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

      I've also attached screenshots of an example device, along with the interface config from this device. Additionally, I've attached the output of the port info obtained through an API call to the endpoint "/ports/{port_id}/". In this output you can see the port is reporting ifVlan = 1 

      Attachments

        1. all ports page shows all vlan 1.png
          all ports page shows all vlan 1.png
          200 kB
        2. get_port_info.txt
          3 kB
        3. interface config.txt
          0.4 kB
        4. specific port page shows vlan 1.png
          specific port page shows vlan 1.png
          144 kB
        5. vlans page shows correct info.png
          vlans page shows correct info.png
          116 kB

        Issue Links

          Activity

            [OBS-4606] Incorrect interface vlan information on Cisco Small Business devices
            landy Mike Stupalov made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

            It should be polled in r13000.

            But here used "slow" way, with many Oids.
            Check polling times for ports module.

            landy Mike Stupalov added a comment - It should be polled in r13000. But here used "slow" way, with many Oids. Check polling times for ports module.
            landy Mike Stupalov made changes -
            Status Original: In Review [ 10101 ] New: In Progress [ 3 ]
            landy Mike Stupalov made changes -
            Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]

            snmpwalk output sent via email. 

            Dustin.Sanders Dustin Sanders added a comment - snmpwalk output sent via email. 
            landy Mike Stupalov made changes -
            Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]

            Yah, I forgot that this devices have troubles with full snmp walks..

            pls try walk only vlan specific mib (.1.3.6.1.4.1.9.6.1.101.48):

            snmpwalk -v3 <your_v3_auth> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.9.6.1.101.48 >> myagent.snmpwalk

            landy Mike Stupalov added a comment - Yah, I forgot that this devices have troubles with full snmp walks.. pls try walk only vlan specific mib (.1.3.6.1.4.1.9.6.1.101.48): snmpwalk -v3 <your_v3_auth> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1.9.6.1.101.48 >> myagent.snmpwalk

            Hey Mike, sorry for the delayed response. I ran into an issue running the command since our devices are using snmp v3, once I figured out how to run it with the authentication creds I needed, the walk seems to be running forever. (After 10 mins of my terminal hanging, I stopped it and ran it again without exporting to "myagent.snmpwalk" so I could see what was happening, and then I let it run for a solid hour and it showed no sign of stopping, so something must be wrong.) 

            Is there some other way I can provide you the info you need to see what's happening with how the vlans are being reported by Observium?

            Dustin.Sanders Dustin Sanders added a comment - Hey Mike, sorry for the delayed response. I ran into an issue running the command since our devices are using snmp v3, once I figured out how to run it with the authentication creds I needed, the walk seems to be running forever. (After 10 mins of my terminal hanging, I stopped it and ran it again without exporting to "myagent.snmpwalk" so I could see what was happening, and then I let it run for a solid hour and it showed no sign of stopping, so something must be wrong.)  Is there some other way I can provide you the info you need to see what's happening with how the vlans are being reported by Observium?
            Dustin.Sanders Dustin Sanders made changes -
            Attachment Original: observium poller debug 356.txt [ 20899 ]
            landy Mike Stupalov made changes -
            Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]

            People

              landy Mike Stupalov
              Dustin.Sanders Dustin Sanders
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: