о뷢չ
JOURNAL OF COMPUTER RESEARCH AND DEVELOPMENT
1999ꡡ3610ڡVol.36No.101999



һֻWebģͼʵ
ľ
ժҪĸӺ칹ҪߵĹ.һֻWebģ.ģͲʷģΪ洢ϢģͣԴΪܹһоĸ߼Ժ͸Ĺṹ.и˸ģʵֵĲνṹ.˸ģ͵ԭʵ.
ؼʡWebģͣ
ͼšTP393
A MODEL AND IMPLEMENTATION FOR WEB-BASED
NETWORK MANAGEMENT
LI Mu-Jin and WANG Guang-Xing
(Center for Network & Communications, Northeastern University, Shenyang 110006)
AbstractAs today's network has become more complex and heterogeneous as well, there is a growing demand for network management tools. A model for Web-based network management is proposed in this paper. A temporal data model is adopted as the underlying information model, and more complex management application(e.g., proactive network management) methods and management architecture of high-speed networks are studied. ATM switches are built on the top of the model. Moreover, the services provided by this model, as well as the architecture of its related software supporting them are presented. The description of the prototype is also given at the end of the paper.
Key wordsWeb, network management model,proactive network management,network management
1
żͨŹģĲ临Ӻ칹Ҫ׼.ĿǰҪ׼ISOOSIϵͳIETFļЭ飨SNMP.
еϵͳHPOpen ViewIBMSystem View AIXSNACabletronSpectrumDECPolycenterSunsoftSunNet ManagerMadgeTrue ViewȵȣЩֻṩӺһͼûӿڣGUIʽʾҪıϢܣûд洢ʷݵĹܣ12.
Webϵͳһṹǻbrowser-serverṹ(μͼ1).ÿ豸һagentάһֲĹϢ⣨MIBҺפڷĹӦͨЭSNMP3ݻCMIP4ݽͨ.Ӧú͹֮ĽϢϢ޸ģӶʵִӼ״̬ıõĸ.


ͼ1Webһṹ
ݿWWW(world wide web)ĲϷչݿ洢MIBɼĹϢĵǰ͹ȥģϢݿ.ڴ˻ϣݿ洢ϢзԤ⣬ƺ͹Եȸ߼ԼоĹϵṹATM.WebԲܲƽ̨ƣκһ̨֮WebϾ.ڵ·ʱϵͳܹԶԱE-mail绰.ԱԲֳκεصκһ̨֮WebϾܶй.
УȶOSI˷ϸظģͺ.Ȼʵָģ͵ṹĹ.˸ģ͵ʵ.
2ģ
2.1
ĿǰֲͬϢģͣһISO4ݵģһIETF35ݵ.ģ;νıĶΪģɹϢ⣨MIB.ISOϢģǳģĶǱĶ.IETFģͽϼ򵥣бĶֳܹࣺ(scalar)ͱtable.ǱĶά飬ñǹϢļ򵥱.
ڵ豸۲һģͣΪеṩϢÿĹϢں̶ܴǲͬģμͼ2.ΪˣǽϢ⣨MIBϢϸ.


