A few tips on how to troubleshoot interrogation.
The vendor is usually good step to start with (unless the remote device is linux based).
Identifying which interrogation script to start with
In order to identify interrogation scripts which sets the vendor: cisco, run grep -R writeTag | grep vendor | grep cisco in the parsers directory:
cisco/ios/ios_device_type_interrogation.ind: # writeTag("vendor", "cisco")
cisco/ios/show_version_interrogation.ind: if ( cisco == 1) { writeTag("vendor", "cisco") }
cisco/nexus/show_version-interrogation.ind: writeTag("vendor", "cisco")
cisco/ios/ios_device_type_interrogation.ind
Line commented out, so not interesting (# writeTag("vendor", "cisco"))
cisco/ios/show_version_interrogation.ind
First lines of the indeni script:
#! META
name: ios-show-version
description: IOS show version
type: interrogation
requires:
vendor: cisco
os.name: ios
A bit funny how it writes "vendor: cisco" and "os.name: ios", but still requires those tags to be set to run the script.
cisco/nexus/show_version-interrogation.ind
First line of the indeni script
#! META
name: nexus-show-version-interrogation
description: fetch system info for interrogation
type: interrogation
#! REMOTE::SSH
show version
#! PARSER::AWK
No requirements, and cisco is written as vendor.
Tags written by the script:
writeTag("os.name", "nxos")
writeTag("vendor", "cisco")
writeTag("product", "switch")
writeTag("model", model)
writeTag("hostname", h[1])
writeTag("os.version", version)
Bingo!
Testing interrogation scripts manually
To test the script manually against the device, run the following command (replace credentials and IP):
command-runner.sh full-command --verbose --basic-authentication indeniuser,indenipassword --ssh indeniuser,indenipassword show_version-interrogation.ind 192.168.2.1
Did you get any tags there? If not, could you please paste the output from the log here (please go ahead and obfuscate any details pertaining to your environment).
Hope that helped!
/Patrik