Enterasys WLC C5110-2 Wireless Tab

ziodona85 commented 2 years ago

Behaviour

i have a problem with Enterasys WLC. I have 2 Enterasys WLC: one with firmware 09.21.19.0003 and one with Firmware 08.11.03.0024.

The problem is: with Firmware 08.11.03.0024 it was recognized as Enterasys switch and librenms doesn't show wireless tab. With second firmware was recognized as Extreme WLC and librenms show wireless tab.

i am tryng to solve myself the problem and i have modified files /opt/librenms/LibreNMS/OS/Enterasys.php and /opt/librenms/includes/definitions/enterasys.yaml

Steps to reproduce this issue

cp /opt/librenms/LibreNMS/OS/Ewc.php /opt/librenms/LibreNMS/OS/Enterasys.php cp /opt/librenms/mibs/ewc/HIPATH-WIRELESS-* /opt/librenms/mibs/enterasys/ cp /opt/librenms/includes/definitions/ewc.yaml /opt/librenms/includes/definitions/enterasys.yaml vi /opt/librenms/LibreNMS/OS/Enterasys.php vi /opt/librenms/includes/definitions/enterasys.yaml

Expected behaviour

If i do a manual debug discovery of the node from LibreNMS node GUI, the Wireless tab appear correctly.

Actual behaviour

When LibreNMS do autodiscovery after few hours and the tab disappear.

Configuration

Docker version (type docker --version) : Docker version 20.10.9, build c2ea9bc
Docker compose version if applicable (type docker-compose --version) : docker-compose version 1.29.2, build 5becea4c
Platform (Debian 9, Ubuntu 18.04, ...) : Ubuntu 20.04.3 LTS
System info (type uname -a) : Linux pvl-netflow-as1 5.4.0-88-generic #99-Ubuntu SMP Thu Sep 23 17:29:00 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Include all necessary configuration files : docker-compose.yml, .env, ...

Docker info

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Build with BuildKit (Docker Inc., v0.6.3-docker)
  scan: Docker Scan (Docker Inc., v0.8.0)

Server:
 Containers: 13
  Running: 12
  Paused: 0
  Stopped: 1
 Images: 11
 Server Version: 20.10.9
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
 Swarm: inactive
 Runtimes: runc io.containerd.runc.v2 io.containerd.runtime.v1.linux
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 5b46e404f6b9f661a205e28d59c982d3634148f8
 runc version: v1.0.2-0-g52b36a2
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.0-88-generic
 Operating System: Ubuntu 20.04.3 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 12
 Total Memory: 31.31GiB
 Name: pvl-netflow-as1
 ID: DSAA:TR4D:EBCB:45CU:YVKW:TX7E:MEZB:UAMN:BYU3:RVJV:646L:FLPV
 Docker Root Dir: /cdmdati/Docker/docker_overlay2
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support

Logs

> Container logs (set LOG_LEVEL to debug if applicable)

ziodona85 commented 2 years ago

I attach files for your need. I would want to know the difference from autodiscovery from poller and discovery from capture debug. I don't unsderstand. Thanks.

librenms.env.txt configurazione SNMP Aruba-Enterasys.txt docker-compose.yml.txt env.txt poller_enterasys.txt discovert_enterasys.txt

crazy-max commented 1 year ago

Don't think this is related to the image but LibreNMS itself. I think you should instead open an issue on https://github.com/librenms/librenms.

librenms / docker