Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-5164

{#SNMPINDEX} incomplete for some SNMP discoveries

    XMLWordPrintable

Details

    • Incident report
    • Resolution: Duplicate
    • Minor
    • None
    • 2.0.0
    • Server (S)
    • None

    Description

      It seems that for the

      {#SNMPINDEX} macro only the last part of the SNMPOID. This works in most cases, where for example the last value in the oid if the ifindex. However, it doesn't work for OIDs where this isn't the case. An example would be:

      - RFC 4273: Definitions of Managed Objects for BGP-4

      $ snmpwalk -v 2c -c xxx xxx bgpPeerRemoteAddr
      BGP4-MIB::bgpPeerRemoteAddr.80.94.64.0 = IpAddress: 80.94.64.0
      BGP4-MIB::bgpPeerRemoteAddr.80.94.64.3 = IpAddress: 80.94.64.3
      BGP4-MIB::bgpPeerRemoteAddr.80.94.64.35 = IpAddress: 0.0.0.0
      BGP4-MIB::bgpPeerRemoteAddr.80.94.65.130 = IpAddress: 80.94.65.130

      As you can see, the remote peer address is user in the OID. But in the zabbix discovery only 0, 3, 35 and 130 are used in the {#SNMPINDEX}

      . This causes a problem for the 3rd in the row, where the bgp session hasn't been established and no remote identifier is known.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              attilla Attilla de Groot
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: