"Unexpected index type" message in log

[onallion]

Hey, I'm getting the following messages in the server log:

Unexpected index type: 6 multiProcIndex 1.0

I'm guessing this is a template going rogue, but how can I know which one? Will increasing log level help?

Thanks

[jsw]

Please check if you use the correct MIB file for your Check Point release.
The type of multiProcIndex has changed in the past.
In the R76 MIB file for the 61K this is defined as "Unsigned32" whereas in R80 it is "Counter32".

You can also check with snmpwalk for any type complaints:

[someuser@zabbix ~]$ snmpwalk -v3 -u snmpuser -l authPriv -a MD5 -A 'notshown' -x DES -X 'secret' 1.2.3.4 multiProcTable
CHECKPOINT-MIB::multiProcIndex.1.0 = Wrong Type (should be Gauge32 or Unsigned32): Counter32: 1
CHECKPOINT-MIB::multiProcIndex.2.0 = Wrong Type (should be Gauge32 or Unsigned32): Counter32: 2

[sfl]

Hello,
Thanks for the inputs.

I have the same issue with checkpoint device in zabbix_proxy.log

Unexpected index type: 6 multiProcIndex 1.0
Unexpected index type: 6 multiProcIndex 2.0
Unexpected index type: 6 multiProcIndex 1.0

but when I try to poll with snmpwalk I have no errors !

snmpwalk -v 1 -c YYYY X.X.X.X CHECKPOINT-MIB::multiProcIndex

CHECKPOINT-MIB::multiProcIndex.1.0 = Counter32: 1
CHECKPOINT-MIB::multiProcIndex.2.0 = Counter32: 2

OID is correctly defined (counter32) in mib file.

Any idea ?

[huntervp]

Up!

Has someone solved this problem?

I have the same problem. OID type is correctly. Zabbix receives data, only the error log gets fat.

Zabbix log:

Unexpected index type: 6 multiDiskIndex 3.0
Unexpected index type: 6 multiDiskIndex 4.0
Unexpected index type: 6 multiDiskIndex 5.0
Unexpected index type: 6 multiDiskIndex 6.0

MIBS:

...
      MultiDiskEntry ::=
              SEQUENCE {
                multiDiskIndex        Counter32,
                multiDiskName        DisplayString,
                multiDiskSize        DisplayString,
                multiDiskUsed        DisplayString,
                multiDiskFreeTotalBytes            DisplayString,
                multiDiskFreeTotalPercent        INTEGER,
                multiDiskFreeAvailableBytes        DisplayString,
                multiDiskFreeAvailablePercent    INTEGER
              }

      multiDiskIndex OBJECT-TYPE
              SYNTAX  Counter32
              MAX-ACCESS read-only
              STATUS  current
              DESCRIPTION ""
              ::= { multiDiskEntry 1 }
...

snpmwalk:

# snmpwalk -v3 -l authPriv -u user -a SHA -A XXXXX-x AES -X YYYYY IP-ADDR CHECKPOINT-MIB::multiDiskIndex
CHECKPOINT-MIB::multiDiskIndex.1.0 = Counter32: 1
CHECKPOINT-MIB::multiDiskIndex.2.0 = Counter32: 2
CHECKPOINT-MIB::multiDiskIndex.3.0 = Counter32: 3
CHECKPOINT-MIB::multiDiskIndex.4.0 = Counter32: 4
CHECKPOINT-MIB::multiDiskIndex.5.0 = Counter32: 5
CHECKPOINT-MIB::multiDiskIndex.6.0 = Counter32: 6

# snmpwalk -v3 -l authPriv -u user -a SHA -A XXXXX-x AES -X YYYYY IP-ADDR CHECKPOINT-MIB::multiDiskIndex.1.0
Unexpected index type: 6 multiDiskIndex 1.0
CHECKPOINT-MIB::multiDiskIndex.1.0 = Counter32: 1

[huntervp]

Help me! Please!

[Vaku]

BUMP!
Any updates on this issue? Has anyone managed to resolve this?
Seems like many people having this problem with buggy Checkpoint mib file.

[martijnl20]

I solved this by downloading the corresponding mib for the running checkpoint version (r80.20 in my case) from https://supportcenter.checkpoint.com...all%20products
Replaced (this is ofcourse dependent from your mibs location) /usr/share/snmp/mibs/ietf/CHECKPOINT-MIB with the new mib (I did also notice differences with use of Gauge32, Counter32, Unsigned32)
restarted zabbix to initialize new mibs and no more messages starting with Unexpected index type: 6.