Netgear SNMP template - best way to fix value mapping of boxServicesFanItemState

[gerald23]

The netgear fastpath template seems to have incorrect value mapping for the fan state FASTPATH-BOXSERVICES-PRIVATE-MIB::boxServicesFanItemState
A value of 2 is detected as 'failure' in the current template version

      
          uuid: 3046d246b1064c749c1c9144442c0fac
          name: 'FASTPATH-BOXSERVICES-PRIVATE-MIB::boxServicesFanItemState'
          mappings:
            -
              value: '1'
              newvalue: operational
            -
              value: '2'
              newvalue: failed
            -
              value: '3'
              newvalue: powering
            -
              value: '4'
              newvalue: notpowering
            -
              value: '5'
              newvalue: notpresent
        -​

However a current MIB download from the netgear m4300 downloads page shows

    
boxServicesFanItemState OBJECT-TYPE
             SYNTAX      INTEGER {
                                  notpresent(1),
                                  operational(2),
                                  failed(3),
                                  powering(4),
                                  nopower(5),
                                  notpowering(6),
                                  incompatible(7)
                                 }​

What would be the best way to fix this? Just adjusting the value mappings manually? I find it odd that a current template contains the wrong value mappings, could it be a misconfiguration instead?

[MM347]

Bump because, still an issue somehow.

[MM347]

Does anyone know a manual way to fix this myself at all?

[alvinstarr]

I fixed the problem by modifying the mapping of the fans and power supplies in the templates maps.
I also had to modify the discovery trigger rules since they used hard coded values

[MeJI]

Hi guys, try this one, add this mib as indicated in the template. Below is a link to instructions for working with mib files.

https://www.linuxshop.ru/forum/f7/t40885--resheno-centos-8-snmp-ne-mogu-najti-mib.html