having a failure when running the Unix Classify Probe against F5 load balancers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2019 08:51 AM
When the standard Unix Classify Multiprobe runs, when it gets down to the "snc_func_1" probe I get the Failure depicted in the image below.
so I change the probe, making the topic "show sys version" get rid of the f5.sh probe parameter. When I log into the F5 and run the command I get
username@fqdn show sys version
Sys::Version
Main Package
Product BIG-IP
Version 12.1.3
Build 0.0.378
Edition Final
Date Mon Nov 27 16:41:03 PST 2017
When I test the probe I get:
it returns error state on the input queue and the below Queue Contents. What I don't get is why this fix doesn't work. The result code=0; why does the input queue think this is an error?
- Labels:
-
Discovery

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2019 10:29 AM
Hi,
I believe you need to add the mid.ssh.shells_supported parameter to your mid server, and then add the name of the shell to the list of supported shells.
I think the unlisted shell might be tmsh. So your list would be ksh, sh, bash, tmsh
Hope this helps.
Let me know if you have any questions.
Thanks,
Cody
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-25-2019 11:24 AM
Add he parameter to the MID against which this stuff is running (although I would have though "allow_unsupported_shell" probe parameter would take care of it, but). Reran the probe; same behavior.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-26-2019 05:58 AM
Hi Duane,
In looking at your output, I see two things. First the command is running successfully. You get the sys version information. However, as you noted, you also get the message about the shell not in the list of supported shells. I don't know why that message comes up.
If you are getting an error in the input record in the ecc queue, then I believe it is either because you don't have a sensor defined for your new probe. Or because the sensor is looking for specific text in the output string and throwing an error because of that.
I see that by default, the F5 0S probe is part of a multi-probe, and does not have a sensor defined for it.
When you re-ran the command after you added the mid.ssh.shells_supported parameter, did you still see the (Shell not in supported shell list) text in the output?
Let me know if you have any questions.
Thanks,
Cody

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-01-2020 08:40 AM