Support for Zenitel device

Device Requests
21

yeah probably, or let them be there for a few weeks to see if anything happens? I can always report back later to have them removed?

22

You are the customer, its your call.

to change later would take another PR… or you can manually edit your .yaml file.

23

Just leave then :slight_smile:
Are the icons suppose to change with this pr? It’s still linux tux here

24

yup, it will.

I just updated the os_discovery/zenitel.yaml file for the correct sensor oids.

Ill work on the other devices later.

1 Like
25

Thanks again for your work @deagle746 ! :grinning_face:

26

This is the output when I apply the PR - and I have no zenitel.svg in the logo folder

libre@nms:~$ ./scripts/github-apply 18711
<stdin>:22: trailing whitespace.

<stdin>:24: trailing whitespace.
     enterprises, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
<stdin>:28: trailing whitespace.

<stdin>:33: trailing whitespace.
             "
<stdin>:34: trailing whitespace.

Checking patch html/images/logos/zenitel.svg...
Checking patch html/images/os/zenitel.svg...
Checking patch mibs/zenitel/ALPHACOM-MIB...
Checking patch mibs/zenitel/VS-Device-MIB...
Checking patch resources/definitions/os_detection/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_detection/zenitel.yaml...
Checking patch resources/definitions/os_discovery/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_discovery/zenitel.yaml...
error: resources/definitions/os_discovery/zenitel.yaml: already exists in working directory
Checking patch tests/data/zenitel-alphacom.json...
Checking patch tests/data/zenitel_ipflush-8823.json...
Checking patch tests/data/zenitel_turbine-8124.json...
Checking patch tests/snmpsim/zenitel-alphacom.snmprec...
Checking patch tests/snmpsim/zenitel_ipflush-8823.snmprec...
Checking patch tests/snmpsim/zenitel_turbine-8124.snmprec...
27

did you manually create the zenite.yaml before applying?

might need to delete it and apply again?

28

What is this ipstation device?

29

It’s probably the same station I was asked to snmpwalk again -

We have many of the “almost” same devices scattered around.

30

yup it was.

could you see if there are additional configurations you can apply regarding its SNMP?

or maybe a new firmware? or maybe a newer model of the same thing?

the walks don’t include any OIDS from the MIB and there’s a whole section related to the “ipstation”

image
image276×322 9.23 KB

on the website “The status of the stations is reported to AlphaWeb as well as to 3rd party management systems using SNMP, Syslog or OPC.”

maybe it has to be registered to a call server before it reports the information?

31

Alphacom = the call server (pbx server perhaps?)
And the rest of the devices are “phones” connected to the server in all different configurations both software and hardware so it’s kinda tricky.

32

try and find one that responds to this OID. (assuming you use 2c)

replace the community and ip with what you have configured.

snmpget -v 2c -c .1.3.6.1.4.1.26122.2.1.1.0

If you find one i would like its snmpwalk.

otherwise, for the ipstations. its going to be pretty bare.

33

can you post a sample with a random ip and community? Not sure I understand how to do it without it :frowning:

Anyways, here is the snmpwalk of said alphacom server

34

thanks.

snmpget -v 2c -c public 192.168.50.21 .1.3.6.1.4.1.26122.2.1.1.0

35

Yeah I got it the second I posted the question of course (hard google search there!) But will I ever find anything or do I have to “install” the MIB info I got from Zenitel?

Edit: Are things suppose to look like this?

