n

management I72.16.46.I
foriming 4th information
12 1Page
2020-21 subnetwork.
MODELS
INFORMATION
ORGANIZATION&
cable.
the
in
0
32
MANAGEMENTa (fig:4.). the acquire
has cat-5 from A a
subnetwork.
designates
conponent &
NMS a
by remotely query
connected
the position
network
theby router. locatedaand can
ping N\1S.we
as network
decimal
theare
a backbone
long
to in hubs logically
SYSTEMS
MODULE-3 as responds
card a 4th the
172.16
46
3
2HD
Hetwork
NETWORK network the
theinterface by
designate
the mapped
of & LAN
to each physically 192.168252.110 Hetwort
Bcknoe
that in
the connected andl 172.17
252.1
2Rater -172.16
46. Managed
elements.
in suite thecard
in to 1Router
& messages
MANAGEMENT component
IP to is
conventions
discovered
network Information nodel
TCPis assigned
interface
)
168.252.1
A
4.1 element.
and network Base)
SNMPv1 be hubs a 172.16
24% eFigu
by sed
addressed
designates
been coimmunity-ba
anv nay address establish Information
Management
the onthe network
2
discover 192.
and
router&
agent have
-Hierar
architeçture
chical
NETWORKtherouter address
MANAGED
LAN is address
managers statistics
components between
services
NETWORK 3:UNIT
management
is --Agent.
and
narmager ASN.I
sVItaxManagenent
over franework
automaticallv
a 72.16.46.1l of -SMP
TCP1P
of the Structure .(ommunication
consists
in IP
IP and
Pelationship " syntax
Transfer
Model
Comnuncation
system
an parameters
cards (whose of network Model
Organization
" Model
InfornatIon
"
the |address Ethernet
the
AN. ’Securiry
can LA\ position SNMP
1ODEL -SMI
MIB
’(ses
cg. intertace Information
NMS
\MSForEthemct thesvstem - -
IP decimal
Once
An agent. TheIhe TheLAN.
" " " " " " on
 Aside
in nteractis continuously
the from
resides server an networkSNMIP Page
2
it between
2020-21 Sometimes.
data
However,
can
which 4.7 the
managers inserted as proy telecommunkations
manager well fg: with
process, them. wh managers.
as in communicates
is Wodel objects
shown
multiple network
RMON Managed nodel
processes Cbjects
SNP.
manager
Manager SNMP
is
SNNP Agent
managed organtalonThis
Thus. networks.
thecalled Agert
Network One Manager mangement.
a & SNMP andagent. and
and of agent
SNMP.agents Network
Bement- agents,
object, Instead nodel the
Managers SNMP
of S.NMP
NETWORK
MANAGEMENT
SYSTEMS from intermediate
from management SNMP
Non- Managed
tier
using tieroganzation Seryer
Prqxy Objects systems
managed data, SHP
Manager
data Three SNMP
an
with
data Mutipte
it receives have compatible
with rawpreprocessed 4.7: of legacy
the an centralized not
consists
modules. receives
communicates {b Figure
in (Fig:4.5). formation. objects
(Fig:
4.6). does
resides Modelbro manager as on.
obtain 4.5: system so is
thatsuch
software manager Agent the
nodel and hat
object.
which in Fgure networkincreased situations,
eleiment
themanager. set
management
that to management
VIODEL are calculatingSNNP Netork One
MaragerSNMPAgent organation a
managed network
process. N\MS manager Bemart
Servernetwork into
agent
- themanaged RMON
Frobe
many data
duly
network Hage greatly
model.
MP
ORGANIZATION any
agent
thethe thenetwork Proxy networks
the
SNMIP
a in
andto models.andthe
manages ne thehas
organization tier inanage
applicable
an responds events about Manage converts
function with
Ctiects4The
(a) SNP
of manager the and
Two-Tier
\Model Three-Tier
Model pure wireless
conststs with
one 2-tier themanaged
agent. objeci agent Model can
and agent for
the manager Server
the monitonng RON is
N\MS benefhcal R\1ON nodel
Ihis BothThe the -tier Nornally,management,
Figyre Three-Tier prOxV
In Imanager.
the
" " " " In The
the SNMP
This
" " "A
" "
 4 the ofthroughvaluesobjectget
exchange amiving of new database.
2020-21? the
in a
sets
a
viaintegrated object. an of 2 discovers
multiple
process of receiptevent contains true
an value a
of have or \MDB NAIS is
are
application value on message This
the only It
layer realizedmay data.
objects,
an object.
Trap the reset
transport SNMP generated when
managementimplementation.
agent
Agent SNMP
Agent
Appication
RospoNse Get
object
requestingor
a
without
imnplementers.
process. the
Request Set SNMP VDP DLC PHT is
entities initialize Agut,: of there the
thethe Architechure an with
situations, is process values
be
andabove Request oetNext process It management associated
management to process. for to
SYSTEMS process
NETWORK
MANAGEMENT rRequet
Management management process objects the the
theneeds
layers agent on by
many MIBduringchosen
second
managed values
Medium
Physicai
application agent
a an
application
ARCHITECTURE managementfrom a manager
among In
Netork get-request.an by aand architecture
fact. measured
generated
the by message
formation
by object. generated
the In
nanager
3 SNAP MIBstatic.
the
The Trap generated the polls
SNAP
Managee set-request in thedatabase
objects,
49 to the mnessage is compiled
that and contains
PHY. Application
QotRospons. by
the SIMP
Managet Figsein sinilaris
MANAGEMIENT management of generated
between
&
Request Sot is instancesmessage database
thedatabase any
SNMP UDP DLC PHY message or unsolicited
DLC GotNetRaqu
is
ger-nex-TequesI process.
manager
get-nex1-fequest about isIt andusing
messages: is network.
dymamic
pathIP. Roqu¢st Gat mutiple get-response
gei-request
ser-request
a vrtual
hasinformationimplenented
dataUDP. of
4.9). comunication an anager
NETWORK mert
protocol is a theis
theprotocols:
(fig: of is
variable.trapthe MIBin MDB
from
portray's TheTbebecause
The Therequest, the
process
A SNMP object2)A
5folowing
1) 2) 3) 4) 5) op Au
is
transport one It
SMP
This SNVP The The
data:
" "
 4Page
