SNMPv2 1993

#SNMPv2, later revised in 1996, is a revision to #SNMPv1 1988 specified by RFC 1901 - 1908 which supports distributed network and adds more functionality to it. It improves the performance, security, confidentiality, and manager-to-manager communications.

SNMP supports both central and distributed management (multiple Management Station or Manager with a pool of Management Agent) as each device in the network maintains local Management Information Base (MIB). The communication is usually done in User Datagram Protocol (UDP)# but SNMPv2 allows the use of Transmission Control Protocol (TCP)# too.

Get commands are not atomic in SNMPv2.

Links to this page

Simple Network Management Protocol (SNMP)

SNMPv2 1993#
SNMPv3 1998

#SNMPv3, defined by RFC 2570 - 2575, addresses security issues of #SNMPv1 1988 and #SNMPv2 1993 by using User Security Model (USM), including overall architecture and security capability. It provides authentication service# that is part of User-Based Security (UBS), privacy# (Data Encryption Standard (DES) message encryption), and Access Control# to allowed operations, device information, and Management Information Base (MIB) access.
SNMPv1 1988

SNMPv1 uses community, a relationship between a SNMP manager and a set of SNMP agents, to establish trust between them. It provides three aspects of agent control including: authentication service#, access policy#, and proxy service. This is later inherited by its successor SNMPv2 1993#. However, it has a major security issue as it transmits a password, called “community string”, in cleartext to authenticate clients.

#networking #communication