Custom probe/sensor classifies but doesn't identify

scott111
Kilo Expert

Writing custom probe for HP Enclosure device. My custom probe allows unsupported shells and does "show enclosure info" ssh command and gets back plenty of info to classify. Discovery output using custom probe says it classifies based on ssh output but then it goes ahead and tries SNMP to classify and fails. I've read that any sensor failure marks the whole discovery as a failure. Discovery output:

SNMP Classify                   SNMP probe timed out. Target is either unreachable or there are no valid credentials for it.

SNMP Classify                   Active, couldn't classify, now finished

UNIX Classify                   Unsupported shell, '$0', and probe parameter 'allow_unsupported_shells' is set to 'false'. Supported shells are [ksh, sh, bash, tcsh, csh]

UNIX Classify                   Active, couldn't classify, now finished

UNIX Classify                   Active, couldn't classify, now finished

UNIX Classify                   Classified, now Identifying

Shazzam                                   Active, now Classifying

ShazzamLaunch         MID midhost.com discovering 10.xx.xx.xx

Discovery                             Discovery started

Debug "gs.log" statements print from my classifier and from custom sensor but not from my identifier.

1 ACCEPTED SOLUTION

Problem solved. I simply needed to add a Bladesystem - Identity probe that was triggered by my Bladesystem classifier. Thanks for the info!


View solution in original post

15 REPLIES 15

Hello Scott,

 

I also have requirement to discovery a device with non-standard CLI. I have list of commands but when i am trying to execute them by custom probe I am getting error "The MID Server code is unable to run this ECC Queue output topic" Any suggestions ?