lib.ipc.shmem.iftable_mib: add ifIndex to the shmem segment#1533
Open
alexandergall wants to merge 1 commit into
Open
lib.ipc.shmem.iftable_mib: add ifIndex to the shmem segment#1533alexandergall wants to merge 1 commit into
alexandergall wants to merge 1 commit into
Conversation
The SNMP agent only generates objects that are included explicitly in the shmem segment. Even though the ifIndex value is created by the agent itself, the OID is not instantiated without ifIndex being present in the shmem segment. Background: SMIv2 (RFC2578) specifies Objects which are both specified in the INDEX clause of a conceptual row and also columnar objects of the same conceptual row are termed auxiliary objects. The MAX-ACCESS clause for auxiliary objects is "not-accessible" The current implementation assumed that ifIndex was of this type and need not be instantiated by the SNMP agent. However, the ifTable MIB predates this specification and declares MAX-ACCESS as "read-only". Therefore, even though it is rare, an SNMP manager can expect that this object exists.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The SNMP agent only generates objects that are included explicitly in the shmem segment. Even though the ifIndex value is created by the agent itself, the OID is not instantiated without ifIndex being present in the shmem segment.
Background: SMIv2 (RFC2578) specifies
Objects which are both specified in the INDEX clause of a
conceptual row and also columnar objects of the same conceptual row
are termed auxiliary objects. The MAX-ACCESS clause for auxiliary
objects is "not-accessible"
The current implementation assumed that ifIndex was of this type and need not be instantiated by the SNMP agent. However, the ifTable MIB predates this specification and declares MAX-ACCESS as "read-only". Therefore, even though it is rare, an SNMP manager can expect that this object exists.