mirror/librenms-librenms
1
0
Fork 0
mirror of https://github.com/librenms/librenms.git synced 2024-10-07 16:52:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
Files
ca891b477e32ad789ffe3f215218b18052d22ea4
librenms-librenms/tests/data/mrv-od.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

3955 lines
173 KiB
JSON
Raw Normal View History

Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
{
"os": {
"discovery": {
"devices": [
{
"sysName": "<private>",
"sysObjectID": ".1.3.6.1.4.1.629.200.1.1.1",
"sysDescr": "OD-NM OD-5.10.1 (32333) (Jul 13 2016 - 08:18:22), U-Boot 2013.01.02.16-00155-gdebf., Linux kernel v3.2.78-1-12777-g012a77d (#7 Wed Mar 9 15:29:57 PST 2016), OD-NM (firmware 20.16) (00:20:1a:06:08:3f)",
"sysContact": "<private>",
"version": "OD 5.2.1 (25684)",
"hardware": "OD-16-HD",
"features": null,
OS test data update (#14417) * OS test data update * edfamux case * restore ftos * revert ird.json
2022-10-03 10:22:03 -05:00
"location": "<private>",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"os": "mrv-od",
"type": "network",
"serial": "012345EMF8K0",
OS test data update (#14417) * OS test data update * edfamux case * restore ftos * revert ird.json
2022-10-03 10:22:03 -05:00
"icon": "mrv.png"
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
}
]
Move sysContact polling to discovery (#12524) * Move sysContact polling to discovery * Update tests * fixup * fixup * fixup * fixup * fixup
2021-02-12 02:04:45 +01:00
},
"poller": "matches discovery"
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
"ports": {
"discovery": {
"ports": [
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "eth0",
"ifName": "eth0",
"portName": null,
"ifIndex": 1,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "ethernetCsmacd",
"ifAlias": "RJ-45 at 1.16.4",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port1",
"ifName": "1.1.1",
"portName": null,
"ifIndex": 101001,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "converter-ifalias-port1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port2",
"ifName": "1.1.2",
"portName": null,
"ifIndex": 101002,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "converter-ifalias-port2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port3",
"ifName": "1.1.3",
"portName": null,
"ifIndex": 101003,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "converter-ifalias-port3",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port4",
"ifName": "1.1.4",
"portName": null,
"ifIndex": 101004,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "converter-ifalias-port4",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "LC at 1.11.1",
"ifName": "1.11.1",
"portName": null,
"ifIndex": 111001,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "LC at 1.11.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "LC at 1.11.2",
"ifName": "1.11.2",
"portName": null,
"ifIndex": 111002,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "LC at 1.11.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.12.1",
"ifName": "1.12.1",
"portName": null,
"ifIndex": 112001,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "FO_SC at 1.12.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.12.2",
"ifName": "1.12.2",
"portName": null,
"ifIndex": 112002,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "FO_SC at 1.12.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.14.1",
"ifName": "1.14.1",
"portName": null,
"ifIndex": 114001,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "FO_SC at 1.14.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.14.2",
"ifName": "1.14.2",
"portName": null,
"ifIndex": 114002,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "FO_SC at 1.14.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "USB at 1.16.1",
"ifName": "1.16.1",
"portName": null,
"ifIndex": 116001,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "USB at 1.16.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "SFP at 1.16.2",
"ifName": "1.16.2",
"portName": null,
"ifIndex": 116002,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "SFP at 1.16.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "SFP at 1.16.3",
"ifName": "1.16.3",
"portName": null,
"ifIndex": 116003,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "SFP at 1.16.3",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "RJ-45 at 1.16.4",
"ifName": "1.16.4",
"portName": null,
"ifIndex": 116004,
"ifSpeed": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": null,
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifOperStatus_prev": null,
"ifAdminStatus": null,
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": null,
"ifType": "other",
"ifAlias": "RJ-45 at 1.16.4",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": null,
"ifInUcastPkts_prev": null,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": null,
"ifOutUcastPkts_prev": null,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": null,
"ifInErrors_prev": null,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": null,
"ifOutErrors_prev": null,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": null,
"ifInOctets_prev": null,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": null,
"ifOutOctets_prev": null,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": null,
"ifInNUcastPkts_prev": null,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": null,
"ifOutNUcastPkts_prev": null,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": null,
"ifInDiscards_prev": null,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": null,
"ifOutDiscards_prev": null,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": null,
"ifInUnknownProtos_prev": null,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": null,
"ifInBroadcastPkts_prev": null,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": null,
"ifOutBroadcastPkts_prev": null,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": null,
"ifInMulticastPkts_prev": null,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": null,
"ifOutMulticastPkts_prev": null,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
}
]
},
"poller": {
"ports": [
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "eth0",
"ifName": "eth0",
"portName": null,
"ifIndex": 1,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 1500,
"ifType": "ethernetCsmacd",
"ifAlias": "RJ-45 at 1.16.4",
"ifPhysAddress": "00201a042a98",
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 77451431,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 16585896,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 4294967295,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 3966386354,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 21303490,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port1",
"ifName": "1.1.1",
"portName": null,
"ifIndex": 101001,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "converter-ifalias-port1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port2",
"ifName": "1.1.2",
"portName": null,
"ifIndex": 101002,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "converter-ifalias-port2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port3",
"ifName": "1.1.3",
"portName": null,
"ifIndex": 101003,
"ifSpeed": 10300000000,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "converter-ifalias-port3",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "converter-ifalias-port4",
"ifName": "1.1.4",
"portName": null,
"ifIndex": 101004,
"ifSpeed": 10300000000,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "converter-ifalias-port4",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "LC at 1.11.1",
"ifName": "1.11.1",
"portName": null,
"ifIndex": 111001,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "down",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "LC at 1.11.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "LC at 1.11.2",
"ifName": "1.11.2",
"portName": null,
"ifIndex": 111002,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "down",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "LC at 1.11.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.12.1",
"ifName": "1.12.1",
"portName": null,
"ifIndex": 112001,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "FO_SC at 1.12.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.12.2",
"ifName": "1.12.2",
"portName": null,
"ifIndex": 112002,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "down",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "FO_SC at 1.12.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.14.1",
"ifName": "1.14.1",
"portName": null,
"ifIndex": 114001,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "FO_SC at 1.14.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "FO_SC at 1.14.2",
"ifName": "1.14.2",
"portName": null,
"ifIndex": 114002,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "down",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "FO_SC at 1.14.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "USB at 1.16.1",
"ifName": "1.16.1",
"portName": null,
"ifIndex": 116001,
Update ports test data to match current data (#14211) * Update ports test data to match current data * fix timos_hc * update aos7 * Update ciena-sds data, I don't think it works when you run just the ports module by itself... * update ciscosb_cbs250-24p-4x.json * restore fortigate * restore luminato_4x4 * restore luminato_c12.json * restore timos * restore timos_7705.json
2022-10-02 14:29:24 -05:00
"ifSpeed": 0,
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "down",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "USB at 1.16.1",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "SFP at 1.16.2",
"ifName": "1.16.2",
"portName": null,
"ifIndex": 116002,
"ifSpeed": 1000000000,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "SFP at 1.16.2",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "SFP at 1.16.3",
"ifName": "1.16.3",
"portName": null,
"ifIndex": 116003,
"ifSpeed": 1000000000,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "down",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "down",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "SFP at 1.16.3",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 0,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 0,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 0,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 0,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 0,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 0,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 0,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 0,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
},
{
"port_descr_type": null,
"port_descr_descr": null,
"port_descr_circuit": null,
"port_descr_speed": null,
"port_descr_notes": null,
"ifDescr": "RJ-45 at 1.16.4",
"ifName": "1.16.4",
"portName": null,
"ifIndex": 116004,
"ifSpeed": 1000000000,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifSpeed_prev": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifConnectorPresent": "true",
"ifOperStatus": "up",
Add bad_ifoperstatus for filtering interfaces having a status for example 'notPresent' (#10977) * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent * Add bad_ifoperstatus for filtering interfaces having a status for example notPresent
2020-01-24 19:58:01 +08:00
"ifOperStatus_prev": "up",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifAdminStatus": "up",
"ifAdminStatus_prev": null,
"ifDuplex": null,
"ifMtu": 0,
"ifType": "other",
"ifAlias": "RJ-45 at 1.16.4",
"ifPhysAddress": null,
"ifLastChange": 0,
Remove unused port fields (#14963) * Remove unused port fields (and set vlan to default to null) * Update test data for deleted fields * update vlan to null * missed field removals * More correct migration * Update new data * restore accidental deletions
2023-04-14 16:47:26 -05:00
"ifVlan": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"ifTrunk": null,
"ignore": 0,
"disabled": 0,
"deleted": 0,
"pagpOperationMode": null,
"pagpPortState": null,
"pagpPartnerDeviceId": null,
"pagpPartnerLearnMethod": null,
"pagpPartnerIfIndex": null,
"pagpPartnerGroupIfIndex": null,
"pagpPartnerDeviceName": null,
"pagpEthcOperationMode": null,
"pagpDeviceId": null,
"pagpGroupIfIndex": null,
"ifInUcastPkts": 15938955,
"ifInUcastPkts_prev": 0,
"ifInUcastPkts_delta": null,
"ifInUcastPkts_rate": null,
"ifOutUcastPkts": 16243796,
"ifOutUcastPkts_prev": 0,
"ifOutUcastPkts_delta": null,
"ifOutUcastPkts_rate": null,
"ifInErrors": 0,
"ifInErrors_prev": 0,
"ifInErrors_delta": null,
"ifInErrors_rate": null,
"ifOutErrors": 0,
"ifOutErrors_prev": 0,
"ifOutErrors_delta": null,
"ifOutErrors_rate": null,
"ifInOctets": 6222404031,
"ifInOctets_prev": 0,
"ifInOctets_delta": null,
"ifInOctets_rate": null,
"ifOutOctets": 4904125517,
"ifOutOctets_prev": 0,
"ifOutOctets_delta": null,
"ifOutOctets_rate": null,
"poll_prev": null,
"ifInNUcastPkts": 0,
"ifInNUcastPkts_prev": 0,
"ifInNUcastPkts_delta": null,
"ifInNUcastPkts_rate": null,
"ifOutNUcastPkts": 0,
"ifOutNUcastPkts_prev": 0,
"ifOutNUcastPkts_delta": null,
"ifOutNUcastPkts_rate": null,
"ifInDiscards": 0,
"ifInDiscards_prev": 0,
"ifInDiscards_delta": null,
"ifInDiscards_rate": null,
"ifOutDiscards": 0,
"ifOutDiscards_prev": 0,
"ifOutDiscards_delta": null,
"ifOutDiscards_rate": null,
"ifInUnknownProtos": 0,
"ifInUnknownProtos_prev": 0,
"ifInUnknownProtos_delta": null,
"ifInUnknownProtos_rate": null,
"ifInBroadcastPkts": 18786793,
"ifInBroadcastPkts_prev": 0,
"ifInBroadcastPkts_delta": null,
"ifInBroadcastPkts_rate": null,
"ifOutBroadcastPkts": 10,
"ifOutBroadcastPkts_prev": 0,
"ifOutBroadcastPkts_delta": null,
"ifOutBroadcastPkts_rate": null,
"ifInMulticastPkts": 47598792,
"ifInMulticastPkts_prev": 0,
"ifInMulticastPkts_delta": null,
"ifInMulticastPkts_rate": null,
"ifOutMulticastPkts": 11339793,
"ifOutMulticastPkts_prev": 0,
"ifOutMulticastPkts_delta": null,
Laravel 6.x (#11397) * Update Laravel core files Fix app/Http/Kernel.php * Use RouteServiceProvider::HOME * Sync Laravel default config files * Update composer dependencies to Laravel 6 * fix resources/lang/en/validation.php * Manually fixing tests required by travis, fails locally??? * Update wpb/string-blade-compiler * Add new viewany() authorization policies * Update minimum PHP version to 7.2 * Re-generate our json test-dumps Due to: https://github.com/laravel/framework/pull/16069 https://github.com/laravel/framework/pull/31100 * update truenas data * fix truenas Co-authored-by: Laravel Shift <shift@laravelshift.com> Co-authored-by: Tony Murray <murraytony@gmail.com>
2020-05-23 19:05:18 +02:00
"ifOutMulticastPkts_rate": null
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
}
]
}
},
"sensors": {
"discovery": {
"sensors": [
{
"sensor_deleted": 0,
"sensor_class": "current",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.33.1.1.3",
"sensor_index": "nbsCmmcPortBiasAmps.1.1.3",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.3 Tx Bias Current",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000000,
"sensor_multiplier": 1,
"sensor_current": 0.069984,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100333",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "current",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.33.1.1.4",
"sensor_index": "nbsCmmcPortBiasAmps.1.1.4",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.4 Tx Bias Current",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000000,
"sensor_multiplier": 1,
"sensor_current": 0.033212,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100433",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.32.1.1.3",
"sensor_index": "nbsCmmcPortRxPower.1.1.3",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.3 Rx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": -16.798,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100332",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.32.1.1.4",
"sensor_index": "nbsCmmcPortRxPower.1.1.4",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.4 Rx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 0.062,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100432",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.32.1.12.2",
"sensor_index": "nbsCmmcPortRxPower.1.12.2",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.12.2 Rx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 6.26,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200232",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.32.1.14.2",
"sensor_index": "nbsCmmcPortRxPower.1.14.2",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.14.2 Rx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": -14.03,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400232",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.31.1.1.3",
"sensor_index": "nbsCmmcPortTxPower.1.1.3",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.3 Tx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 1.552,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100331",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.31.1.1.4",
"sensor_index": "nbsCmmcPortTxPower.1.1.4",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.4 Tx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": -2.413,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100431",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.31.1.12.1",
"sensor_index": "nbsCmmcPortTxPower.1.12.1",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.12.1 Tx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 15.26,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200131",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "dbm",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.31.1.14.1",
"sensor_index": "nbsCmmcPortTxPower.1.14.1",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.14.1 Tx Power",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": -3.76,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"sensor_limit_low": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400131",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.6.1.1.11.1",
"sensor_index": "nbsCmmcChassisFan1Status.1",
"sensor_type": "nbsCmmcChassisFanStatus",
"sensor_descr": "Chassis 1 Fan 1",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 3,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10000011",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcChassisFanStatus"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.6.1.1.7.1",
"sensor_index": "nbsCmmcChassisPS1Status.1",
"sensor_type": "nbsCmmcChassisPSStatus",
"sensor_descr": "Chassis 1 Power Supply 1",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 4,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "1000007",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcChassisPSStatus"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.6.1.1.8.1",
"sensor_index": "nbsCmmcChassisPS2Status.1",
"sensor_type": "nbsCmmcChassisPSStatus",
"sensor_descr": "Chassis 1 Power Supply 2",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 4,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "1000008",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcChassisPSStatus"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.38.1.1.3",
"sensor_index": "nbsCmmcPortDigitalDiags.1.1.3",
"sensor_type": "nbsCmmcPortDigitalDiags",
"sensor_descr": "Port 1.1.3 Overall DigiDiags State",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 2,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100338",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcPortDigitalDiags"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.38.1.1.4",
"sensor_index": "nbsCmmcPortDigitalDiags.1.1.4",
"sensor_type": "nbsCmmcPortDigitalDiags",
"sensor_descr": "Port 1.1.4 Overall DigiDiags State",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 2,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100438",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcPortDigitalDiags"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.38.1.12.1",
"sensor_index": "nbsCmmcPortDigitalDiags.1.12.1",
"sensor_type": "nbsCmmcPortDigitalDiags",
"sensor_descr": "Port 1.12.1 Overall DigiDiags State",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 2,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200138",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcPortDigitalDiags"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.38.1.12.2",
"sensor_index": "nbsCmmcPortDigitalDiags.1.12.2",
"sensor_type": "nbsCmmcPortDigitalDiags",
"sensor_descr": "Port 1.12.2 Overall DigiDiags State",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 2,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200238",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcPortDigitalDiags"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.38.1.14.1",
"sensor_index": "nbsCmmcPortDigitalDiags.1.14.1",
"sensor_type": "nbsCmmcPortDigitalDiags",
"sensor_descr": "Port 1.14.1 Overall DigiDiags State",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 2,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400138",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcPortDigitalDiags"
},
{
"sensor_deleted": 0,
"sensor_class": "state",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.38.1.14.2",
"sensor_index": "nbsCmmcPortDigitalDiags.1.14.2",
"sensor_type": "nbsCmmcPortDigitalDiags",
"sensor_descr": "Port 1.14.2 Overall DigiDiags State",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 2,
"sensor_limit": null,
"sensor_limit_warn": null,
"sensor_limit_low": null,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400238",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": "nbsCmmcPortDigitalDiags"
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.6.1.1.15.1",
"sensor_index": "nbsCmmcChassisTemperature.1",
"sensor_type": "mrv-od",
"sensor_descr": "Chassis 1 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 25,
"sensor_limit": 45,
"sensor_limit_warn": null,
"sensor_limit_low": 5,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10000015",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.30.1.1.3",
"sensor_index": "nbsCmmcPortTemperature.1.1.3",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.3 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 35,
"sensor_limit": 55,
"sensor_limit_warn": null,
"sensor_limit_low": 25,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100330",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.30.1.1.4",
"sensor_index": "nbsCmmcPortTemperature.1.1.4",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.4 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 31,
"sensor_limit": 51,
"sensor_limit_warn": null,
"sensor_limit_low": 21,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100430",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.30.1.12.1",
"sensor_index": "nbsCmmcPortTemperature.1.12.1",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.12.1 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 28,
"sensor_limit": 48,
"sensor_limit_warn": null,
"sensor_limit_low": 18,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200130",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.30.1.12.2",
"sensor_index": "nbsCmmcPortTemperature.1.12.2",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.12.2 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 28,
"sensor_limit": 48,
"sensor_limit_warn": null,
"sensor_limit_low": 18,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200230",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.30.1.14.1",
"sensor_index": "nbsCmmcPortTemperature.1.14.1",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.14.1 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 26,
"sensor_limit": 46,
"sensor_limit_warn": null,
"sensor_limit_low": 16,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400130",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.30.1.14.2",
"sensor_index": "nbsCmmcPortTemperature.1.14.2",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.14.2 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 26,
"sensor_limit": 46,
"sensor_limit_warn": null,
"sensor_limit_low": 16,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400230",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.7.1.1.34.1.13",
"sensor_index": "nbsCmmcSlotTemperature.1.13",
"sensor_type": "mrv-od",
"sensor_descr": "Slot 1.13 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 28,
MRV: temperature limits from MIB (#10326) * Update MRV MIBs to version 5.14.1 * Learn SlotTemperature limits from the new MIB. * Rename MIB files to the name of the MIB. * Update mrv-od.snmprec * Update mrv-od.json
2019-07-24 06:50:37 +02:00
"sensor_limit": 65,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
MRV: temperature limits from MIB (#10326) * Update MRV MIBs to version 5.14.1 * Learn SlotTemperature limits from the new MIB. * Rename MIB files to the name of the MIB. * Update mrv-od.snmprec * Update mrv-od.json
2019-07-24 06:50:37 +02:00
"sensor_limit_low": 5,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11300034",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "temperature",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.7.1.1.34.1.15",
"sensor_index": "nbsCmmcSlotTemperature.1.15",
"sensor_type": "mrv-od",
"sensor_descr": "Slot 1.15 Temperature",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1,
"sensor_multiplier": 1,
"sensor_current": 26,
MRV: temperature limits from MIB (#10326) * Update MRV MIBs to version 5.14.1 * Learn SlotTemperature limits from the new MIB. * Rename MIB files to the name of the MIB. * Update mrv-od.snmprec * Update mrv-od.json
2019-07-24 06:50:37 +02:00
"sensor_limit": 60,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_warn": null,
MRV: temperature limits from MIB (#10326) * Update MRV MIBs to version 5.14.1 * Learn SlotTemperature limits from the new MIB. * Rename MIB files to the name of the MIB. * Update mrv-od.snmprec * Update mrv-od.json
2019-07-24 06:50:37 +02:00
"sensor_limit_low": 5,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11500034",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "voltage",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.34.1.1.3",
"sensor_index": "nbsCmmcPortSupplyVolts.1.1.3",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.3 Tx Supply Voltage",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 3.339,
"sensor_limit": 3.83985,
"sensor_limit_warn": null,
"sensor_limit_low": 2.83815,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100334",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "voltage",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.34.1.1.4",
"sensor_index": "nbsCmmcPortSupplyVolts.1.1.4",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.1.4 Tx Supply Voltage",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 3.245,
"sensor_limit": 3.73175,
"sensor_limit_warn": null,
"sensor_limit_low": 2.75825,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "10100434",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "voltage",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.34.1.12.1",
"sensor_index": "nbsCmmcPortSupplyVolts.1.12.1",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.12.1 Tx Supply Voltage",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 3.28,
"sensor_limit": 3.772,
"sensor_limit_warn": null,
"sensor_limit_low": 2.788,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11200134",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
},
{
"sensor_deleted": 0,
"sensor_class": "voltage",
"poller_type": "snmp",
"sensor_oid": ".1.3.6.1.4.1.629.200.8.1.1.34.1.14.1",
"sensor_index": "nbsCmmcPortSupplyVolts.1.14.1",
"sensor_type": "mrv-od",
"sensor_descr": "Port 1.14.1 Tx Supply Voltage",
Remove guessed limits for some health sensors, documentation for sensor classes (#10327) * Default to null for group yaml discovery. * Update test data for a154bda yaml group null fix. * Changes to guessed limit functions for sensors. Original behaviour =================== The file `includes/discovery/functions.inc.php` contains `sensor_limit_low()` and `sensor_limit()` which both attempt to guess a sane value for sensors when no explicitly defined low_limit or high_limit can be found during discovery. Both switch control structures used in those two functions have empty case statements which means that if one of those matches, it's going to fall through and run the code for each subsequent case until a `break` is reached. For example, when we call `function sensor_low_limit(dbm, -13.036)` it will return the value `-12.3842` instead of `null`. That is because there will be a match at `case 'dbm':` which falls through all the way to `case 'cooling':`, where it performs `$limit = -13.036 * 0.95` before hitting a `break`. Changed behaviour =================== Removed `power_consumed` and `count` guessed low_limit and high_limit, I personally added those sensor classes in PR #9471 when I didn't understand that a switch control structure has fall-through behaviour so I can guarantee that guessing limits for those is a mistake on my behalf. It should not be there, only power_factor can have guessed limits. Apologies for the issue, I'm still a beginning programmer! Furthermore, I removed guessed high_limit values for `current` and `power` because these are supposed to draw higher values as more devices or components are installed on for example a PDU or a chassis. Finally, I removed guessed low_limit and high_limit for `dbm` sensors, there is a much too large variance in power budget on commercially available optical transceivers for there to be a sensible window where you can guess these values. * Documentation on adding sensor classes. * Update test data - sensor limit changes @ 30212d2
2019-06-21 16:03:27 +02:00
"group": null,
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"sensor_divisor": 1000,
"sensor_multiplier": 1,
"sensor_current": 3.28,
"sensor_limit": 3.772,
"sensor_limit_warn": null,
"sensor_limit_low": 2.788,
"sensor_limit_low_warn": null,
"sensor_alert": 1,
"sensor_custom": "No",
"entPhysicalIndex": "11400134",
"entPhysicalIndex_measured": null,
"sensor_prev": null,
"user_func": null,
Sensors - Allow changing RRD type in YAML and PHP sensor discovery (#14208) * new row variant * syntax * syntax * DB * syntax * schema * test * allAdvaTests * Tests * Tests * Tests * missingMigration * missingMigration * Tests * Tests * Tests * Tests * tests * tests * tests * tests * tests * test * fix_Aos7 * fix snmprec arista * fix snmprec arista * fix snmprec arista * tests * merge_fix * aos7 backslash * aos7 * more * more * defaultValue * arista * typehint * tests * tests * voss * aos7 * aos7 * aos7 * testWithoutarista-mos_metamux48-c-0-16.json * tests * ciscosb * new tests with 2004 and only sensors module * adding wireless module again * adding wireless module again (cont) * airos * aos7 * arista * arista * bdcom * fortigate * fortigate * fortigate * ftos * ftos * tests on 1804 * tests once more * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * tests once more, cont * more * bdcom * comware * edgeosolt * enexus * arista-mos * removeAristaAgain * ies500_manual_edit * ies500_manual_edit * mni * volius * zywal * manually imported arista-mos * manually imported arista-mos * arista-mos test is triggering something ... * restoreArista * tests * tests * aristamos * ies52xxM_4206.json * revert linux_supermicro.json * revert linux_supermicro.json * benuos * fortiadc * rnx-updu
2022-10-25 15:31:02 +02:00
"rrd_type": "GAUGE",
Convert OS mrv-od to yaml, discover more sensors, discover entity-physical (#10266) * Dynamic entPhysicalIndex values for YamlDiscovery * Use degree symbol when displaying temperature values * Adjust SNMP options for new snmp_get_multi() The OS polling module for mrv-od was using snmpget commands with -Ovqs, rather than -OQUs, which meant that the equal sign was stripped in the snmpget output. But that equal sign is now used as the explode() delimiter so it broke the construction of the returned array for the snmp_get_multi() function. Additionally, I removed the NBS-CMMC-MIB:: prefix which is no longer returned by snmp_get_multi() as part of the OID. Now, the mrv-od.inc.php OS polling module is retrieving data from positions in the array with actual content. * Convert mrv-od to yaml, improve sensors discovery Converted sensors discovery for mrv-od to yaml, retaining all functionality for pre-cache, dbm, and temperature. Replaced specific SFF-8472 Digital Diagnostics state sensors with generic ones, given that we are now reading out detailed values through new dbm, current, voltage sensors. Reasoning: the generic Digital Diagnostics state sensors report state diagsOk, or else the worst severity level measured among all of the Digital Diagnostics values for that optical data point. You'd really only want to set a generic "alarm" so the box can report that it thinks something is wrong, whereafter a human can look at the graphs and/or the CLI to draw their conclusions about the alarm. Otherwise, things would quickly become too spammy as you are essentially duplicating every sensor across both regular measurements and state measurements. Further changes: - Increase maximum number of detected PSUs from 4 to 8 per the MIB. - State sensor to detect (in)sufficient power budget for all modules. - Use skip_values to hide state sensors with the notSupported value. - Use skip_values to hide sensors which are unsupported per the MIB, signified by the device returning special values -1 or -2147483648. - Add dBm, temperature "over" graphs to the mrv-od device header bar. * Add mrv-od entity-physical support MRV does not use the ENTITY-MIB data format, so we had to reconstruct the inventory from their proprietary format using the following tables from their NBS-CMMC-MIB: - nbsCmmcChassisTable - nbsCmmcSlotTable - nbsCmmcPortTable Additionally, since sensors didn't have their own ifindex in the NBS-CMMC-MIB, I went ahead and appended the last OID digit to the "containing" ifindex create a unique number. The same was done for the sensors in the yaml-discovery. * Test data for mrv-od, fix 2* pre-commit.php issues * Fix entPhysicalIndex returning 0 instead of null Some unit test breakage was caused by 62167ebcb which changed the code to return 0 instead of null when {{ $index }} was set as the entPhysicalIndex in the YamlDiscovery. So now we detect if it returns some value which may be interpreted as false, and if so we set null rather than 0.
2019-05-29 20:30:33 +02:00
"state_name": null
}
],
"state_indexes": [
{
"state_name": "nbsCmmcChassisFanStatus",
"state_descr": "notSupported",
"state_draw_graph": 0,
"state_value": 1,
"state_generic_value": 3
},
{
"state_name": "nbsCmmcChassisFanStatus",
"state_descr": "bad",
"state_draw_graph": -1,
"state_value": 2,
"state_generic_value": 2
},
{
"state_name": "nbsCmmcChassisFanStatus",
"state_descr": "good",
"state_draw_graph": 1,
"state_value": 3,
"state_generic_value": 0
},
{
"state_name": "nbsCmmcChassisFanStatus",
"state_descr": "notInstalled",
"state_draw_graph": 0,
"state_value": 4,
"state_generic_value": 2
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "notInstalled",
"state_draw_graph": 0,
"state_value": 1,
"state_generic_value": 2
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "acBad",
"state_draw_graph": -1,
"state_value": 2,
"state_generic_value": 2
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "dcBad",
"state_draw_graph": -1,
"state_value": 3,
"state_generic_value": 2
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "acGood",
"state_draw_graph": 1,
"state_value": 4,
"state_generic_value": 0
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "dcGood",
"state_draw_graph": 1,
"state_value": 5,
"state_generic_value": 0
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "notSupported",
"state_draw_graph": 0,
"state_value": 6,
"state_generic_value": 3
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "good",
"state_draw_graph": 1,
"state_value": 7,
"state_generic_value": 0
},
{
"state_name": "nbsCmmcChassisPSStatus",
"state_descr": "bad",
"state_draw_graph": -1,
"state_value": 8,
"state_generic_value": 2
},
{
"state_name": "nbsCmmcPortDigitalDiags",
"state_descr": "notSupported",
"state_draw_graph": 0,
"state_value": 1,
"state_generic_value": 3
},
{
"state_name": "nbsCmmcPortDigitalDiags",
"state_descr": "diagsOk",
"state_draw_graph": 0,
"state_value": 2,
"state_generic_value": 0
},
{
"state_name": "nbsCmmcPortDigitalDiags",
"state_descr": "diagsWarning",
"state_draw_graph": 1,
"state_value": 3,
"state_generic_value": 1
},
{
"state_name": "nbsCmmcPortDigitalDiags",
"state_descr": "diagsAlarm",
"state_draw_graph": 2,
"state_value": 4,
"state_generic_value": 2
}
]
},
"poller": "matches discovery"
}
}
Reference in New Issue Copy Permalink