SNMP V1 Network Management:

Organization and Information

Models
Video Lecture Links
› https://www.youtube.com/watch?v=spbZmJaoitY&list=PL
4j_fCKQ7Bso1wGplcaF2pcDGeLVCuKHU
› https://www.youtube.com/watch?v=-
55DYxgzuEQ&list=PL4j_fCKQ7Bso1wGplcaF2pcDGeLVCu
KHU&index=2
› https://www.youtube.com/watch?v=E44m7BSKGc4&list=
PL4j_fCKQ7Bso1wGplcaF2pcDGeLVCuKHU&index=3
(Courtesy: FLAMINGO Project)
 › Introduction
› Case Study and Real-Time Example of
OUTLINES SNMP
› SNMP History and Standards
› SNMP Architecture
› Organization Model
› Information Model
– SMI v1 & v2
– MIB I & II
INTRODUCTION
Introduction (1)
› SNMP management refers as Internet management but it
manage more than internet such as
– Intranet and telecommunication networks
– Any network using TCP/IP suite
– Non-TCP/IP network elements using proxy agents
› SNMP is widely used NMS
– Network element has built-in agent, which respond to NMS
– It can easily start managing the newly added hardware as most of
device have built-in SNMP agent.
– The ease of adding and configuring components, added to its
acceptance and popularity
Introduction (2)
› Initially, SNMP is started as interim set of specifications
– Enhanced by development of v2 & v3
› Power of technology could result in positive and negative
results. HOW?
› NMS could also bring network down. HOW?
› To identify the error using Artificial Intelligence. HOW?
› To identify the network failure reason, which is due to newly
added Interface card, done from NOC. How?
Case Study and Real-
Time Example of SNMP
Case Study – Managed LAN using NMS (1)
› NMS auto-discover the network component as long as it has
management agent
› Management agent could be as simple as it respond to ping
› Modern agents are more sophisticated
› The network shown is configured as
– 1 router with 2 hubs, connecting to a backbone network
› Once a network component is discovered & mapped by NMS
› The system manager can query and acquire on system
parameter and statistic on network element.
CASE STUDY –
MANAGED LAN USING
NMS (1)
Network IP configuration
Router IP: 172.16.46.1
Hub 1 IP: 172.16.46.2
Hub 2 IP: 172.16.46.3
NMS physical and logically
located remotely
configured on LAN
192.168.252.1
NMS IP: 192.168.252.110
CASE STUDY –
MANAGED LAN USING
NMS (2)
No specific names
System Information acquired by
the NMS from the network
elements
Enterprise # 43
Private MIB of 3Com # 1.8.5
Description and Object Id are
factory set
Up timing
CASE STUDY –
MANAGED LAN USING
NMS (3)
Addresses Information
Acquired by an SNMP NMS
History of SNMP
History of SNMP (1)
› SNMP begins in 1970s, ICMP develop to manage ARPANET
› Use to transfer control messages between nodes e-g: PING
› Adopted the name “Internet ”from “ARPANET” in 1984
› With the growth of Internet
– SGMP was developed for remote monitoring
– SNMP is enhancement of SGMP
– SNMP is interim solution, OSI standard CMIP/CMIS was long term
solution
– SNMP become de-facto standard, due to simplicity and extensive
implementation
– SNMPv2 with new features, overcome few limitations of v1.
– SNMPv3 address security features
History of SNMP (2)
› IAB was designed to managed two task forces
– IETF (Internet Engineering Task Force)
› Protocol engineering, development and standardization
– IRTF (Internet Research Task Force)
› Long and short term research projects related to protocols, application,
architecture and technology

› IANA (Internet Assigned Numbers Authority)

– Responsible for assignment of unique parameters such as
› Internet Address, domain name, autonomous system number, protocol
number, port number, MIB object identifier (private enterprise number) and
many others
History of SNMP (3)
› InterNIC (Internet Network Information Center) maintains
documents such as
– RFC (STD): Specify the Internet standard
– RFC (FYI): For document overview and introductory topics
› Both RFCs are indexed and retrieved by RFC number, with
the addition of unique STD and FYI number
Organization Model
TWO-TIER MODEL
Agent process resides in
managed object
Network manager process
resides in NMS
Agent respond to any
management system using
SNMP
Multiple managers can interact
with agent
Two-Tier Model
› Why the need of multiple managers?
– However, its easy to monitor all objects in the network with the
standard messages
– To configure a system in detail a more intimate knowledge of object
is needed, hence NMS provided by the same vendor could have
more capabilities than another vendor
– It’s common practice to use multiple vendor products and multiple’
NMSs
› Sometimes, temporal data is require rather than continuous
data or we want to look at traffic statistics
THREE-TIER
ORGANIZATION
MODEL
RMON is used, it constantly
monitors the object and send
temporal data to manager
RMON is implemented between
managed object and network
manager
Manager received data from
both RMON and agent directly
Implemented in distributed
fashion on the network, which
greatly increases the central
management of the network
PROXY SERVER
ORGANIZATION
A pure SNMP management
system, to manage a network
element without the SNMP
agent
In cases like outside plant or
equipment in customer
premises
Proxy server is used that
converts data to SNMP
compatible format
NMS BEHAVING AS
AN AGENT AND A
MANAGER
Two NMSs exchange
information when both
networks are connected
through gateway
For example: two customer
service provider wants to
communicate
SNMP Network
Management Architecture
SNMP Network Management Architecture
› It represents the data path between manager and agent
application process via four transport function protocols
UDP, IP, DLC & PHY
› RFC 1157 define SNMP as
– “by which a management information for a network element can be
inspected or altered by logically remote users”
› Communication management information among
management entities is done through five exchange protocol
messages
– Three of those are initiated by the manager process and two by
agent process
SNMP
ARCHITECTURE
Communication is done
thorough 5 (3+2) protocol
messages
Get-Request to the value of the
object
Get-Next-Request to get
multiple instance of the object
Set-Request to initialize or reset
the value of the object
Get-Response a reply to any of
the above two messages
Trap is a unsolicited messages
generated against the event
such as threshold value, link
up/down
SNMP Architecture – MIB & MDB
› MIB (Management Information Base)
– Contains information about the objects
– Virtual and static database
– It is compiled in manager during implementation
– During discovery process MIB need to be their else discovered
object is marked as unidentified
– PING is used to discover the network components
– MIB must be implemented in both manager and agent to acquire the
information such as System Information
› MDB (Managed Database)
– is dynamic and contains measured values associated with objects
(can be implemented using any database architecture)
– Only manager have MDB