<rt id="bn8ez"></rt>
<label id="bn8ez"></label>

  • <span id="bn8ez"></span>

    <label id="bn8ez"><meter id="bn8ez"></meter></label>

    afunms

    My Software,My Dream—Forge a more perfect NMS product.

    2012年5月3日 #

    速方日志審計系統

    posted @ 2014-12-18 17:41 afunms 閱讀(228) | 評論 (0)編輯 收藏

    中國移動WLAN業務PORTAL協議規范

    用java實現中國移動WLAN業務PORTAL協議規范




    有需要代碼的可聯系本人。
    QQ:316909543

    posted @ 2014-11-13 22:30 afunms 閱讀(450) | 評論 (0)編輯 收藏

    IT資源監管系統ES

    廣州速方軟件IT資源監管系統ElementSentry
    V5.8,提供免費下載試用。

    http://www.soofound.com/biz/product/es/intro.htm
    QQ:316909543
    Email:afunms@soofound.com




    posted @ 2013-08-30 13:54 afunms 閱讀(349) | 評論 (0)編輯 收藏

    硬件監控--磁盤陣列

    通過SNMP實現對磁盤陣列的監控

    posted @ 2012-07-24 20:49 afunms 閱讀(388) | 評論 (0)編輯 收藏

    SNMP Message Format – SNMP PDU Format

    Simple Network Management Protocol i.e. SNMP is a simple request/response protocol in which SNMP manager communicates with SNMP agents/managed devices using SNMP PDU’s (Packet Data Unit). These PDUs are encapsulated in SNMP Messages. An snmp message consists of a sequence that contains SNMP version, Community String, and SNMP PDU and an SNMP PDU forms the body of the message. Look here to read about seven types of SNMP PDUs.

    We need to understand that SNMP Message is different from SNMP PDU and hence their formats. Let us now understand SNMP Message Format and SNMP PDUD Format for SNMPv1, SNMPv2 and SNMPv3.

    SNMPv1 Message Format

    SNMPv1 Message Format

    • SNMP Version – It is an Integer that identifies the version of SNMP. For SNMPv1, it is 0.
    • Community String – An Octet String that may contain a string used to add security to SNMP devices.
    • SNMP PDU – The SNMP PDU (Protocol Data Unit) is used for communication between the SNMP entities.

    SNMPv1 PDU Format

    For SNMPv1, there are two pdu formats, one for Trap and other for rest of the pdu types.

    Below PDU format is applicable for Get, GetNext, Set and Response PDUs:

    SNMPv1 PDU Format

    • PDU Type – Specifies the type of PDU
    • Request ID – Associates SNMP requests with responses.
    • Error status – Indicates one of a number of errors and error types. It is set only in Response PDU, for rest it is set as 0.
    • Error index – Associates an error with a particular object instance. It is set only in Response PDU, for rest it is set as 0.
    • Variable bindings – Each variable binding associates a particular object instance with its current value. For Get and GetNext requests, the value is ignored.

    Below PDU format is applicable for Trap PDU:

    SNMPv1 Trap PDU Format

    • PDU Type – Specifies the type of PDU as Trap
    • Enterprise – Identifies the management enterprise under whose registration authority the trap was defined.
    • Agent address – IP address of the agent
    • Generic trap type – Used to identiy the generic trap. There are six types of generic traps.
    • Specific trap type – Used to identify a specific trap.
    • Time Stamp – Value of the sysUpTime mib object

    SNMPv2 Message Format

    SNMPv2 Message Format

    • SNMP Version – It is an Integer that identifies the version of SNMP. For SNMPv2, it is 1.
    • Community String – An Octet String that may contain a string used to add security to SNMP devices.
    • SNMP PDU – The SNMP PDU (Protocol Data Unit) is used for communication between the SNMP entities.

    SNMPv2 PDU Format

    For SNMPv2, there are two pdu formats, one for GetBulk and other for rest of the pdu types.

    Below PDU format is applicable for Get, GetNext, Set, Response, Trap and Inform PDUs:

    SNMPv2 PDU Format

    • PDU Type- Specifies the type of PDU
    • Request ID- Associates SNMP requests with responses.
    • Error Status- Indicates one of a number of errors and error types. It is set only in Response PDU, for rest it is set as 0.
    • Error Index- Associates an error with a particular object instance. It is set only in Response PDU, for rest it is set as 0.
    • Variable Bindings- Each variable binding associates a particular object instance with its current value. For Get and GetNext requests, the value is ignored.

    Below PDU format is applicable for GetBulk PDU:

    SNMPv2 GetBulk PDU Format

    • PDU Type – Specifies the type of PDU as GetBulk
    • Request ID- Associates SNMP requests with responses.
    • Non repeaters- Specifies the number of object instances in the variable bindings field that should be retrieved no more than once from the beginning of the request.
    • Max repetitions- Defines the maximum number of times that other variables beyond those specified by the Non repeaters field should be retrieved.
    • Variable Bindings- Each variable binding associates a particular object instance with its current value.

    SNMPv3 Message Format

    SNMPv3 message format is very different from the above two because of lot of security parameters introduced in this version. Below is how it looks like:

    SNMPv3 Message Format

    • Version – It is an Integer that identifies the version of SNMP. For SNMPv3, it is 3.
    • ID – This field contains the SNMP message identifier which is a unique ID associated with the message. The msgID field is different from the reqID field available in the PDU.
    • Max Size – This field represents the maximum size of message which the requesting SNMP entity can accept.
    • Flags – This field contains the message security level. 0 – message is authenticated, 1 – message uses privacy, 2 – a report PDU is expected for the message
    • Security Model – This field indicates the security model used to generate the message. When USM is used, it has a value of 3
    • Engine ID – This field has the SNMPEngineID of the authoritative SNMP entity involved in the transaction. When a request PDU is generated from an SNMP engine, the remote peer (agent for Get request and manager for Trap request) is the authoritative SNMP entity.
    • Engine Boots – This field has the snmpEngineBoots value of the authoritative SNMP entity involved in the transaction
    • Engine Time – This field has the snmpEngineTime value of the authoritative SNMP entity involved in the transaction
    • User Name – This field contains the principal who originated the request.
    • Security Parameters – This field contains the security parameters that are security model dependent. It contains the authentication parameters and the privacy parameters for USM.
    • Context Engine ID – Within an administrative domain, the contextEngineID uniquely identifies an SNMP entity that may realize an instance of a context with a particular contextName.
    • Context Name – A contextName is used to name a context. Each contextName must be unique within an SNMP entity.
    • PDU – The SNMP PDU (Protocol Data Unit) is used for communication between the SNMP entities.

    SNMPv3 PDU Format

    The PDU types for SNMPv3 are the same as the SNMPv2.

    Thus, above are the message and pdu formats for SNMPv1, SNMPv2 and SNMPv3. Hope you find the information presented here useful. Feel free to leave your footprints for any queries, feedback or suggestions in the comments section below.

    posted @ 2012-05-04 16:12 afunms 閱讀(853) | 評論 (0)編輯 收藏

    snmp4j FAQ


    • Why is SNMP4J free?
      Currently there is a lack of an affordable well object
      oriented designed SNMP implementation for Java. SNMP4J tries to fill this gap.
      It is free to get the best support and feedback from the Internet community. In
      addition it is a small compensation for the help we got from other open source
      projects.
      Nevertheless you are welcome to support the development of SNMP4J
      by purchasing commercial e-mail support.
       
    • Where can I find examples for SNMP4J API usage?
      Simple examples are provided by
      the JavaDoc of the SNMP class which can be viewed here.
      A (nearly) complete example for the SNMP4J API usage
      is the console tool. It can be found in the org.snmp4j.tools.console.SnmpRequest
      class.
       
    • Is SNMP4J thread-safe?
      Yes, SNMP4J is designed for multi-threaded
      environments. Nevertheless, objects put into a PDU must not be modified while
      the corresponding SNMP request is being processed.
       
    • Why do I get sometimes a time-out (response == null) on a request although I see log
      messages like “Received response that cannot be matched to any outstanding
      request...”?

      The response of the agent has been received after the
      request had been timed out. To solve this, increase the time-out value for the
      target.
       
    • Why am I always getting a time-out (response == null) when sending a request?
      Probably you have forgotten to call the listen() method of the
      TransportMapping (once) or the Snmp class before sending the
      request.
       
    • Can I use a single Snmp instance to request data from multiple SNMP agents at the same time?
      Yes, of course! You can either use asynchronous requests and
      collect their responses in a one or more callback listeners or you can use
      synchronous requests that are send from several threads concurrently.

    • Can SNMP4J be used with Java EE?
      Yes, the SNMP4JSettings class provides the
      option to replace the default thread and timer factories by custom ones that use
      Java EE resources instead of Java SE threads (timers).

    posted @ 2012-05-03 16:09 afunms 閱讀(403) | 評論 (0)編輯 收藏

    My Links

    News

    留言簿(18)

    隨筆檔案

    相冊

    搜索

    最新評論

    閱讀排行榜

    主站蜘蛛池模板: 777爽死你无码免费看一二区| 五级黄18以上免费看| 国产精品白浆在线观看免费| 国产偷国产偷亚洲高清日韩| 一级做a爰片性色毛片免费网站| 日韩免费一区二区三区| 亚洲精品无码久久| 女性无套免费网站在线看| 四虎永久在线观看免费网站网址| 亚洲va久久久噜噜噜久久| 国产免费AV片在线观看| 亚洲av无码潮喷在线观看| 中文字幕无码一区二区免费| 国产亚洲精AA在线观看SEE| 男人天堂免费视频| 亚洲AV成人无码久久精品老人| 免费污视频在线观看| 色播亚洲视频在线观看| 日本XXX黄区免费看| 亚洲国产精品综合久久20| 日韩成人毛片高清视频免费看| 免费jjzz在线播放国产| 18gay台湾男同亚洲男同| 亚洲视频在线免费看| 亚洲国产精品综合久久20| 国产一级淫片免费播放电影| 国产精品亚洲综合一区在线观看 | 99在线免费观看| 亚洲VA中文字幕不卡无码| 久久午夜夜伦鲁鲁片免费无码影视| 亚洲av一本岛在线播放| 精品国产精品久久一区免费式| 亚洲情a成黄在线观看动漫尤物| 亚洲香蕉免费有线视频| 亚洲欧美在线x视频| 伊人久久大香线蕉亚洲五月天| 无码精品人妻一区二区三区免费看 | 中文字幕不卡亚洲| 亚洲免费在线播放| 亚洲精品无码少妇30P| 亚洲精品无码专区在线在线播放|