* Add support for Firebrick memory monitoring.
* Add mempool testing for Firebrick.
* We have to specify the OID by numeric, because otherwise it assumes it's some kind of indexed table.
* Specify by OID.
* Fix test result data for the FB mempools.x
* Firebrick reports in KB.
* Fix precision in the tests.
* Change ESXi port naming to be stable
Currently every time discovery runs against ESXi, the port names change generating a lot of log spam.
This is because ESXi uses this as the ifDescr:
```Device vmnic1000202 at 01:00.0 nmlx4_en```
The poller parses this, and extracts the interface name, whereas discovery does not, causing the interface names to flip every 6 hours.
https://github.com/librenms/librenms/blob/22.10.0/includes/polling/ports.inc.php#L578-L580
This change gives the discovery process the same behaviour, so the naming is now stable.
* Try to fix test data with a squash
* vcsa test data
* Synthesise VCSA ifName, use it in place of ifDescr
* Refresh test data
* Update ports.inc.php
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Fix vsolution discovery yaml
Fetching too much data and incorrect config for scalar values.
* revert json changes
* one sensor_prev
* fix
* revert all changes
* Add support for Trellix ATD devices
- Add discovery for mlos ATD devices
- Monitor various OIDs related to ATD system health and status
- Add required MIBs
- Add test data
* add json test data
* Rename MCAFEE-SMI to MCAFEE-INTRUVERT-SMI
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
Was origionally intended to use the 1 minute values, but was discovering the one second value and polling the twoHour value
Was also restricted to only one CPU.
Now discovers and polls all CPUs at the oneMin avg
* Expand discovery of gigavue os
- Expand discovery so all Gigamon products are discovered
- Query for hardware version using GIGAMON-SNMP-MIB::model.0 OID if present
- Add more Gigamon gigavue test data
* Create gigavue_hc2.json
Looks like there was no json file before...
* update gigavue_hc2.json
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Update fortivoice.yaml
Add in pulling in device hardware and software info
* Add files via upload
* Add files via upload
* merge test data
* Delete fortivoice_fortivoice.snmprec
* Update fortivoice.json
* Update fortivoice.json
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Add discovery of NVT Phybridge FLEX24
* Update phybridge-flex.yaml
Added FLEX-24 Switch under sysDescr
* Test Data phybridge-flex_flex-24 json and snmprec
* Add initial OS detection for LoadBalancer.org
* Match on Linux sysObjectID first for efficiency
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Add test for loadbalancer OS detection
* Add test for loadbalancer OS detection - fix author
* Add test for loadbalancer OS detection
* Add test for loadbalancer OS detection - fix author
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
Co-authored-by: Chris Ware <cjw26@bath.ac.uk>
Hikvision cameras model number does not forcibly starts with 'DS-' anymore.
Here is an sample of a OEM new model made by HIKVISION
[
.1.3.6.1.4.1.39165.1.1.0 = STRING: "IPC7A27-ANPR"
.1.3.6.1.4.1.39165.1.2.0 = STRING: "0"
.1.3.6.1.4.1.39165.1.3.0 = STRING: "V5.7.80 build 220525"
.1.3.6.1.4.1.39165.1.4.0 = STRING: "98-f1-12-c7-0b-a2"
.1.3.6.1.4.1.39165.1.5.0 = STRING: "88"
.1.3.6.1.4.1.39165.1.6.0 = STRING: "IPcamera"
.1.3.6.1.4.1.39165.1.7.0 = STRING: "38 PERCENT"
...]
Some FTD systems like 4110 and 4120 (probably more) use different OIDs (not .1 or .4) for that, so these were added. The version extension is probably not helpful, as the result is an empty string … but at least that OID exists.
Not: without this change, hardware+serial fields will be empty after a (re)discovery.
Previously, the code would query all the oids it received. Now it will split it up into multiple queries if too many are sent.
Prevents some devices snmp service from crashing.
* APC: Add support for Battery Recommended Days Remaining
* Extract number from string later during polling
Odd that this is different from the discovery process
* wip
* wip
* Apply fixes from StyleCI
* wip
* wip
* Apply fixes from StyleCI
---------
Co-authored-by: Tony Murray <murraytony@gmail.com>
* Modify Avocent discovery so Avocent MergePoint Unity KVM switches are discovered
* Extract hardware model and version stored in sysDescr OID
* add avocent mpu snmprec
* add json dump test data
* update to not conflict with dell-rcs discovery
* fix styleci findings
* update Avocent.php
* update Avocent.php
* add support for avocent mp unity kvm switches
* add support for avocent mp unity kvm switches
* add support for avocent mp unity kvm switches
* add support for avocent mp unity kvm switches
* add support for avocent mp unity kvm switches
* add support for avocent mp unity kvm switches
* cleanup
* fix os name typo
* Add support for Vertiv Avocent MergePoint Unity
- Remove unnecessary sysdescr_regex in discovery file
- Only show device_bits graph in device header bar
- Use Vertiv icon
- Replace .png Vertiv icon and logo with .svg
- Disable unnecessary discovery and poller modules
- Add more snmpsim test data
* Update avocent-mp.yaml
Only disable poller and discovery modules if they cause problems
* Add Modified V-sol MIB
* Add Vsolution Discovery OS
* Add Vsolution Discovery OS
* Add os-logo
* Add snmp test data
* Add .json test data
* Add .json actual test data
Tested against X7600 and X4300. Both of which change from being a generic device to a Samsung printer device. Subsequent poller.php runs result in toner, fuser, impressions counts, etc data being returned.
