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

Re: bug or feature?

Phil Shafer wrote:

Martin Bjorklund writes:

The XSD in RFC 4741 allows <startup> as <target> in an <edit-config>.
It is not clear if this a bug in the XSD or a feature.  Section
8.7.5.1 lists the operations the server MUST support for the :startup
capability, but it doesn't say that the server MAY support others.  So
is this intentional or not?  (if the intention was that the server MAY
support this, how would a manager know?)


This is definitely a bug.  The intention was to not allow editing
of the startup config, since it was really just a chunk of flash
memory and isn't loaded into a real database.


Another related bug (or feature) is that the XSD supports <startup> as
<target> in <delete-config>.  In section 7.4 there is actually an
example where this is used.  But is this really supposed to be
supported?  It is not listed in 8.7.5.1.


My initial reaction here is that this is a bug.  Startup represents
a section of flash memory, and deleting it IIRC isn't possible.  My
memory is fuzzy, but I don't think we intended to allow this.  The
fact that it's in an example conflicts this, so maybe my memory's off.



I remember many WG discussions about this.
RFC 4741 is supposed to allow <startup> to be edited or deleted,
but not mandate it by the agent implementor.

IMO, there is absolutely no use case for editing the <startup>.
There is some use for deleting a corrupted <startup>, but minor.
If the agent SW is buggy, such that *it* is responsible for the
<startup> corruption, then <copy-config> may not work to fix it.
Perhaps something in the <startup> is causing the bug to show up,
or even cause a reboot.

Perhaps in some implementation, deleting the <startup> could allow
the agent to boot 'far enough' to reload a previous SW image, and
then recover the config to <running> somehow.



Thanks,
 Phil


Andy

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