SNMPCollector stopped polling critical devices CheckPoint 13500 Firewalls

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Today we are struggling with an issue on the Internal Firewalls which used to be monitored by SNMPCollector (UIM) and now we have noticed we have no metrics for them. 

I even tried to delete one of them and discover it again, stop snmpcollector, modify associated templates and so on, but the thing seems to be on SNMPCollector which is having issues discovering it. 

UIM version 8.5.1
SNMPCollector version 4.03
Device Certification Deployer 3.1

Have a look at this lines from SNMPCollector.log. I will attach the log to the case. 

Line 3900850: Mar 05 15:42:00:580 [Thread-9, snmpcollector] Discovering device 10.0.227.11 with ID D3d5b729434e1db33ebdad797568c3cee
Line 3900869: Mar 05 15:42:00:592 [DiscoveryController1, snmpcollector] Discovering device 10.0.227.11 with Metric Family NormalizedSystemInfo
Line 3900870: Mar 05 15:42:00:605 [DiscoveryController1, snmpcollector] Device 10.0.227.11 does not support Vendor Cert systemMib for metric family NormalizedSystemInfo
Line 3900871: Mar 05 15:42:00:605 [DiscoveryController1, snmpcollector] Did not find an valid vendor certifications for device 11.10.223.11 in metric family NormalizedSystemInfo
Line 3900872: Mar 05 15:42:00:606 [DiscoveryController1, snmpcollector] Discovering device 10.0.227.11 with Metric Family NormalizedVirtualCentersInfo
Line 3900873: Mar 05 15:42:00:612 [DiscoveryController1, snmpcollector] Device 10.0.227.11 does not support Vendor Cert vmvcAimStatVCGroupMib for metric family NormalizedVirtualCentersInfo
Line 3900874: Mar 05 15:42:00:612 [DiscoveryController1, snmpcollector] Did not find an valid vendor certifications for device 10.0.227.11 in metric family NormalizedVirtualCentersInfo
Line 3900875: Mar 05 15:42:00:612 [DiscoveryController1, snmpcollector] Discovering device 10.0.227.11 with Metric Family NormalizedHostAggregateMetricsInfo

Environment

UIM: 8.51

Component : UIM - SNMPCOLLECTOR 4.0.3

Cause

This issue happens when users monitor the SNMPV3 devices having different credentials, our suspect was the is was being caused by an unsupported device (like Fortigate 1500D) or specific protocol (SNMPV3)
This seems to be a known issue with the probe and same is mentioned in the probe Docs.

Resolution

Engineering team fixed this problem in hot fix "snmpcollector-4.0.3-HF3"