ͼ2Ϣ֮Ĺϵͼ
1ϢãϢԷֳɲݡṹݺͿ3ͣ1ݣݱʾɹ۲״̬һԭʼ.ṹ߼ĽṹݲĲ.2չϢ仯Ƶ֣ϢԷֳ׼̬Ͷ̬.׼̬˵ǰãĽӿĿ·ɱȣǵֵ.̬¼йأĿȣǵֵ仯Ƶʸ.3ʱҪһʵʱܼӵĹӦúһݷĹӦãʱҪŸĲͬ.ֲҪϵͳʱҪйܵʷϢ.ǽʱֳ3ʵʱʱʱٽȫʱ.ʵʱʱʵʱйأʱٽĳʱйصĲйأȫʱǻڳڵϢϵйز.
۵㣬һOSIĹܹ3ڣ
(1) ù.ṩһϢļдȡһù豸ơϵͳλúϵͳйص.ӿռ䶨Ϊȫʱ׼̬ϢṹݣһΪӵùܹԶռʹ洢װõϢ洢ڸùڵĿϵͳǰýбȽϣʹûܹ޸豸ãӿռ䶨Ϊʱٽ׼̬Ϣ.
(2) ܹ.罫ǰû޽бȽжǷޱܹӿռ䶨Ϊʵʱ̬Ϣ.
(3) Ϲ.һⱻ·ÿӿڽյĴ䳬Ԥȶֵ򱨾ĹϹӿռ䶨Ϊʵʱ̬Ϣ.һҵбӿڵifAdminStatusifOperStatusֵжϸýӿ״̬ĹϹӿռ䶨Ϊʵʱ׼̬Ϣ.
2.2ģ
ĵһǴбĹϢɼϢ洢ݿ.ǰ֪洢ݿĹϢǰϢҰʷġϢ.ʷݿĺ.Աֻݿ򽻵ﵽĿ.
TRDMʷģ洢ʷݣģͻͨڱ׼ϵʱvalidFrom, validToõֹϵģvalidFrom,validToݱʾ֮ڴʱڵֵЧǶ뵥ʱvalidAtչ׼ϵ.validAtʾһ¼ʱ.
µʷģ͵Ĺ۵㣬Ϣ⣨MIBÿһͱӳֱʽ.validFrom, validTovalidAtʱֵʾڹߣmanagerʱ䣬Ϣ⣨MIBʱйصֵMIB-IIsysUpTime, ifLastChangeԼSNMPv2M2MMIBsnmpEventLastTimeSentȱʾڼʽṹڴʱڷֲʽṹмڵ㴦ʱ.ӳSNMPv2MIBsʱйصĶֵַܹʽʾпŵ.
ǽʷݿֳ׼̬ʷݿͶ̬ʷݿ.׼̬ʷݿɹϢ⣨MIB׼̬ɣ̬ʷݿɹϢ⣨MIBĶ̬.һipRouteTable׼̬ʷݵͼ3ʾvalidToֵرʾһֱЧ.һipĶ̬ʷݵͼ4ʾֵʾʱvalidFrom, validToڵĲֵ.ʷݿִܹеĶǴͬ.׼̬ʷݿִܹмӡɾ滻̬ʷݿִܹм.

Valid time
nodeIDipRouteDestIpRouteNextHop(from)(to)
NEU202.18.10.8202.118.10.2115070
center202.18.10.7202.118.10.21270


ͼ3ipRouteTable׼̬󲿷ʷ

Valid time
NodeIDIpInReceivesipForwDatagramsIpOutRequests(from)(to)
Center495884466


ͼ4IpĶ̬Ĳʷֵ
ģ͵Ĳνṹͼͼ5ʾ.ڵͲ㣬Network Monitorsһѯ䱻ɼʹ洢׼̬Ͷ̬ϢNetwork Executorsʵ׼̬ӡɾ滻.м䣬ṩʷϢĶ̬׼̬Ϣ.ϲ㣬.


ͼ5ģ͵Ĳνṹͼ
3ṹ͹
żͨŹģĲЩǾLAN'sǳMAN'sǹWAN's1ݵɣЩ罫ǸӺ칹.Ҫйǰĳַʽ岻ͬÿʹһ.ÿߺѯװúһĹϢģͣɼĹϢģʹʷݿ.
ģ͵ĽṹǹϢ⣨MIBṹչͨMIBĶʱʵֵģԱŹϢ⣨MIB.WebϵͳַʽÿĹߵʷݿܹκĹߵʷݿͨţַͨʽܹһĻ֮ṹһ÷ֲʽhierarchical67ݵĻƽ̨TINAṹ8ݣԽʡɼõͨŴˮƽɿԵ.
ַʵֵνṹ9ͼ6ʾÿвκԪأ


ͼ6ʵֵνṹ
(1) 1
һSNMPЭ.ṩSNMPv1 get-request, getnext-request, set-request, get-response trapԭӲϢԭʼ.Э鲻SNMPv1Э.SNMPv2CMIPԼκЭҲܱһ.
(2) 2
һṩ3ַ.
1ṩ޸ϢMIBķ񣬲һSNMPԭӷset-request֮.޸ãĿΪ˱ȹ涨ܼ͵Ԫطʱϻָװ.
2ṩӷ.һֳܷʵʱܼӷʵʱ״̬ӷ.
3ṩɼʹMIBϢķ.
(3) 3
һɸ߼ԣԣ.ʵֶԶӦĹ.òǻڵ2Ļʵֵ.
4ʵ
4.1ԭ͵
Ϊʵģͣǿ˰ĳЩԭ.ǽԭ͵ҪԼǵľ.
ԭڷΪWindows NT4.0 server, SQL server 6.5Ļʵֵ.õЭSNMPv1͹ϢMIB IIMIBAToMMIB׵صõ.Ϊ˻ñϢǲѯķѯҪɼԼĽڵй.⣬ǻһStatus MIBMIBı洢ڵ״̬Ϣ.ASN.1¼.
ԭʵֵĽṹʾͼͼ7ʾ.ÿҪɣѯ̺ʵWWWҳĽ.


ͼ7ԭʵֵĽṹ
ǵĿУѯVisual C++ 5.0Աдĳʵֵ.óںִ̨Уһѯɼ޸ı豸ĹϢ.ѡӼӰ쵽Ĵ٣ҲӰ쵽洢ЩʷݵĴ̿ռĴС.׼̬˵ѡڣ30,3֣֮䣬ڶ̬˵ѡڣ30룬90֮㹻.
WWWܹģ顢ùģ͹Ϲģ.ActiveXؼWWWҳʵʱغͶ̬ؽн.WWWҳ¹ܣ
(1) ʵʱвԴĲ״̬MIBƺñ
(2) ʵʱʾߺʷߣ
(3) ʵʱʾͼ
(4) ʵʱʾ״̬緢ʱϵͳԶϻָͷE-mail
(5) ԭʼϢά.
ǵϵͳܹʵܹϹù.ƪƣصܹ.
4.2ܹ
ǸʾܹйصĲܲ·ʡʣĹʽ.Щʽģṩǰʷݣֵܹͨܲ⵽豸״̬ЩܲݡʽͼʾWebҳ(СʾĳһʱڵĲֵ)

*ؽڵ(for nodes acting as gateway);

