Same with us, but I'm having to double check IPs, names, port status, etc. Needless to say CLI seems to have gotten a little slower over the years, so we've outgrown this solution. Modeling Gateway seems to fix a lot of the issues we have doing this via CLI, but the issue of every existing model issued a create moving to the Universe view is a bit annoying (Particularly with 5200 devices).
I'm hoping I can find a way that the topology stays put when issued a new
create and the device just stays alone. I'm dreading having to dump the entire
device and topology update all my changes and re-import it. That's a scripting
nightmare. The CLI integration was bad enough, but now having to worry about
issuing a create to an existing device, updating and the topology changing
instead of holding on to it isn't very fun. Unfortunately, right now, I can
never guarantee the IP, the DNS or that the device truly exists or not ,since
this isn't the authoritative source and I don't have a good way of mapping
topology from a script stand point, hence, this whole conversations.
Dave
From: [email protected] [mailto:[email protected]]
Sent: Thursday, April 22, 2010 4:24 AM
To: spectrum
Subject: SV: [spectrum] Modeling Gateway
Hi,
It's so funny to here you say this. I have had my eyes on it, had begun to
build plans to use it, but not tried it or even looked at it for so many many
year. We have a rather advanced integration with our CMDB were all devices are
auto modelled/deleted in Spectrum using global collections as "service
enablers". But I've built this with the CLI scripting only, as I haven't had
the time to learn about the modeling GW.
Bad, bad me ;)
/Roberth
________________________________
Från: Koski, David [mailto:[email protected]]
Skickat: den 21 april 2010 17:16
Till: spectrum
Ämne: [spectrum] Modeling Gateway
I must admit after many years, I have yet to touch the modeling gateway.
With this said, I see the modeling gateway will not create duplicate models
(great!), but my issue so far is it seems you have to specify a container to
create a device.
So this leads to me the question, if we are importing the device into Spectrum
and the model already exists, is there a way not to get the device to move to
the Universe view without specifying the Topology view? The issue is we don't
have a consistent nature as of yet of containers in the topology and I'd like
to start importing devices but not disturb the existing topology till we can
tackle at consistent topology structure.
Is there a way to do this?
David
------------------
David Koski
GCFA, GISP, GSEC, RHCE
ITS Communications Systems and Data Centers
734-647-8993 (Office)
734-678-5824 (Mobile)
[cid:[email protected]]
* --To unsubscribe from spectrum, send email to
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum
[email protected]
* --To unsubscribe from spectrum, send email to
[email protected]<mailto:[email protected]> with the body: unsubscribe spectrum
[email protected]
---
To unsubscribe from spectrum, send email to [email protected] with the body:
unsubscribe spectrum [email protected]<<inline: image001.png>>
