SNMPv1:
Communication and
Functional Model
Video Lecture Links
› https://www.youtube.com/watch?v=zmSKl-
CIn4c&list=PL4j_fCKQ7Bso1wGplcaF2pcDGeLVCuKHU&in
dex=5
› https://www.youtube.com/watch?v=9KMBfIYFY7k&list=PL
4j_fCKQ7Bso1wGplcaF2pcDGeLVCuKHU&index=6
(Courtesy: FLAMINGO Project)
Communication Model
Communication Model
› It defines specifications for 4 aspects
– Architecture
– Administrative Model
– SNMP Protocol & Operations
– SNMP MIB
Architecture
› It consist of network management stations (manager) and
network elements or objects (managed elements)
› It is used to communicate between network management
stations and management agents in elements
› Three major goals of architecture are:
– Minimize the number and complexity of management functions
– Flexible for future expansion
– Should be independent of architecture and mechanism of particular
hardware
Administrative Model
Administrative Model – Application Entity
› SNMP Application entity
– Application entities resides in SNMP agent and manager
– SNMP manager: application entity resides in management station
– SNMP agent: application entity resides in network element
– SNMP community: Pairing of two entities (SNMP agent and manager)
– Community name: string of octets
– Multiple pairs can belong to same community
Administrative Model – Application Entity
› Multiple managers can communicate with single agent
– First, is to monitor traffic
– Second, to configuring some administrative policies
– Third, to perform some statistics study
Administrative Model – SNMP Authentication
› Basic authentication and access policy is specified as:
– Common community name between two application entities
– Encryption can be used in higher levels
– Authorization is implemented in MIB
› Community MIB view
– A network element comprise of many manage objects, standard &
private
– Management agent only able to view sub-set of network element’s
managed objects is called Community MIB view
– Each community is also assigned an access mode
Administrative Model - Community Profile
› Community Profile
– SNMP agent only have a MIB view of objects 2,3 and 4, there
may be other objects existing in network element.
– Each community name also assign an SNMP access mode
– Pairing of SNMP MIB view with access mode is called community
profile
– It determines the operation that can be performed on the object
by the agent
ADMINISTRATIVE
MODEL - SNMP
ACCESS POLICY
Pairing of SNMP community with
an SNMP profile, It defines
administrative model of SNMP
management
Manager 1 & 2: have access to
one community
Manager 3: have access to both
communities
SNMP ACCESS POLICY
- NON-SNMP
COMMUNITY
SNMP agent associated with the
proxy policy is called proxy
agent or proxy server
The proxy agent monitors a
non-SNMP community with
non-SNMP agent and then
converts data objects to SNMP
compatible objects and data
feed to a SNMP manager
SNMP Protocol
SNMP Protocol Specifications
› Protocol Entities
– Peer Processes, which implements SNMP, thus supports SNMP
application entities termed as protocol entities
– Communication between protocol entitles is accomplished in
encapsulated messages using UDP datagram
› SNMP message consists of:
– Version Identifier
– Community Name
– PDU
› Port used
– 161 (all others)
– 162 (traps only)
RFC 1157 - SNMP
MACRO DEFINITION
Imports: to use pre-define
objects types
Comments represents as “--”
GET AND SET PDU
ASN.1 CONSTRUCT
PDU Type: get, set, trap
Request ID: use to track
messages
Error Status: indicate an error
occurance
Error Index: additional
information on the error
Variable Binding: (VarBind)
pairing of object with its value
Trap PDU
› PDU Type: get, set, trap
› Enterprise: MIB {private 1}
› n-VarBinds: n managed objects
› Agent address: system that generates the trap
› Time stamp: elapsed time since last re-initialization
› Specific trap: Programmable trap
› Time-Stamp trap: elapse time since last re-installation
SNMP Operations
SNMP OPERATIONS Manager Agent
– GET-REQUEST
PDU OPERATION
Diagram show the
operation between agent
and manager request using
Get-Request PDU
Get-Request operation
between managers and
agent, ends when value 72
is received for last object
SNMP OPERATIONS – Manager Agent
GET-NEXT-REQUEST
PDU OPERATION
Diagram show the get-
Next-Request operation
perform by managers and
agent
Functional Model
Functional Model
› No formal definition in SNMPv1
› Some configuration, security and privacy-related issues were
already addressed by Protocol operations and specifications
› Configuration: Set or Get function are for re-configuration
› Fault: error counter are built into agent, traps are useful to
monitor network elements
› Performance: Intermediate agent or RMON, perform such
statistics
› Security: Already address in Administrative model
› Accounting: Not address in SNMP model
