Free BSD discovery?

lada
Kilo Contributor

Hallo,

Does discovery discover FreeBSD servers?

Thanks,

Lada

14 REPLIES 14

Hi Doug,


Posted the XML input . Please have a look.


Thanks


Amit


Hi Doug,

We are facing the below issue.

Input:
<results probe_time="27067" result_code="0">
<result id="6f10ed420a0a0b7e49052d83a32b586f" name="sh ${file:esx.sh}" order="1" topic="SSHCommand">
<results error="SSH authentication or connection failure" probe_time="18002" result_code="900000">
<result error="SSH authentication or connection failure">
<output/>
</result>
<parameters>
<parameter name="discover" value="CIs"/>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="priority" value="0"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="command_to_run" value="sh ${file:esx.sh}"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="name" value="sh ${file:esx.sh}"/>
<parameter name="topic" value="SSHCommand"/>
<parameter name="esx.sh" value="#!/bin/sh # This command is rarely installed, so a Bourne shell script is used to squelch the exit status and sensor warning when not found. # tcsh doesn't squelch exist status codes within backticked statements echo `vmware -v 2>&1`"/>
</parameters>
</results>
</result>
<result id="e5e075a2a9fe1561018f2a9636d5ec39" name="uname -a" order="1" topic="SSHCommand">
<results error="SSH authentication or connection failure" probe_time="4306" result_code="900000">
<result error="SSH authentication or connection failure">
<output/>
</result>
<parameters>
<parameter name="discover" value="CIs"/>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="priority" value="0"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="command_to_run" value="uname -a"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="name" value="uname -a"/>
<parameter name="topic" value="SSHCommand"/>
</parameters>
</results>
</result>
<result id="ab613cdf9f5312003cb191aec32e7044" name="sh ${file:f5.sh}" order="1" topic="SSHCommand">
<results error="SSH authentication or connection failure" probe_time="4306" result_code="900000">
<result error="SSH authentication or connection failure">
<output/>
</result>
<parameters>
<parameter name="discover" value="CIs"/>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="f5.sh" value="#!/bin/sh echo `tmsh show sys version 2>&1`"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="priority" value="0"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="command_to_run" value="sh ${file:f5.sh}"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="name" value="sh ${file:f5.sh}"/>
<parameter name="topic" value="SSHCommand"/>
</parameters>
</results>
</result>
<parameters>
<parameter name="agent" value="mid.server.usavispsnsapp01"/>
<parameter name="use_class" value="discovery_classy_unix"/>
<parameter name="source" value="10.143.39.114"/>
<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>
<parameter name="sys_id" value="7d4cafd86f355700ddfb8ebf2c3ee496"/>
<parameter name="sys_created_on" value="2018-04-27 10:05:40"/>
<parameter name="used_by_discovery" value="true"/>
<parameter name="state" value="ready"/>
<parameter name="discover" value="CIs"/>
<parameter name="response_to" value="094c6b5c6f355700ddfb8ebf2c3ee406"/>
<parameter name="priority" value="0"/>
<parameter name="agent_correlator" value="353cab986f355700ddfb8ebf2c3ee4cd"/>
<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>
<parameter name="sequence" value="1630690c1300000001"/>
<parameter name="port" value="22"/>
<parameter name="cidata" value="<CIData><data><fld name="ip_address">10.143.39.114</fld></data></CIData>"/>
<parameter name="name" value="UNIX - Classify"/>
<parameter name="topic" value="MultiProbe"/>
<parameter name="queue" value="output"/>
<parameter name="ecc_queue" value="7d4cafd86f355700ddfb8ebf2c3ee496"/>
</parameters>
</results>
 
Thanks,
Pavan

Amit Sharma4
Mega Expert

This XML file does not appear to have any style information associated with it. The document tree is shown below.


<results probe_time="2203" result_code="0">


<result id="6f10ed420a0a0b7e49052d83a32b586f" name="sh ${file:esx.sh}" order="1" topic="SSHCommand">


<results probe_time="1344" result_code="0" warn="vmware: not found ">


<result warn="vmware: not found ">


<output/>


</result>


<parameters>


<parameter name="agent" value="mid.server.VMID01T"/>


<parameter name="use_class" value="discovery_classy_unix"/>


<parameter name="source" value="10.3.191.246"/>


<parameter name="table_name" value="ecc_queue"/>


<parameter name="command_to_run" value="sh ${file:esx.sh}"/>


<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>


<parameter name="used_by_discovery" value="true"/>


<parameter name="esx.sh" value="#!/bin/sh


# This command is rarely installed, so a Bourne shell script is used to squelch the exit status and sensor warning when not found.


# tcsh doesn't squelch exist status codes within backticked statements


echo `vmware -v 2>&1`"/>


<parameter name="discover" value="CIs"/>


<parameter name="priority" value="2"/>


<parameter name="use_snc_ssh" value="true"/>


<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>


<parameter name="port" value="22"/>


<parameter name="cidata" value="<CIData><data><fld name="dns_name">bsdserver1.abc.com</fld><fld name="ip_address">10.3.191.246</fld><fld name="dns_domain">abc.com</fld><fld name="name">bsdserver1</fld><fld name="location">5dc6581737963140859627d2b3990e80</fld></data><rl name="cmdb_ip_service_ci:ci"><fld name="isM2M">true</fld><fld name="table_name">cmdb_ip_service_ci</fld><fld name="field_name">ci</fld><fld name="target_table_name">cmdb_ip_service</fld><fld name="target_ref_field_name">service</fld><rl_rec><fld name="description">Apache </fld><fld name="service">e433d6bdc0a8016400081f03a8dd1536</fld></rl_rec></rl></CIData>"/>


<parameter name="name" value="sh ${file:esx.sh}"/>


<parameter name="topic" value="SSHCommand"/>


</parameters>


</results>


</result>


<result id="e5e075a2a9fe1561018f2a9636d5ec39" name="uname -a" order="1" topic="SSHCommand">


<results probe_time="94" result_code="0">


<result>


<output>


FreeBSD bsdserver1.abc.com 7.2-RELEASE FreeBSD 7.2-RELEASE #0: Fri May 1 08:49:13 UTC 2009 root@walker.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386


</output>


</result>


<parameters>


<parameter name="agent" value="mid.server.VMID01T"/>


<parameter name="use_class" value="discovery_classy_unix"/>


<parameter name="source" value="10.3.191.246"/>


<parameter name="table_name" value="ecc_queue"/>


<parameter name="command_to_run" value="uname -a"/>


<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>


<parameter name="used_by_discovery" value="true"/>


<parameter name="discover" value="CIs"/>


<parameter name="priority" value="2"/>


<parameter name="use_snc_ssh" value="true"/>


<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>


<parameter name="port" value="22"/>


<parameter name="cidata" value="<CIData><data><fld name="dns_name">bsdserver1.abc.com</fld><fld name="ip_address">10.3.191.246</fld><fld name="dns_domain">abc.com</fld><fld name="name">bsdserver1</fld><fld name="location">5dc6581737963140859627d2b3990e80</fld></data><rl name="cmdb_ip_service_ci:ci"><fld name="isM2M">true</fld><fld name="table_name">cmdb_ip_service_ci</fld><fld name="field_name">ci</fld><fld name="target_table_name">cmdb_ip_service</fld><fld name="target_ref_field_name">service</fld><rl_rec><fld name="description">Apache </fld><fld name="service">e433d6bdc0a8016400081f03a8dd1536</fld></rl_rec></rl></CIData>"/>


<parameter name="name" value="uname -a"/>


<parameter name="topic" value="SSHCommand"/>


</parameters>


</results>


</result>


<parameters>


<parameter name="agent" value="mid.server.VMID01T"/>


<parameter name="use_class" value="discovery_classy_unix"/>


<parameter name="source" value="10.3.191.246"/>


<parameter name="error" value=""/>


<parameter name="table_name" value="ecc_queue"/>


<parameter name="port_probe" value="97ff2abd0a0a070300b7f37daa11a241"/>


<parameter name="sys_id" value="548599020f5b9200934ce388b1050e09"/>


<parameter name="from_host" value=""/>


<parameter name="sys_created_on" value="2016-05-11 14:25:52"/>


<parameter name="used_by_discovery" value="true"/>


<parameter name="state" value="ready"/>


<parameter name="discover" value="CIs"/>


<parameter name="response_to" value="3f751d420f5b9200934ce388b1050ebf"/>


<parameter name="from_sys_id" value=""/>


<parameter name="agent_correlator" value="c8751d020f5b9200934ce388b1050e5a"/>


<parameter name="priority" value="2"/>


<parameter name="probe" value="10e0eebd0a0a0b4f61f46a5027df7fb6"/>


<parameter name="processed" value=""/>


<parameter name="sequence" value="154a035ab580000001"/>


<parameter name="port" value="22"/>


<parameter name="cidata" value="<CIData><data><fld name="dns_name">bsdserver1.abc.com</fld><fld name="ip_address">10.3.191.246</fld><fld name="dns_domain">abc.com</fld><fld name="name">bsdserver1</fld><fld name="location">5dc6581737963140859627d2b3990e80</fld></data><rl name="cmdb_ip_service_ci:ci"><fld name="isM2M">true</fld><fld name="table_name">cmdb_ip_service_ci</fld><fld name="field_name">ci</fld><fld name="target_table_name">cmdb_ip_service</fld><fld name="target_ref_field_name">service</fld><rl_rec><fld name="description">Apache </fld><fld name="service">e433d6bdc0a8016400081f03a8dd1536</fld></rl_rec></rl></CIData>"/>


<parameter name="name" value="UNIX - Classify"/>


<parameter name="topic" value="MultiProbe"/>


<parameter name="queue" value="output"/>


<parameter name="ecc_queue" value="548599020f5b9200934ce388b1050e09"/>


</parameters>


</results>


Ok,



So without the debug which would really be valuable you could try adding another classification criteria in the linux classifier that triggered on if the name contained BSD..I dont know if it does, Im only assuming so would be sure with the debug log..



find_real_file.png



If that creates a linux server then you are off to the races, then it would be just checking the probes make sure they all work.



HOWEVER, you now have a few decisions to make...



1. Do you want to create your own BSD Classifier?   Maybe the probes for linux need to be tweaked a bit to work on BSD and would justify having its own classifier


2. Do you want your BSD servers in their own class?   Or can they share the linux class?


This works. It created a new Linux server with same basic info. I'll present it further and see what my management plans.


Thanks a lot to you and Tim.