Reference record for OID 1.3.6.1.2.1.21.3.1


parent
1.3.6.1.2.1.21.3 (partyViews)
node code
1
node name
viewTable
dot oid
1.3.6.1.2.1.21.3.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snmpSecrets(21) partyViews(3) viewTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) snmpSecrets(21) partyViews(3) viewTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) snmpSecrets(21) partyViews(3) viewTable(1)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) snmpSecrets(21) partyViews(3) viewTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) snmpSecrets(21) partyViews(3) viewTable(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) snmpSecrets(21) partyViews(3) viewTable(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/snmpSecrets/partyViews/viewTable
  • /iso/identified-organization/dod/internet/mgmt/mib/snmpSecrets/partyViews/viewTable
  • /iso/org/dod/internet/mgmt/mib-2/snmpSecrets/partyViews/viewTable
  • /iso/org/dod/internet/mgmt/mib/snmpSecrets/partyViews/viewTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/snmpSecrets/partyViews/viewTable
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/snmpSecrets/partyViews/viewTable
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/21/3/1

    Description by oid_info

    viewTable OBJECT-TYPE
    SYNTAX SEQUENCE OF ViewEntry
    ACCESS not-accessible
    STATUS mandatory
    DESCRIPTION
    "The table contained in the local database which
    defines local MIB views. Each SNMP party has a
    single MIB view which is defined by two
    collections of view subtrees: the included view
    subtrees, and the excluded view subtrees. Every
    such subtree, both included and excluded, is
    defined in this table.
    To determine if a particular object instance is in
    a particular SNMP partys MIB view, compare the
    object instances Object Identifier with each
    entry (for this party) in this table. If none
    match, then the object instance is not in the MIB
    view. If one or more match, then the object
    instance is included in, or excluded from, the MIB
    view according to the value of viewStatus in the
    entry whose value of viewSubtree has the most
    sub-identifiers. If multiple entries match and
    have the same number of sub-identifiers, then the
    lexicographically greatest instance of viewStatus
    determines the inclusion or exclusion.
    An object instances Object Identifier X matches
    an entry in this table when the number of sub-
    identifiers in X is at least as many as in the
    value of viewSubtree for the entry, and each sub-
    identifier in the value of viewSubtree matches its
    corresponding sub-identifier in X. Two sub-
    identifiers match either if the corresponding bit
    of viewMask is zero (the wild card value), or if
    they are equal.
    Due to this wild card capability, we introduce
    the term, a
    amily of view subtrees, to refer to
    the set of subtrees defined by a particular
    combination of values of viewSubtree and viewMask.
    In the case where no wild card is defined in
    viewMask, the family of view subtrees reduces to a
    single view subtree."

    View at oid-info.com

    Description by mibdepot

    The table contained in the local database which
    defines local MIB views. Each SNMP party has a
    single MIB view which is defined by two
    collections of view subtrees: the included view
    subtrees, and the excluded view subtrees. Every
    such subtree, both included and excluded, is
    defined in this table.

    To determine if a particular object instance is in
    a particular SNMP party's MIB view, compare the
    object instance's Object Identifier with each
    entry (for this party) in this table. If none
    match, then the object instance is not in the MIB
    view. If one or more match, then the object
    instance is included in, or excluded from, the MIB
    view according to the value of viewStatus in the
    entry whose value of viewSubtree has the most
    sub-identifiers. If multiple entries match and
    have the same number of sub-identifiers, then the
    lexicographically greatest instance of viewStatus
    determines the inclusion or exclusion.

    An object instance's Object Identifier X matches
    an entry in this table when the number of sub-
    identifiers in X is at least as many as in the
    value of viewSubtree for the entry, and each sub-
    identifier in the value of viewSubtree matches its
    corresponding sub-identifier in X. Two sub-
    identifiers match either if the corresponding bit
    of viewMask is zero (the 'wild card' value), or if
    they are equal.

    Due to this 'wild card' capability, we introduce
    the term, a 'family' of view subtrees, to refer to
    the set of subtrees defined by a particular
    combination of values of viewSubtree and viewMask.
    In the case where no 'wild card' is defined in
    viewMask, the family of view subtrees reduces to a
    single view subtree.

    Parsed from file rfc1353.mib.txt
    Company: None
    Module: RFC1353-MIB

    Description by circitor

    The table contained in the local database which
    defines local MIB views. Each SNMP party has a
    single MIB view which is defined by two
    collections of view subtrees: the included view
    subtrees, and the excluded view subtrees. Every
    such subtree, both included and excluded, is
    defined in this table.

    To determine if a particular object instance is in
    a particular SNMP party's MIB view, compare the
    object instance's Object Identifier with each
    entry (for this party) in this table. If none
    match, then the object instance is not in the MIB
    view. If one or more match, then the object
    instance is included in, or excluded from, the MIB
    view according to the value of viewStatus in the
    entry whose value of viewSubtree has the most
    sub-identifiers. If multiple entries match and
    have the same number of sub-identifiers, then the
    lexicographically greatest instance of viewStatus
    determines the inclusion or exclusion.

    An object instance's Object Identifier X matches
    an entry in this table when the number of sub-
    identifiers in X is at least as many as in the
    value of viewSubtree for the entry, and each sub-
    identifier in the value of viewSubtree matches its
    corresponding sub-identifier in X. Two sub-
    identifiers match either if the corresponding bit
    of viewMask is zero (the 'wild card' value), or if
    they are equal.

    Due to this 'wild card' capability, we introduce
    the term, a 'family' of view subtrees, to refer to
    the set of subtrees defined by a particular
    combination of values of viewSubtree and viewMask.
    In the case where no 'wild card' is defined in
    viewMask, the family of view subtrees reduces to a
    single view subtree.

    Parsed from file RFC1353-MIB.mib
    Module: RFC1353-MIB

    Information by oid_info

    Automatically extracted from RFC1353

    Information by mibdepot

    viewTable OBJECT-TYPE SYNTAX SEQUENCE OF ViewEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table contained in the local database which defines local MIB views. Each SNMP party has a single MIB view which is defined by two collections of view subtrees: the included view subtrees, and the excluded view subtrees. Every such subtree, both included and excluded, is defined in this table. To determine if a particular object instance is in a particular SNMP party's MIB view, compare the object instance's Object Identifier with each entry (for this party) in this table. If none match, then the object instance is not in the MIB view. If one or more match, then the object instance is included in, or excluded from, the MIB view according to the value of viewStatus in the entry whose value of viewSubtree has the most sub-identifiers. If multiple entries match and have the same number of sub-identifiers, then the lexicographically greatest instance of viewStatus determines the inclusion or exclusion. An object instance's Object Identifier X matches an entry in this table when the number of sub- identifiers in X is at least as many as in the value of viewSubtree for the entry, and each sub- identifier in the value of viewSubtree matches its corresponding sub-identifier in X. Two sub- identifiers match either if the corresponding bit of viewMask is zero (the 'wild card' value), or if they are equal. Due to this 'wild card' capability, we introduce the term, a 'family' of view subtrees, to refer to the set of subtrees defined by a particular combination of values of viewSubtree and viewMask. In the case where no 'wild card' is defined in viewMask, the family of view subtrees reduces to a single view subtree." ::= { partyViews 1 }

    Information by circitor

    viewTable OBJECT-TYPE SYNTAX SEQUENCE OF ViewEntry ACCESS not-accessible STATUS mandatory DESCRIPTION "The table contained in the local database which defines local MIB views. Each SNMP party has a single MIB view which is defined by two collections of view subtrees: the included view subtrees, and the excluded view subtrees. Every such subtree, both included and excluded, is defined in this table. To determine if a particular object instance is in a particular SNMP party's MIB view, compare the object instance's Object Identifier with each entry (for this party) in this table. If none match, then the object instance is not in the MIB view. If one or more match, then the object instance is included in, or excluded from, the MIB view according to the value of viewStatus in the entry whose value of viewSubtree has the most sub-identifiers. If multiple entries match and have the same number of sub-identifiers, then the lexicographically greatest instance of viewStatus determines the inclusion or exclusion. An object instance's Object Identifier X matches an entry in this table when the number of sub- identifiers in X is at least as many as in the value of viewSubtree for the entry, and each sub- identifier in the value of viewSubtree matches its corresponding sub-identifier in X. Two sub- identifiers match either if the corresponding bit of viewMask is zero (the 'wild card' value), or if they are equal. Due to this 'wild card' capability, we introduce the term, a 'family' of view subtrees, to refer to the set of subtrees defined by a particular combination of values of viewSubtree and viewMask. In the case where no 'wild card' is defined in viewMask, the family of view subtrees reduces to a single view subtree." ::= { partyViews 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.21.3.1.1 viewEntry 4 4 Information on a particular family of view
    subtrees included in or excluded from a particular
    SNMP party's MIB view.