We are using modelinggateway to export the Spectrum models in CMDB format using the below command.
./modelinggateway -vnm lxcaspecd01 -cmdb -e specCMDB.xml
Command is working fine and able to export the data. However, half of the file contains the relationships of the type "null". We are interested in only the actual relations and not interested in null relation type. How can we ignore these while exporting using the modelinggateway tool? Please suggest.
Below is an example.
<relation> <type>null</type> <provider> <name>NTSERVER1</name> <product_version>6.3, Windows Server 2012 R2 Standard, 64-bit</product_version> <mac_address>00:00:11:1a:ee:f4</mac_address> <system_name>NTSSERVER1</system_name> </provider> <dependent> <name>LXSERVER1</name> <product_version>3.10.0-957.10.1.el7.x86_64, Red Hat Enterprise Linux Server release 7.6 (Maipo)</product_version> <mac_address>00:10:16:2a:ef:ba</mac_address> <system_name>LXSERVER1</system_name> </dependent></relation>
meaja05Roger_Nasonpolmi05Matthew_Gay please help me if you have idea on this.
Looks like the cmdb option supports the following relationships:
SPECTRUM Relationship CMDB RelationshipDevice-to-Device connects toService-to-Device monitorsService-to-Service supports
Are those vms? are they for an ESX? Not sure if the cmdb export function works with those. If those are connected you can edit the xml to use this:
Thank you Jay for quick response.
We disabled the Device-to-Device relationship in .cmdbresource.xml file as we are not interested in it. However, these are coming as null relation type when we run modelinggateway utility to export. If I enable that relation type, these will be coming as connects to relation type.
Is it possible to not get the Device-to-Device relation in any other ways?
Oh, ok, I thought you were noting it was broken
What happens if you try to import it? Does it actually fail or does it bypass it? I assume it fails. Unfortunately I can't see how to exclude those without manually editing the import file and removing them.