scispace - formally typeset
Search or ask a question

Showing papers on "Network management published in 1989"


Patent
06 Dec 1989
TL;DR: In this article, an Expert System 10 for providing diagnostics to a data communications network 5 is described, where alarms from a Network Manager 24 are received and queued by an Event Manager 117 and then filtered by an Alarm Filter 118 to remove redundant alarms.
Abstract: An Expert System 10 for providing diagnostics to a data communications network 5. Alarms from a Network Manager 24 are received and queued by an Event Manager 117 and then filtered by an Alarm Filter 118 to remove redundant alarms. Alarms which are ready for processing are then posted to a queue referred to as a Bulletin Board 120. A Controller 112 determines which one of the posted goals has the highest priority by considering a priority number associated with the goal plus a time of arrival of the goal. An Inference Engine 122 uses information from an Expert Information Structure 111 to solve the highest priority goal by a process called instantiation. The process of solving the goal may be interrupted by a pause or suspension in order to perform tests under the direction of a Network Test Manager 124 or retrieve other information during which time other goals may be processed. Expert information is entered using a user friendly User Interface 104 which reduces need for the participation of a Knowledge Engineer. Configuration information about the network is maintained in a Network Structure Knowledge Base 109 by a Network Configuration Module 108. The Expert System 10 may operate in any of three modes: manual, wherein tests must be approved by or directed by an operator; automatic, where the tests are run automatically without operator intervention; and semiautomatic, where operator approval is required for certain tests such as interruptive tests and other tests such as non-interruptive tests may proceed without operator intervention.

146 citations


Proceedings ArticleDOI
15 Oct 1989
TL;DR: A distributed time-slot-assignment protocol for a mobile multihop broadcast packet radio network, using time division multiple access channel access, virtual circuit switching, and minimum hop path routing is developed.
Abstract: A distributed time-slot-assignment protocol for a mobile multihop broadcast packet radio network, using time division multiple access channel access, virtual circuit switching, and minimum hop path routing is developed. The protocol eliminates the single-point failure mode of centralized network management and the delays of centralized processing. It is applicable to the user-to-user communications functions of such systems as the Army's Enhanced Position Location and Reporting System (EPLRS). The important functions of the distributed protocol, including time-slot assignment, virtual circuit setup, and network synthesis, are identified, and implementing algorithms are presented and analyzed. >

99 citations


Proceedings ArticleDOI
10 Oct 1989
TL;DR: An overview is presented of the statistical sampling of measurements from a computer network, a necessary task in all five facilities of the proposed ISO network management architecture.
Abstract: An overview is presented of the statistical sampling of measurements from a computer network, a necessary task in all five facilities of the proposed ISO network management architecture. Network measurement, viewed from the standpoint of real-time status reporting, is performed either to approximate the condition of a network parameter over a given interval or to detect a significant change in system behavior over consecutive intervals. Appropriate statistical tools for sampling and analyzing traffic in real time are presented. >

56 citations


Proceedings ArticleDOI
10 Oct 1989
TL;DR: SAFENET (survivable adaptable fiber optic embedded network), a local area network profile covering all seven ISO/OSI layers, has been selected to meet the needs of systems used aboard the US Navy's combat ships and aircraft.
Abstract: SAFENET (survivable adaptable fiber optic embedded network), a local area network profile covering all seven ISO/OSI layers, has been selected to meet the needs of systems used aboard the US Navy's combat ships and aircraft and is one of the Navy's NGCR (Next Generation Computer Resources) programme standard sets which are being developed to provide an architecture for computing resources in future Navy systems. While much of the SAFENET profile is taken directly from the existing GOSIP and MAP profiles, requirements of the combat environment necessitate some different capabilities. Areas of concern include: network cable plant, provision and reconfiguration of redundant paths, support for time synchronization across the network, a real-time oriented transport protocol, network management, directory services, and communication from application process to application process. Activities of the SAFENET Working Group to overcome the shortfalls of commercial standards are discussed. >