ʱ仯ͼʾͨԱ֪Щı仯.
ʿ⴫ýĹϣܹӸýӿڵ.̫EthernetսĶ͵½յİ.ʴһֵܱʾĳ˿ڷ.⣬ҲΪö˿ڶ.
ʣĲTCP/IPй.磬ϸʺTCPظ͸ʿԼTCP/IPֵĹϺ.
ЩֵԤȶֵʱ򱨾ʾʱ䡢صȺͷE-mail.һЩܹ߼ܹԣMIBϢһԤ⣩Խ.
5
۵ķѾõɹҡ߼ƻĿ⡰ҵIntranetо.Ա÷1˵ŵ֮⣬ص㣺
(1) ѯʷϢ㣬Ҿʵʱԣ
(2) ʡϢռõĴ
(3) ʡ洢ϢӲ̿ռ䣻
(4) пŵ.
õҡƻĿ863511711003ȻѧʽĿ69583001͹ҽίʿĿ9514514.
߼:ľУ196310ʿоҪоΪͶýͨо.
ˣУ19379ʿʦڣҪоΪͶýͨо.
ߵλ:ѧͨġ110006
ο
1Jayant R, Haritsa, Michael O Ball, Nicholas Roussopoulos et al. MANDATE: Managing networks using database technology. IEEE Journal on Selected Areas in Communications, 1993, 11(9): 13611372
2Kyu-Young Whang, Stephen Brady. High-performance expert systemDBMS interface for network management and control. IEEE Journal on Selected Areas in Communications, 1989, 7(3): 408417
3Case J, Fedor M, Schoffstall M et al. A simple network management protocol. DDN Network Information Center, SRI International, 1990
4Information processing, open system interconnection, common management information protocol (CMIP). International Organization for Standardization and International Electrotechnical Committee, International Standard 9596
5Rose M, McCloghrie K. Structure of management information for TCP/IP based Internets. DDN Network Information Center, SRI International,1990
6Ying-Dar Lin, Mario Gerla. Induction and deduction for autonomous networks. IEEE Journal on Selected Areas in Communications, 1993, 11(9): 14151425
7Manfred R Siegl, George Trausmuth. Hierarchical network management: A concept and its prototype in SNMPv2. Computer Networks and ISDN Systems, 1996, 28: 441452
8Raouf Boutaba, Simon Znaty. An architectural approach for integrated network and systems management. Computer Communication Review, 1995, 20: 1378
9Jonathan Weinstock, Rajiv Tewari. An object-oriented approach to the management of distributed application systems. Computer Networks and ISDN Systems, 1997, 29: 18691879
¼
Status MIBASN.1£
DIAGNOSIS-MIB DEFINITIONS =BEGIN
EXPORTSeverything-;
IMPORTS
OBJECT-TYPE, OBJECT-GROUP
FROM SMI-SMI
Enterprise, IPAddress
FROM RFC1155-SMI
DisplayString
FROM RFC1213-MIB;
DiagnosisMIB OBJECT IDENTIFIER = {enterprise 627}this number is NOT official
DIAGGroup OBJECT-GROUP
OBJECTS { DiagTreeNMSid}
DESCRIPTION
The diagnosis group.
={DiagnosisMIB 1}
DiagTree OBJECT-TYPE
SYNTAX SEQUENCE OF DiagTreeEntry
ACCESSnot-accessible
STATUSmandatory
DESCRIPTION
Table in which each testing node keeps network diagnosis info.
= { DIAGGroup 1 }
DiagTreeEntry : OBJECT-TYPE
SYNTAXDiagTreeEntry
ACCESSnot-accessible
STATUSmandatory
DESCRIPTION
Each entry of DiagTree identifiers which node the testing node recognized as up in the last testing round.
INDEX {testingID}
= { DiagTree 1}
DiagTreeEntry =SEQUENCE { NodeIDINTEGER,
NodeADIpAddress,
NodeStatusINTEGER, }
NodeID OBJECT-TYPE
SYNTAXINTEGER
ACCESSread-only
STATUSmandatory
DESCRIPTION
The integer unique identifer of all the nodes participating
= { DiagTreeEntry 1 }
NodeAD OBJECT-TYPE
SYNTAXIPAddress
ACCESSread-write
STATUSmandatory
DESCRIPTION
IP-address of all the nodes participating
= { DiagTreeEntry 2 }
NodeStatus OBJECT-TYPE
SYNTAXINTEGER
ACCESSread-write
STATUSmandatory
DESCRIPTION
0-node is fault-free; 1-node is faulty; 2-node replies to ping but not to SNMP.
= { DiagTreeEntry 3 }
NMSid OBJECT-TYPE
SYNTAXIPAddress
ACCESSread-write
STATUSmandatory
DESCRIPTION
Used by the human manager to set the id of the machine from which someone is monitoring the network
= { DIAGGroup 2}
END
Diagnosis MIBDiagTreeԼSNMPʽʵ.NodeIDÿڵıţ1-NNodeADǸýڵIPַNodeStatusʾڵ豸״ֵ̬0-1-ϣ2-PingӦǶSNMPûӦ
NMSidǷվIPַϢ洢ڸ÷վ.
ԭյڣ1998-12-02
޸ĸյڣ1999-03-22.
