Details

    • Improvement
    • Resolution: Fixed
    • Major
    • None
    • Professional Edition
    • Poller

    Description

      Hi,

      the FabricEngine Devices from Extreme Networks do have a very long port_label, e. g.:

      Extreme Networks 5420M-48W-4YE-FabricEngine - 1000BaseTX Port 1/1

      So i modified the port_label in includes/definitions/os/extreme.inc.php

      Now the port_label is: 1000BaseTX Port 1/1 which sounds good.

      I attached a patch file.

      Attachments

        Activity

          [OBS-4940] Extreme FabricEdge Devices Portlabel
          landy Mike Stupalov made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]

          Improved in r13769.
          Pls note, you regex was little incorrect, I changed it.

          landy Mike Stupalov added a comment - Improved in r13769. Pls note, you regex was little incorrect, I changed it.
          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 ]

          this is not needed

          FloMeyer Florian Meyer added a comment - this is not needed
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]

          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.
          FloMeyer Florian Meyer created issue -

          People

            landy Mike Stupalov
            FloMeyer Florian Meyer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: