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

Mtlink-BDCOM

Details

    • Add New Device / OS
    • Resolution: Unresolved
    • Major
    • None
    • CE-22.5
    • Discovery, Poller, Ports, Scripts
    • None

    Description

      need to add Mtlink and BD com switches and OLT MIB files 

      Attachments

        Activity

          [OBS-4997] Mtlink-BDCOM
          landy Mike Stupalov added a comment -

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

          landy Mike Stupalov added a comment - Can you show me Vendor site and link to hardware page?
          fizsyed ASAD added a comment -

          I hve added Mtlink switch MIB details too

          fizsyed ASAD added a comment - I hve added Mtlink switch MIB details too
          fizsyed ASAD added a comment -

          I hve added JSD-JX08 EPON OLT Operating System details

          fizsyed ASAD added a comment - I hve added JSD-JX08 EPON OLT Operating System details
          landy Mike Stupalov added a comment -

          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

          landy Mike Stupalov added a comment - 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
          fizsyed ASAD added a comment -

          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

          fizsyed ASAD added a comment - 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
          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.

          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.

          People

            landy Mike Stupalov
            fizsyed ASAD
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: