Has anyone faced issues with monitoring the hardware health of Huawei and Fortinet devices through SolarWinds? If not, could you please share the action plan or steps you followed to ensure successful monitoring?
@thwackahsanpk are you referring to the missing hardware health monitoring resource, when you list resources on these vendors? From a Fortinet perspective, I have wondered when we'd see OOTB support for hardware on more of these devices. Some Fortinet devices are supported (FortiSwitches, for example), but the key ones, imho, are FortiGuard firewalls, which as far as I'm aware still have no hardware health support.
Until this happens, we have to rely on custom pollers which we build ourselves, using the SNMP OIDs provided by the vendor.This fairly old thread details that SWI are working on implementing additional support for Fortnet devices, but it's not implemented yet:
FortiGate Hardware Details not Polled
You're right, and I believe the main issue is that the OIDs provided by Fortinet are often not included in SolarWinds' built-in MIB database. As a result, when we try to use custom pollers with those OIDs, we usually get an "OID not supported" error.
I think it's time SolarWinds seriously considers expanding their MIB support for Fortinet devices, especially for critical hardware like FortiGate firewalls. Until then, we're stuck trying to work around these limitations manually.
What problems are you facing?
Data not visible
I've managed to get quite a few custom pollers working on various FortiNet devices over the years, so the OIDs are there. It's just manual work
Regarding any missing ones, if a SNMP walk of a device shows OIDs which are not in the MIB browser within the platform, there is a process to have them added to the global MIB database we all share:https://solarwindscore.my.site.com/SuccessCenter/s/article/Add-MIBs-to-the-SolarWinds-MIB-database?language=en_US
I have followed this process a few times, and it's usually a pretty quick turnaround. However, once the MIBs are added, it simply means we can use them in a new Universal Device Poller going forward.
That's right
