Re: setting ifAdminStatus when interface cannot go up

Dave Shield <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
On 19 May 2010 17:23, Lewis Adam-VNQM87 <[email protected]> wrote:
> Hmmm, no replies.
>
> As a matter of interest, can anyone tell me whether the question was too
> dumb, not appropriate for this forum, so incredibly clever it's beyond
> the scope of this forum, ...

Definitely not the first.
The other two - probably a bit of both.


> Maybe it's regarded as an implementation-specific design decision
> but I had hoped there would be some official guidance somewhere.

If you're looking for official guidance about SNMP, then you are definitely
in the wrong place.   These lists are for the support of one particular
SNMP implementation.   We have no special status or role in the
development of the SNMP protocol.
  (Individual contributors may have been involved at various times,
but not the Net-SNMP project itself.   This list should not be regarded
as a source of definitive knowledge about SNMP standards).



> Better still, if anyone knows where I could get an answer, it would be
> much appreciated.

SNMP is an IETF-supported standard, so you might try asking on one
of their mailing lists.


My 2p worth:
>  1. Do we allow the ifAdminStatus to be set but happily ignore it
>  2. Silently ignore the request (i.e. return success but don't set value).
>  3. Immediately return an error code e.g. inconsistentValue.

Either 1) or 3) is probably a reasonable approach.
You could make a good case for either of those choices.
2) is Just Plain Wrong.


Dave

------------------------------------------------------------------------------

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.