Kirby,
If you would be so kind as to elaborate on a few of your points outlined below.
On Apr 8, 2005 6:52 PM, Kirby Files <ksfiles@gmail.com> wrote:
> What we were looking for was a full network equipment and relationship
> model, generic enough to model all types of routers, switches and
> containers, along with a scriptable configuration generation engine to
> interpret that model into device-dependent configuration deltas, and a
> service activation manager to resolve dependencies (which services
> required changes to which devices) and schedule config changes.
Perhaps it's the cleaning fluid fumes in my apartment today, but I'm
having trouble fully grasping what you're describing there. Can you
take it down a notch to laymens terms?
> Unfortunately, 4 years later, we still wouldn't be able to replace our
> homegrown configuration management system with any COTS system that
> had comparable features. And the importance of having a queryable
> network model cannot be overstated. This has become the core of our
> OSS systems: driving data collection, automating NMS configuration and
> performance measurement, and enabling much better inventory control
> than we ever had before.
What is a "queryable network model" ?
Thank you,
aaron.glenn
Follow-Ups:
References:
|
|