43 citations


Journal ArticleDOI
TL;DR: Key areas of agreement and disagreement in the network management community are presented using the evolving open systems interconnection network management architecture as an informal guide.
Abstract: Key areas of agreement and disagreement in the network management community are presented using the evolving open systems interconnection network management architecture as an informal guide. A key observation is that the open-networking community has apparently settled on a management model that places management information base (MIB) on each network node and manages these MIBs remotely with application level protocols. Various network systems based on this model are examined, along with some systems that use alternative management architectures. >

39 citations


Journal ArticleDOI
M.R. Garzia1, C.M. Lockhart1
TL;DR: Compartmental modeling is applied to nonhierarchical circuit-switched networks allowing a formulation of network dynamics in terms of a system of deterministic equations among global variables, and steady-state results demonstrate the expected bistability property.
Abstract: Compartmental modeling is applied to nonhierarchical circuit-switched networks allowing a formulation of network dynamics in terms of a system of deterministic equations among global variables. Network dynamics under stress conditions of overload and damage are examined, and steady-state results demonstrate the expected bistability property. Network controls are implemented with the result that bistable behavior disappears. The model equations are sufficiently complex as to permit investigation of the relative merits of various network management controls and to capture time-sensitive effects, such as user calling behavior and time-varying network stress. Optimal control parameter setting is addressed for network steady-state conditions. While the model assumes a deterministic environment and trunk group blocking only, the model can be extended to include stochastic environments and switch related effects, such as queue overflow and delay. >

38 citations


Book
01 Jan 1989
TL;DR: The Intelligent Network’s architecture and Capabilities, including the Switching Layer and the OSS-1, have changed significantly in the past decade, and the design and management of these functions has changed significantly too.
Abstract: 1. Overview of the Intelligent Network.- 1. The Intelligent Network.- 1.1 IN Architecture and Capabilities.- 1.1.1 IN Goals.- 1.1.2 IN Technical Overview.- 1.2 IN Definition.- 1.2.1 IN Elements.- 1.2.2 An IN Service Example.- 1.3 IN-User Programmability.- 1.4 IN Introduction Scenarios.- 1.4.1 The Model.- 1.4.2 Introduction Scenarios.- 1.5 IN Architecture Validation.- 2. Functional Characteristics Common to Selected IN Services.- 2.1 Overview.- 2.2 Methodology.- 2.3 Summary of Findings.- 2.4 Standards.- 2.5 Service Interaction.- 2.5.1 Service User.- 2.5.2 Service Subscriber.- 2.5.3 SMS Access Instrument.- 2.5.4 Network Operator.- 2.6 Billing.- 2.6.1 SSP.- 2.6.2 SCP.- 2.6.3 SMS.- 2.7 Service Logic.- 2.8 Databases.- 2.8.1 Size.- 2.8.2 Database Integrity Requirements.- 2.8.3 Location of Databases.- 2.8.4 Database Administration.- 2.9 Transaction Rate Estimates.- 2.9.1 Methodology.- 2.9.2 Transactions Between SMS and its Users.- 2.9.3 SMS-SCP Transaction Rates.- 2.9.4 SCP- SSP Transaction Rates.- 2.10 Measurement Requirements.- 2.10.1 SSP.- 2.10.2 SCP.- 2.10.3 SMS.- 2.11 Performance and Dynamic Requirements.- 2.11.1 Response Time.- 2.11.2 Response Times for IN Elements.- 2.11.3 Overload Handling.- 2.12 Availability Requirements and Objectives.- 2.13 National Considerations.- 2.14 Future Considerations.- 3. Network and Service Management.- 3.1 Overview.- 3.2 Methodology.- 3.2.1 Summary of Findings.- 3.3 NSMS Requirements.- 3.3.1 NSMS Global Qualities.- 3.3.2 Basic Operations, Administration and Management Functions.- 3.3.3 Network Management Users.- 3.4 Switching Layer and the OSS-1. Overview of the Intelligent Network.- 1. The Intelligent Network.- 1.1 IN Architecture and Capabilities.- 1.1.1 IN Goals.- 1.1.2 IN Technical Overview.- 1.2 IN Definition.- 1.2.1 IN Elements.- 1.2.2 An IN Service Example.- 1.3 IN-User Programmability.- 1.4 IN Introduction Scenarios.- 1.4.1 The Model.- 1.4.2 Introduction Scenarios.- 1.5 IN Architecture Validation.- 2. Functional Characteristics Common to Selected IN Services.- 2.1 Overview.- 2.2 Methodology.- 2.3 Summary of Findings.- 2.4 Standards.- 2.5 Service Interaction.- 2.5.1 Service User.- 2.5.2 Service Subscriber.- 2.5.3 SMS Access Instrument.- 2.5.4 Network Operator.- 2.6 Billing.- 2.6.1 SSP.- 2.6.2 SCP.- 2.6.3 SMS.- 2.7 Service Logic.- 2.8 Databases.- 2.8.1 Size.- 2.8.2 Database Integrity Requirements.- 2.8.3 Location of Databases.- 2.8.4 Database Administration.- 2.9 Transaction Rate Estimates.- 2.9.1 Methodology.- 2.9.2 Transactions Between SMS and its Users.- 2.9.3 SMS-SCP Transaction Rates.- 2.9.4 SCP- SSP Transaction Rates.- 2.10 Measurement Requirements.- 2.10.1 SSP.- 2.10.2 SCP.- 2.10.3 SMS.- 2.11 Performance and Dynamic Requirements.- 2.11.1 Response Time.- 2.11.2 Response Times for IN Elements.- 2.11.3 Overload Handling.- 2.12 Availability Requirements and Objectives.- 2.13 National Considerations.- 2.14 Future Considerations.- 3. Network and Service Management.- 3.1 Overview.- 3.2 Methodology.- 3.2.1 Summary of Findings.- 3.3 NSMS Requirements.- 3.3.1 NSMS Global Qualities.- 3.3.2 Basic Operations, Administration and Management Functions.- 3.3.3 Network Management Users.- 3.4 Switching Layer and the OSS-an Example.- 3.5 Signaling Network and the SEAS.- 3.5.1 Management Functions Related to the Signaling Network.- 3.6 IN-Services and the SMS.- 3.6.1 Service Management System Overview.- 3.6.2 SMS Function Description.- 3.7 Administrative System Functions and IN Requirements.- 3.7.1 IN-Wide Service Management Examples.- 3.8 Trends.- 3.8.1 Evolving Operations Architecture.- 4. Network Components.- 4.1 Main Objectives of the IN Architecture.- 4.2 Network Topology.- 4.2.1 Performance and Throughput Requirements.- 4.2.2 Availability Requirements.- 4.2.3 IN Architecture.- 4.3 Service Control Point (SCP).- 4.3.1 Requirements.- 4.3.2 SCP Architecture.- 4.4 Signaling Transfer Point (STP).- 4.4.1 Functional STP Requirements.- 4.4.2 CCS7 Network Architecture and IN.- 4.5 Service Switching Point (SSP).- 4.6 Future Considerations.- 2. Green Number Service.- 5. GNS Service Description.- 5.1 Overview.- 5.2 Functional Description.- 5.3 Standards.- 5.4 Service Interaction.- 5.5 Billing.- 5.6 Service Logic.- 5.6.1 Distribution.- 5.6.2 Functional Flow.- 5.7 Traffic Measurement Requirements.- 5.8 Dynamic Requirements and Performance.- 5.9 National Dependencies.- 5.10 Future Considerations.- 6. GNS Application Description.- 6.1 Functional Requirements and Allocation.- 6.2 Functional Units in the EWSD SSP.- 6.3 Administrative Units in SSP.- 6.4 Functional Units in SCP.- 6.5 Administrative Units in SCP.- 3. Alternate Billing Service.- 7. ABS Service Description.- 7.1 Overview.- 7.2 Functional Description.- 7.3 Standards.- 7.4 Service Interaction.- 7.5 Billing.- 7.6 Service Logic.- 7.6.1 Distribution.- 7.6.2 Functional Flow.- 7.7 Traffic Measurements Requirements.- 7.8 Dynamic Requirements and Performance.- 7.9 National Dependencies.- 7.10 Future Considerations.- 8. ABS Application Description.- 8.1 Functional Requirements and Allocation.- 8.2 Functional Units in SSP.- 8.3 Administrative Units in SSP.- 8.4 Functional Units in SCP.- 8.5 Administrative Units in SCP.- 4. Emergency Response Service.- 9. ERS Service Description.- 9.1 Overview.- 9.2 Functional Description.- 9.3 Standards.- 9.4 Service Interaction.- 9.5 Billing.- 9.6 Service Logic.- 9.6.1 Distribution.- 9.6.2 Functional Flow.- 9.7 Traffic Measurement Requirements.- 9.8 Dynamic Requirements and Performance.- 9.9 National Dependencies.- 9.10 Future Considerations.- 10. ERS Application Description.- 10.1 Functional Requirements and Allocation.- 10.2 Functional Units.in SSP.- 10.3 Administrative Units in SSP.- 10.4 Functional Units in SCP.- 10.5 Administrative Units in SCP.- 5. Private Virtual Network.- 11. PVN Service Description.- 11.1 Overview.- 11.2 Functional Description.- 11.3 Standards.- 11.4 Service Interaction.- 11.5 Billing.- 11.6 Service Logic.- 11.6.1 Distribution.- 11.6.2 Functional Flow.- 11.7 Traffic Measurement Requirements.- 11.8 Dynamic Requirements and Performance.- 12. PVN Application Description.- 12.1 Functional Requirements and Allocation.- 12.2 Functional Units in SSP.- 12.3 Administrative Units in SSP.- 12.4 Functional Units in SCP.- 12.5 Administrative Units in SCP.- 6. Area Wide Centrex.- 13. AWC Service Description.- 13.1 Overview.- 13.2 Functional Description.- 13.3 Standards.- 13.4 Service Interaction.- 13.5 Billing.- 13.6 Service Logic.- 13.6.1 Distribution.- 13.6.2 Functional Flow.- 13.7 Traffic Measurement Requirements.- 13.8 Dynamic Requirements and Performance.- 13.9 National Dependencies.- 13.10 Future Considerations.- Appendix A. Supplementary Services.- Appendix B. Bellcore Preliminary-Defined Functional Components and Requests.

33 citations


01 Aug 1989
TL;DR: This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989, and the results of the first such meeting were reported in RFC 1052.
Abstract: This RFC reports an official Internet Activities Board (IAB) policy position on the treatment of Network Management in the Internet. This RFC presents the results and recommendations of the second Ad Hoc Network Management Review on June 12, 1989. The results of the first such meeting were reported in RFC 1052.

33 citations


01 Apr 1989
TL;DR: This memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base.
Abstract: This memo defines a network management architecture that uses the International Organization for Standardization's (ISO) Common Management Information Services/Common Management Information Protocol (CMIS/CMIP) in a TCP/IP environment. This architecture provides a means by which control and monitoring information can be exchanged between a manager and a remote network element. In particular, this memo defines the means for implementing the Draft International Standard (DIS) version of CMIS/CMIP on top of Internet transport protocols for the purpose of carrying management information defined in the Internet-standard management information base. DIS CMIS/CMIP is suitable for deployment in TCP/IP networks while CMIS/CMIP moves toward becoming an International Standard. Together with the relevant ISO standards and the companion RFCs that describe the initial structure of management information and management information base, these documents provide the basis for a comprehensive architecture and system for managing TCP/IP- based internets, and in particular the Internet.

23 citations


Proceedings ArticleDOI
L. Chang1, W.-L. Chan1, J. Chang1, P.D. Ting1, M. Netrakanti1 
27 Nov 1989
TL;DR: The Customer Operations Service Management Interface Control (COSMIC) system, a network status monitoring system used by an AT&T Network Control Center (NCC) to monitor the status of a large private telecommunications network is described.
Abstract: The Customer Operations Service Management Interface Control (COSMIC) system, a network status monitoring system used by an AT&T Network Control Center (NCC) to monitor the status of a large private telecommunications network is described. COSMIC integrates and correlates network alarm information and graphically displays the network's status on a near-real-time basis. COSMIC has established the use of personal computers for network status monitoring. Its main capabilities are in the areas of real-time graphical displays for network management. Its features include a hierarchical graphical display of the network configuration, alarm correlation, and additional database referencing features. COSMIC provides a user-friendly and easy-to-use interface to the technicians in the NCC. The system has been deployed in the NCC for more than a year, and the efficiency of network management operations with the NCC has improved substantially. The software and hardware architecture of the COSMIC system and the features and functionality it provides to the NCC are described. >

20 citations


Proceedings ArticleDOI
27 Nov 1989
TL;DR: The authors describe an AI-assisted, real-time, centralized network management prototype that consists of two cooperating AI (artificial intelligence) components: the LARS (learning and recognition systems) and a rule-based expert system (RBES).
Abstract: The authors describe an AI-assisted, real-time, centralized network management prototype that consists of two cooperating AI (artificial intelligence) components: the LARS (learning and recognition systems) and a rule-based expert system (RBES). The LARS system uses neural networks for the detection and isolation of communications network anomalies. This offers significant advantages over expert systems an conventional algorithms when dealing with complex patterns, ill-defined problems, and noisy input. The two-layer multiple manifold architecture greatly facilitates the training of the LARS system. The RBES is a real-time, data-driven expert system that is activated by the arrival of diagnostic messages from the LARS system. It uses diverse types of knowledge and reasoning techniques to assess the situation and recommend the application or removal of appropriate routing and traffic flow controls. A discrete-event network simulator (NETSIM) is assisting the development and testing of the above prototype,. The network management prototype can handle single and multiple anomalies, including node and link failures, link degradation, link congestion, and general overload. >

Proceedings ArticleDOI
27 Nov 1989
TL;DR: The authors describe the prototype application of selected techniques from artificial intelligence to selected network management problems and discuss possible applications of neural network techniques to switch message diagnosis.
Abstract: The authors describe the prototype application of selected techniques from artificial intelligence to selected network management problems. One software prototype supports tactical planning activities using knowledge-based system techniques. A second software prototype applies heuristic search techniques to a network design problem. The authors discuss possible applications of neural network techniques to switch message diagnosis. >

Journal ArticleDOI
TL;DR: The conception and implementation of the REB and CEB are discussed, along with the differences between the two brouters, and a detailed description of hardware and software architecture is given.

Journal ArticleDOI
03 Jan 1989
TL;DR: The method presented here is limited in the kinds of information it can display, but the authors believe that some method for diagramming MIBs like the one described here will be needed in the future.
Abstract: A method for pictorially representing objects in a Management Information Base (MIB) used for network management is presented. Although the method presented here is limited in the kinds of information it can display, the authors believe that some method for diagramming MIBs like the one described here will be needed in the future.

Book
01 Jan 1989
TL;DR: 1.1.
Abstract: 1. Data transmission 2. Error detection and recovery 3. Shared media 4. Flow control 5. Network routing and congestion 6. Network service and interface 7. Terminal support 8. Presentation 9. File transfer and access 10. Network mail 11. Application level services 12. Performance and system issues 13. Network management 14. Security and authentication 15. Gateways 16. Standards Glossary Index.

Proceedings ArticleDOI
06 Nov 1989
TL;DR: The application layer services of a field bus are presented, starting from the end-user needs for distributed field database management and compared with the MMS ones, pointing out the main differences.
Abstract: The application layer services of a field bus are presented, starting from the end-user needs for distributed field database management. The authors summarize the main basic principles used in MAC and logical link layers and explain the services for the application layer and network management. They compare these services with the MMS ones, pointing out the main differences. The question of compatibility between field bus and MAP networks is considered. >

Journal ArticleDOI
TL;DR: The growing web of computer networks has triggered a search for an organizing principle to monitor and control operations, and the various system management functions are identified and the development of network management standards is discussed.
Abstract: The growing web of computer networks has triggered a search for an organizing principle to monitor and control operations. The various system management functions are identified, and the development of network management standards is discussed. Particular attention is given to the Basic Reference Model for Open Systems Interconnection (OSI), developed by the International Organization for Standardization (ISO). >

Proceedings ArticleDOI
27 Nov 1989
TL;DR: An object-oriented operations model which permits the explicit representation and manipulation of operator activities in the network management system software is presented and the proposed activity-based user interface style is outlined.
Abstract: It is noted that network management systems can enhance the effectiveness of operators by providing goal-oriented user interfaces which support the way operators view their networks and their network operation activities. An object-oriented operations model which permits the explicit representation and manipulation of operator activities in the network management system software is presented. The benefits of the model include the selective grouping of tools relevant to operators' activities, the intelligent interworking and coordination of the tools within an activity, and the ability to manage an operation activity as a single entity. The model principles and the proposed activity-based user interface style are outlined, along with a prototype implementation and examples of the model's use for the management of packet switching networks. >

Proceedings ArticleDOI
10 Oct 1989
TL;DR: The simple network management protocol (SNMP) is an application protocol that allows logically remote users to inspect or alter management variables and its architectural principles are described.
Abstract: The simple network management protocol (SNMP) is an application protocol that allows logically remote users to inspect or alter management variables. The SNMP is typically used for the management network of networks, or internets, which utilize the TCP/IP protocol suite. A brief introduction to the SNMP is presented, and its architectural principles are described. The transport paradigm and SNMP applications are discussed. The status of the SNMP standard is described. Important lessons learned from the SNMP experience and a brief look at the future are included. >

Proceedings ArticleDOI
27 Nov 1989
TL;DR: A generic switching architecture that supports asynchronous time sharing and guarantees quality of service as negotiated at call setup is presented and exhibits switch fabric independence and only requires that the switch fabric be nonblocking.
Abstract: The concept of asynchronous time sharing is based on a multiclass network model and a distributed scheduling algorithm that provides guaranteed quality of service. There are three traffic classes for transporting user information and a fourth class for network management and control. Access to resources is resolved through a scheduling mechanism based on time sharing and space partitioning. A generic switching architecture that supports asynchronous time sharing and guarantees quality of service as negotiated at call setup is presented. The architecture exhibits switch fabric independence and only requires that the switch fabric be nonblocking. An operating implementation is described in detail. >

Journal ArticleDOI
TL;DR: In this paper, a version of the Kaiman filter algorithm is adopted to deal with traffic fluctuations in telephone networks, and the overall approach is tested against the real data gathered by the supervisor of the French toll network.
Abstract: Discrete- time stochastic models of sequential traffic records in telephone networks are considered. They appear to be well suited for a use of the Kaiman filter. A version of the filtering algorithm is adopted to deal with traffic fluctuations. The overall approach is tested against the real data gathered by the supervisor of the French toll network. The adaptive traffic estimator is inserted into a simulator of a testbed network operated in the urban zone of Paris. The traffic estimations provided by the filter are used to decide an overflow hierarchy.

