Linux based appliance discovered as router

[Beginner_Servi1]

Hi, I need some suggestions here with Discovery. I have a CI (its an appliance running on Linux Kernel) getting discovered as a Router. I want it to be discovered as an Appliance (there is no Class for Appliances , however, I can create one under Servers) or Linux Server. I tried adding the sysoid ref from the xml payload under Linux CI Classification , however, it did not succeed . Any help?

We are able to login to the appliance via SSH on port 22 and it is showing OS as Linux. The probable reason for ServiceNow to get confused is that the appliance has lots of routing information as it is a WebSense.

Please suggest...

[A Westervelt]

The Linux SNMP classifier, by default, is inactive and typically wouldn't be used. Enabling the classifier tends to collect a lot more things as Linux Servers then you'd actually want it to. It's likely your device has a lot of routing capabilities, which is why Discovery is classifying it as such.

If the device is running a Linux OS and you can use SSH, I'd recommend trying that route first. However, most appliances are running a hardened version that you might not be able to query everything by default.

In the end, you may have to come up with your own Discovery SNMP pattern to create your CI properly in the table you want and with the right attributes that are specific to the manufacturer/model. I'd recommend watching Doug's video on creating SNMP patterns to help you out.

https://community.servicenow.com/community?id=community_article&sys_id=dfd86535db172300f21f5583ca961...

[tim_broberg · Accepted solution]

So, you're saying you want to discover it with ssh?

Does it currently run Unix - Classify before SNMP - Classify?

If so, you probably want to ensure that you have a Discovery Credential created that works on the device.

If not, go to Discovery Definition / port probes, and make sure that the classification priority for ssh before (lower in value) snmp such that it will try ssh first.

Once you have it running Unix - Classify, and it's at least returning some information from the device, you'll need to add a new record in Discovery Definition / CI Classification / Unix to tell it how to recognize this kind of appliance. If you're not getting sufficient information from the existing Unix - Classify, you may need to add another subprobe to the Unix - Classify multiprobe to collect what information you need.

    - Tim.