librenms@nms:~$ snmpget -v 2c -c community 192.168.xx.xx .1.3.6.1.4.1.26122.2.1.1.1
MIB search path: /opt/librenms/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf
Cannot find module (IANA-STORAGE-MEDIA-TYPE-MIB): At line 19 in /usr/share/snmp/mibs/ietf/VM-MIB
Did not find 'IANAStorageMediaType' in module #-1 (/usr/share/snmp/mibs/ietf/VM-MIB)
Cannot find module (IEEE8021-CFM-MIB): At line 30 in /usr/share/snmp/mibs/ietf/TRILL-OAM-MIB
Cannot find module (LLDP-MIB): At line 35 in /usr/share/snmp/mibs/ietf/TRILL-OAM-MIB
Did not find 'dot1agCfmMdIndex' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'dot1agCfmMaIndex' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'dot1agCfmMepIdentifier' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'dot1agCfmMepEntry' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'dot1agCfmMepDbEntry' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'Dot1agCfmIngressActionFieldValue' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'Dot1agCfmEgressActionFieldValue' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'Dot1agCfmRemoteMepState' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'LldpChassisId' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'LldpChassisIdSubtype' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'LldpPortId' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Did not find 'LldpPortIdSubtype' in module #-1 (/usr/share/snmp/mibs/ietf/TRILL-OAM-MIB)
Bad operator (INTEGER): At line 73 in /usr/share/snmp/mibs/ietf/SNMPv2-PDU
Cannot find module (IANA-SMF-MIB): At line 28 in /usr/share/snmp/mibs/ietf/SMF-MIB
Did not find 'IANAsmfOpModeIdTC' in module #-1 (/usr/share/snmp/mibs/ietf/SMF-MIB)
Did not find 'IANAsmfRssaIdTC' in module #-1 (/usr/share/snmp/mibs/ietf/SMF-MIB)
Cannot find module (IANAPowerStateSet-MIB): At line 20 in /usr/share/snmp/mibs/ietf/ENERGY-OBJECT-MIB
Did not find 'PowerStateSet' in module #-1 (/usr/share/snmp/mibs/ietf/ENERGY-OBJECT-MIB)
Cannot find module (IANA-OLSRv2-LINK-METRIC-TYPE-MIB): At line 26 in /usr/share/snmp/mibs/ietf/OLSRv2-MIB
Did not find 'IANAolsrv2LinkMetricTypeTC' in module #-1 (/usr/share/snmp/mibs/ietf/OLSRv2-MIB)
Cannot find module (IANA-ENERGY-RELATION-MIB): At line 22 in /usr/share/snmp/mibs/ietf/ENERGY-OBJECT-CONTEXT-MIB
Did not find 'IANAEnergyRelationship' in module #-1 (/usr/share/snmp/mibs/ietf/ENERGY-OBJECT-CONTEXT-MIB)
Cannot find module (IANA-BFD-TC-STD-MIB): At line 30 in /usr/share/snmp/mibs/ietf/BFD-STD-MIB
Did not find 'IANAbfdDiagTC' in module #-1 (/usr/share/snmp/mibs/ietf/BFD-STD-MIB)
Did not find 'IANAbfdSessTypeTC' in module #-1 (/usr/share/snmp/mibs/ietf/BFD-STD-MIB)
Did not find 'IANAbfdSessOperModeTC' in module #-1 (/usr/share/snmp/mibs/ietf/BFD-STD-MIB)
Did not find 'IANAbfdSessStateTC' in module #-1 (/usr/share/snmp/mibs/ietf/BFD-STD-MIB)
Did not find 'IANAbfdSessAuthenticationTypeTC' in module #-1 (/usr/share/snmp/mibs/ietf/BFD-STD-MIB)
Did not find 'IANAbfdSessAuthenticationKeyTC' in module #-1 (/usr/share/snmp/mibs/ietf/BFD-STD-MIB)
Timeout: No Response from 192.168.xx.xx
36

you don’t need the MIB.

librenms@debian-librenms:~$ snmpget -v 2c -c public 192.168.50.21 .1.3.6.1.4.1.26122.2.1.1.0
iso.3.6.1.4.1.26122.2.1.1.0 = No Such Instance currently exists at this OID

librenms@debian-librenms:~$ snmpget -v 2c -c public 192.168.50.21 .1.3.6.1.2.1.1.5.0
iso.3.6.1.2.1.1.5.0 = STRING: “ipstation”

Edit:
that doesn’t look right.

Edit:
The Timeout at the bottom means the IP you tried did not respond.
wrong community string , or the device doesn’t have SNMP capabilities , or its offline

37

Yeah well, I tried at least 30 devices and got no results :frowning:

38

I removed one zenitel.yaml - but it still wont work :upside_down_face:

Still got the “trailing whitespace”…


librenms@nms:~$ ./scripts/github-apply 18711
<stdin>:22: trailing whitespace.

<stdin>:24: trailing whitespace.
     enterprises, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
<stdin>:28: trailing whitespace.

<stdin>:33: trailing whitespace.
             "
<stdin>:34: trailing whitespace.

Checking patch html/images/logos/zenitel.svg...
error: html/images/logos/zenitel.svg: already exists in working directory
Checking patch html/images/os/zenitel.svg...
error: html/images/os/zenitel.svg: already exists in working directory
Checking patch mibs/zenitel/ALPHACOM-MIB...
Checking patch mibs/zenitel/VS-Device-MIB...
Checking patch resources/definitions/os_detection/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_detection/zenitel-ipstation.yaml...
Checking patch resources/definitions/os_detection/zenitel-vsdevice.yaml...
Checking patch resources/definitions/os_discovery/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_discovery/zenitel-vsdevice.yaml...
Checking patch tests/data/zenitel-alphacom.json...
Checking patch tests/data/zenitel-ipstation.json...
Checking patch tests/data/zenitel-vsdevice.json...
Checking patch tests/snmpsim/zenitel-alphacom.snmprec...
Checking patch tests/snmpsim/zenitel-ipstation.snmprec...
Checking patch tests/snmpsim/zenitel-vsdevice.snmprec...
39