SMI manager OBJECT the
under
2020-21 (CONT.) by objects.
defined
(fig:4.10). 1 and associated objects under
agent
do6)
and number 6)
(13
ndenal
MANAGEMENT =
IDENTIFIER
not example.
crat3 4 sub-nodes
MODELS instance
is
between
an
are
(sa)
Juantet.
and iis0
instance
object For3ECT types
object identifier.

and
DESCRIPTOR

there
eg.
For

Internet.
-

a
experiments.
acquire
IAB-approved
can
2
the IETF
an irterne data hieterce
as internet.
in (omnercialvendors
52)
Cantr
verdkes
INFORMATION andthe of nAxe defined
Directorunder
SYSTEMS
MANAGEMENT
NETWORK typei.e. object transfer and
to
Ccree
u
a or
NETWORK instance.
object and ASN.I.
d bv
Tye
be
can
.36.1 OSIlETF-reconmended
objects (4)) 3
for identifiedT! fce
an descriptor scheme itject: dodt67 of
which IEP ee
object the fix definenode. rter
of using processeS. pre use node.
tct
Pise
w)
composed
Information. Managed
ihe future to ate(4)
IDENTIFIERI.3.6.1.
uniquely org(3)
not a encoding (tiet
bv defined with created
used 14
andfollowing for all hgue4
ORGANIZATION&
SNMPv1 be thpe
uniquely manager 41#
is
Figue
IDENTIFIER:iso
start reserved
identify
priv
heavily
was fhe
\lanagement
to is the ceFER name) DENTFE
shuctee object
considered
the
has typeas
represented
type.
adopted
een
object betw
C6.ECT will
AIIB i to is
every OBJECT nodeused3) nodeis
a under
node
experinentai(
4: Interneti) is ) ).which
|SMT
with
of be data an beenas (ie. OBJECT directorvt
mgm(2) 4
well
UNIT Structure a is
can onlyis of
name syntax
have
(fig:4.1|).
tvpe has-its
(fig:4.13)
object
internet private(
l
To
object which as the enterprises(
concemed
for
The BERprocesses
2The object \1IBinterner
IDENTIFIER.
in The2The The
3)The
tvpe. object
standmanaged T" I) 4)
S Every Internet
is Object Any
S\Ml SMI
SMI A
" " " " " "
 Counter.which 32 a types are in the Its
5Page
of 0.
2020-21 2020-21 The to
up
value
that
indicates
to tvpes.
supports
family. data
intertace. initial1zed
IpAddress. 190.146.252.255,
value maNimum intertaces data
of value
Intemet in values thatdefined
an
increase was
on its of Is type
NetworkAddress. defining it
errors numbersecond.
IP-based at inle datapreviously
NTEGER
etre e.g. only pegs
Wraprounc
nnrngabe
teges
packet the appl1cation-wide
by for for a
Contes Ni Enmrts sDeated 19ess Cacced
Doted
mD rcrregaertey TCP can l the of and
Structut A
artta, IPv4. useful down.as hundredths onimplementation.
n output mstant based
Type I
iNTEGER nwee
dec"eae
are eg. of order. integer. such
NETWORK
MANAGEMENT
SYSTEMS SNJD
ASH
1 Data TypecOMMENTS
Aboicason case cn woe
used For
notation
is
types or
or
up decreases current types
family. bytenon-negative
Stut
Pacenode on faceeither of
ASN.1 Oata Speca Suttroes Apo'aal types an
Stt network (ounter
inter unts
the It
is data
SNMP 1 decimal move its
ASN primitiveprotocol an or in ecn informaion. create
Ue n
STRUCTURE SNMP-based DCTET STR.NG tvotAcress 4.in 0. on an increases tinebetw problem
Corsru 4,15 DATA
TYPE SECUENCE
OF dotted fron received to
SEQUENcE the a
length value measures
TEGER ipsress The is ume uscd
Flgure andstarting value
Core Opag
e of of some
typ*s.address of Its
packets of bnary
lus
4.1
groups type
STRING but andunits causes
TVPE Table around whose syntax.
primitive data integer,
nteger of
the four input of
Crares octets which
DATA $TRUCTURE
of OTETapplication-wide
wraps types nunber ASNI
conventipnalas no-negauve
using choice IpAddress. such data
non-negative
specifySNMPvI,
ASN.I then the
as arbirary
defiged a
Ticks. increase for hub. second 2?
is designatedand s to
S\\MP-BASED Addressthe usedor value
Iime ivpe a a used in
are Is
an also rputer
continuaily is
passundefined
a
baseipAddress is of2 Is
of imun
Timeicks is to
hd Neorh
Define is "(ounter
naxunuin is Gauge hundred1hs
string Gauge a Opaque
capabil1ty
Gaugethe n max
uscs that
active is
" " bit The SiZe
" " "
 NETWORK MANAGEMENTSYSTEMS

MIB
(fig:4.27). obtain
Internet standard network,it has to
SYSTEM GROUP basic roup in the
managed objects. components in the
is the accessed new
n oroup -ha most network or the |D and so on.
* in a -hiect Gar this purpose. Lat helns a network

NETWORK MANAGEMENT SYSTEMS 2020-21

MANAGED OBJECTS
"A managed object has following 5 parameters:
DThe textual nane for an object tvpe is
DESCRIPTOR defines only the obiect typemnemonic and is defined as OBJECT DESCRIPTOR OBJECT
and not the occuence or instantiation of it. Associaled with
cach OBJECT DESCRIPTOR is an OBJECT
MIB. IDENTIFIER, which is the unique position itoccupies in the
2Svntax is the ASN.I definition of the object type.
S)A definition is an accepted textual description of the obiect tvpe. It is a basis for the
or semantics. to be used by all vendors. It is common language.
intended
between the managed object and the manavement svstem
to avoid confusion in the exchange of
information
as well as between the various network
management systems.
4) Access is the specification for the type of
privilege associated with accessing the information: read-on ly.
read-write or not-accessible. Its value is defined by the svstem vendor
S) Status specifies whether the managed obiect is during the manufacturing process.
current or obsolete. The 3 choices for status are
mandatory, optional and obsolete. Amanaged object. once defined, can only be made obsolete and not
removed or deleted. If it is current. the implementation of it is specified as
either mandatory or optional.
OBECT
$ysDer. (yste 1)
Syntar DspuySnng (SZE (0 255)
Delvtan
hould ndude he Wang nd verson
OonlcaOn of the systom's hardware ype.
sofnare operatng yem, and netuorung
Ris mandatory th g4 oan ony
prntable ASC# charcters
Aooess read-onty
Status mandatory

Figure 4.17 Speaiaions for System Descnption

MACROS FOR NMANAGED OBJECTS
OBJECT-TYPE MMACRO
9EGIN
YPE NOTATION ='$YNTAK YPE (TYPE OOSyrtas)
'ACCESS Acess
"SIATUS Stas
VAL UE NOTATION vae VALUE OD,KNne)
Access:: "road-ny|'resd-wrtewrte only|'rgl-esstle
Staas : ndatory"i'ogtonar'obsolere
END

