Reference record for OID 1.3.6.1.6.3.1134.1.1


parent
1.3.6.1.6.3.1134.1 (v2AdminSnmpScalars)
node code
1
node name
snmpID
dot oid
1.3.6.1.6.3.1134.1.1
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminSnmpScalars(1) snmpID(1)}
  • {iso(1) org(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminSnmpScalars(1) snmpID(1)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) snmpV2(6) snmpModules(3) v2AdminMIB(1134) v2AdminSnmpScalars(1) snmpID(1)}
  • iri oid
  • /iso/identified-organization/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminSnmpScalars/snmpID
  • /iso/org/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminSnmpScalars/snmpID
  • /iso/iso-identified-organization/dod/internet/snmpV2/snmpModules/v2AdminMIB/v2AdminSnmpScalars/snmpID
  • iri by oid_info
    /ISO/Identified-Organization/6/1/6/3/1134/1/1

    Description by mibdepot

    An SNMPv2 entity's administratively-unique identifier.

    The initial value for this object may be configured via an
    operator console entry or via an algorithmic function
    defined by the vendor or administrator. In the later case,
    the following guidelines are recommended:

    1) The first four octets should be set to the binary
    equivalent of the device vendor's SNMP network management
    private enterprise number as assigned by the Internet
    Assigned Numbers Authority (IANA). For example, if
    Acme Networks has been assigned { enterprises 696 },
    the first four octets would be assigned '000002b8'H.

    2) The remaining eight octets are the cookie whose










    contents are determined via one or more enterprise-
    specific methods. Such methods must be designed so as
    to maximize the possibility that the value of this
    object will be unique in the device's administrative
    domain. For example, the cookie may be the IP address
    of the device, or the MAC address of one of the
    interfaces, with each address suitably padded with
    random octets, or possibly a unique cookie determined
    by the device's model# and serial#. If multiple methods
    are defined, then it is recommended that the cookie be
    further divided into one octet that indicates the method
    being used and seven octets which are a function of
    the method.

    Parsed from file cacheflow-v2-adm.mib.txt
    Company: cacheflow
    Module: V2ADMIN-MIB

    Information by oid_info

    Child arc 0 is used to translate between SNMPv1 and SNMPv2 notification parameters as explained in IETF RFC 2576, section 3.

    Information by mibdepot

    snmpID OBJECT-TYPE SYNTAX SnmpID MAX-ACCESS read-only STATUS current DESCRIPTION "An SNMPv2 entity's administratively-unique identifier. The initial value for this object may be configured via an operator console entry or via an algorithmic function defined by the vendor or administrator. In the later case, the following guidelines are recommended: 1) The first four octets should be set to the binary equivalent of the device vendor's SNMP network management private enterprise number as assigned by the Internet Assigned Numbers Authority (IANA). For example, if Acme Networks has been assigned { enterprises 696 }, the first four octets would be assigned '000002b8'H. 2) The remaining eight octets are the cookie whose contents are determined via one or more enterprise- specific methods. Such methods must be designed so as to maximize the possibility that the value of this object will be unique in the device's administrative domain. For example, the cookie may be the IP address of the device, or the MAC address of one of the interfaces, with each address suitably padded with random octets, or possibly a unique cookie determined by the device's model# and serial#. If multiple methods are defined, then it is recommended that the cookie be further divided into one octet that indicates the method being used and seven octets which are a function of the method." ::= { v2AdminSnmpScalars 1 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6)

    US DoD

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.6.3.1134.1.1.0 snmpID 0 0 None

    Brothers (6)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.6.3.1134.1.3 snmpMaxMessageSize 1 1 The maximum length in octets of an SNMPv2 message which
    this SNMPv2 entity can send or receive and process, determined
    as the min…
    1.3.6.1.6.3.1134.1.4 maxIdentityNameLength 1 1 The maximum length in octets which a particular implementation
    will allow for any object which specifies an identityName.
    This ob…
    1.3.6.1.6.3.1134.1.5 maxGroupNameLength 1 1 The maximum length in octets which a particular implementation










    will allow for any object which specifies a groupName.
    This object…
    1.3.6.1.6.3.1134.1.6 maxV2ContextNameLength 1 1 The maximum length in octets which a particular implementation
    will allow for the v2ContextName object, the acContextName
    object,…
    1.3.6.1.6.3.1134.1.7 maxViewTreeNameLength 1 1 The maximum length in octets which a particular implementation
    will allow for the viewTreeName object, and any other
    object which…
    1.3.6.1.6.3.1134.1.8 maxTransportLabelLength 1 1 The maximum length in octets which a particular implementation
    will allow for objects whose syntax is TransportLabel.
    This object…