⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 rfc3014.txt

📁 <VC++网络游戏建摸与实现>源代码
💻 TXT
📖 第 1 页 / 共 4 页
字号:
RFC 3014                  Notification Log MIB             November 2000--nlmLogTable OBJECT-TYPE    SYNTAX      SEQUENCE OF NlmLogEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION     "A table of Notification log entries.     It is an implementation-specific matter whether entries in this     table are preserved across initializations of the management     system.  In general one would expect that they are not.     Note that keeping entries across initializations of the     management system leads to some confusion with counters and     TimeStamps, since both of those are based on sysUpTime, which     resets on management initialization.  In this situation,     counters apply only after the reset and nlmLogTime for entries     made before the reset MUST be set to 0."    ::= { nlmLog 1 }nlmLogEntry OBJECT-TYPE    SYNTAX      NlmLogEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION     "A Notification log entry.     Entries appear in this table when Notifications occur and pass     filtering by nlmConfigLogFilterName and access control.  They are     removed to make way for new entries due to lack of resources or     the values of nlmConfigGlobalEntryLimit, nlmConfigGlobalAgeOut, or     nlmConfigLogEntryLimit.     If adding an entry would exceed nlmConfigGlobalEntryLimit or system     resources in general, the oldest entry in any log SHOULD be removed     to make room for the new one.     If adding an entry would exceed nlmConfigLogEntryLimit the oldest     entry in that log SHOULD be removed to make room for the new one.     Before the managed system puts a locally-generated Notification     into a non-null-named log it assures that the creator of the log     has access to the information in the Notification.  If not it     does not log that Notification in that log."    INDEX       { nlmLogName, nlmLogIndex }    ::= { nlmLogTable 1 }Kavasseri                   Standards Track                    [Page 14]RFC 3014                  Notification Log MIB             November 2000NlmLogEntry ::= SEQUENCE {    nlmLogIndex                Unsigned32,    nlmLogTime                 TimeStamp,    nlmLogDateAndTime          DateAndTime,    nlmLogEngineID             SnmpEngineID,    nlmLogEngineTAddress       TAddress,    nlmLogEngineTDomain        TDomain,    nlmLogContextEngineID      SnmpEngineID,    nlmLogContextName          SnmpAdminString,    nlmLogNotificationID       OBJECT IDENTIFIER}nlmLogIndex OBJECT-TYPE    SYNTAX     Unsigned32 (1..4294967295)    MAX-ACCESS not-accessible    STATUS     current    DESCRIPTION     "A monotonically increasing integer for the sole purpose of     indexing entries within the named log.  When it reaches the     maximum value, an extremely unlikely event, the agent wraps the     value back to 1."    ::= { nlmLogEntry 1 }nlmLogTime OBJECT-TYPE    SYNTAX      TimeStamp    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value of sysUpTime when the entry was placed in the log. If     the entry occurred before the most recent management system     initialization this object value MUST be set to zero."    ::= { nlmLogEntry 2 }nlmLogDateAndTime OBJECT-TYPE    SYNTAX      DateAndTime    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The local date and time when the entry was logged, instantiated     only by systems that have date and time capability."    ::= { nlmLogEntry 3 }nlmLogEngineID OBJECT-TYPE    SYNTAX      SnmpEngineID    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The identification of the SNMP engine at which the NotificationKavasseri                   Standards Track                    [Page 15]RFC 3014                  Notification Log MIB             November 2000     originated.     If the log can contain Notifications from only one engine     or the Trap is in SNMPv1 format, this object is a zero-length     string."    ::= { nlmLogEntry 4 }nlmLogEngineTAddress OBJECT-TYPE    SYNTAX      TAddress    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The transport service address of the SNMP engine from which the     Notification was received, formatted according to the corresponding     value of nlmLogEngineTDomain. This is used to identify the source     of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted     from the SNMPv1 trap pdu.     This object MUST always be instantiated, even if the log     can contain Notifications from only one engine.     Please be aware that the nlmLogEngineTAddress may not uniquely     identify the SNMP engine from which the Notification was received.     For example, if an SNMP engine uses DHCP or NAT to obtain     ip addresses, the address it uses may be shared with other     network devices, and hence will not uniquely identify the     SNMP engine."    ::= { nlmLogEntry 5 }nlmLogEngineTDomain OBJECT-TYPE    SYNTAX      TDomain    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "Indicates the kind of transport service by which a Notification     was received from an SNMP engine. nlmLogEngineTAddress contains     the transport service address of the SNMP engine from which     this Notification was received.     Possible values for this object are presently found in the     Transport Mappings for SNMPv2 document (RFC 1906 [8])."    ::= { nlmLogEntry 6 }nlmLogContextEngineID OBJECT-TYPE    SYNTAX      SnmpEngineID    MAX-ACCESS  read-only    STATUS      current    DESCRIPTIONKavasseri                   Standards Track                    [Page 16]RFC 3014                  Notification Log MIB             November 2000     "If the Notification was received in a protocol which has a      contextEngineID element like SNMPv3, this object has that value.      Otherwise its value is a zero-length string."     ::= { nlmLogEntry 7 }nlmLogContextName OBJECT-TYPE    SYNTAX      SnmpAdminString    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The name of the SNMP MIB context from which the Notification came.     For SNMPv1 Traps this is the community string from the Trap."    ::= { nlmLogEntry 8 }nlmLogNotificationID OBJECT-TYPE    SYNTAX      OBJECT IDENTIFIER    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The NOTIFICATION-TYPE object identifier of the Notification that     occurred."    ::= { nlmLogEntry 9 }---- Log Variable Table--nlmLogVariableTable OBJECT-TYPE    SYNTAX      SEQUENCE OF NlmLogVariableEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION     "A table of variables to go with Notification log entries."    ::= { nlmLog 2 }nlmLogVariableEntry OBJECT-TYPE    SYNTAX      NlmLogVariableEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION     "A Notification log entry variable.     Entries appear in this table when there are variables in     the varbind list of a Notification in nlmLogTable."    INDEX       { nlmLogName, nlmLogIndex, nlmLogVariableIndex }    ::= { nlmLogVariableTable 1 }NlmLogVariableEntry ::= SEQUENCE {Kavasseri                   Standards Track                    [Page 17]RFC 3014                  Notification Log MIB             November 2000    nlmLogVariableIndex              Unsigned32,    nlmLogVariableID                 OBJECT IDENTIFIER,    nlmLogVariableValueType          INTEGER,    nlmLogVariableCounter32Val       Counter32,    nlmLogVariableUnsigned32Val      Unsigned32,    nlmLogVariableTimeTicksVal       TimeTicks,    nlmLogVariableInteger32Val       Integer32,    nlmLogVariableOctetStringVal     OCTET STRING,    nlmLogVariableIpAddressVal       IpAddress,    nlmLogVariableOidVal             OBJECT IDENTIFIER,    nlmLogVariableCounter64Val       Counter64,    nlmLogVariableOpaqueVal          Opaque}nlmLogVariableIndex OBJECT-TYPE    SYNTAX     Unsigned32 (1..4294967295)    MAX-ACCESS not-accessible    STATUS     current    DESCRIPTION     "A monotonically increasing integer, starting at 1 for a given     nlmLogIndex, for indexing variables within the logged     Notification."    ::= { nlmLogVariableEntry 1 }nlmLogVariableID OBJECT-TYPE    SYNTAX     OBJECT IDENTIFIER    MAX-ACCESS read-only    STATUS     current    DESCRIPTION     "The variable's object identifier."    ::= { nlmLogVariableEntry 2 }nlmLogVariableValueType OBJECT-TYPE    SYNTAX      INTEGER { counter32(1), unsigned32(2), timeTicks(3),                 integer32(4), ipAddress(5), octetString(6),                 objectId(7), counter64(8), opaque(9) }    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The type of the value.  One and only one of the value     objects that follow must be instantiated, based on this type."    ::= { nlmLogVariableEntry 3 }nlmLogVariableCounter32Val OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTIONKavasseri                   Standards Track                    [Page 18]RFC 3014                  Notification Log MIB             November 2000     "The value when nlmLogVariableType is 'counter32'."    ::= { nlmLogVariableEntry 4 }nlmLogVariableUnsigned32Val OBJECT-TYPE    SYNTAX      Unsigned32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'unsigned32'."    ::= { nlmLogVariableEntry 5 }nlmLogVariableTimeTicksVal OBJECT-TYPE    SYNTAX      TimeTicks    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'timeTicks'."    ::= { nlmLogVariableEntry 6 }nlmLogVariableInteger32Val OBJECT-TYPE    SYNTAX      Integer32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'integer32'."    ::= { nlmLogVariableEntry 7 }nlmLogVariableOctetStringVal OBJECT-TYPE    SYNTAX      OCTET STRING    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'octetString'."    ::= { nlmLogVariableEntry 8 }nlmLogVariableIpAddressVal OBJECT-TYPE    SYNTAX      IpAddress    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'ipAddress'.     Although this seems to be unfriendly for IPv6, we     have to recognize that there are a number of older     MIBs that do contain an IPv4 format address, known     as IpAddress.     IPv6 addresses are represented using TAddress or     InetAddress, and so the underlying datatype isKavasseri                   Standards Track                    [Page 19]RFC 3014                  Notification Log MIB             November 2000     OCTET STRING, and their value would be stored in     the nlmLogVariableOctetStringVal column."    ::= { nlmLogVariableEntry 9 }nlmLogVariableOidVal OBJECT-TYPE    SYNTAX      OBJECT IDENTIFIER    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'objectId'."    ::= { nlmLogVariableEntry 10 }nlmLogVariableCounter64Val OBJECT-TYPE    SYNTAX      Counter64    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION     "The value when nlmLogVariableType is 'counter64'."    ::= { nlmLogVariableEntry 11 }nlmLogVariableOpaqueVal OBJECT-TYPE    SYNTAX      Opaque    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -