[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: On box implementation

HI,

Glenn - the Juniper case is somewhat untypical because the CLI
looks like XML.

The real problem is when the management models used in the CLI
and SNMP MIBs are very different and/or when the management operations
in the CLI are very different than SNMP operations (such as for
performing actions).

The other aspect is whether organizationally, the same person or
team are developing the CLI code and the code for other management
interfaces. If they are different (or done at different times),
then due to human nature, the code will diverge.

At 02:03 PM 7/2/2002 -0400, Phil Shafer wrote:
>"Glenn Waters" writes:
>>Phil, does the implementation of XML on the box share the same "method"
>>routines as the CLI implementation? Is the XSD used to create the CLI?
>
>The same data that drives the JUNOS UI drives the generation of the
>XSD and DTD files. The function that is run when you type 'show
>interfaces media' is the same function that is run when you do
>the matching rpc:
>
>   <rpc>
>      <get-interface-information>
>        <media/>
>      </get-interface-information>
>   </rpc>
>
>There's a pipe operation called 'display xml' which allows the
>user to see the raw xml output in the CLI:
>
>    show interfaces media | display xml
>
>>One of the discussion points that comes up frequently is that many SNMP
>>implementations are different enough from the CLI implementations that two
>>sets of code get written on the box (one for CLI and one for SNMP). When
>>considering a move to XML it is important that the vendors can implement
>>once and get more than one transport encoding.
>
>Shared infrastructure is always a win, This is similar to folks
>that have built their internal infrastructure around SNMP. Any
>standard should allow this without requiring it.
>
>Thanks,
> Phil
Regards,
/david t. perkins


--
to unsubscribe send a message to xmlconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/xmlconf/>