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

fix discovery BGP on Huawei VRP

Details

    • Help
    • Resolution: Cannot Reproduce
    • Minor
    • None
    • Professional Edition
    • Discovery

    Description

      I have Huawei S6330-H48X6C on Huawei Versatile Routing Platform Software, Version 5.170 (S6330 V200R021C00SPC100).
      I setup OSPF, BGP and VRF's on this device, but Observium discover only VRF.

      There is some problem with bgp discovery.

      It seems that observium can't detect localAS and that why there is "No BGP on host" during discovery.

      I manually disable check for local AS (line 134 in includes/discovery/bgp-peers.inc.php) and BGP session was discovered.

      Attachments

        Issue Links

          relates to

          Improvement - An improvement or enhancement to an existing feature or task. OBS-2434 BGP Prefix count monitoring on Huawei

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            [OBS-4196] fix discovery BGP on Huawei VRP
            landy Mike Stupalov added a comment -

            It seems as your local changes

            landy Mike Stupalov added a comment - It seems as your local changes
            mtivi Martyushev Tim added a comment -

            send snmpwalk to landy in private message

            mtivi Martyushev Tim added a comment - send snmpwalk to landy in private message
            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 -ObentxU <hostname> .1 > myagent.snmpwalk
              		 
              snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -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
              mtivi Martyushev Tim
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: