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

Cisco WLC 9800-40-K9 detected as Network type

Details

    • Improvement
    • Resolution: Duplicate
    • Minor
    • None
    • Professional Edition
    • Discovery, OS, Poller

    Description

      Hello,

      The Cisco hardware C9800-40-K9 is been detected as type=network and not as type=wireless, which is not loading the wireless information.

      Thanks,
      EM

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. OBS-4286 Cisco C9800 isn't recognized as a wireless controller

          • Major - Major loss of function.
          • Resolved

          Activity

            [OBS-4292] Cisco WLC 9800-40-K9 detected as Network type
            emiliomejias Emilio MEJIAS added a comment -

            Hello,
            Any news?
            Thanks,
            EM

            emiliomejias Emilio MEJIAS added a comment - Hello, Any news? Thanks, EM
            landy Mike Stupalov made changes -
            Link New: This issue duplicates OBS-4286 [ OBS-4286 ]
            landy Mike Stupalov made changes -
            Issue Type Original: Library Bug [ 10100 ] New: Improvement [ 4 ]
            Resolution New: Duplicate [ 3 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            landy Mike Stupalov made changes -
            Status Original: Pending Response [ 10000 ] New: In Progress [ 3 ]
            bot Observium Bot made changes -
            Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
            emiliomejias Emilio MEJIAS created issue -
            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
              emiliomejias Emilio MEJIAS
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: