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

📄 rfc1067.txt

📁 著名的RFC文档,其中有一些文档是已经翻译成中文的的.
💻 TXT
📖 第 1 页 / 共 5 页
字号:
   The form of the Trap-PDU is:     Trap-PDU ::=         [4]              IMPLICIT SEQUENCE {                 enterprise          -- type of object generating                                     -- trap, see sysObjectID in [2]                     OBJECT IDENTIFIER,                 agent-addr          -- address of object generating                     NetworkAddress, -- trap                 generic-trap        -- generic trap type                     INTEGER {                         coldStart(0),                         warmStart(1),                         linkDown(2),                         linkUp(3),                         authenticationFailure(4),                         egpNeighborLoss(5),                         enterpriseSpecific(6)                     },                 specific-trap     -- specific code, present even                     INTEGER,      -- if generic-trap is not                                   -- enterpriseSpecific                 time-stamp        -- time elapsed between the last                   TimeTicks,      -- (re)initialization of the network                                   -- entity and the generation of the                                      trap                 variable-bindings   -- "interesting" information                      VarBindList             }   The Trap-PDU is generated by a protocol entity only at the request of   the SNMP application entity.  The means by which an SNMP application   entity selects the destination addresses of the SNMP application   entities is implementation-specific.   Upon receipt of the Trap-PDU, the receiving protocol entity presents   its contents to its SNMP application entity.Case, Fedor, Schoffstall, & Davin                              [Page 26]RFC 1067                          SNMP                       August 1988   The significance of the variable-bindings component of the Trap-PDU   is implementation-specific.   Interpretations of the value of the generic-trap field are:4.1.6.1.  The coldStart Trap   A coldStart(0) trap signifies that the sending protocol entity is   reinitializing itself such that the agent's configuration or the   protocol entity implementation may be altered.4.1.6.2.  The warmStart Trap   A warmStart(1) trap signifies that the sending protocol entity is   reinitializing itself such that neither the agent configuration nor   the protocol entity implementation is altered.4.1.6.3.  The linkDown Trap   A linkDown(2) trap signifies that the sending protocol entity   recognizes a failure in one of the communication links represented in   the agent's configuration.   The Trap-PDU of type linkDown contains as the first element of its   variable-bindings, the name and value of the ifIndex instance for the   affected interface.4.1.6.4.  The linkUp Trap   A linkUp(3) trap signifies that the sending protocol entity   recognizes that one of the communication links represented in the   agent's configuration has come up.   The Trap-PDU of type linkUp contains as the first element of its   variable-bindings, the name and value of the ifIndex instance for the   affected interface.4.1.6.5.  The authenticationFailure Trap   An authenticationFailure(4) trap signifies that the sending protocol   entity is the addressee of a protocol message that is not properly   authenticated.  While implementations of the SNMP must be capable of   generating this trap, they must also be capable of suppressing the   emission of such traps via an implementation-specific mechanism.4.1.6.6.  The egpNeighborLoss Trap   An egpNeighborLoss(5) trap signifies that an EGP neighbor for whomCase, Fedor, Schoffstall, & Davin                              [Page 27]RFC 1067                          SNMP                       August 1988   the sending protocol entity was an EGP peer has been marked down and   the peer relationship no longer obtains.   The Trap-PDU of type egpNeighborLoss contains as the first element of   its variable-bindings, the name and value of the egpNeighAddr   instance for the affected neighbor.4.1.6.7.  The enterpriseSpecific Trap   A enterpriseSpecific(6) trap signifies that the sending protocol   entity recognizes that some enterprise-specific event has occurred.   The specific-trap field identifies the particular trap which   occurred.Case, Fedor, Schoffstall, & Davin                              [Page 28]RFC 1067                          SNMP                       August 19885.  Definitions     RFC1067-SNMP DEFINITIONS ::= BEGIN      IMPORTS          ObjectName, ObjectSyntax, NetworkAddress, IpAddress, TimeTicks              FROM RFC1065-SMI;          -- top-level message          Message ::=                  SEQUENCE {                      version          -- version-1 for this RFC                          INTEGER {                              version-1(0)                          },                      community        -- community name                          OCTET STRING,                      data             -- e.g., PDUs if trivial                          ANY          -- authentication is being used                  }          -- protocol data units          PDUs ::=                  CHOICE {                              get-request                                  GetRequest-PDU,                              get-next-request                                  GetNextRequest-PDU,                              get-response                                  GetResponse-PDU,                              set-request                                  SetRequest-PDU,                              trap                                  Trap-PDU                          }Case, Fedor, Schoffstall, & Davin                              [Page 29]RFC 1067                          SNMP                       August 1988          -- PDUs          GetRequest-PDU ::=              [0]                  IMPLICIT PDU          GetNextRequest-PDU ::=              [1]                  IMPLICIT PDU          GetResponse-PDU ::=              [2]                  IMPLICIT PDU          SetRequest-PDU ::=              [3]                  IMPLICIT PDU          PDU ::=                  SEQUENCE {                     request-id                          INTEGER,                      error-status      -- sometimes ignored                          INTEGER {                              noError(0),                              tooBig(1),                              noSuchName(2),                              badValue(3),                              readOnly(4),                              genErr(5)                          },                      error-index       -- sometimes ignored                         INTEGER,                      variable-bindings -- values are sometimes ignored                          VarBindList                  }          Trap-PDU ::=              [4]                 IMPLICIT SEQUENCE {                      enterprise        -- type of object generating                                        -- trap, see sysObjectID in [2]                          OBJECT IDENTIFIER,Case, Fedor, Schoffstall, & Davin                              [Page 30]RFC 1067                          SNMP                       August 1988                      agent-addr        -- address of object generating                          NetworkAddress, -- trap                      generic-trap      -- generic trap type                          INTEGER {                              coldStart(0),                              warmStart(1),                              linkDown(2),                              linkUp(3),                              authenticationFailure(4),                              egpNeighborLoss(5),                              enterpriseSpecific(6)                          },                      specific-trap  -- specific code, present even                          INTEGER,   -- if generic-trap is not                                     -- enterpriseSpecific                      time-stamp     -- time elapsed between the last                          TimeTicks, -- (re)initialization of the                                        network                                     -- entity and the generation of the                                        trap                       variable-bindings -- "interesting" information                          VarBindList                  }          -- variable bindings          VarBind ::=                  SEQUENCE {                      name                          ObjectName,                      value                          ObjectSyntax                  }         VarBindList ::=                  SEQUENCE OF                     VarBind         ENDCase, Fedor, Schoffstall, & Davin                              [Page 31]RFC 1067                          SNMP                       August 19886.  Acknowledgements   This memo was influenced by the IETF SNMP Extensions working   group:             Karl Auerbach, Epilogue Technology             K. Ramesh Babu, Excelan             Amatzia Ben-Artzi, 3Com/Bridge             Lawrence Besaw, Hewlett-Packard             Jeffrey D. Case, University of Tennessee at Knoxville             Anthony Chung, Sytek             James Davidson, The Wollongong Group             James R. Davin, Proteon             Mark S. Fedor, NYSERNet             Phill Gross, The MITRE Corporation            

⌨️ 快捷键说明

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