Update sdwan.pm - Fix incorrect traffic counters calculation #5343
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The traffic counters are reported via SNMP are in kbps and only needs to be multiple by 1000 to get the bps values.
From the Fortigate MIBI file:
The available bandwidth in kbps of bi-direction traffic detected by a health-check on a specific member link.
Type of change
How this pull request can be tested ?
Run
perl src/centreon_plugins.pl --plugin=network::fortinet::fortigate::snmp::plugin \ --mode sdwan \ --hostname firewall-cluster.example.com \ --snmp-version 3 \ --snmp-username='SNMP-User1' \ --authpassphrase='secret1' \ --authprotocol='SHA' \ --privpassphrase='secret2' \ --privprotocol='AES' \ --use-new-perfdata
Example SNMP data
.2.3.6.1.4.1.12356.101.4.9.2.1.2.7 = INTERNET
.1.3.6.1.4.1.12356.101.4.9.2.1.4.7 = 0
.1.3.6.1.4.1.12356.101.4.9.2.1.5.7 = 8.617
.1.3.6.1.4.1.12356.101.4.9.2.1.6.7 = 0.065
.1.3.6.1.4.1.12356.101.4.9.2.1.9.7 = 0.000
.1.3.6.1.4.1.12356.101.4.9.2.1.10.7 = root
.1.3.6.1.4.1.12356.101.4.9.2.1.11.7 = 27453
.1.3.6.1.4.1.12356.101.4.9.2.1.12.7 = 29552
.1.3.6.1.4.1.12356.101.4.9.2.1.13.7 = 57005
.1.3.6.1.4.1.12356.101.4.9.2.1.14.7 = wan1
Checklist