Great Circle Associates Network-Automation
(April 2005)
 

Indexed By Date: [Previous] [Next] Indexed By Thread: [Previous] [Next]

Subject: Re: available network automation tools
From: "Georg Magschok" <gio @ epygi . de>
Organization: Epygi Labs DE GmbH
Date: Wed, 13 Apr 2005 18:07:49 +0200
To: "'Paxton'" <paxton @ binsh . com>,<network-automation @ greatcircle . com>
Importance: Normal
In-reply-to: <Pine.GSO.4.33.0504130759140.2006-100000@darksun.binsh.com>

> (1) is good because your model can be more explicit, less confusing,
> probably easier to automate from; but is bad because you lose the ability
> to do comparisons between different devices/vendors
> (2) is good because you can do across the network
> audits/comparisons/reporting, regardless of device type/vendor, but is bad
> because you end up force-fitting some devices into your model, which
> complicates automation for those devices down the road

(1) would lead to a lot of propriatory management information

for (2) to work you need a good base of standards for many different 
applications/devices/network types/layers, defining the management information!
This is easy to achieve for a network of pure IPv4 routers with nothing
else. It is hard to achieve though if the network is truly heterogenous
in the technologies used :(

(Somebody wrote it already, but: of course we need the right mixture of that)

bye,
  Gio

Epygi Labs DE GmbH - Georg 'Gio' Magschok 



References:
Indexed By Date Previous: Re: available network automation tools
From: Paxton <paxton@binsh.com>
Next: Re: available network automation tools
From: Daniel Hagerty <hag@linnaean.org>
Indexed By Thread Previous: Re: available network automation tools
From: Paxton <paxton@binsh.com>
Next: Re: available network automation tools
From: Daniel Hagerty <hag@linnaean.org>

Google
 
Search Internet Search www.greatcircle.com