[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: netconf and working "on the box"
Hi Faye,
Either case doesn't really have any OOB
management except driving all the way to the curb and plug the laptop
into the console port. I guess we can argue in this case what is the
point of using XML then because they also have the legacy OSS to deal
with?
Maybe I'm just ignorant (I've never built any global access networks),
but why couldn't you run xmlconf on the laptop when it is
connected to the serial port? The xmlconf protocol certainly
doesn't care what media is used to carry the packets...
But shouldn't we say that out front that we are not addressing
the network management scenario where the in-band is the only means?
I don't understand this question.
Also the problem with SNMP, XML over a bunch of stuff plus FTP/TFTP will
probably not do well with a low bandwidth management interface. Has
anybody look into the wireless management yet? They are much worse than
DSL last time I looked.
Could you give some real numbers? What type of configuration
changes need to be made over what bandwidth in what time period?
I am not actually sure that xmlconf will be that much more bandwidth-
intensive than a CLI session (often you would have to do multiple
CLI commands to do something that could be accomplished with one
xmlconf RPC call)... In what situations will this be a problem?
Could you give real-life examples?
Also I have a question regarding low bandwidth
management interface: Does this mean we need an ACK for critical
management traffic or we definitely DON'T need a ACK to stress out the
interface even more? Very interested in finding out what is your
experience with this? I certainly don't know the answer.
Could you explain what you mean by "ACK"? The current xmlconf
encoding runs over TCP, which needs ACKs to progress. Also the
RPC mechanism always includes a (good or error) response.
Margaret
--
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/>