(a) An 06ECT- TYPE Atacro AFC 155)

Figure 4.18 Scaar 08JECT-TYPE Maco and Exanple

SYsOesg OBECT.YPE
SYNTAX Dsolsy Serng (SIZE (0 255)3
ACCESS red-ony
STATUS nandatory
DESCRIPTIKON
"A bea descrgton of he entty. Ths value shouid ncuÛe ho k
rame and vervos denghcation of he systen's re pe.
sOhware operatng system, ard notorung sofe. aa
mandasry rat s cortan ory printate ASCA characers
(system 1)
(D)A Scar Singe hstanc MgD sesy RFC 12131
Flgure 4.,18 (contnued)
"The body of the macro module consists of 3parts: type notation. value notation and supporting productions.
DTYPE NOTATION defines the object types in the module and VALUE NOTATION de fines the name of
the object.
2) Access can be only one of 4options: read-only, read-write. write-only or not-accessibk.
3) Allowed values for Status are mandatory, optional or obsolete.

Page 6
 2020-21
NETWORK MANAGEMENT SYSTEMS

AGGREGATE OBJECT
" A group of objects.
" Also called tabular objects.
with
" Can be represented by a table
-Columnns of objects
Rows of instances
" Example: IP address table
" Consists of objects:
IP address
Interface
address belongs to)
’ Subnet mask (which subnet this
Broadcast address (value of L.s.b. in IP broadcast address)
’
- Largest IP datagram that can be assembled
associated with the node.
objects
" Multiple instances of these
MACRO
AGGREGATE MANAGED OBJECT
" Index ipAdEntAddr uniquely
identifies an instance.
" May require more than one object in the instance to uniquely identify it.
Table Object la TabieOBECTTYPE
SYNTAX QENCE OF AdeEsy
ACCESS n0coesSle
STATUS randoy
DESCRPTION
e w t o e t s Poresses
Te t e of tressg t m o o
20)

Entry Object AddErtry 08JECT-rYPE

SYNTAX ArErory
COESs notacoST
STATUS ntory
DESCRPTION

EX i E A o

TEGER

koAres
AEBcssA
NTEGER
ACERssmSve
NIEGER (O 655J5))

Page 7
 NETWORK MANAGEMENT SYSTEMS
2020-21 NE

TABULAR REPRESENTATION OF AGGREGATE OBJECT

grouping and are
" The objects TABLE T andENTRY E are objects that are logical objects. They de fine the
not accessible.
accessible.
"Columnar objects are obijects that represent the attributes and hence are
" Each nstance ofE is a row of columnar objectsl through 5.
" Multipke instances of E are represented by multiple rows.
roW-colunn.
"\oice that the column-row numeric designation is reverse of what we are used to as

CaLnAR
: 00.4c1 4

?E)2

!4 ‘4 34

Figure 4.z2 Nurberng Converton of a Maraga Osect Tabe

Page 8
 NETWORK MANAGEMENT SYSTEMS 2020-21

VB
" MIB stand for Managenent Infomation Base.
" This is a vitual information base. Manayed objects are accessed via this virtual information base.
" Objets in the MIB are defined using ASN.I. The objects defined in MIB-2 have the OBJECT IDENTUFIER
prefix:
mib-0BJECTSDENTIFIER := /mgmt 1!
OBJECT GROUPS
" Objects that are related are grouped into object groups.
" Object groups facilitate logical assign1nent of object identifiers.
" One of the criteria for choosing objects to be included in standards is that the object is essential for either fault or
configuration nanagement.
i <maule name > DEFINITIONS BE GIN
<mports>
<defetons
ENO

Figure 4.25 MIB Module Structure

" |lgroups are defined in MIB2. (Fig:4.26).

Table 4.4 MI8-#Groups
GROUP OIO DESCRIPTION (BRIEF)
9y3emn Syslem descrpton and

tertces m2 2 hetaeS re ertty and

4ss0cLed niorma5on
23 Assoss traniar seween

In'omattnon P protocol
2S ntorma on on CL4P protoco
Inlomton on TC protocof
Intormston on UDP protocoi
28 Intonaton on EGP protoco
-2 9 PscANocer tor OSl proOcc
ro210 Pcchocor tÍc ansn$son
tormaon
tntormatn on SNAIP protoo

