question Re: Custom probe/sensor classifies but doesn't identify in Developer forum

Custom probe/sensor classifies but doesn't identify

scott111 — Thu, 26 Jan 2017 17:18:41 GMT

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 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.

Re: Custom probe/sensor classifies but doesn't identify

rajeevlochan82 — Thu, 26 Jan 2017 19:39:45 GMT

Not sure of your exact issue but look for ECC Queue entries associated with problem record......

Re: Custom probe/sensor classifies but doesn't identify

ismailkiswani — Thu, 26 Jan 2017 19:46:39 GMT

Hello Scott,

did you create Classifiers for HP Enclosures?

for SNMP check the configuration on the Switch and it should be the same in Servicenow but it looks that it returns OIDs and it's working. try to increase the default timeout on the MID Server.

Please check this video

SNMPClassifier.mov - YouTube

hope that helps.

Regards,

Ismail Al-Kiswani

Re: Custom probe/sensor classifies but doesn't identify

scott111 — Thu, 26 Jan 2017 20:33:31 GMT

I created an classifier for HP Enclosure and the gs.log statement you see in the classifier below does write to the log. Also, the discovery log I provided above does say "Classified, now Identifying". We tried SNMP discovery and it doesn't work.

Re: Custom probe/sensor classifies but doesn't identify

ismailkiswani — Thu, 26 Jan 2017 20:46:50 GMT

Could you share the SNMP xml imput and output.

not Identified means it's not able to get the devices or the CI information. check the HP MIBs in the instance.

Re: Custom probe/sensor classifies but doesn't identify

rajeevlochan82 — Thu, 26 Jan 2017 20:47:38 GMT

Can you check your ECC queue to see if you getting name contains bladesystem in your ecc

Re: Custom probe/sensor classifies but doesn't identify

scott111 — Thu, 26 Jan 2017 21:40:55 GMT

Did not see "name contains bladesystem" in ECC queue but I assume my classifier worked. This would suggest it found correct class for target:

Look at "correct answer" in this thread. It looks very much like the same issue but his back-ticks solution did not work for me.

https://community.servicenow.com/thread/154583?q=Custom%20probe/sensor%20classifies%20but%20doesn%27t%20identify#860968

Re: Custom probe/sensor classifies but doesn't identify

rajeevlochan82 — Thu, 26 Jan 2017 21:44:50 GMT

check the 6 ECC queue entries....

Re: Custom probe/sensor classifies but doesn't identify

ismailkiswani — Thu, 26 Jan 2017 22:01:18 GMT

Check the ECC Queue (Input and Output XML)

Re: Custom probe/sensor classifies but doesn't identify

ismailkiswani — Thu, 26 Jan 2017 22:10:39 GMT

Check the ECC queue entries and check if SNMP returned the sysObjectID.

if returned check it in the SNMP OID table

for HP enclosure you should create custom probe, and than create a parameter called allow_unsupported_shells and set that value to true. This resolved the issue, and I was to able to test the probe and run some commands.

Re: Custom probe/sensor classifies but doesn't identify

venkatiyer1 — Thu, 26 Jan 2017 22:15:07 GMT

Hi Scott,

In the screenshot you have attached above for UNIX classification i dont see a trigger probe attached to it. Do you have one attached to it during classification phase? May be this wiki article will aid you.

Horizontal discovery process flow

Re: Custom probe/sensor classifies but doesn't identify

ismailkiswani — Thu, 26 Jan 2017 22:23:54 GMT

Hi Scott,

This might help you same issue

HP BladeSystem c7000 Enclosures

Re: Custom probe/sensor classifies but doesn't identify

scott111 — Fri, 27 Jan 2017 15:24:30 GMT

The Bladesystem has a non-standard cli and so yes you need to allow unsupported shells and I had figured that out early on.

The SNMP probe returns: <results probe_time="12995"><result error="SNMP probe timed out. Target is either unreachable or there are no valid credentials for it."

We may re-visit discovery through SNMP at some point but right now can I tell the discovery to NOT use SNMP? Apparently, if any one method (snmp, ssh, wmi, etc.) fails then the whole discovery of the target is marked failed.

"... there is code in the sensor that interprets any error as a failure and it triggers additional classifier even though the class matched". From the link I posted above.

Re: Custom probe/sensor classifies but doesn't identify

scott111 — Fri, 27 Jan 2017 17:21:01 GMT

I looked at that link on "horizontal discovery" and it applies to Istanbul. I have Fuji. But i did get me thinking: must my classifier trigger an "identifier probe"?

Re: Custom probe/sensor classifies but doesn't identify

scott111 — Fri, 27 Jan 2017 19:01:29 GMT

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

Re: Custom probe/sensor classifies but doesn't identify

b__RajatC — Mon, 10 Jun 2024 16:10:00 GMT

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 ?