Hi -
> From: "Joe Marcus Clarke" <[email protected]>
> To: "Randy Presuhn" <[email protected]>
> Cc: <[email protected]>
> Sent: Thursday, August 29, 2013 4:11 PM
> Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on
> draft-asai-vmm-mib-04)
...
> I would be happy with read-only objects that showed the operational
> values. But there was a use case for changing the operational
> parameters via SNMP SET.
In my book, that's a configuration change. It might be made with the
intention of reverting to some previous configuration at some time in
the future, but a configuration change nonetheless.
It sounds like the claim here is that there are knobs whose initial
settings are presumed to persist as part of system configuration,
but for which any "tweaks" are forgotten. Those are two different
knobs, should be clearly identified as such, and their relationship
formally spelled out. Depending on the complexity of their relationship,
it sounds like you may be asking for THREE objects (not all in MIB
modules, of course):
- the persistent configuration parameter, Netconf or whatever
- the writable "tweak" knob, whose values might potentially
be constrained by persistent configuration
- the read-only operational value, which would be some
function of the configuration, the tweak knob, and heaven-knows-what
else.
Randy
_______________________________________________
OPSAWG mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/opsawg
