- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-26-2017 09:18 AM
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.
Solved! Go to Solution.
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2017 11:01 AM
Problem solved. I simply needed to add a Bladesystem - Identity probe that was triggered by my Bladesystem classifier. Thanks for the info!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-10-2024 09:10 AM
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 ?