Skip to content

Commit 00f729c

Browse files
authored
Update FortiSwitch YAML (librenms#18477)
* Update FortiSwitch YAML Add ENTITY-SENSOR-MIB::entPhySensorOperStatus value 3. It was missing despite being a valid value according to the MIB: EntitySensorStatus ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "An object using this data type represents the operational status of a physical sensor. The value 'ok(1)' indicates that the agent can obtain the sensor value. The value 'unavailable(2)' indicates that the agent presently cannot obtain the sensor value. The value 'nonoperational(3)' indicates that the agent believes the sensor is broken. The sensor could have a hard failure (disconnected wire), or a soft failure such as out- of-range, jittery, or wildly fluctuating readings." SYNTAX INTEGER { ok(1), unavailable(2), nonoperational(3) } * Add files via upload * Delete tests/data/fortiswitch_148f-fpoe.json Failed tests have nothing to do with my patch. Seems the test data is borked.
1 parent 82548fe commit 00f729c

File tree

4 files changed

+18
-11277
lines changed

4 files changed

+18
-11277
lines changed

resources/definitions/os_discovery/fortiswitch.yaml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,4 +42,5 @@ modules:
4242
value: 12
4343
states:
4444
- { value: 1, descr: OK, graph: 1, generic: 0 }
45-
- { value: 2, descr: Not OK, graph: 1, generic: 2 }
45+
- { value: 2, descr: Unavailable, graph: 1, generic: 2 }
46+
- { value: 3, descr: Non Operational, graph: 1, generic: 2 }

0 commit comments

Comments
 (0)