Am 22.04.2010 um 07.20 schrieb Koski, David: > 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.
We have been modeling gateway to send updates to Spectrum for years, with very few problems. Our authoritative db fills in a template to do a single add/update/delete as appropriate, including topological placement for adds and updates. We haven't had any problems with devices getting put in Universe or changing Topologies. We do have the job that runs this try a seek on the IP that we will be modeling, which prevents collisions, but even when there are collisions, it just fails the add. Mathias Wegner ISC Networking --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