(136

CApement

() (23

erteos (2: ynmson 10)

tcp (Bi

Flqure 4.26 Intemet MIB-II Group

 NETWORK MANAGEMENT SYSTEMS

SYSTENM GROUP
" The System group is the basic group in the Internet
"Its elements are probably the most accessed
standard MIB (fig:4.27).
managed objects.
" After an N\IS discovers all the components in a network or the new components in the r
intormation on the svstem it discovered such as system name,object ID and so on.
" The NMS willinitiate the get-request message on the objects in this
group for this purpose.
" The grOup also has administrative information such as contact peron and
physical location.
manager.
" Implementation of the System group is mandatory for all systems in both agent & manager.
Table 4.5 System Group
ENTITY ONO OESCRPTION (BRIEF)
sysDse Tertua oscnpon
Sysion 2 OBECT OENTFIER o etsy
sytom 3 Tne pn ungedts of a socond

yCona Sstm 4 Contact person lor he noos

Admnisarte nme of he system
sysLocason $ysm 6 Pysical iocason a he node
syServic Syslerm 7 Vee desgtng he ye seces
provided by enety

syTne(3)
-sysContact(4)
 Sperd tps
NETWORK MANAGEMENT SYSTEMS 2020-21
F 2 3

ANTERFACES GROUP
The Interiacc group contains managed objects associated with the interfaces of a system.
" If there is more than one interface the system. the group describes the parameters associated with each interface
" This specifies the number of interfaces in a network component and the managed objects associated with each
interface.
" Implementation of the Interfaces group is mandatory for all system.
TabBe 4.6 ntertaces Group
ENTITY DESCRIPTION (BRIEF)
Numbr Totd mbor cf ngwr netecsahe system
natte ertaces 2 Lst ol ertnes desonting lormaton on each rertaca o e
system
Enry An ntertac enry contarng obyecs the sbnetwork ryor
or a paraler nerlace
Inndes Aunque teger vaue tor each terece
AEnty 2 Tar! dea on product nane nd vorson
Type Enry 3 Type of ntorace layer beiow hernr layer Cefned as n
eneMed neger
Entry 4
Soed fEmy 5 Current or nomn data rate or the nertace n bos
PnysAoess Entry 6 Intertace 's adoress at he prolocol layer ennedatety betow the

Mdnnsuts Enty 7 Desred status o he ntenoe vp. ow, o estrg

1OperStaus Entry & Curent operasonal staus of he ertace
Aasichange Emy 9 Vae c sysUpTe at he umerd oprtona staus
AeOcets Eory 10 Total oube ol put ocets ecm
AncasPs Entry 11 Number oB sonetnorkucast packets doverod toa hãner
layer proco!
nNUCSPts Enty 12 Number of non-uscast packots delvered to a hacper-tayer
protoco
AeOscts AEry 13 Munbr of ntnd pdets dscarded irespecte cf ero
sias
A£rors Numbe of nbound p0ets mn eTors
AnUnkonProtos ty i$ ber of unsupportcd protoco ptes scaded
OOctets Ensry 16 umbar o odets ransmled out of enteta
Entry 17 Tota runber ct uncast padets hat hgher-veayer
requessed lo be ransmtod
OUcasPrts knty 18 Tota nunber ct non-uncast padtets ha ghe-ter
Peguesed io be ransmted
OuDsods Enty 19 Numoer of outbound t e s dscarded TRSpecve & emo
40ERors Erey 20 Nurater o otDond packets that cod not e rarsm
because of erors
1OutOken Erty 21 Length o he cutput quenrets

Table 4.8 IP Address Table

ENTm DESCRtP TION (BRIEF)
pAddr Tatble 20
pAdorEnAry Ono of the rtesnhe Paddress tato
pAdEmAddr Th IP daress to wt ths enys
addresung ntominpertans
AdE inde IpAserEnry ? ndex vabe of o entry same anse
pst NetAlas IgAddr ny J Subnel mast kx he doress o the
ntry
lpAcar£ ntry 4 Broakoss address ndctor bt
22
pAotfResmMaaS2e ipAddrEny 5 Lagest IP datagram tht can De
easernbld on tha ntroco

12

LPage 11
 NETWORK MANAGEMENT SYSTEMS
2020-21
Table 4.9 IP Routng Tabe
ENTITY
DESCRIPTON (BRIEF)
oRoteTae p 2: P roatng labe
pRaveEntry RouseTatte 1 Route 1o a ptñ destnton
ipRouteDet RoteEny 1 Destnason P s0ge3s ol tras foute
pRastetndes RoteEnry 2 Indes of detace same as hcer
pRateetc1
pRoueenc) pRcuteEnty 4 An aeTale rotrg metc lor thes
roude
ÇRotolerc3 pRoueEntry 5 An atematve foug metnc tor s
routo
pRateetrcA pRouteEnry 6 An anemStYe roung metnc tor
hs route
cRasteNeatHoo pRoueEnry 7 IP aress cl te nest
hop
ÇRaetyoe
pRotProto pRouteEnry 9 Routng mechansm by
w2s learned
wcn thos rovte
cRataage pRoue£ry 10 PirOe o sKonts snce rosny nas wsi
UDdatod
cRotelask pRoreEnry 11 Masa to te iogaly
ANDed wth the
desnaton adress betore companng w)
the RoleDest Les
pRatoetrcs
pRotento
pRouleEny 12 An aletralve me'hc 1or
hsde
spRoutet ntry 13 Reterence to k8
toutng prooco
derston speofc to the

Intoay
Cuis-)
speue

t).
r

I)

Tntrpu
 NETWORK MANAGEMENT SYSTEMS
