Network Management in Communication

18.12.1998

Zhou Yuchen
Department of Civil Environmental Engineering
Helsinki University of technology
Zhou@cc.hut.fi

Abstract

Network management has been an integral part of DECnet. Even at that early stage of the DECnet architecture, an effective management capability was recognized as an essential part of an organized approach to networking. The DECnet network management architecture has undergone a major revision based on Digital's Enterprise Management Architecture. The functions and service provided by a network management system are described to analyse the basic principles of network management architecture. At the same time, strengthly explain to importance of security and reliability of a network in network management system, and indicated advanced information processing techniques are taken for network management and network configuration management. Finally, shown us the good prospects of development network management.


1. Introduction

Our initial work on the network management were the broad range of networking functions planned. First, network managers would have to be able to manage all the components in a consistent manner. A method was needed to build management components that would give the same general look and feel and the same modeling approach to all components.

Second, network management would have to be extensible. The network architecture was being designed to allow the use of multiple modules that would provide the same or similar services at each layer and to simultaneously support multiple-layer protocols in a network. Therefore, the management architecture transparently assimilate new devices and technologies. Our management architecture had to become as extensible as the network architecture.

Finally, since network layer was designed to be an open architecture, management of network layer components would have to be effective in a multivendor network. Our design had to ensure that the ability to provide effective management of network components was independent of the vendors supplying them.

We began our development network project by examining in detail the requirements for a new network management architecture. Our goal was to design an open architecture that allowed for consistent management of an extensible array of network components in a multivendor environment. As we identified the specific requirements that would have to be addressed to meet this goal, we realized that we had the opportunity to develop a architecture that went beyond management of Phase V networks. We realized that we could provide an architecture for the management of both networks and systems. The architecture eventually became known as the Enterprise Management Architecture or EMA.

2. Functions of Network Management System

Network management tasks (eg. device polling) consume a considerable amount of bandwidth by themselves, so the system should be designed so that the distributed VR user interface does not add much more traffic.[6]

Early in the network management, we recognized that the conceptual separation of manageable components from the software that manages them was a fundamental design principle. EMA therefore distinguished entities, the basic components of the network that had to be managed, from directors, the software systems and accompanying applications used by managers to manage the components.[3]

Formally, an entity was further split into a service element, a managed object, and an agent. The service element is the portion of the entity that performs the primary function of the entity, e.g., a data link layer protocol module whose primary purpose is communication with a peer protocol module on another machine. The managed object encapsulates the software that implements the functions supported by the entity for its own management. For example, it responds to management requests for the current values of state variables or to requests for the values of certain configuration variables to be set to new values. The agent is the software that provides the interface between the director and the managed object. The agent encodes and decodes protocol messages it exchanges with the director and passes requests to and receives responses from the managed object.

Each network layer address of the node (a node can have more than one) is encoded in a standard way as a soft link to the node's name[3]. This allows a manager (or director) to translate a node address into the equivalent node name, making many diagnostic problems much simpler.

2.1 Service Provided by Network Management

In network management, the specification of the management of each module is an integral part of the architecture of the subsystem. Moving responsibility for the management of a subsystem from a central network management architecture to the subsystem architecture has made the specifications clearer and more complete. In network management, a great deal of effort was spent coordinating the subsystem specifications and the network management specification. Placing responsibility in one person's hands made writing an internally consistent subsystem much easier.

In DECnet/OSI, the transport, network, and data link subsystems were among the first to have the EMA concepts applied to their management. Others quickly followed and, presently, more than 50 modules have been specified, with others being added as new subsystems are designed[5]. Not surprisingly, during the early days considerable interaction took place between the architects responsible for the central network management architecture and those responsible for developing the management of specific subsystems. The EMA evolved and was refined based on the experiences of the many subsystem architects using it.

2.2 Communications Expertise of Network

The global telecommunications is able to service providers and Internet service providers (ISPs), helping them build the infrastructures they will use to deliver advanced services to their customers into the next century[2]. Our experience working with companies that support millions of users makes us uniquely qualified to work with companies that must support tens or hundreds of thousands of users.

A wide range of complementary capabilities including:

  • Mail and messaging solutions based on Microsoft Exchange
  • Collaborative computing and workflow solutions
  • Application development and integration
  • Data warehousing and information management
  • Industry-specific solutions for the manufacturing, financial services, and communications industries.

    Extensive knowledge of the global communications infrastructure maintains strong relationships with dozens of service providers around the world including large traditional telecommunications service providers, ISPs, and specialty carriers. We are working with these providers to extend their capabilities and infrastructures. This experience gives us the insight required to help you plan a strategic direction for your IP infrastructure.

    3. Network Management System

    We augment these general networking solutions with industry-focused solutions for communications, manufacturing, and financial services.

    At DIGITAL, we thrive on helping organizations around the globe win by confronting and resolving their toughest business challenges. As the top-ranked systems integrator in North America and one of the top five in the world, DIGITAL Worldwide Services excels at deploying proven technologies in powerful, innovative ways to solve complex, real-world business problems[2]. Our resources include a highly skilled and experienced workforce, a rich set of alliances with other technology and SI leaders, and a truly global services organization that can deliver consistent, high-quality support wherever you do business.

    DIGITAL integration solutions can help you: