Mtlink-BDCOM

Attached snmpdump unrelated with BDCOM mib files.

We not have any other "related" mib files for this hardware.

Without correct mib files - add support in observium impossible.

You attached snmpdump from some unknown hardware with base OID .1.3.6.1.4.1.50224

For BDCOM base OID must be .1.3.6.1.4.1.3320
(same OID you showed in switch config).

Can you show me Vendor site and link to hardware page?

I hve added Mtlink switch MIB details too

I hve added JSD-JX08 EPON OLT Operating System details

Without snmpdump not possible improve/add support for any device.

Try make snmpdump as described here (by our snmpdump script):
https://docs.observium.org/developing/add_device/#snmp-dump

asad@nbb-nms:/opt/observium$ snmpwalk -v2c -c nbb123 -Cc --hexOutputLength=0 -Ih -ObentxU 192.168.65.249 .1.3.6.1.4.1 > /opt/observium/myagent.snmpwalk
Timeout: No Response from 192.168.65.249
asad@nbb-nms:/opt/observium$ ping 192.168.65.249
PING 192.168.65.249 (192.168.65.249) 56(84) bytes of data.
64 bytes from 192.168.65.249: icmp_seq=1 ttl=247 time=9.93 ms
64 bytes from 192.168.65.249: icmp_seq=2 ttl=247 time=21.2 ms
64 bytes from 192.168.65.249: icmp_seq=3 ttl=247 time=8.01 ms
64 bytes from 192.168.65.249: icmp_seq=4 ttl=247 time=8.21 ms
64 bytes from 192.168.65.249: icmp_seq=5 ttl=247 time=18.9 ms
64 bytes from 192.168.65.249: icmp_seq=6 ttl=247 time=7.95 ms
64 bytes from 192.168.65.249: icmp_seq=7 ttl=247 time=7.79 ms
64 bytes from 192.168.65.249: icmp_seq=8 ttl=247 time=7.99 ms
64 bytes from 192.168.65.249: icmp_seq=9 ttl=247 time=8.20 ms
64 bytes from 192.168.65.249: icmp_seq=10 ttl=247 time=14.2 ms
64 bytes from 192.168.65.249: icmp_seq=11 ttl=247 time=8.12 ms
64 bytes from 192.168.65.249: icmp_seq=12 ttl=247 time=8.18 ms
64 bytes from 192.168.65.249: icmp_seq=13 ttl=247 time=7.89 ms
64 bytes from 192.168.65.249: icmp_seq=14 ttl=247 time=11.2 ms
64 bytes from 192.168.65.249: icmp_seq=15 ttl=247 time=10.3 ms
64 bytes from 192.168.65.249: icmp_seq=16 ttl=247 time=7.85 ms
64 bytes from 192.168.65.249: icmp_seq=17 ttl=247 time=8.16 ms
^C
— 192.168.65.249 ping statistics —
17 packets transmitted, 17 received, 0% packet loss, time 16023ms
rtt min/avg/max/mdev = 7.786/10.238/21.228/3.949 ms

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.