Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..
428 views

SUSE linux not identified as Unix CI type in VMWare discovery

Hi,

I am discovering VMWare infrastructure using VMware vCenter Connection by WMI and VIM job, followed by the VMware vCenter Topology by VIM job.

After discovery observed that, it has not identified SUSE linux as Unix CI type, but it has included RHEL in Unix CI type.

Please let me if I need to do any additional configuration for this.

Regards,

Sridhara.

Regards,
Sridhara.
12 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

Hi there,

 

what's your current CP level?

The accurate discovery of Unix and Windows nodes was greatly improved in CP30

https://docs.microfocus.com/itom/Universal_Discovery_Content_Pack:30/CP_sw/CP_rn

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

A quick fix would be to handle the Suse scenario in the normalization rules where you can change the class type (CIT) of the incoming Suse node from discovery.
Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: SUSE linux not identified as Unix CI type in VMWare discovery

Hi, Thanks for your suggestion. This node is discovered by VMWare job. Can you please let me know which domain should I select while creating normalization rule. Should I restart discovery job again after adding normalization rule.
Regards,
Sridhara.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

to what domain do you refer? 

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: SUSE linux not identified as Unix CI type in VMWare discovery

I am referring to package name, marked in attached screenshot. Which package name should I choose for VMWare discovery

Regards,
Sridhara.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

In Host Connection by shell you should have something like this


 
[CDATA: lsb_release -a ; echo ERROR_CODE:$?]
[CDATA: LSB Version: n/a
Distributor ID: SUSE LINUX
Description: SUSE Linux Enterprise Server 12 SP1
Release: 12.1
Codename: n/a
ERROR_CODE:0]
</EXEC>

[CDATA: cat /etc/SuSE-release ; echo ERROR_CODE:$?]
[CDATA: SUSE Linux Enterprise Server 12 (x86_64)
VERSION = 12
PATCHLEVEL = 1
# This file is deprecated and will be removed in a future service pack or release.
# Please check /etc/os-release for details about this release.
ERROR_CODE:0]
</EXEC>

one if these commands it's failing, probably due to permissions. With data from these results we will model some node attributes with Suse relevant data.

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

In Adapter Management search for the file named oidToHostClass.xml

and add to the end of it a new rule.

Run the VMware topology job again but this time with results included. You will find in the huge Communication Log the hostname of your problematic node.

In my CP29 lab env this is who I have in the VMware CommLog a Suse node (I don't have a problem with accurate discovery as you have)

<object class="unix" isReference="false" is_anchor="false">
<attribute name="host_isvirtual" type="Boolean">true</attribute>
<attribute name="node_role" type="String" list="true" operator="ADD">
<vector>
<value>virtualized_system</value>
</vector>
</attribute>
<attribute name="host_hostname" type="String">ucmdbsle11</attribute>
<attribute name="host_key" type="String">000C2233F444</attribute>
<attribute name="host_iscomplete" type="Boolean">true</attribute>
<attribute name="data_description" type="String">SUSE Linux Enterprise 11 (64-bit)</attribute>
<attribute name="os_family" type="String">unix</attribute>
<attribute name="platform_vendor" type="String">VMware</attribute>
<attribute name="host_biosuuid" type="String">3234497-99E5-272F-5F45-0C2BF6D4F464</attribute>
</object>

 

once you found your object in the result vector (hopefully the complete declaration of it) paste it here and we can work on it with a custom normalization rule.

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
Tags (1)
0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: SUSE linux not identified as Unix CI type in VMWare discovery

Hi,

 

Should I add these lines after

</ns2:normalization-rule>

</ns2:normalization-rules>

or before these lines.

Regards,
Sridhara.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

In order to avoid confusion, can you provide the node object from the result vector?
I can create the normalization rule for you.

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: SUSE linux not identified as Unix CI type in VMWare discovery

Hi,

 

I have attached file export of node properties. OS type identified if SUSE, it classified as NODE CI Type.

Regards,
Sridhara.
0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: SUSE linux not identified as Unix CI type in VMWare discovery

There it is


<rule-input>
<attribute name="data_description" value="Linux" compare-type="contains" />
</rule-input>
<rule-output>
<attribute name="discovered_model">
<value>Linux</value>
</attribute>
<class-type>unix</class-type>
</rule-output>

norm-linux.JPGMake sure to keep the proper identation for the xml file as in the attached picture.

The id is 2989 in my scenario but you can change it as long as it's unique.

You will have to rerun the VMware discovery job to see if it works.

Kind regards,
Bogdan Mureșan
EMEA CMS Technical Success
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.