Indexes with more than one number

[jesmit]

Hello all. I am running into a problem with snmp indexes that contain more than a single number.

For example, I am trying to monitor the vServer instances of a Netscaler an the base OID of the index is 1.3.6.1.4.1.5951.4.1.3.1.1.1. Rather than the typical Index of 1.3.6.1.4.1.5951.4.1.3.1.1.1.1 = STRING: "vServerName", the Netscaler is spitting out OIDs like 1.3.6.1.4.1.5951.4.1.3.1.1.1.9.115.101.99.117.114. 101.118.112.110 = STRING: "vServerName"

Zabbix appears to only be grabbing the last number. 9557:20091231:101201.275 Item [Netscaler1:vServerName] error: OID [1.3.6.1.4.1.5951.4.1.3.1.1.1.110] value has unknown type [0x81]

I am not sure if this is a bug or a design decision, and I have never seen a wierd index like this from a peice of hardware. In the meantime I have hardcoded all the OIDs, so this is not critical for me. Just figured I would put it out there for comment/informational purposes.

[ratonu]

netscaler template

Hi

can someone help with some kind off citrix netscaler low level discovery rules, i'm running into the same problem with complex indexes,

thanks

[danrog]

Search the forums for advsnmp.discovery (or even just google). This has already been discussed a few times and someone has come up with a perl script to get around this current limitation.

[dirckcopeland]

netscaler template

Danrog,
Do you have a link to the perl script you mention?
thanks