2020-21
TCP GROUP
Table 4.13 TCP Group
ENTITY
Rtoigorkhm DESCRIPTION (BRIEF)
Tmoout o'gonthm lor
LopRiolkn Ico 2
retronsmsson of ocets
Mnmum vae or tmeot n mieconds lor
retrangmsson
cpRoMa lco 3
MaItum va lor umeot
mdeconds n
retansmsson
kaarCon Waumum umbe cf TCP onnecions
kpAtveOpers Nnoe cte conneons made CLOSED to
SYN SENT Sale
cpPassveOpens tcp 6 Nmber o' passe onnecuons made LISTEN to
SYN-RCVD e
caARemoFas kp 7 Numoe o faied adempts lo make conneon
kpEssResets !o 8 Number o resets done to e CLOSED
USTEN stae
tcpCurEslab Nner o onociuns lor wtch he curont stato
s ehe
ESTABLISHED o CLOSEO-WAJT
spinSegs lop 10 Toa! number of senents receved
ncdng wh
TOrs
tcpOtSogs !cp 11 Tota! nTrosoçments enGrcudng
rerarsmsson
tcpRetansSegs tcp 12 Toa nuTber o segments retransmted
IkpCornTabie lco 13 TCO conecon abe
tcpinEms Ico 14 Toka nMbor ol gments recoed nero
kpOuRsts lco 15 Number of segment serd conanng RST tag

TCP CONNECTION TABLE

Table 4.14 TCP Connecion Table
ENTITY
DESCRIPTION (BRIEF)
topConnTable tcp 13 TCO conncion able
tepoonnEntry TooConnTablo 1 Irdormabon abou a parbcular TCP
annoon
tpConnSlaze ToConEney 1 State of te TCP connecbon
tcpConnlocalAGdregs TopCanEny 2 Local IP address
cpConnocatPon TpConnEnery 3 Local pon numbr
tepConnRemaddrs TpConnEney 4 RomolePddrens
tcpConnRomPo TcoConnEney S Remote pon number

UDP GROUP
Table 4.15 UDP Group

ENTITY DESCRIP TION (BRIEF

udpinDalagas Total nmbor o datagrams dervord o
Ihe users
Q n r r i sspe
e
UdONOPorts Tol rber o! receved datagraTs lor
ahchere is no spplcaton
uóptrEsrors udo 3 Nynber revod datagrs wtn
erTors
ucpOatagrams ydo 4 ToLa number of dtagms sone
vdpTatie udo 5 UDP Lstenar ble
udpTable 1 !ntormatA abouta p a t a corresbon
UDPLner
udplocalAddress UdpE y 1 Local P address
ugoLocsuP ort Locl UOP o t

Page 13
 ¬n eacl heface.
nTAIORK MANAGEMENT SYSTEMS 2020-21

NETWORK MANAGEMENT SYSTEMS

2020-21

UNIT 4(CONT.): SNMPv1

NETWORK MANAGEMENT -
COMMUNICATION & FUNCTIONAL MODELS
SNMIP COMMUNICATION ARCHITECTURE
The SN\MP architecture consists of
elements. (Fig:4.9). communication between network management stations and managed
" Network elements have network
built-in management agents if theyare
" The SNMP
communication protocol is managed elements.
stations and the management agents in the used to communicate information between the network management
" Only elements.
non-aggregate objects are communicated using SNMP. The aggregate objects are
instances of the object.
"
communicated as
ASN.l and
BER are used for data transfer in
" The information about the SNMP.
network is obtained primarily by the
" The SN\IP manages the
network with the following 5 messages:management stations polling the agents.
DThe gel-rèquest message is generated by the
2) The ger-nex-request is similar to management process requesting the value of an object.
get-request. In many situations. an object may have multiple
because of multiple instances of the object. values
3) The set-request is generated by the
variable.
management process to initialize or reset the value of an object
4) The get-response message is generated by an agent
process. It is generated only on receipt of a get
request. get-next-request'or set-request message from a management process.
5) A rap is an unsolicited message generated by an
agent proce[s without a message or event arriving
from the manager process.
" Following are 3 types of traps:
O) The generic ctrap type con_ists of coldStart, warmStart, linkDown, linkUp.
o egpNeighbourLoss and enterpriseSpecific. authenticationFailure.
2)The specific-trap is a specific code and is generated even when an
o 3) Thétme-siamp is the time elapsed between the last initialization nterpriseSpecific trap is not present.
the geneation of the trap.
er--mitiatizatio of theelement and

SNMP Manager SNMP Agent

) mrt
SNMP Managet
Application
SNMP Agent
Application

SHMP SNMP

UDP

IP IF

DLO DLC

PHY PHY

Physica! Medium
Figre 4.9 SNMP letvor k Msnsgement Actitectue
Page 14
 NETWORK MANAGEMENT SYSTEMS 2020-21

ADMINISTRATIVE MODEL
" The application entity that reside the management station is called SNMP manager. and the application entíty
that reside in the network element
called SNMP agent. The pairing of these two entities is called an S\MP
community.
" In (fig:5.l).while an SNMP manager is nonitoring traffc on an element. another manager can be configuring
some administrative information on it. A third manager can be monitoring it to perform some statistical stud..
" In (fig:5. l).the authentication schene filter module in the manger and nthe agent. The simplest form of
authentication is theconmon community name between the two application entities.
" A network element conprises many managed objects. both standard& prívate. However.a management agent
may be permitted to view only a subset of the network element's managed objects. This is called the community
MIB view (fig:5.2).
" In addition to the MIB view, cach community name is also assigned an SNMP access mode either READ-ONLY
or RE.AD-WRITE.
" The pairing of the SNMP MIB view with the SNMP access mode is called the community profile.
" A con1munity profile in combination with the access node of a managed object deterinines the operation that can
be perforned on the object by an agent.

S P Manager SPMan SPBVP Mage

Atortcton Sce Arertton Sctene

ALenoncton Shne

SNP Aet

Figure 5.1 SNMP Communty

S P Aoert
READ READ
WRITE

Flgure 5.2 SNMP Communty Profle

Page 15
 Z0Z0-21
NETWORKMANAGEMENTSYSTEMS

