In Spectrum 9.2 ( I am not sure when it actually started shipping) there are as you have discovered a couple of files that are used with the modelinggateway utility. We run on Linux Red Hat 5.7 ES virtual server images. These two files are used to create and map Spectrum data element names to those used in your CMDB. We happen to use the CA Service Desk product so we end up with their CMDB structure. These were initially provided as part of a Services Offering back in the Spectrum 8.1 days. That is how we initially got involved with the exporting of Spectrum network resources and their relationships to other network devices to initially load and update into the CMDB.
/spectrum/SS-Tools/.cmdbresource.dtd
/spectrum/SS-Tools/.cmdbresource.xml
There is an undocumented ( as far as the Spectrum(r) Modeling Gateway
Toolkit manual is concerned ) -cmdb option you can run as a parameter to
the modelinggateway task. Our command looks something like this and yes
we have a script that sets up some the parameters but you can simply
hard code the path, VNM, and export file to give it a try.
${SPECROOT}/SS-Tools/modelinggateway -vnm ${VNM} -cmdb -e ${EXPORTFILE}
What that will generate for you is a log file along with an xml file
that has a CI for each device type defined in the .cmdbresource.xml file
listed above and relationship CI's for each connection between those
network resources.
That output.xml file is used as input to the GRLoader utility provide on
the Service Desk / CMDB side.
We have used it off and on over the past few years with some success,
but I can tell you that this methodology also creates challenges on the
CMDB side mostly caused by the GRLoader. We were running on a weekly
basis and updating every CI and relationship based on that point in
time. I am sure you already can see one of the problems - links
removed over time and devices removed from Spectrum are not accounted
for in this process. There are several other challenges using the
modelinggateway export and GRLoader import/update but it is not a bad
initial one time step to get data from Spectrum into the CMDB.
Thanks
Raymond Ferber
IT Architect
Office 402-777-1868
Mobile 402-960-5126
[email protected] <mailto:[email protected]>
From: Leandro Daniel [mailto:[email protected]]
Sent: Monday, February 27, 2012 11:44 AM
To: spectrum
Subject: [spectrum] CMDB and Spectrum
Hello guys!
Let me ask a question about CMDB, we have spectrum and USD-CMDB working
togheter, all the information about routers, servers and switches are in
the spectrum (Componet detail tab), I mean; asset configuration, ISO
version, etc... my question is; how can I get all the information from
spectrum and bring to CMDB using modelinggateway?
Using default modelling gateway we can see only hostname, IPADDRESS and
Mac Address, but we need to know others information such as IOS version,
manufacture, model name, O.S version, and others configuration like that
in order to fill out the CMDB fields.
I've tried figure out some iformation in the files
$SPECROOT/SS-Tools/.cmdbresource.dtd and
$SPECROOT/SS-Tools/.cmdbresource.xml, but I did find anything
Could please help me on this case?
Thanks in advance, have a great week for everybody!
--
Leandro Daniel
Msn=> [email protected]
Skype=> [email protected]
* --To unsubscribe from spectrum, send email to [email protected]
with the body: unsubscribe spectrum [email protected]
-----------------------------------------
The information in this message may be proprietary and/or
confidential, and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify First Data
immediately by replying to this message and deleting it from your
computer.
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]<<image001.png>>
