Differences

This shows you the differences between two versions of the page.

--- networking:snmp:about_snmp [2020/05/12 16:27] – [SNMPv2c:] peter
+++ networking:snmp:about_snmp [2020/07/15 09:30] (current) – external edit 127.0.0.1
@@ Line 23: / Line 23: @@
 ===== SNMP Manager =====
-A manager or management system is a separate entity that is responsible to communicate with the SNMP agent implemented network devices. This is typically a computer that is used to run one or more network management systems.
+A manager or management system is a separate entity that is responsible to communicate with the SNMP agent implemented network devices.
+This is typically a computer that is used to run one or more network management systems.
 SNMP Manager’s key functions
@@ Line 42: / Line 45: @@
 ===== SNMP Agent =====
-The agent is a program that is packaged within the network element. Enabling the agent allows it to collect the management information database from the device locally and makes it available to the SNMP manager, when it is queried for. These agents could be standard (e.g. Net-SNMP) or specific to a vendor (e.g. HP insight agent)
+The agent is a program that is packaged within the network element.
+Enabling the agent allows it to collect the management information database from the device locally and makes it available to the SNMP manager, when it is queried for.
+These agents could be standard (e.g. Net-SNMP) or specific to a vendor (e.g. HP insight agent)
 SNMP agent’s key functions:
@@ Line 50: / Line 57: @@
   * Signals an event to the manager.
   * Acts as a proxy for some non–SNMP manageable network node.
+{{:networking:snmp:snmp_-_agent.png?600|}}
 ----
@@ Line 87: / Line 96: @@
 Every Object ID is organized hierarchically in MIB. The MIB hierarchy can be represented in a tree structure with individual variable identifier.
-A typical object ID will be a dotted list of integers. For example, the OID in RFC1213 for "sysDescr" is .1.3.6.1.2.1.1.1
+A typical object ID will be a dotted list of integers. For example, the OID in [[https://tools.ietf.org/html/rfc1213|RFC 1213]] for "sysDescr" is .1.3.6.1.2.1.1.1
+{{:networking:snmp:mib_tree.jpeg?600|}}
 ----
@@ Line 107: / Line 118: @@
 ===== Typical SNMP communication =====
-Being the part of TCP⁄ IP protocol suite, the SNMP messages are wrapped as User Datagram Protocol (UDP) and intern wrapped and transmitted in the Internet Protocol. The following diagram will illustrate the four–layer model developed by Department of Defense (DoD).
+Being the part of TCP⁄ IP protocol suite, the SNMP messages are wrapped as User Datagram Protocol (UDP) and intern wrapped and transmitted in the Internet Protocol.
+The following diagram will illustrate the four–layer model developed by Department of Defense (DoD).
+{{:networking:snmp:snmp_-_layers.png?600|}}
+__GET⁄ GET NEXT⁄ GET BULK⁄ SET__
+{{:networking:snmp:snmp_-_get_-_response.gif?600|}}
+__TRAP__
+{{:networking:snmp:snmp_-_trap.gif?600|}}
+__INFORM__
+{{:networking:snmp:snmp_-_inform_-_acknowledgment.gif?600|}}
 By default SNMP uses port 161 and TRAP⁄ INFORM uses port 162 for communication.
@@ Line 119: / Line 146: @@
 ==== SNMPv1: ====
-This is the first version of the protocol, which is defined in RFCs [[https://tools.ietf.org/html/rfc1155|1155]] and [[https://tools.ietf.org/html/rfc1157|1157]].
+This is the first version of the protocol, which is defined in [[https://tools.ietf.org/html/rfc1155|RFC 1155]] and [[https://tools.ietf.org/html/rfc1157|RFC 1157]].
 ==== SNMPv2c: ====
@@ Line 127: / Line 154: @@
 ==== SNMPv3: ====
-SNMPv3 defines the secure version of the SNMP. SNMPv3 also facilitates remote configuration of the SNMP entities. It is defined by RFC 1905, RFC 1906, RFC 3411, RFC 3412, RFC 3414, RFC 3415.
+SNMPv3 defines the secure version of the SNMP. SNMPv3 also facilitates remote configuration of the SNMP entities. It is defined by [[https://tools.ietf.org/html/rfc1905|RFC 1905]], [[https://tools.ietf.org/html/rfc1906|RFC 1906]], [[https://tools.ietf.org/html/rfc3411|RFC 3411]], [[https://tools.ietf.org/html/rfc3412|RFC 3412]], [[https://tools.ietf.org/html/rfc3414|RFC 3414]], [[https://tools.ietf.org/html/rfc3415|RFC 3415]].
 Though each version had matured towards rich functionalities, additional emphasis was given to the security aspect on each upgrade. Here is a small clip on each editions security aspect.