This
fined as SNMP access policv.
SNNMP ACCESS POLICY community profile is de
with an S\\MP community
pairng of an S\NIP comnunity management. community profiles.
"A model of SNMP they have different
defines the administative belong to Community 1. However.
agent l and 2 However. it cannot
"In fig:s.3. communicate with both Agents 1and 2. bcause it also
profiles Iand 2.
part of Community I. can Community 2. Manager ? has access t¡ thei
" \Manager I.
which is
4. which belong to
communkate with Agents 3 and SN\IP proxy
belongs to Conmunity 2. non-S\MP community that uses the
managing a
policy can be extended to
The S\\MP acess aproxy server.
acess policy (fig:s 4). proxv policv is called a proxy agent or conmereially the objects and data
"The SNMP agent
associated with the agent and then converts
non-SN\MP community with non-SNMP
The proxy agent monitors a manager.
and data to feed to an SNMP
to SN\MPompatible cbjects

Cirty

Comty 1

Commt, Prçt d

Nanage 2
Commy 2)

Flqure 5.3 SNMP Access Pohcy

SMUAansge

Agar
iProy Agen
$VP Commty

Fiqure 5.4 SNMP Proxy Access

Potcy

Erplain Somp Srur

Organízatisn msdel

Page 16
 NETWORK MANAGEMENT SYSTEMS 2020-21

SNMP PROTOCOL SPECIFICATIONS

" The peer proesses. which implement the SN\IP. and thus support the SNMP application entities. are called
protocol entities.
" Commun ication among protocol entities is accomplished using messages encapsulated in UDP datagrams.
" An SWP message consists of aversion identifier. an S\\IP community name and a PDU (fig:5.5).
" An S\VP protocol entity is received on por 16] on the host except for trap. which is received on port l6a
" The maximum length ofthe protocol in SNMPvl is 484 bytes.
" This is mandatory that all five PDUs be supported in allimplementations:GetRequest-PDU.GetNextRequest
PDU.GetResponse-PDU.SetRequest-PDU and Trap-PDU.
Basic operations of the protocol entity involve the following steps as a guide to implementation:
D
The protocol entity that generates the message constructs the appropriate data PDU as an ASN.I object.
2 ltthen passes the ASN.iobject. along with acommunity name and the ransport addresses of itself and
the destination .to the authentication scheme.
3) The authentication scheme returns another ASN.Iobject.
4)The protocolentity now constructs the message to be transmitted with the version number. community
name and the new ASN.Jobject. then serializes it using the BER. and transmits it.
$) The reverse process goes on at the receiver.
6) The message is discarded if error is encountered in any of the steps.
7)A trap may be generated in case of authentication failure.
8)On successful receipt of the message. a retum message is generated. if the original message is a get or
set inessage.

Kpoicsen.
verso CmmtyDta POU

Tremon POU $ocKon PU

TrasoPOU

POU
Hesder

Figure5.5 Encapsulated SNMP Messsge

RFC1157 SNIP DEFINITIONS BEGIN

InORTS
OboctNamo. Oto1Syntas NotworAgoress IpAcress Tme Tos
FROM RFCI199 SAI

wesovENCE verso
INTEGER!
-vefS n

verssn {0)

OCTET STRING
caa
ANY dthencaton s bery used

-oroco du ns

CHO CE

Get-nest-rezes! GotRes+POU
(Gett detRocvess POU.
GetReonsePOU.
SotRogos POU
Trap-POU
comoy usd ca pes wbo defned LAser
-ne r u POUs nd
END

Fiqure S.6 RFC1157-SNMP Macro

Page 17
 NETWORK MANAGEMENT SYSTEMS 2020-21

GET AND SET TYPE PDUS

" In fig:5.S. RequestlD is used to
track a message with the expected response or
ot-message detection is implementation specific, such as time out if no responseindicate
loss of the message. Loss
gIven time. is received for a request within a
" ErorStatus is used to
" Emorlndex is used to
indicate that an eror occurred.
provide additional information on the eror status. The
where it is not applicable. Otherwise. it is fillked with the varBind value is filled with NULL in cases
number where the error occurred.
PCU Eror
ReguetO Ermor Varßrg 1 Vaßnd1
Tyo Vernodn VaBadn
Name Vaue
Vag

Figure 5.8 Gel and Set Type POUs

TRAP PDU
" In fig:s.9. the enterprise and
" The generic-trap consists of agent-address pertain to the system generating the trap.
’ following 7 types:
coldStart(0):sending protocolentity is reinitializing itself. agent's
implementation may be altered. configuration or protocol entity
’ warmStart( l ):sending
protocol entity is reinitializing itself. agent's
implementation not altered. configuration or protocol entity
- limkDown( 2):failure of one of
the communication links.
linkupt3 ):one of the links has come up.
’ authenticationFailure(4):authentication failure.
- egpNeighborLoss( 5): loss of EGP
neighbor.
- enterpriseSpecifict6):Enterprise-specific trap.
The integer in parenthesis
associated with each nane indicates the enumerated
" The specific-trap is a trap that is not INTEGER.
" Time-stamp indicates the covered by the enterpriseSpecific trap.
elapsed time since last re-initialization.
PO Agen Genonc Spoote
TOR psdrs Trap Tvoei Trao Twoe iTmeSO Vßs41: YBrd 1 Vandnivnd a
V
Figure 5.9 Trap PDU

Tabie 5.1 Genenc Traps

GENERC-TRAP TYPE
DESCRPTION (BRIEF)
oldSt)
Sendng protocol erahy is reiniang tset n
conhguraton
aered
or orotoco entty mplementabon may be
Sa) Sendng protocoi entty
ongutsbon or protocols\enakzeg tsed, ageni
entty mplementsbon not aterod
ror) Faduro f ono of he comuncaDon ks

Auheneaton faure
ggtous; LoSs o EGP neghbor

erterprsespeuby Ertergnso-speckc tag

Page 18
 NETWORK MANAGEMENT SYSTEMS 2020-21

GETREQUEST-PDU OPERATION

