<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月4日 #

    速方日志審計系統(tǒng)

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

    中國移動WLAN業(yè)務PORTAL協(xié)議規(guī)范

    用java實現(xiàn)中國移動WLAN業(yè)務PORTAL協(xié)議規(guī)范




    有需要代碼的可聯(lián)系本人。
    QQ:316909543

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

    IT資源監(jiān)管系統(tǒng)ES

    廣州速方軟件IT資源監(jiān)管系統(tǒng)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 閱讀(361) | 評論 (0)編輯 收藏

    硬件監(jiān)控--磁盤陣列

    通過SNMP實現(xiàn)對磁盤陣列的監(jiān)控

    posted @ 2012-07-24 20:49 afunms 閱讀(396) | 評論 (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 閱讀(871) | 評論 (0)編輯 收藏

    My Links

    News

    留言簿(18)

    隨筆檔案

    相冊

    搜索

    最新評論

    閱讀排行榜

    主站蜘蛛池模板: 在线免费一区二区| 亚洲AV无码一区二区三区电影| 亚洲午夜国产片在线观看| 亚洲不卡无码av中文字幕| 亚洲欧洲国产精品香蕉网| 久久综合日韩亚洲精品色| 亚洲一区免费视频| 婷婷亚洲综合一区二区 | 亚洲伊人久久大香线蕉AV| 亚洲精品无码少妇30P| 国产精品1024在线永久免费| 69精品免费视频| 午夜网站免费版在线观看| 亚洲av成人中文无码专区| 国产午夜免费秋霞影院| 亚洲国产日韩一区高清在线 | 久久高潮一级毛片免费| 中文字幕乱码免费视频| 亚洲欧洲中文日韩av乱码| 国产日本亚洲一区二区三区| 免费在线看黄网站| 亚洲AV无码之日韩精品| 中文字幕在线免费看| 免费h成人黄漫画嘿咻破解版| 亚洲国产日韩视频观看| 永久黄色免费网站| 国产成人A人亚洲精品无码| 高h视频在线免费观看| 亚洲天堂免费在线| 亚洲av永久无码精品国产精品 | 嫩草成人永久免费观看| 国产一级淫片免费播放电影| 一级做a爰性色毛片免费| 永久免费av无码网站大全| 亚洲电影在线免费观看| 免费无码作爱视频| 国产精品亚洲二区在线观看 | 亚洲片国产一区一级在线观看 | 9久9久女女免费精品视频在线观看 | 亚洲AV无码第一区二区三区 | 一级毛片大全免费播放下载|