Upload
yatish-bathla
View
214
Download
0
Embed Size (px)
Citation preview
7/25/2019 Design of Management Application
1/32
Coursework for CNMTCNMTEuropean Master of Reseach on Information and
Communication Technologies
Spring semester 2010-2011
Barcelona
Design of ManagementDesign of ManagementApplicationApplication
Filip Mestanov, Marcelline ilson,
!atis" Bat"la
7/25/2019 Design of Management Application
2/32
2Communications-#etwork Management $ec"nologies
% network management must ensure t"at t"e network an& applications are up-
an&-running smoot"l' an& efficientl'(
$"e Manager e)ecutes logical programs * managements applications(
Managed Network : TopologyManaged Network : Topology
7/25/2019 Design of Management Application
3/32
+Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% configuration of a network
% p"'sical an& logical arrangement of t"e no&es t"at form t"e network(
ogical $opolog' *
% t"e pat"s taken .' &ata to travel over t"e network
/"'sical topolog' *
% mapping of t"e network no&es
% p"'sical connections .etween t"em(
Signal topolog' *
% t"e pat"s use for signals to pass over t"e network(
7/25/2019 Design of Management Application
4/32
Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% /"'sical $opolog'
BS *
all t"e no&es are connecte& to a common transmission me&ium(
7/25/2019 Design of Management Application
5/32
Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% /"isical $opolog'
3ing *
ever' no&e is connecte& to two ot"er( Data transmitte& over t"e network pass
t"roug" eac" of t"e no&es in t"e ring until t"e' reac" t"e &estination no&e
7/25/2019 Design of Management Application
6/32
4Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% /"isical $opolog'
$ree *
central root no&e is connecte& to one or more no&es of a lower "ierarc"'(
7/25/2019 Design of Management Application
7/32
5Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% /"isical $opolog'
Star *
eac" no&e of t"e network is connecte& to a central no&e, transmitte& passes
across t"e central no&e
7/25/2019 Design of Management Application
8/32
6Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% /"isical $opolog'
Mes"
7ac" network no&e is connecte& to ever' ot"er no&e in t"e network(
7/25/2019 Design of Management Application
9/32
8Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% /"'sical $opolog'
9ntercone)ion of #etwork
More comple) networks can .e .uilt as "'.ri&s of two or more of t"e a.ove .asic
topologies(
7/25/2019 Design of Management Application
10/32
10Communications-#etwork Management $ec"nologies
Managed Network : TopologyManaged Network : Topology
% $"e Management #etwork $opolg' associate& *
Centralise&
Distri.ute&
Bot"
M
M
M
M
M
M
M
7/25/2019 Design of Management Application
11/32
11Communications-#etwork Management $ec"nologies
SNMP Entity General View SNMP EngineSNMP Entity General View SNMP Engine
% S#M/ 7ngine
Dispatc"er
% Sen&ing:3eceiving S#M/ massages
from t"e #etwork
% Determinign t"e version of t"e
S#M/ message an& respon&ing
wit" t"e proper Message processing
mo&el ;M/Muitous
environment( t"e services of t"e &evices are
invoke& .' ot"er control points, an& t"en t"e
&evices sen& t"e appropriate event notifications
to pro)' agent(
% $"e pro)' agents /n/ control point gat"ers
information from t"e &evices an& its S#M/ agent
keeps t"em in t"e M9B format ($"e manager
w"enever nee&e& can >uer' t"e agent,
7/25/2019 Design of Management Application
17/32
15Communications-#etwork Management $ec"nologies
%MP'EMENTAT%&N%MP'EMENTAT%&N
9n or&er to anal'=e t"e performance of our s'stem we "ave emulate& our
s'stem using t"e following simple scenario( e consi&ere& a Single /ersonapartment an& we can control following &evices*
Main &oor sensor, $, air con&itioner, $u.e lig"ts
as" room Bul.s, Fri&ge( Microwave oven an& /C(
e &ivi&e& t"e time into parts to simulate t"e peak "our usage or no usage .reakfast an& wakeup timings ;4 to 10< an& &inner an& rela)ation time ;4 to
11
7/25/2019 Design of Management Application
18/32
16Communications-#etwork Management $ec"nologies
Psedo CodesPsedo Codes
Step 1* /sEco&enG H Computer clock timeI
Step 1(1* 1J n J :: Set four pseu&o co&es accor&ing to sage of Manage&
&evice::
Step 2* /sEco&e1G H 4*00 * 10*00 ::Ma)imum sage::
Step 2(1* Set clock H 0*10 ::After 10 Minutes Communication .etween
Manager an& agent ia S#M/ an& $ranslate co&es::
Step 2(2 * 9f M9BnGHH 7rrorEoccure&
step 2(2(1* Set AlarmnG::Different alarm tune is set for &ifferent Manage&
&evice::
Step +* /sEco&e2G H 10*00 * 16*00 ::Almost no sage ffice timing::
Step +(1* Set clock H 0*+0 ::After +0 Minutes Communication .etween
Manager an& agent ia S#M/ an& $ranslate co&es as manage& &evice is
less use&::
Step +(2 * 9f M9BnGHH 7rrorEoccure&
7/25/2019 Design of Management Application
19/32
18Communications-#etwork Management $ec"nologies
Psedo CodesPsedo Codes
step +(2(1* Call userEmo.ile an& serEoffice::Call .' manager to user wit"/re-recor&e& message;&one .' softwares like 3'nga,Sms&iscount< ::Step * /sEco&e+G H 16*00 * 2+*00 ::Ma)imum sage::
Step (1* Set clock H 0*0 ::After 0 Minutes Communication .etween
Manager an& agent ia S#M/ an& $ranslate co&es::
Step (2 * 9f M9BnGHH 7rrorEoccure&
step (2(1* Set AlarmnG::Different alarm tune is set for &ifferent Manage&
&evice::
Step * /sEco&eG H 2+*00 * 04*00 ::Almost no sage::
Step (1* Set clock H 0*20 ::After 20 Minutes Communication .etweenManager an& agent ia S#M/ an& $ranslate co&es::
Step (2 * 9f M9BnGHH 7rrorEoccure&
step (2(1* Set AlarmnG::Different alarm tune is set for &ifferent Manage&
&evice::
7/25/2019 Design of Management Application
20/32
20Communications-#etwork Management $ec"nologies
Control Point it* SNMP AgentControl Point it* SNMP Agent
!atis" Bat"la
7/25/2019 Design of Management Application
21/32
21Communications-#etwork Management $ec"nologies
T$ANS'ATE CET$ANS'ATE CE
% From S#M/ to Dn/
3eceive-get3e>uest*
step 1* 3esponse9&HookupM9BEDB;o.@ect 9&entifier
7/25/2019 Design of Management Application
22/32
22Communications-#etwork Management $ec"nologies
T$ANS'ATE CET$ANS'ATE CE
Step 2*9f 3esponse9& is null or ot"er error occur
Step 2(1* 9ssue get3esponse;gen7rr;3esponse9&uest*
step 1* 3esponse9&HookupM9BEDB;o.@ect 9&entifier
7/25/2019 Design of Management Application
23/32
2+Communications-#etwork Management $ec"nologies
T$ANS'ATE CET$ANS'ATE CE
Step +(2(1*9ssue get3esponse;alue, .@ecti&entifier
7/25/2019 Design of Management Application
24/32
2Communications-#etwork Management $ec"nologies
T$ANS'ATE CET$ANS'ATE CE
% From /n/ to S#M/
nMo&ifie&Statear
Description* Call Back Function
Step 1* SetpM9BEDB;/n/3ecor&,L/n/L
7/25/2019 Design of Management Application
25/32
2Communications-#etwork Management $ec"nologies
T$ANS'ATE CE E+planationT$ANS'ATE CE E+planation
% 9t inclu&es .ot" /n/ control point an& S#M/ agent, t"us acting as a gatewa' .etween
/n/ environment an& S#M/ manager(% $"e translation co&e is &emonstrate&( 9t is >uite simple for .ot" 3eceive-get 3e>uest
an& 3eceive-get#e)t 3e>uest(
% 9n case of 3eceive-set 3e>uest, after vali&ating t"e 9D , control is transferre& to t"e
Control /oint ;/n/ Kan&ler
7/25/2019 Design of Management Application
26/32
24Communications-#etwork Management $ec"nologies
SAMP'E APP'%CAT%&NSAMP'E APP'%CAT%&N
Figure s"ows our S#M/ manager, w"ic"
coul& loa& M9B files an& listen to S#M/ trapsan& perform &ifferent S#M/ comman&s an&
operations( 9t stores t"e listene& &ata in a
&ata.ase an& "elps in performing &ifferent
t'pe of anal'sis(
% $o c"eck t"e effectiveness of our s'stem, we
&eci&e& to calculate t"e power consumptionof &ifferent &evices(
% e assume& all t"e &evices power
consumption is alrea&' known an& its unit is
kilowatt( 7nerg'H/ower$ime (
% 7lectricit' CostH 7nerg';Cost /er Nilo-watt-
"ouruite well, .ut it
consumes more memor', w"ic" is not suita.le for small &evices( 9n or&er to &emonstrate
t"e via.ilit' of our s'stem we &emonstrate& t"e simple scenario, .ut we are 'et toanal'=e its result in a "ig"l' complicate& environment, w"ere man' services move to
an& fro, in an& out of t"e s'stems( sing S#M/ for management of /n/ .ase&
&evices, we coul& easil' manage "eterogeneous /n/ an& S#M/ .ase& &evices from
one single platform, particularl' in environments wit" large num.er of &evices,
7/25/2019 Design of Management Application
29/32
28Communications-#etwork Management $ec"nologies
Stdy case Managed network topologyStdy case Managed network topology
% All &evices on
t"e network areS#M/ ena.le&
% All client iFi
C/7s are
e>uipe& wit"
DD-3$
7/25/2019 Design of Management Application
30/32
+0Communications-#etwork Management $ec"nologies
Stdy case ApplicationsStdy case Applications
% $"ree simple applications
1< At t"e S#M/ Manager to get information a.out t"e connecte& s'stem
2< At t"e S#M/ Agent to inform a.out c"ange of clients &evice
+< At t"e S#M/ Manager:Agent to monitor t"e >ualit' of t"e wireless link
1< Managerif local$imeH20*00*00 P
repeat loop for iH1 until iHAS$ES73 P
?7$ ;s'stem(s'sDescr(0
7/25/2019 Design of Management Application
31/32
+1Communications-#etwork Management $ec"nologies
Stdy case SNMP Manager app Net.SNMP e+apleStdy case SNMP Manager app Net.SNMP e+aple
Uinclu&e Tnet-snmp:net-snmp-config("V
Uinclu&e Tnet-snmp:net-snmp-inclu&es("V
Uinclu&e Tstring("V
int main;int argc, c"ar argv