PPRESENTATIONS
RESENTATIONSIN
INN
NETWORK
ETWORK M
MANAGEMENT
ANAGEMENT
SNMP: Simple Network
Management Protocol
Introduction to SNMP
Simple Network Management Protocol (SNMP) is an "
Internet-standard protocol for managing devices on IP
networks." Devices that typically support SNMP include
routers, switches, servers, workstations, printers, modem
racks, and more.
SNMP is an application layer protocol that facilitates the
exchange of management information between network
devices .
It is a part of the Transmission Control Protocol/Internet
Protocol(TCP/IP) protocol suite.
SNMP: Simple Network Management Protocols
SNMP Components
A Computer Running Management Software (with GUI)
Host
SNMP
Management
Station
Agent
Managed
Node
Management
LAN
Managed
Node
Printer
Process
Bridge Agent
Router
Agent
Agent
Managed
Node
Managed
Node
An SNMP-managed network consists of three key
components:
Managed device
Agent software which runs on managed devices
Network management system (NMS) software which
runs on the manager
Managed device
Network node that contains an SNMP agent
Resides on a managed network
Collect and store management information
Make information available to NMSs using SNMP
Sometimes called network elements
Managed devices can be any type of device including,
but not limited to:
Routers and access servers
Switches and bridges
Hubs
IP telephones
Computer hosts
Printers
Agent
Network-management software module
Resides in a managed device
Has local knowledge of management information
Translates that information into a form compatible
with SNMP
NMS
Executes applications that monitor and control
managed devices
NMSs provide the bulk of the processing and memory
resources required for network management
One or more NMSs may exist on any managed network
SNMP
Basic
Commands
Managed devices are monitored and controlled using four basic SNMP
commands: read, write, trap, and traversal operations
The read command is used by an NMS to monitor managed devices.
The NMS examines different variables that are maintained by
managed devices
The write command is used by an NMS to control managed devices.
The NMS changes the values of variables stored within managed
devices.
The trap command is used by managed devices to asynchronously
report events to the NMS. When certain types of events occur, a
managed device sends a trap to the NMS.
Traversal operations are used by the NMS to determine which
variables a managed device supports and to sequentially gather
information in variable tables, such as a routing table.
SNMP Multi-Vendor Principles
An Agent for Every Managed Node
to run SNMP management process
Variables (Objects)
to describe the state of each device
Information (Format) Specification
ASN-1: Standard Object Definition Language
SMI: Defines (SNMP) Data Structures
MIB: Data Structure for (Variables) Objects (Uses SMI)
BER: Basic Encoding Rule (transfer syntax)
(sequence of bytes for transmission)
SNMP Information Flow
Managed
Node
Agent
Devices
Devices
Device
Using SMI (ASN-1)
Rules to Describe
Objects (Variables)
Object
Object
Object
Object
Object
Object
Variables to
describe
devices
MIB
Data
Structure
Modules
Using BER
Rules to Convert SMI
Data Structures into a
Sequence of Bytes
Sequence
of Bytes
for
Transmission
SNMP Operations
SNMP Framework
Protocol: Manager-Agent interaction
BER: Basic Encoding Rules
MIB: Management Information Base
(Database on managed devices)
SMI: Structure of Management Information
(Rules of describing management information)
Sub-Super-Set of: ASN-1:
Abstract Syntax Notation One
SNMP Management
Information Base
A Management Information Base (MIB) is a collection of information
that is organized hierarchically. MIBs are accessed using a networkmanagement protocol such as SNMP. They are comprised of managed
objects and are identified by object identifiers.
A managed object (sometimes called a MIB object, an object, or a MIB)
is one of any number of specific characteristics of a managed device.
Managed objects are comprised of one or more object instances, which
are essentially variables.
An object identifier (or object ID) uniquely identifies a managed object
in the MIB hierarchy. The MIB hierarchy can be depicted as a tree with
a nameless root, the levels of which are assigned by different
organizations
The top-level MIB object IDs belong to different standards
organizations, while lower-level object IDs are allocated by associated
organizations.
The MIB Tree Illustrates the Various Hierarchies Assigned by Different Organizations
SNMP Operation
Management
Station
Request PDU
Time
Agent
Managed
Node
Response PDU
PDU: Protocol Data Unit
Basic Messages
Requesting & Updating Variable Values
Originator: Manager / Receiver: Agent
Get-request: Requests the value of one or more variables
Get-next-request: Requests the value of the next variable
(Alphabetically through MIB)
Get-bulk-request: Requests large transfer (such as Tables)
Set-request: Updates one or more variables
Originator: Agent
Receiver: Manager
Response-PDU:
Response Message
Trap-PDU:
Trap Report
Originator: Manager
Receiver :Another Manager
Inform-request
Local MIB Description
SNMPv1 Message Formats
SNMP is a simple request/response protocol. The networkmanagement system issues a request, and managed devices return
responses. This behavior is implemented by using one of four
protocol operations: Get, GetNext, Set, and Trap
SNMPv1 messages contain two parts: a message header and a
protocol data unit (PDU).
SNMPv1 Message Header:
SNMPv1 PDU:
Trap PDU Format:
SNMPv2 Message Format
SNMP version 2 (SNMPv2) is an evolution of the initial version,
SNMPv1. SNMPv2 offers a number of improvements to SNMPv1,
including additional protocol operations.
SNMPv2 messages consist of a header and a PDU
SNMPv2Message Header:
SNMPv2 PDU:
GetBulk PDU Format:
THANK YOU