Journal ArticleDOI
01 Mar 1989
TL;DR: An approach to real‐time expert systems for integrated network management, aimed at automatically maintaining Pacific Bell′s internal data networks, and an application for solving problems with travel tickets in real time.
Abstract: Describes an approach to real‐time expert systems for integrated network management. Presents an overview of expert systems technology, proceeding to develop the requirements for a real‐time system in network management. Describes a system being developed (1989) by Pacific Bell. Describes NETREX, a prototype real‐time system, aimed at automatically maintaining Pacific Bell′s internal data networks. Concentrates on an application for solving problems with travel tickets in real time.

Proceedings ArticleDOI
10 Oct 1989
TL;DR: The multiple crossbar network (MCN) will interconnect supercomputers, network servers, and workstations from various commercial vendors at the Los Alamos National Laboratories to serve as a framework for multicomputer applications.
Abstract: A description is given of the multiple crossbar network (MCN), a prototype high-speed local network. It will interconnect supercomputers, network servers, and workstations from various commercial vendors at the Los Alamos National Laboratories. The MCN can also serve as a backbone for message traffic between local area networks. The MCN is a switched local network of switching nodes called cross-point stars (CP*). Hosts and CP*s are connected by 800-Mbit/s (100-Mbyte/s) point-to-point ANSI high-speed channels. CP*s include RISC-based network protocol processors called crossbar interfaces and a switching core called the crossbar switch. Protocols include physical, data link, intranet, and network access functionality. Various internet and transport protocols are intended to run above the MCN protocol suite. A network management and simple naming service is also included within the Los Alamos network architecture. Immediate applications include visualization. The MCN is intended to also serve as a framework for multicomputer applications. >

Proceedings ArticleDOI
A. Kara1, S. Nakai1, M. Kawasumi1
27 Nov 1989
TL;DR: The kernel module of the proposed architecture is called the Network Resource Manager (NRM), which is a uniform management of the network objects which reside both in the individual subnetwork and in the INMS center.
Abstract: An architecture is proposed for an integrated network management system (INMS) based on an object-oriented approach. The INMS consists of a central manager (INMS center) and subnetwork management systems (subNMSs). Each of the subNMSs manages a subnetwork which usually consists of similar types of equipment. The INMS center manages network objects such as end-to-end paths and intersubnetwork links, which cannot be viewed from individual subNMSs. The network management protocols between the central manager and the subNMSs are based on the OSI (Open Systems Interconnection) systems management protocols. An object-oriented network modeling is devised to facilitate interfacing the network management software to the managed objects. The kernel module of the proposed architecture is called the Network Resource Manager (NRM). The principal function of the NRM is a uniform management of the network objects which reside both in the individual subnetwork and in the INMS center. >

Proceedings ArticleDOI
J.N. Brunken1, R. Mager1, R.A. Putzke1
11 Jun 1989
TL;DR: The NEtwork Management Operations System (NEMOS) as discussed by the authors is a system supporting AT&T's evolving Dynamic Non-Hierarchical Routing (DNHR) network.
Abstract: A description is given of the NEtwork Management Operations System (NEMOS), the operations system supporting AT&T's evolving Dynamic Non-Hierarchical Routing (DNHR) network. NEMOS provides the ability to monitor and control the nationwide DNHR network from a single site. The system is a multiprocessor application consisting of AT&T 3B20S processors and hardware relational database machines interconnected with the AT&T 3BNET local area network. Unique hardware and software contributions and state-of-the-art computer science techniques are used in the areas of fault-tolerant software systems, distributed systems and database processing, network management systems, particularly the automatic rerouting of calls to use idle capacity, and interactive graphics display systems. These topics, along with a general systems overview and operational experience are presented. >

Proceedings ArticleDOI
23 Apr 1989
TL;DR: A general approach to designing a hierarchical algorithm for routing in multi-domain networks is presented and a heuristic procedure suitable for packet-switched networks is proposed.
Abstract: The problem of management and control in a large and, for simplicity, homogeneous packet-switched network is investigated. In particular, routing is considered as an important function of network management. The network consists of several individually controlled domains interconnected via gateway links. Each domain is controlled by its own network control center, while the overall network performance is managed by the integrated network control center. Each center has only a portion of the information required for global routing. The impact of the reduced information available at each center on network performance is investigated. A general approach to designing a hierarchical algorithm for routing in multi-domain networks is presented. A heuristic procedure suitable for packet-switched networks is proposed. An example of the algorithm is shown. Its performance is compared against a lower bound to the network performance. >

