I would start with an SNMP walk of that device (or a documentation check) to determine the MIBs it uses for hardware health (assuming it has them). Once you know the MIBs you can create a custom poller for them.
Custom pollers for switch L2 and L3 ports can be complex. I do believe that this should work without custom pollers. I have a case open with SolarWinds, and am delving into Force10's support web site.
It may be that Force10 does something unexpected in regard to standard switching MIBs. But I found this in their SNMP FAQ:
Force10Networks:Technical Documentation - login required
Q. How do I calculate interface utilization, including IFG?
A. Use the standard MIB-II (RFC 1213) to monitor interfaces. To calculate a throughput value that includes the inter-frame gap (IFG), use the MIB-II octet counters and factor in the necessary constants.
But, alas, no such stats appear in NPM.
I am able to get stats for interfaces using the SolarWinds Bandwidth Gauges tool in the Engineer's Toolset. But the same ports appear grey in NPM.
See also this thread, which is about NTM, not NPM:
But I think I've digressed from the original post, which was about Hardware Health, which I'm also not getting in NPM.
don't look at Solarwinds...if you have a switch that is not responding to mib II
They poll only for RFC 1213 SNMP is well known standard
make me wonder what kind of vendor is that.....
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process.