SNMP Monitoring Important Notice

Hello!

In today’s article we will go through some important points when using SNMP Monitor with Henimos.

At the time SNMP Monitoring is not well detected, this guide might be helpful.

About SNMP MonitoringNMP

When operating SNMP Monitoring with Hinemos, be sure to provide the following information:

– OID to monitor

– Numeric Monitoring > Critical, Warning and Info judgment threshold

– Character String Monitoring > Character String to be detected

Internal Specifications

When using SNMP Monitoring, Hinemos uses the command “snmpget” to retrieve the information.

Please note that the information is NOT acquired by snmpwalk.

If the command snmpget fails, the priority will be identified as “Unknown”.

Important Details

In the case where SNMP Monitoring results in multiple instances for one specific OID, Hinemos will set the priority level to “Unknown”.

Example

The current operational state of the interface will be described as “ifOperStatus” in the following example.
“ifOperStatus” can be obtained by reading the OID “.1.3.6.1.2.1.2.2.1.8”.
If you check this OID, it will be detected as “Unknown” priority level in Hinemos!

Indeed, if I use the command snmpwalk in my environment with the mentioned above OID, I will obtain the following result:

As you can see, I fetched 2 instances.

Now let’s see what happens when using snmpget

That’s right… As you can see it failed!

That is the reason why Hinemos will interpret this error as “Unknown” in the Manager.

Workaround

As you may have noticed, if we have multiple instances, it is necessary to set your trap definition to the matching OID.

ifOperStatus.1 > 1.3.6.1.2.1.2.2.1.8.1
ifOperStatus.2 > 1.3.6.1.2.1.2.2.1.8.2
Etc…

In our example, if you want to monitor the first instance, you must specify “1.3.6.1.2.1.2.2.1.8.1”.

“I have too many instances, setting up all SNMP Monitor one by one is going to take so long…!” you would say, however there is no alternative but to create your own shell script and monitor it through the Custom Monitor for the moment.
※ We will get the chance to look in more detail to the script creation another time.

Conclusion

People might say “I can run a ping and/or get a snmpwalk properly… Yet my SNMP Monitor doesn’t work!”.
I know this aspect can be a little bit difficult to understand, that is why I came to the idea of writing this article.
In the end, I hope you found this guide helpful!

Thank you for reading!


ご意見やお問い合わせについて

この記事へのご意見やお問い合わせについては、こちら(お問い合わせフォーム)もしくは
Hinemos営業担当【hsd-sales@atomitech.jp】までご連絡ください。

※お問い合わせフォームからご連絡の場合には、お問い合わせ内容で「Hinemosについて」を選択し、
 本文の冒頭に「Hinemos研究日記_【タイトル名】」とご記載ください。
※メールアドレスへご連絡の場合には、件名を「Hinemos研究日記_【タイトル名】」でご連絡ください。