On 8 March 2018 at 22:43, Phil Shafer wrote:
> Unfortunately not, since MIBs use numeric identifier for fields,
> so if a developer inserts "leaf foxtrot" between "leaf echo" and
> "leaf geronimo" (where it really belongs) then the MIB ordering has
> changed and the numbers and all off. The MIB
Saku Ytti writes:
>As a user I'd be comfortable at stability which matches display
>XML/JSON stability, and I think that level of stability would be
>implied.
Unfortunately not, since MIBs use numeric identifier for fields,
so if a developer inserts "leaf foxtrot" between "leaf echo" and
"leaf ger
Hey,
> I'm not an snmp-head, but something could certainly be done here.
> I see two issues, one being the need for a formal MIB where our
> content evolves release-to-release. Making per-release MIBs would
> be a pain, and I'm not sure how well tools would handle those. A
> "generic" MIB might
[changed subject line)
Saku Ytti writes:
>You have | display json and xml, I assume json was relatively modest
>amount of work, as you have formal source of data, so someone only
>needed to write translator, without being aware of all context to
>support | display json, which also means, no one ne
4 matches
Mail list logo
