Re: text format of configurations

[Jon Saperia <saperia@jdscons.com>]

>     > - the tools to _automate_ interaction with the box.  eg: SNMP or XML over
>     >   telnet/ssh with standardized DTDs, ala snmp MIBs.  any thing that can
>     >   be done in CLI, MUST be possible via XML.
> 
> Is XML, per se, a hard requirement for you?  Or would a syntax which was
> the same on the CLI, and had the same advantages that you see in XML be
> preferable?
> 
>     > - it MUST be possible to determine the FULL configuration of a box.  ie: NO
>     >   hidden "defaults".  if 'ip directed-broadcast' is the default, a 'show
>     >   config' option MUST exist that will display that in the o/p (ascii or XML).
> 
> Hmmm.  In principle I like this, but it could get awfully bulky awfully
> fast.  There are a _lot_ of defaults in some configs.  Perhaps required
> support for a "super verbose" version of "show config"?  Something like
> "show config full" or "show config all"?
> 
>                                 -Bill
> 
Having an external representation in XML could be a good thing. Having
local configurations take a file in XML parse it and generate native
configuration files is also potentially a good thing. That said, I still
think that may not be the best way for interactive machine to machine
management.
> 
> 
> 

Thanks,
/jon
--

Jon Saperia		     saperia@jdscons.com
			     Phone: 617-744-1079
			     Fax:   617-249-0874
			     http://www.jdscons.com/