network device discovery - error for unsupported shell

[Ravish Shetty]

we are getting the message for a network device discovery (for an IP switch) as

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

how do we enforce the specific type of shell execution ('tcsh') from the ServiceNow end?

we are using SSH credentials.

[tim_broberg]

ios is definitely not bourne-shell compatible.

The feature meant to deal with ios is allow unsupported shells. You can add allow_unsupported_shells = true to your probe and it will not assume bourne-shell compatibility: it won't try to set the path, it won't do anything with sudo, it won't handle scripts, etc.

The catch is, probes are stateless and ios is very stateful. I am aware of no way to string commands together in ios.

You might consider looking at patterns.
    - Tim.

[preston_burkha1]

So, to give you background on what I am doing/struggling with... I am failing to get Discovery to identify switch port relationships to the devices and mac addresses that are associated. I have read through the docs around l2 discovery here. Under the section "additional" probe called, I had enabled the option but get the error above that the shell is unsupported when I review the ecc queue. I have also added in the allow unsupported shells parameter to the probe but I'm still getting the error.

[robertgeen]

Ravish,

Network device discovery is only really supported by SNMP. What's more then likely happening here is that it has SSH port open so it's trying it first and then giving you that message because the shell isn't supported. From what I remember (and there was a really good indepth article on here somewhere) it's futile effort to try to discover network devices with shell and you should just use SNMP. Hope this helps.