Static vs. dynamic CMIP/SNMP network management using CORBA

  • Luca Deri
  • Bela Ban
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1238)


The increasing complexity and heterogeneity of modern networks is pushing industry and research to look for a single and consistent way of managing networks. With the advent of open object-oriented distributed computing models such as CORBA, there are efforts to make the operational and management models the same, i.e. to manage and operate the network using CORBA.

The aim of this paper is to show some techniques that allow to manage CMIP/SNMP network resources using CORBA. Static techniques which map each managed object class into a corresponding CORBA interface are compared with dynamic techniques which rely on runtime information. Finally this paper demonstrates that CORBA-based network management applications are becoming attractive in terms of efficiency and application size, overcoming limitations of early solutions.


Network Management CORBA Scripting Language 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. [1]
    ISO/IEC, CCITT, Specification of Abstract Syntax Notation One (ASN.1), ISO/IEC 8824, CCITT Recommendation X.208, 1988.Google Scholar
  2. [2]
    B. Ban, Towards a Generic Object-Oriented Model for MultiDomain Management, Proceedings of ECOOP '96 Workshop on Systems and Network Management, Linz, Austria, July 1996Google Scholar
  3. [3]
    ISO/IEC, CCITT, Information Technology-OSI, Common Management Information Protocol (CMIP)-Part 1: Specification ISO/IEC 9596-1, CCITT Recommendation X.711, 1991.Google Scholar
  4. [4]
    L. Deri, Droplets: Breaking Monolithic Applications Apart, IBM Research Report RZ 2799, September 1995.Google Scholar
  5. [5]
    L. Deri, Surfin' Network Management Resources Across the Web, Proc. of 2nd IEEE Workshop on Systems and Network Management, Toronto, June 1996.Google Scholar
  6. [6]
    L. Deri, Network Management for the 90s, Proceedings of ECOOP '96 Workshop on Systems and Network Management, Linz, Austria, July 1996.Google Scholar
  7. [7]
    IBM Corporation, DSOM Development Toolkit, October 1994.Google Scholar
  8. [8]
    J. Hierro, Architectural Issues For Using CORBA Technology in OSI Systems Management, Append of draft to XoJIDM forum, August 1994.Google Scholar
  9. [10]
    Joint Inter-Domain Working Group, X/Open and Network Management Forum, Inter-Domain Management Specifications: Preliminary CORBA/CMISE Interaction Translation Architecture, April 1995.Google Scholar
  10. [11]
    P. Maes, Concepts and Experiments in Computational Reflection, Proceedings of the 2nd OOPSLA Conference, 1987, pp. 147–155.Google Scholar
  11. [12]
    T. Magedanz and T. Eckardt, Mobile Software Agents: A New Paradigm for Telecommunications Management, Proc. of 2nd Intl. IEEE Workshop on Systems Management. Toronto, Ontario, 1996.Google Scholar
  12. [13]
    Object Management Group, The Common Object Request Broker: Architecture and Specification, Revision 2.0, July 1995.Google Scholar
  13. [14]
    J. Case, M. Fedor, M. Schoffstall and C. Davin, The Simple Network Management Protocol (SNMP), RFC 1157, May 1990.Google Scholar
  14. [15]
    Joint Inter-Domain Working Group, X/Open and NMF, Inter-Domain Management Specifications: Specification Translation, April 1995.Google Scholar
  15. [16]
    ISO/IEC, CCITT, Information Technology — OSI — Management Information Services — Structure of Management Information — Part 4: Guidelines for the Definition of Managed Objects, CCITT Recommendation X.722, ISO/IEC 10165-4, 1992.Google Scholar
  16. [17]
    Object Management Group, CORBA-based Telecommunication Network Management System, OMG White Paper, Draft 2, Telecom Special Interest Group, January 1996.Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1997

Authors and Affiliations

  • Luca Deri
    • 1
    • 2
  • Bela Ban
    • 1
    • 3
  1. 1.IBM Research DivisionZurich Research LaboratoryRüschlikonSwitzerland
  2. 2.Institut für Informatik und angewandte Mathematik, Software Composition GroupUniversität BernBernSwitzerland
  3. 3.Institut für InformatikUniversität ZürichZürichSwitzerland

Personalised recommendations