0% found this document useful (0 votes)
67 views26 pages

SNMP

SNMP and NMS provide network management through monitoring network elements using agents and management stations. SNMP uses a simple protocol to communicate between these components to monitor statistics, status, and alerts using MIB variables. The MIB defines network objects that are monitored using SNMP's get, get-next, set, trap and response PDUs. This allows network administrators to remotely monitor and control network devices.

Uploaded by

Venkat Yasalapu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
67 views26 pages

SNMP

SNMP and NMS provide network management through monitoring network elements using agents and management stations. SNMP uses a simple protocol to communicate between these components to monitor statistics, status, and alerts using MIB variables. The MIB defines network objects that are monitored using SNMP's get, get-next, set, trap and response PDUs. This allows network administrators to remotely monitor and control network devices.

Uploaded by

Venkat Yasalapu
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 26

SNMP and NMS

Need for Network


management
 Increase in the number of computers
 Necessity for monitoring
 Necessity for Controlling by some central
authority
Monitoring the network

Statistics
Current Status
Alerts in case of faults
Monitoring the Network cont.
 Network statistics include traffic levels,
utilization, Data type etc..
 Status include operation of link, congestion,
NIC status in hosts etc..
 Alerts or alarms are raised by the agent
when a fault occurs
Components of Network mgt.

 Management Agent
 management Stations
 Management Information Base(MIB)
 Structured of Management
Information(SMI)
 Simple Network Management Protocol
(SNMP)
Components
 Network elements
 Management agent
 Management Station
 MIB
 Protocol used for
communicating:
SNMP
 Structure : SMI
Network elements
 Hosts i.e. the end terminals like the
computers, phones(in voip), printers and
servers
 Gateways, routers etc..
 Links (the hardware connectivity)
Management agents and stations
 Systems using SNMP are divided into two
categories: management stations (sometimes
called clients) and agents (sometimes called
servers).
 The stations send out query to the agents and the
agents process the query and send response after
accessing the information abt the host from the
MIB
 Every host has its own agent with which the
management stations talk to.
Management Information Base
 Description of each object in a network
element is stored in MIB
 e.g.: Let’s take the gateway with object as
max TTL. The NMS would be able to
monitor this object and change (control) the
value
 In case of a link whether the link is
operational or not and to enable or disable
SNMP
 SNMP uses a connection less protocol to
communicate between the stations and
agents
 format <PDU>
 5 simple PDU
 PDU- Protocol Data Unit the object which
is referred to.
Structure of Management
Information
 SMI uses a data Description language
 Objects in the MIB are defined using
Abstract Syntax Notation One (ASN.1)
 Each type of object (termed an object type)
has a name, a syntax, and an encoding. The
name is represented uniquely as an
OBJECT IDENTIFIER.
MIB in detail
MIB
 Object descriptor(Object description and
object identifier)
 Syntax type :integer, octet
identifier,null,constructed types, object
identifier, defined types
 Defined types : IP address,counter, gauge,
time ticks, opaque
MIB
 Definition: description of the object in
words
 Access: read only, read write, not
accessible, write only
 Status : whether the object description is
mandatory, optional or obsolete.
Object types
 System(sys desc, sys id, uptime)
 Interfaces(desc, MTU, out errors)
 Address translation
 IP
 ICMP
 TCP
 UDP
 EGP
Global registration tree

For the object


identifiers. In the
dotted format.
Extra objects in the MIB II
 Transmission
 CMOT
 SNMP
A short note on RMON MIB
 Segment statistics  alarms
 history  filters
 host table  packet capture types
 host top n  events
 Traffic matrix
SNMP in detail
 Uses UDP
 Max of 484 bytes( 484 + 8(UDP) + 20(IP) =
512 packet size)
 Popular port number 161
 Version, Community and PDU
 Version is the version number of the SNMP
 Community: every network is given a
particular name.
PDU
 Get request
 Get next request
 Set request
 Get response
 trap
PDU format for Get and Set
 Request ID: Sequence number
 Error status : Error id
 Error index: which field in error
 Var. bind list: var. names and their values
Error status
 0- No error
 1-Response is too big to fit in
 2-Get error
 3-set value is above limit
 4- Set request on a read only object
 5- General error
PDU format for trap

 Enterprise(identifier)
 Agent address
 Generic and specific trap
 Time stamp
 Variable bindings
Generic trap
SNMP v2 overview
 More intelligence in the stations than agents
 Better security( upgraded to secure SNMP)
 Enhanced PDU( get bulk and inform)
 Station to station communication)
 Get Response with exception conditions
 Introduces hierarchical NMS
 Runs on apple talk, OSI and IPX
 Increase in counter size
Thanx

You might also like