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

On Huawei switches S5700 & S6700 LAg ports not showing participants

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Discovery
    • None
    • Huawei S6720, S6730 and S5720

    Description

      When navigating through device ports, Eth-Trunks (Link Aggrtegation) do not show interfaces participating on the LACP bundle.

      This feature is available on other devices (like CloudEngine8800).

      Attachments

        Activity

          [OBS-3816] On Huawei switches S5700 & S6700 LAg ports not showing participants
          landy Mike Stupalov added a comment -

          I mean rediscovery device (not -u):

          ./discovery.php -d -h <device>
          		 
          # or without debug
          		 
          ./discovery.php -h <device>

          landy Mike Stupalov added a comment - I mean rediscovery device (not -u): ./discovery.php -d -h <device> # or without debug ./discovery.php -h <device>
          hernanm Hernan Moguilevsky added a comment -

          Hi Mike,

          I've updated to r11480 (21.7.11450), did the discovery -u and discovery to devices.

          Still don't see LAg members on Eth-Trunk ports.

          Am I missing something?

          Thanks

          hernanm Hernan Moguilevsky added a comment - Hi Mike, I've updated to r11480 (21.7.11450), did the discovery -u and discovery to devices. Still don't see LAg members on Eth-Trunk ports. Am I missing something? Thanks
          landy Mike Stupalov added a comment -

          Improved in r11480.

          landy Mike Stupalov added a comment - Improved in r11480.
          hernanm Hernan Moguilevsky added a comment -

          Added S6720.

          It should be the same for 5720 and 6730.

          hernanm Hernan Moguilevsky added a comment - Added S6720. It should be the same for 5720 and 6730.
          landy Mike Stupalov added a comment -

          yah, huawei not like to use common mibs.
          need snmpdump for device as bot requested.

          landy Mike Stupalov added a comment - yah, huawei not like to use common mibs. need snmpdump for device as bot requested.
          bot Observium Bot 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.

          • 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

          Note, this comment is added automatically.

          bot Observium Bot 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. 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 Note, this comment is added automatically.

          People

            landy Mike Stupalov
            hernanm Hernan Moguilevsky
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: