1

Presented to : Mam Amara

§ Saqlain Akram 294
§ Muhammad Uzair Akbar 270
§ Asadullah Habib 258
§ Naveed Ahmad 290
§ Abbas Haider 293

2
§ What is Network Management?
§ Five areas of network management
§ Evolution of SNMP
§ What is SNMP?
§ Purpose of SNMP
§ Network management architecture
§ Components of a managed network
§ SNMP Protocol Basics
§ SNMP Messages

3
§ Ports & UDP
§ Four Basic Operations
§ SNMP Protocol Data Unit (PDU)
§ The Three Parts of SNMP
§ Issues

4
§ Network management includes deployment,
integration, and coordination of the hardware,
software, and human elements

§ to monitor, test, poll, configure, analyze, and

control the network and element resources to meet
the real-time , operational performance, and quality
of service requirements at a reasonable cost.

5
§ Performancemanagement: to quantify, measure, report, analyze and
control the performance of network components.
§ Fault management : to log, detect, and respond to fault conditions in
the network.
§ Configuration management : allows network manager to track which
a devices are on the managed and the hardware and software
network configurations of these devices.
§ Accounting management : allows the network manager to specify, log,
and control user and devices access to network resources.
§ Security management : to control access to network resources according
to some well defined policy.

6
§ In early days of the ARPANET, they used ping to detect the problem.
§ When ARPANET turned into WWW, better tools to network management
are needed.
§ SNMP provided a systematic way of monitoring and managing a computer
network.
§ Three versions in SNMP
SNMPv1 : The initial implementation of the SNMP protocol, which is
described in RFC 1098 and RFC 1157
SNMPv2 : An improved version of SNMPv1 that includes additional
protocol operations for the SNMPv2 Structure of Management Information
(SMI) (RFC 1441-1452)
SNMPv3 : SNMPv3 has yet to be standardized

7
§ In 1989
§ SNMP was adopted as TCP/IP-based Internet standards
§ In 1991
§ RMON – Remote network Monitoring
§ Supplement to SNMP to include management of LAN and LAN devices
§ In 1995
§ SNMPv2
§ Functional enhancements to SNMP
§ SNMP on OSI-based networks
§ RMON2
§ In 1998
§ SNMPv3
§ Further enhancements
§ Security capability for SNMP
8
§ The Simple Network Management Protocol (SNMP) is
an application-layer protocol that facilitates the exchange
of management information between a network
management system (NMS), agents, and managed devices.
SNMP uses the Transmission Control Protocol/Internet
Protocol (TCP/IP) protocol suite.
§ SNMP is a part of Internet network Architecture
§ SNMP enables network administrators to manage network
performance, find and solve network problems, and plan for
network growth.

9
SNMP & The OSI Model
Management & Agents APIs
Application Layer
SNMP
Presentation Layer ASN.1 AND BER

Session Layer RPC and NetBIOS

Transport Layer TCP and UDP
Network Layer IP and IPX
DataLink Layer Ethernet, Tokenring, FDDI
Physical Layer

10
§ Although the original purpose of SNMP was to let
network administrators remotely manage an Internet system,
the design of SNMP lets network administrators manage
applications as well as systems.

§ Lets you manage and monitor all network components from one
console

11
12
§ Manager
§ Agent
§ NMS (Network management System)

13
• Manager - process running on a management
workstation that requests information about devices on
the network.

• Agent process running on each managed node

-collectin information about the device it is running on.
g
14
§ Anetwork-management systems
(NMS) executes application which
monitor and manage devices.

15
n SNMP does not manage the network by itself but
instead provides a tool for the manager to manage the
corresponding devices.
n The preferred transport protocol for carrying SNMP
messages is UDP and the preferred port number for
the SNMP is port 161. Port 162 is used for trap
messages.

16
§ SNMP messages may be initiated by either the network
management system (NMS) or by the network element.
§ An SNMP TRAP is a message which is initiated by a
network element and sent to the network management
system. For example, a router could send a message if
one of it's redundant power supplies fails or a printer
could send an SNMP trap when it is out of paper.

17
§ An SNMP GET is a message which is
initiated by the network management system
when it wants to retrieve some data from a
network element. For example, the network
management system might query a router for
the utilization on a WAN link every 5 minutes

18
§ An SNMP SET is a message which is initiated by the
NMS when it wants to change data on a network
element. For example, the NMS may wish to alter a
static route on a router.

19
Ports & UDP
• SNMP uses User Datagram Protocol (UDP) as the
transport mechanism for SNMP messages

Ethernet
CRC
Frame IP
Packe
SNMP Message
t UDP
Datagram

• Like FTP, SNMP uses two well-known ports to

operate: •UDP Port
•UDP
Port
16 - SNMP Messages 1
16 - SNMP Trap Messages 2
20
Four Basic Operations •
Get
Retrieves the value of a MIB variable
stored on the agent machine
(integer, string, or address of another MIB
variable)

• GetNext
Retrieves the next value of the next lexical
MIB variable
21
• Set
Changes the value of a MIB variable
• Trap
An unsolicited notification sent by an
agent to a management application
(typically a notification of something
unexpected, like an error)

22
23
§ Get, GetNext, Response, Set, and Trap PDUs Contain the Same Fields.

24
§ The following descriptions summarize the fields
illustrated in Figure:
§ PDU type—Identifies the type of PDU transmitted (Get,
GetNext, Inform, Response, Set, or Trap).
§ Request ID—Associates SNMP requests
with responses.

25
§ Error status—Indicates one of a number of errors
error
and types. Only the response operation sets this field.
Other operations set this field to zero.
§ Error index—Associates an error with a
object instance. Only the response operation sets this
particular
field. Other operations set this field to zero.
§ Variable bindings—Serves as the data field of the
SNMPv2 PDU. Each variable binding associates a
particular object instance with its current value (with
the exception of Get and GetNext requests, for which
the value is ignored).
26
The Three Parts of SNMP
SNMP network management is based on three parts:
• SNMP
P Protocol
• Defines format of messages
exchanged by management
systems and agents.
• Specifies the Get, GetNext,
Set, and Trap operations

27
• Management Information Base (MIB)

A map of the hierarchical order of all

managed objects and how they are
accessed

• Structure of Management Information (SMI)

Rules specifying the format used to

define objects managed on the network
that the SNMP protocol accesses

28
§ Issues with SNMP v1
Security- Very low standards.
Passwords transmitted as plain text.
No provision for authenticating message source.
MIBs were not secured with ACL’s.
Limited number of error handling.

29
§ SNMP v2
Improvement over SNMP v1.
Improved security feature.
added manager to manager communication.
Four version of SNMP v2
SNMP v2p, SNMP v2c, SNMP v2u, SNMPv2*.
SNMP v2 is not backward compatible with SNMP v1.

30
§ Issues with SNMP v2
Multiple versions of SNMP v2- no consensus.
Security-not much improvement.
Incompatibility with earlier version (v1).

Overhead implementing Bilingual Manager or Proxy

Server.

31
§ SNMP v3
A general framework for all three SNMP versions.
Implements SNMP v1 and v2 specifications along with
proposed new features.

Improved security feature.

Secure remote configuration.
Protection against modification of information.

32
§ SNMP v3 Security
Major security improvement of v3 from earlier versions are

Message Integrity-ensures that data has not been modified

or tampered while in transit.
Authentication-checksif the message is from a
authorized source.
Encryption-encryptthe data to prevent others from seeing
the content.
Data can be collected securely from SNMP devices without fear
of the data being tampered with or corrupted.

33
Any Question? 34