Agert
Manegr Prooens
Process GoROone( r n c 0SunoS
GuRb,ecro 0)
GeRanome{ systedi Oeterpnses 1!23 1012
GoReponse (aysupIm 0e22A734530)
GeRoest tsysCotat )
Gponae(snContat
GeRegn (sName O)

Geegesl yServces O)

Flgure 5.10 Get-Reguest Operabon for System Group

GETNEXTREQUEST-PDU OPERATION

Prons
Manager Reore tsraesgSuS
Procss
GetheR
GetRongonoe isyOtod oererpes 112330 : 2)
GehersRegutbt (snotoaD.0:
1Geesponoe Tne 0-241349530).

GetResoose yConlact O
GestecRouest isysCortaca

-GestROsSane C)

G e t t e R t ( c O n C)
GaReonse snSennces 72)
Ceeen (ysServces D
-GetRoome (nosuchae!

Operaton for a System Group

Figure 5.11 Get-Next-Request

i21}

(22)
5.15
Operaton Examptes n Fiqures 5. 13 and
Figure 5.12 MIB lor

Page 19
 NETWORK MANAGEMENT SYSTEMS
2020-21
LEXICOGRAPHIC ORDER

Table S.2 Lexcographic-Order Number Example

NUMERICAL ORDER LEXICOGRAPHIC ORDER
1 Table S.3 MI8 Exanpto for Lexicographc Ordenng
1118
1 1
115
115
126
1.! 18
15 15
12
22 2 126
22 2
115 250 22
126 809 2 10
250 2 10.9
321 321
1118 34
34
2509 321
9

" Procedure for

ordering:
) Start with leftmost
digit as first
2 Before increasing the order in theposition.
3Continue the process tillthe first position. select the lowest digit in the second position.
4) Increase the order in the last lowest digit in the last position is captured.
S1Move back to the last but oneposition until all the digits in the last
position are captured.
61Continue adv ancing to the position and repeat the process.
"Iree structure for the above first position until all the numbers are ordered.
process is shown below:

10

Flgure 5.14 MIB Example for

Lexicographic Ordering
GoRenponse (A)
-CeteReost A
-GeteRegst()
GteReastTE11
GeNeato (‘ E12
-GettesAeut E21
GskaspcomL221
Gt4ReQ (1 E22
GReoon(TE1
-GeteR TEJ2
EIE!
TEN|TE 22|1¬32

Figure 5.15
Gel-Next-Request Operauon for a MIB in FQure 5.12

Page 20
 NETWORK MANAGEMENT SYSTEMS 2020-21

USE OF GETNEXTREQUEST-PDU OPERATION

" In fig:S.12. the tirst two objects, A and B, are single-valued scalar objects.
" They are followed by an aggregate object represented by the table T with an
entry E and two rows of three
columnar objects, T.E. 1.l through T.E.3.2.
" The \iIB group ends with a scalar object Z..
" fig:5. 13 shows the use of nine get-request messages to retrieve the nine objects.

Figure 5.16 GetNextRequest Example with lndices

 NETWORK MANAGEMENT SYSTEMS 2020-21

VLNCTIONAL MODEL

nnOtTrKs 23

sm BadVerss (3) srrnoutSetecets (27,

snmCourshtie (4)
brpinacCommtyses5:
snmçhS?ParseE rors (6 sITOAGenErg 24
uset1231
$TpOBatiaes :22:
kTgrhoSucms (9:
Srmyr8adVaves (19:
bnmcResdOns:1)
s1ghGerEs(12) IsATEGetHesccrses :8.
semorTctaRegvers13)
|<mgr.SetRegues (17)
krpnTctaSet/rs (141
somainGetRoqess i1S)

Figure 5.21 SNMP Group

Table 5.4 SNMP Group

DESCRIPTION (BRIEF)
ENTITY
SArçinprts yrnaoortun
Tota nbor of mossaos devnd to
SnnpOuPkts sno (2) from transport semo t N
Total nbor of essages
SArpinBdVerons unsupported versSon
are o
rom transoon snoe that
sampnBadCommunyNanes snnp (4) Totat rnber of messaoes

rom traspon senco. not

snno (5) Total numbor o messags
smprBa0ComunyUses aowd operzton by h sendng
C0mUy
os
Total runber of ASN Iand BER
snmpinASNParseES
Not us
snro (7) hve
from ransport senvce tha
snnp (B} Total nnbor of nessaoes
Snmpn TooBgs too8g' erors ave
rom taspon smoe h
SAno (3) Totl rumber of messaos
snmpinNaSvchNmes 'noSuchame erors
rom ransport sevae
rmo(10) Toty ube ol moss0es
snmpinBaNs
from ransport Sevoe
Srnp (11) Tot nunber messaÍes
rnpinReadOrtys reOnty' rors h
from ransport senWce tht
srmp (12) Total nunor o messag
genEr orors
Get-ReQueN an G-Nen
Tota rumbor o sucossW
srro (13) messages
sr.mpin TãsRocVs receved
woessNy aed by Set-Reu
umo (14) Tolw nunr of oCects
smpnToSetvars messa90s rocved
prooKO
otal numbor of
Go-Requ POUs 0cepted and
sSmo (15) accepted and proossed
urpnGRecvosts POUS
srmp (16) Votal number of Gel-Not
POUS cepled and procossed
snmpnGUiets
smo (17) Tola number of Set-Reçues
urpnsReests Ge-Rosponse POUs acopled and
smp (18) Tola n w of
MnpnGRosponss procassed
acCNOed and prooAsed
Tota unber ol Trag POUs
no(19)
POUs gonoraed for wach eor
npnTrnps smo (20) Toa umbr of SNMP
sampOtTooBgs stas is boBg
generled lor wch emor
Smo (21) Toal nunbar of SNMP POS
smpOuoSuchNames slolus noSicNne'
eror
Total nunber of SNMP
POUs generaled or which
sngBtaies smp (22) ats is badVu
eror
of SNMP PDUs penerted lor which
snmGenEmy wmp (24) To number
stas 'oenEr POU genertod
SNMP Get-Requou
m (25) To number l
mpGeReqests
Page 22
 R MD
oNevit

denstol
p yNETWORK MANAGEMENT SYSTEMS 2020-21

UNIT 5: SNMP MANAGEMENT - RMON

f2
PNMS
HATIS REMOTE MONITORING?
The monitored information. gathered &analyzed locally, can be trans1nited to a remote network management
^tation. In such a case. Yemotely monitoring the etworwith a probe is referred to as RMDN (Remote Nerwork
Monitorung) (fig:8. ).
Two remote LANS, one atoken ring-LAN and another, an FDDI LAN ,are connected to the backbone network.
The NMS is on the lbcal Ethernet LAN.
"FDDI
An probe
Eihernet probe is on the Ethernét LAN monitoring the local LAN The FDDI backbone is monitored by an
via the bridge and Ethermet LAN,A token ring probe inonitors the token ring LAS. It comnunicates
wnh the NMS via the routcTS the WAN &the backbone network)The remote FDDlis monitored by the buit-in
probe onthe router. The FDDIprobe communicales with NIS.
All 4probes that monitor the 4 LANs and communicate with the NMS are RMON devices.
Advantages:
MEach R\1ON device monitors the local network segment and does the necessary analyses.
This relays infornation in both solicited &unsolicited fashion to the NMS.)
For example, RMON could be localypolling the network elements in a segment, If it
detects an abnormal condition such as heavy packet loss or excessive collisions. it sends
an alarm. Because the polling in local, the infornation is fairly reliable.
The local monitoring and reporting to a renote NMS significantly reduces
SNMP traffic in the network.
2) RMON reduces the need for ayents in the network to be visible at.all tines to the N\MS.
3) Monitoring packets such as ICP pings, may getlost in long-distance communication. especially under
heavy traffic conditions. Sucth losses may wrongly be interpreted by the NMS that the managed object is
down. RMON pings locatly and hence has less chance of losing packets. thus increasing monitoring
reliability.
4) The individual segments can be mon itored almost continuously. This capability provides better statistics
and control.
Thus a faut can be diagnosed more quickly by the R\1ON and reportedto the N\MS.
5 RAION provides higher network availability for users and greater productivity for ad1ministrators.

