[OBS-2906] Add LXD edfa/emtx devices - Observium

Details

Type: Add New Device / OS
Resolution: Fixed
Priority: Trivial
Fix Version/s: None
Affects Version/s: Professional Edition
Component/s: Discovery, OS
Labels:
- device
- discovery
- patch

Description

In a network we monitor there are Langxunda (Lxd) Externally Modulated Optic Transmitters and Erbium Dotted Fibre Amplifiers. E.g:

http://www.langxunda.com/en/goods/1167.html

The current OS detection for the NSCRTV-ROOT mib does not work on them. So I added rules for them in os.inc.php.

The limits which are set for the sensors in nscrtv-root.inc.php do not work for us. So I added some checks to not set a limit. Additionally I added some more sensors.

We do not own the copyright of the Lxd logo, I don't know what your policy is, wrt the use of logos. I got it from the web page and cropped it to look nicer.

It would be nice if the attached patch and logo could be added. If there are changes needed, please let me know (style, naming convention, etc).

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List
- Download All

debug-output-edfa-1port
57 kB
2019/02/14 05:18 PM
debug-output-edfa-2port
49 kB
2019/02/14 05:18 PM
debug-output-emtx
46 kB
2019/02/14 05:18 PM
lxd.patch
7 kB
2019/02/14 05:12 PM
lxd.png
11 kB
2019/02/14 05:12 PM
myagent-01.snmpwalk
25 kB
2019/05/23 07:44 AM
myagent-01-Cc.snmpwalk
32 kB
2019/05/23 07:44 AM
myagent-01-new.snmpwalk
0.1 kB
2019/05/23 02:57 PM
myagent-01-no.snmpwalk
0.1 kB
2019/05/23 07:55 AM
myagent-02.snmpwalk
0.4 kB
2019/05/23 07:44 AM
myagent-02-Cc.snmpwalk
33 kB
2019/05/23 07:44 AM
myagent-02-new.snmpwalk
34 kB
2019/05/23 02:57 PM
myagent-02-no.snmpwalk
0.4 kB
2019/05/23 07:55 AM

Activity

[OBS-2906] Add LXD edfa/emtx devices

Reto Zingg added a comment - 2019/07/03 10:41 AM

thanks a lot, we have r9956 running now a while, seems there are no problems with the new code, sensors are recognized and graphs are drawn.

Reto Zingg added a comment - 2019/07/03 10:41 AM thanks a lot, we have r9956 running now a while, seems there are no problems with the new code, sensors are recognized and graphs are drawn.

Mike Stupalov added a comment - 2019/06/01 06:08 PM

Adden in r9929.

Since discovery for this MIBs rewritten to new definitions style, probably some sensors can be incorrect
Please check.

Mike Stupalov added a comment - 2019/06/01 06:08 PM Adden in r9929. Since discovery for this MIBs rewritten to new definitions style, probably some sensors can be incorrect Please check.

Reto Zingg added a comment - 2019/05/23 02:57 PM

attached, but for host01 it's still empty

Reto Zingg added a comment - 2019/05/23 02:57 PM attached, but for host01 it's still empty

Mike Stupalov added a comment - 2019/05/23 02:42 PM

Hrm, seems as without starting OID output is empty..

rzingg Can you do additionally walks with starting .1.3.6?

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST01 .1.3.6 > myagent-01-new.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST02 .1.3.6 > myagent-02-new.snmpwalk

Mike Stupalov added a comment - 2019/05/23 02:42 PM Hrm, seems as without starting OID output is empty.. rzingg Can you do additionally walks with starting .1.3.6? snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST01 .1.3.6 > myagent-01-new.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST02 .1.3.6 > myagent-02-new.snmpwalk

Mike Stupalov added a comment - 2019/05/23 08:17 AM

Tnx, in this case, output without .1 mostly same as required.
I will see what useful information can be monitored.

Support for this NSCRTV-ROOT is very old and rewriting required.

Mike Stupalov added a comment - 2019/05/23 08:17 AM Tnx, in this case, output without .1 mostly same as required. I will see what useful information can be monitored. Support for this NSCRTV-ROOT is very old and rewriting required.

Reto Zingg added a comment - 2019/05/23 07:55 AM - edited

The devices don't speak v2c, so I changed it to v1.

There are 2 kind of devices one with one input the other with two. So I did the walk with for both:

myagent-01.snmpwalk -> one input
myagent-02.snmpwalk -> two inputs

The .1 didn't output anything! Other than "End of MIB"

The output aborts after some entries, with `Error: OID not increasing`, so I ran the commands also with -Cc:

myagent-01-Cc.snmpwalk
myagent-02-Cc.snmpwalk

Since there is not much output with starting OID .1, I also add the one without:

myagent-01-no.snmpwalk
myagent-02-no.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU  HOST01 .1 > myagent-01.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU  HOST01 .1.3.6.1.4.1 >> myagent-01.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU  HOST02 .1 > myagent-02.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU  HOST02 .1.3.6.1.4.1 >> myagent-02.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST01 .1 > myagent-01-Cc.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST01 .1.3.6.1.4.1 >> myagent-01-Cc.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST02 .1 > myagent-02-Cc.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST02 .1.3.6.1.4.1 >> myagent-02-Cc.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST01 > myagent-01-no.snmpwalk

snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc  HOST02 > myagent-02-no.snmpwalk

Does that help?

Reto Zingg added a comment - 2019/05/23 07:55 AM - edited The devices don't speak v2c, so I changed it to v1. There are 2 kind of devices one with one input the other with two. So I did the walk with for both: myagent-01.snmpwalk -> one input myagent-02.snmpwalk -> two inputs The .1 didn't output anything! Other than "End of MIB" The output aborts after some entries, with `Error: OID not increasing`, so I ran the commands also with -Cc: myagent-01-Cc.snmpwalk myagent-02-Cc.snmpwalk Since there is not much output with starting OID .1, I also add the one without: myagent-01-no.snmpwalk myagent-02-no.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU HOST01 .1 > myagent-01.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU HOST01 .1.3.6.1.4.1 >> myagent-01.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU HOST02 .1 > myagent-02.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU HOST02 .1.3.6.1.4.1 >> myagent-02.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST01 .1 > myagent-01-Cc.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST01 .1.3.6.1.4.1 >> myagent-01-Cc.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST02 .1 > myagent-02-Cc.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST02 .1.3.6.1.4.1 >> myagent-02-Cc.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST01 > myagent-01-no.snmpwalk snmpwalk -v1 -c COMMUNITY --hexOutputLength=0 -ObentxU -Cc HOST02 > myagent-02-no.snmpwalk Does that help?

Mike Stupalov added a comment - 2019/05/22 09:36 PM

Sorry for delay.

rzingg Can you provide full snmpwalk for both devices by this cmds?

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

snmpwalk -v2c -c <community>  --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

If possible, please attach here.

Mike Stupalov added a comment - 2019/05/22 09:36 PM Sorry for delay. rzingg Can you provide full snmpwalk for both devices by this cmds? snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If possible, please attach here.

People

Assignee:: Mike Stupalov

Reporter:: Reto Zingg

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 2019/02/14 05:18 PM

Updated:: 2019/07/03 10:41 AM

Resolved:: 2019/06/01 06:08 PM