[network::nokia::timos::snmp::plugin] new mode sas-alarm

[rmorandell-pgum]

Community contributors

Description

new mode for sas alarms.
TIMETRA-SAS-ALARM-INPUT-MIB.txt

SNMP walk:

.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.2.1 = STRING: "PSU_1_Sammelalarm"
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.2.2 = STRING: "PSU_1_230V_fehlt"
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.2.3 = STRING: "PSU_2_Sammelalarm"
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.2.4 = STRING: "PSU_2_230V_fehlt"
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.3.1 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.3.2 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.3.3 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.3.4 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.4.1 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.4.2 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.4.3 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.4.4 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.5.1 = INTEGER: 3
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.5.2 = INTEGER: 3
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.5.3 = INTEGER: 3
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.5.4 = INTEGER: 3
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.6.1 = INTEGER: 2
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.6.2 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.6.3 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.6.4 = INTEGER: 1
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.7.1 = Timeticks: (280) 0:00:02.80
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.7.2 = Timeticks: (280) 0:00:02.80
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.7.3 = Timeticks: (280) 0:00:02.80
.1.3.6.1.4.1.6527.6.2.2.2.9.1.1.7.4 = Timeticks: (280) 0:00:02.80

Alarm should be raised if OID .1.3.6.1.4.1.6527.6.2.2.2.9.1.1.6. = 2
OID .1.3.6.1.4.1.6527.6.2.2.2.9.1.1.7. could be ignored, values are not updated

Output: tmnxSasAlarmInputDescription, tmnxSasAlarmInputPolarity, tmnxSasAlarmOutputSeverity
Warning-status and critical-status for tmnxSasAlarmOutputSeverity

--warning-status
(Default: '%{alarm_input_admin_state} eq "up" and %{alarm_input_status} eq "alarm" and %{alarm_output_severity} =~ /minor/')
You can use the following variables: %{alarm_input_admin_state}, %{alarm_input_status}, %{alarm_output_severity}

--critical-status
Set critical threshold for status (Default: '%{alarm_input_admin_state} eq "up" and %{alarm_input_status} eq "alarm" and %{alarm_output_severity} =~ /major|critical/').
You can use the following variables: %{ipv4_oper_state}, %{admin_state}, %{display}

Type of change

• Patch fixing an issue (non-breaking change)
• New functionality (non-breaking change)
• Functionality enhancement or optimization (non-breaking change)
• Breaking change (patch or feature) that might cause side effects breaking part of the Software

How this pull request can be tested ?

mib attached

Checklist

• I have followed the coding style guidelines provided by Centreon
• I have commented my code, especially hard-to-understand areas of the PR.
• I have rebased my development branch on the base branch (develop).
• I have provide data or shown output displaying the result of this code in the plugin area concerned.

[lucie-dubrunfaut]

Hello @rmorandell-pgum
Thank you again for your contribution 🙏
This PR is handle internally here : #5274