Remote FDDI LLAN

F0®1,probe
pede FROIPt

ERDI
Pratti
Badbone Nebepk

-Local LANT

Doeh

Remote Toen Ring LAH

prese
Figre 8 1Metwor kCornigur ation with RN

Page 23

Loc Lan
 won?
NETWORK MANAGEMENT SYSTEMS 2020:21
C l o n n e

RIONIGROUPS &FUNCTIONS
" The data gatherng modules. which are LAN probes. yather data from the remotely monitored
COmpnsing Ethemet & token nng LANS. The data can serve as inputs to 4 sets of functions. 3 of which network. monitor
traffic statistics fig:S.3).
The functions perforned by various groups is as
1Statistics: provides lin level statistics. follows:
Aistor: collects periodic statistical data & stores them for later retrieval.
Alarm. generates events hen the data sample gathered crosses
4 Host: gathers stat istical data on pre-established threshold.
hoss.
SHosA Top N: compates the top N hosts on the respective categories of
6 \tatrN: gathers statístics on traffic statistics gathered.
betwèen pairs of kosS
7Filter: perfomsTller iicton that enables capture of desired
S Packet capture: prov ides patket capture paraneters.
channel. capabMiy Tor gathering packets after they flow through a
9 Event: controls the
generation
" The ouputs of the various modules are ofevents notifications,
&
network manager in the NUS. analvzed & presented in tabular and graphical forms to
the user by the
" The filter group is a cascade of2
filters. The packet filter filters incoming packets by
and or XOR With a mask specified. The perfor1ming a Boolean
selections based on the channel mask. filtered packet stream is considered a channel. and we can nake further
" The filtered outputs inay generate either
alarns or events. which are reported to the
of the filter group can be stored in the
packet capture module for further analysis by thenetwork manager The output
network manager.

Touen-ng Token-Rg
Contr
frotsdthy
4

ston
Con4

Remcta
Montore
Gneg Sudes
Sa Menoer

Lnlpob
Ferng ´Capra

ALar Érert
Gytn Genen
Figure 8.3 RMON1Groups and Functons

sbtistiy
Percode monttoriy
nefrt con
Page 24
NETWORK MANAGEMENT SYSTEMS 2020-21

Table 8.2 RMON1 MIB Grouos and Tables

TABLES
GROUP FUNCTION
-otherSts Tatle
mon 1 Provdos bnk-lee! sastes
-eerss2Taoie
Cotects perocc sSsstcs cA nd so0s -hrsioryCono Tsbie
Hstoy mon 2
Aor Later retreva
-etstory Taba
stonycoro2Tete
-enertstory2Table
Gener es events when he da's smple lmTable
Aasm ROn 3
9hored ossus pro-esEhed
threshods
Gates sLatca caa on hosts
-hostCorttfabie
Host
-hos! Taie d e

-hos! Tme Tatly

-hostCorto2 Table

Canpes the koo N NOSs on the hos! TopNcontroToe

Host Top N mon S
respoctvo atogonos of atsbcs gatored
-maraCorroTate
Gatrs sabsts on rafic benpars
rnon 6
d hoss
matuSOTable
ataDSTabie
-natuconto2Tabie
Pertorms fer tncton hal onables -erlabie
Fner cROhre of desed parameters
-chaerTab'e

-6Rer2Toble
crn2Table
-bulercontro Table
Pa mon 8 Drowdes pchet capre
gath packets te they ow
capre
charnel
-capueBfler Ltle
ontTabie
goeraten of events nd
Ev

Rmon 10
Conros
otfcabons
See Tabe 83
Soe Table & 3
proe
Can
monisto
Token nng

lu)

Page 25