Proceedings ArticleDOI
27 Nov 1989
TL;DR: An operations system designed to establish the network management and provisioning functions for a CCS network being deployed in Korea and applies part of SMX-1 itself to the front end of SIGNOS, anticipating that CCITT protocol no.7 will be suitable for signaling network management in the future.
Abstract: The authors describe an operations system designed to establish the network management and provisioning functions for a CCS (common channel signaling) network being deployed in Korea. The SIGNOS, which is a sort of centralized system to accommodate a number of SMX-1s (signaling message exchanges), consistently monitors and maintains the CCS network from a networkwide point of view to assure efficient utilization of the network. The authors introduce the system architecture and functions of SIGNOS and present an example of the interface between the operations system and network elements. In order to resolve the interface between SMX-1 and SIGNOS, the authors apply part of SMX-1 itself to the front end of SIGNOS, anticipating that CCITT protocol no.7 will be suitable for signaling network management in the future. >

01 Dec 1989
TL;DR: Program provides batch and device queueing facilities for various computers networked in UNIX environment and allows network manager to allocate and track resources across network without requiring user to specifically log in on remote target machines.
Abstract: Program provides batch and device queueing facilities for various computers networked in UNIX environment. Allows network manager to allocate and track resources across network without requiring user to specifically log in on remote target machines.

Proceedings ArticleDOI
S.-W. Yeh, C. Wu, H.-D. Sheng, C.-K. Hung, R.-C. Lee 
20 Sep 1989
TL;DR: An expert system for network management is designed and prototyped to do network troubleshooting automatically and shows that the expert-system-based fault management system can automatically diagnose problems and take corrective actions.
Abstract: An expert system for network management is designed and prototyped to do network troubleshooting automatically. The expert system employs management information provided by a monitoring mechanism of the network. The whole spectrum of the fault management information is analyzed. The management knowledge derived is categorized into five types: the physical property, the experience in the past, the heuristic rule of thumb, the predictable problems, and the deep knowledge. These knowledge types and related rules are divided into groups to improve reasoning speed. The expert system is composed of a problem manager, a problem analyzer, and many problem solvers. A prototyped expert system, using simulated faults, shows that the expert-system-based fault management system can automatically diagnose problems and take corrective actions. >

Journal ArticleDOI
01 Jul 1989
TL;DR: [ABRA82] W .H.
Abstract: [ABRA82] W .H. Abrahams, "Communications network management in the IB M Information Network", Proc . IEEE Fall COMPCON-82, Washington , D .C. (Sept. 1982), pp . 209-218 . [AGRE86] J .R. Agre, "A message-based fault diagnosis procedure", Proc . ACM SIGCOMM-86 Symposium on Communications Architectures & Protocols, Stowe, Vermont (Aug. 1986), pp . 328-337 . [AHMA88] M. Ahmadi, J .H. Chou, and G. Gafka, "Netview/PC", IBM Systems Journal Vol. 27 No. 1 (1988), pp . 32-44 . [ALBA88] A. Albanese and D. Shia, "Network management software for th e Bellcore METROCORE network", Proc . 13th IEEE Conference on Local Computer Networks, Minneapolis, MN (Oct. 1988), pp . 330-334. [AMER82] P.D. Amer, "A measurement center for the NBS local area computer net work", IEEE Transactions on Computers Vol. C-31 No . 8 (Aug. 1982) , pp . 723-729 . [AMER85] P.D. Amer and R.N. Kumar, "Local area broadcast network measurement, Part I Measurement center design and implementation", Technica l Report No . 85-3, Dept. of Computer & Information Sciences, University of Delaware, Newark, DE (April 1985) .