* Added models in hirshmann definition file
* Added Hirschmann_ms4128.snmprec to ~/tests/snmpsim
* Generic SysObjectID
* Some devices are not replying with all the table data
* fix tests accordingly
* add more sensors
* Move Temperature to YAML
Discovery and polling are currently buggy, this will fix it and make it capable of handling more than one temp sensor.
History of temperatures will be lost here.
---------
Co-authored-by: PipoCanaja <38363551+PipoCanaja@users.noreply.github.com>
* fix regex for hardware and version
* updated test data
* Update hwg-ste2.snmprec
* Create hwg-ste2.json
---------
Co-authored-by: PipoCanaja <38363551+PipoCanaja@users.noreply.github.com>
* Added support of new OS for NTP/PTP systems:
- support of Meinberg microSync OS (mbg-meinbergos)
- support of Safran (Orolia) SecureSync OS (orolia-securesync)
- support of Adva OSA (5401 and 5412) OS (adva_fsp150cm)
* Fix Safran (Orolia) images
* Added Test-unit JSON files
* Changed SVG images
* Changed SVG images
* Changed SVG images
* Add more filter options for the BGP API endpoint. bgp_descr, bgp_state and bgp_adminstate
* typo and lint
* Adress family filter would also be helpful. casting AS1234 Like inputs to plain numbers
* linting again...
Disc is typically used for optical media, not hard disks (so unlikely
to encounter discs in mdraid related circumstances).
mdadm and friends use the disk spelling, the host script also shows
shows this `"disc_count": $(maybe_get "${mdadmSysDev}/md/raid_disks"),`
Fixing the variable names as well would be nice, but that change would
be a lot bigger and probably break things as it would need host script
adjustment synchronising and all that, but I think we can at least
change the cosmetic spelling.
https://en.wikipedia.org/wiki/Spelling_of_disc
* Fix Fortinet HA status polling
* Test data
* Update fortigate.inc.php
* Update fortigate.inc.php
* Update all test data
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Adding basic support for Datacom DmOS devices.
Adding basic support for Datacom DmOS devices. These devices includes OLTs and Switches developed by Datacom (Teracom Telematica Ltda):
https://www.datacom.com.br/en/produtos/dmos
All the product models which uses this OS (DmOS) have the same specific sysObjectID = .1.3.6.1.4.1.3709.1.2.137 So new future devices will also have this OID.
* Rename DMOS-SYSMON-MIB.mib to DMOS-SYSMON-MIB
removing extension ".mib" from the filename
* Rename DMOS-TC-MIB.mib to DMOS-TC-MIB
removing extension ".mib" from the filename
* JSON files
json files related to the snmprec files sent in an earlier commit.
* Update dm4770 test data
* Fix mib_dir
* Update datacom-dmos.yaml
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Fixed BGP Remote peer link and graph in Routing Overview, or just static text when not a device in LibreNMS
* Added extra space
* Reverted back to overlibLink (due to BGP update graphs on hover)
* Added extra space
* Remove graph for remote peer, as it is falsely (showed earlier the Updates Graph for local peer)
* Removed unnecessary/unused code
* Remove graph for remote peer, as it is falsely (showed earlier the Updates Graph for local peer), replaced with just a DeviceLinks
* Change Url::deviceLink to return $text if the device doesn't exist. Default to ''
Import some of the things to improve readability.
* update phpdoc
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Add support for FiberStore "data center" switches
FiberStore has two different model lines of switches, and this adds
support for the "data center" line. This was configured and tested
against the N5860-48SC model.
The MIBs are from FiberStore's website, with the exception of the
FS-FIBER-MIB (the website version is a little behind the software, so
support sent me an updated version and should be getting it published
soon).
This does not currently handle 4x10 or 4x25 QSFP+ light levels, as I
don't currently have any to test against.
* Add test data for fs-switch-dc
This is from a production switch, with data filtered to just the
FiberStore enterprises OID.
* Update fs-switch-dc_fs-switch-dc.json
* correct processors warn field name
* Update fs-switch-dc_fs-switch-dc.json
* Update fs-switch-dc.yaml
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
Added logging output to renamehost() if an RRD Folder already exists for the new hostname.
Before: NOT renamed: Renaming of 10.4.0.146 failed
Now: NOT renamed: Renaming of 10.4.0.146 failed due to existing RRD folder forDEVICE
* Added values from SFP DDM's
* Added tempreture as well
* Fixed indention and generel code style
* Update awplus.inc.php
* Fixed coding style
* More code style fixes
* More style fixes
* Test data
* Test data that only contains/matches the sensors added.
* rework
Sorry for the long waiting time. I've made some tests and found that the value 0 should be ignored anyway because some Cisco switches report a non-existing fan with a speed of 0 which causes several errors when adding e.g. a fanless switch. Therefore I would like to suggest to keep the skip_value for this case.
I've also seen no more fan flapping with the most recent switch firmware so maybe Cisco has fixed something internally.
* Fix Test Data sg350x-24p
* Corrected other ciscoSB-Test data
Corrected other ciscoSB-Test data
* Removed ciscosb generic test data
This snmprec behaves different for my test system and the git checks. In addition the model is missing.
* Reverted cbs250 testfile
For some reason the generated test file contains errors. Reverting
* Weired fix
* Fixed weired update
* Recreated snmp data for cbs250
Recreated snmp data for cbs250
* updatet test data
Reworked Test data with most recend version
* Removed unused SNMPsim-Data
the ciscosb_x snmpsim Data are not used. Most device types are covered with the other test data. SRW-Switch line is currently not fully working. I have such an old device I'll add test data in the future.
* Recaptured cbs250 Test Data
* Renamed cbs250 test data
I have the impression that the online test somehow does not reload the snmprec data correctly. Therefore I rename it to make sure it handles it as a new device
* Removed VLANs
* Removed Farenheit to Celsius conversion
It seems that with the most recent version cisco reports the temperature in C. https://community.librenms.org/t/cisco-cbs-350-reads-wrong-temperature/22038
* Fixed wrong copied data
* Altered warning limit to CLI-values
* Added snmprec data back
Added snmprec data back
* Add FortiGate Environment stats
Adding Temperature, Fanspeed and Voltage sensors
* Fix test data
* New test data
* Update fortigate test data
* 500d ospf ifIndex
* 60f3g4g bgpPeerIface null
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Add support for Fujifilm printer
* Add support for Fujifilm printer
* fix Fujifilmprinter.yaml
* Add Fujifilm printer test unit
* remove snmprec supply descr contains utf8 character
* fix discovery yaml
* Freenas zpool improvement
Don't try to multiply two strings (cast units to int)
No need to double fetch database entries to check if it exists.
Only poll zpoolUsed to speed up polling
* Block zpool usage on new devices, they dropped support.
TRUENAS-MIB included for reference
* Fix polling, update test data
* API: get poller group
* missed string in doc
* return all poller groups if name/id aren't specified
* add missing doc link
* style fixes
* more style
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Fix health temperature degree display
It will be converted to html later. (otherwise it was double converted)
* Remove all ° it will only cause troubles
* Add support for Nokia 1830 PSS Optical gear
Tested against 1830 PSS-8 Chassis, in single and multi-chassis configurations
Supports Optical Power, temperature, current, power, and a variety of card states, alarms, and trail status.
Of note: With multi-chassis nodes, reading values from the non-master can be a "slow" process, slow in that the default timeout Libre ships with can cause the SNMP client to begin issuing retries. This can result in the chassis daemon rate limiting and/or blocking the client. The solution here is to raise the SNMP timeout within each device's configuration; unfortunately those values are not configurable on a per-OS basis (at least not at this time).
* Removing Unused / Duplicate MIBs
* IP::fromHexString handle ascii
Some bad MIBs convert the hex to ascii on display.
Attempt to decode that if the situation is detected.
fixes#15501
* add ascii tests