you have to remove the files its flagging as error.
the zenitel.svg files are present, delete them and run it again.

librenms@debian-librenms:~$ ./scripts/github-apply 18711
<stdin>:22: trailing whitespace.

<stdin>:24: trailing whitespace.
     enterprises, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
<stdin>:28: trailing whitespace.

<stdin>:33: trailing whitespace.
             "
<stdin>:34: trailing whitespace.

Checking patch html/images/logos/zenitel.svg...
Checking patch html/images/os/zenitel.svg...
Checking patch mibs/zenitel/ALPHACOM-MIB...
Checking patch mibs/zenitel/VS-Device-MIB...
Checking patch resources/definitions/os_detection/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_detection/zenitel-ipstation.yaml...
Checking patch resources/definitions/os_detection/zenitel-vsdevice.yaml...
Checking patch resources/definitions/os_discovery/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_discovery/zenitel-vsdevice.yaml...
Checking patch tests/data/zenitel-alphacom.json...
Checking patch tests/data/zenitel-ipstation.json...
Checking patch tests/data/zenitel-vsdevice.json...
Checking patch tests/snmpsim/zenitel-alphacom.snmprec...
Checking patch tests/snmpsim/zenitel-ipstation.snmprec...
Checking patch tests/snmpsim/zenitel-vsdevice.snmprec...
Applied patch html/images/logos/zenitel.svg cleanly.
Applied patch html/images/os/zenitel.svg cleanly.
Applied patch mibs/zenitel/ALPHACOM-MIB cleanly.
Applied patch mibs/zenitel/VS-Device-MIB cleanly.
Applied patch resources/definitions/os_detection/zenitel-alphacom.yaml cleanly.
Applied patch resources/definitions/os_detection/zenitel-ipstation.yaml cleanly.
Applied patch resources/definitions/os_detection/zenitel-vsdevice.yaml cleanly.
Applied patch resources/definitions/os_discovery/zenitel-alphacom.yaml cleanly.
Applied patch resources/definitions/os_discovery/zenitel-vsdevice.yaml cleanly.
Applied patch tests/data/zenitel-alphacom.json cleanly.
Applied patch tests/data/zenitel-ipstation.json cleanly.
Applied patch tests/data/zenitel-vsdevice.json cleanly.
Applied patch tests/snmpsim/zenitel-alphacom.snmprec cleanly.
Applied patch tests/snmpsim/zenitel-ipstation.snmprec cleanly.
Applied patch tests/snmpsim/zenitel-vsdevice.snmprec cleanly.
warning: squelched 56 whitespace errors
warning: 61 lines add whitespace errors.

   INFO  Clearing cached bootstrap files.

  config ............................................................................................. 9.02ms DONE
  cache .............................................................................................. 5.68ms DONE
  compiled ........................................................................................... 1.21ms DONE
  events ............................................................................................. 1.29ms DONE
  routes ............................................................................................. 1.32ms DONE
  views .............................................................................................. 9.25ms DONE
40

Still not going that great with the images removed

librenms@nms:~$ ./scripts/github-apply 18711
<stdin>:22: trailing whitespace.

<stdin>:24: trailing whitespace.
     enterprises, MODULE-IDENTITY, OBJECT-TYPE, Counter32,
<stdin>:28: trailing whitespace.

<stdin>:33: trailing whitespace.
             "
<stdin>:34: trailing whitespace.

Checking patch html/images/logos/zenitel.svg...
Checking patch html/images/os/zenitel.svg...
Checking patch mibs/zenitel/ALPHACOM-MIB...
Checking patch mibs/zenitel/VS-Device-MIB...
Checking patch resources/definitions/os_detection/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_detection/zenitel-ipstation.yaml...
Checking patch resources/definitions/os_detection/zenitel-vsdevice.yaml...
Checking patch resources/definitions/os_discovery/zenitel-alphacom.yaml...
Checking patch resources/definitions/os_discovery/zenitel-vsdevice.yaml...
Checking patch tests/data/zenitel-alphacom.json...
Checking patch tests/data/zenitel-ipstation.json...
Checking patch tests/data/zenitel-vsdevice.json...
Checking patch tests/snmpsim/zenitel-alphacom.snmprec...
Checking patch tests/snmpsim/zenitel-ipstation.snmprec...
Checking patch tests/snmpsim/zenitel-vsdevice.snmprec...
Applied patch html/images/logos/zenitel.svg cleanly.
Applied patch html/images/os/zenitel.svg cleanly.
error: unable to write file 'mibs/zenitel/ALPHACOM-MIB' mode 100644: Not a directory

Edit: as you probably know, VS-DEVICES = Vingtor Stentofon devices - all devices that connects to the alpacom servers. Vingtor Stentofon is now Zenitel @deagle746