Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • Enterprise Edition
    • Poller
    • None

    Description

      Cisco WLC does not store any information regarding dissasociated accesspoints, and you have an option to mark an AP as deleted in html/pages/device/wifi/accesspoints.inc.php

      if($accesspoint['ap_status'] == 'down') //if device is down, offer the possibility to delete it from the DB
          {
             if ($_SESSION['userlevel'] > 9)
             {
                     echo '<a class="pull-right" href="#modal-delete-ap-'.$accesspoint['wifi_ap_id'].'" data-toggle="modal" title="Delete Current Access Point"><span><i class="sprite-minus"></i></span></a>';

       

      This works, but there seems to be two places in includes/polling/wifi.inc.php that handles the deletion of AP

       

      Line 105-118 is OK, but line 208-230 just deletes the AP without any regard for the state of the AP being marked as deleted or not

       

      Attached svn.diff

      Attachments

        Activity

          [OBS-4049] Deletion of Cisco AP's
          cheri001 Christian Eriksson added a comment - - edited

          includes/discovery/wifi.inc.php inserts "1" to column "deleted" in table "wifi_aps, so I have made another svn.diff removing those lines, since we loose all historical data when an entity dissapears. Not sure if this is an oversight or intended. If this is intended then just close the case

          Also added some log_events

          cheri001 Christian Eriksson added a comment - - edited includes/discovery/wifi.inc.php inserts "1" to column "deleted" in table "wifi_aps, so I have made another svn.diff removing those lines, since we loose all historical data when an entity dissapears. Not sure if this is an oversight or intended. If this is intended then just close the case Also added some log_events

          wops, wrong diff attached previously, corrected now.

          snmpwalk not necessary here

          cheri001 Christian Eriksson added a comment - wops, wrong diff attached previously, corrected now. snmpwalk not necessary here

          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
            cheri001 Christian Eriksson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: