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

Switch Port Reporting Incorrectly in Map

Details

    • Help
    • Resolution: Not A Bug
    • Trivial
    • None
    • CE-22.5
    • Graphs, Ports

    Description

      I've got an issue where my Netgear GS752TPv2 switches have the correct ifDesc and ifName in Port data but ifVlan is NULL. These are connected to HP procurve and Aruba switches which work flawlessly.

      LLDP neighbor information is correct in the Netgear switch table via the webUI.

      I can't be certain but this seems to mess up the network map and create breaks where these specific models are working.

      Attachments

        1. ObserviumLLDP.jpg
          44 kB
          Matt Murphy
        2. ObserviumSwitch.jpg
          198 kB
          Matt Murphy

        Activity

          [OBS-4603] Switch Port Reporting Incorrectly in Map
          hazmatguy Matt Murphy added a comment -

          So sorry for any of your wasted time, I re-enabled [Q-BRIDGE-MIB] but also found a list of supported MIBs. Looks like [LLDP-MIB] isn't supported by this switch.

          NetGear GS752TPv2 - Supported MIBs

          BRIDGE-MIB The Bridge MIB module for managing devices that support IEEE 802.1D
          ENTITY-MIB The MIB module for representing multiple logical entities supported by a single SNMP agent.
          EtherLike-MIB The MIB module to describe generic objects for Ethernet-like network interfaces.
          IF-MIB The MIB module to describe generic objects for network interface sub-layers.
          P-BRIDGE-MIB The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998.
          Q-BRIDGE-MIB The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE 802.1Q-1998.
          RFC1213-MIB Groups in MIB-II, as defined by RFC 1213.
          RFC-1215 It has been created solely for the purpose of allowing other modules to correctly import the TRAP-TYPE clause from RFC-1215 where it should be imported from.
          RMON-MIB Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network.
          SNMP-COMMUNITY-MIB This MIB module defines objects to help support coexistence between SNMPv1, SNMPv2c, and SNMPv3.
          SNMP-NOTIFICATION-MIB This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of notifications.
          SNMP-TARGET-MIB This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of SNMP messages.
          SNMP-USER-BASED-SM-MIB The management information definitions for the SNMP User-based Security Model.
          SNMPv2-MIB The MIB module for SNMP entities.
          SNMP-VIEW-BASED-ACM-MIB The management information definitions for the View-based Access Control Model for SNMP.
          POWER-ETHERNET-MIB The MIB module for managing Power Source Equipment (PSE) works according to the IEEE 802.3 Powered Ethernet standard.
          hazmatguy Matt Murphy added a comment - So sorry for any of your wasted time, I re-enabled [Q-BRIDGE-MIB] but also found a list of supported MIBs. Looks like [LLDP-MIB] isn't supported by this switch. NetGear GS752TPv2 - Supported MIBs BRIDGE-MIB The Bridge MIB module for managing devices that support IEEE 802.1D ENTITY-MIB The MIB module for representing multiple logical entities supported by a single SNMP agent. EtherLike-MIB The MIB module to describe generic objects for Ethernet-like network interfaces. IF-MIB The MIB module to describe generic objects for network interface sub-layers. P-BRIDGE-MIB The Bridge MIB Extension module for managing Priority and Multicast Filtering, defined by IEEE 802.1D-1998. Q-BRIDGE-MIB The VLAN Bridge MIB module for managing Virtual Bridged Local Area Networks, as defined by IEEE 802.1Q-1998. RFC1213-MIB Groups in MIB-II, as defined by RFC 1213. RFC-1215 It has been created solely for the purpose of allowing other modules to correctly import the TRAP-TYPE clause from RFC-1215 where it should be imported from. RMON-MIB Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. SNMP-COMMUNITY-MIB This MIB module defines objects to help support coexistence between SNMPv1, SNMPv2c, and SNMPv3. SNMP-NOTIFICATION-MIB This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of notifications. SNMP-TARGET-MIB This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of SNMP messages. SNMP-USER-BASED-SM-MIB The management information definitions for the SNMP User-based Security Model. SNMPv2-MIB The MIB module for SNMP entities. SNMP-VIEW-BASED-ACM-MIB The management information definitions for the View-based Access Control Model for SNMP. POWER-ETHERNET-MIB The MIB module for managing Power Source Equipment (PSE) works according to the IEEE 802.3 Powered Ethernet standard.
          landy Mike Stupalov added a comment -

          Vlans not discovered, because you have disabled Q-BRIDGE-MIB.

          MIB [Q-BRIDGE-MIB] disabled in device config.

          As I see in snmpdump - device not report LLDP information at all.

          landy Mike Stupalov added a comment - Vlans not discovered, because you have disabled Q-BRIDGE-MIB. MIB [Q-BRIDGE-MIB] disabled in device config. As I see in snmpdump - device not report LLDP information at all.
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

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

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

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

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

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            hazmatguy Matt Murphy
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: