Topic
Network management
About: Network management is a research topic. Over the lifetime, 17859 publications have been published within this topic receiving 234520 citations. The topic is also known as: computer network management & NM.
Papers published on a yearly basis
Papers
More filters
22 Oct 2007
TL;DR: This paper describes a new version of the DEN-ng policy model, which is part of the FOCALE autonomic network architecture, and is built using three guiding principles: the policy model is rooted in information models, so that it can govern managed entities, and the model is expressly constructed to facilitate the generation of ontologies.
Abstract: The purpose of autonomic networking is to manage the business and technical complexity of networked components and systems. However, the lack of a common lingua franca makes it impossible to use vendor-specific network management data to ascertain the state of the network at any given time. Furthermore, the tools used to analyze management data, which include information and data models, ontologies, machine learning algorithms, and policy languages, are all different, and hence require different data in different formats. This paper describes a new version of the DEN-ng policy model, which is part of the FOCALE autonomic network architecture. This new policy model has been built using three guiding principles: (1) the policy model is rooted in information models, so that it can govern managed entities, (2) the model is expressly constructed to facilitate the generation of ontologies, so that reasoning about policies constructed from the model may be done, and (3) the model is expressly constructed so that a policy language can be developed from it.
55 citations
Patent•
20 Dec 2002
TL;DR: In this paper, the automatic generation and storage of bundled error messages indicative of fault conditions of one or more managed networks is disclosed, which may provide more complete information relating to the managed networks such as information indicative of a detected fault condition as well as information describing the network on which the condition occurred.
Abstract: The automatic generation and storage of bundled error messages indicative of fault conditions of one or more managed networks is disclosed. The error messages may provide more complete information relating to the managed networks such as information indicative of a detected fault condition as well as information describing the network on which the condition occurred. Fewer duplicative error messages are generated and the number of “false-positive” messages is reduced while still preserving and providing important fault condition information to operators.
55 citations
Proceedings Article•
01 Nov 2006
TL;DR: The Leslie Graph is defined as the graph representing the dependencies between the system components, with subgraphs representing the dependency pertaining to a particular application or activity, and directed edges capture their inter-dependencies.
Abstract: It is lamentable that Leslie Lamport’s famous quote [9] “A distributed system is one in which the failure of a computer you didn’t even know existed can render your own computer unusable” describes a scenario familiar to almost every computer user As IT systems are increasingly distributed, it is not only the clients and servers themselves that can render a computer useless for an afternoon, but any of the many routers, links and network services also involved In distributed systems, the underlying problem is the absence of tools to identify the components that “can render your own computer unusable”: the implicit web of dependencies among these components exists only in the minds of the human experts running them The complexity of these dependencies quickly adds up, requiring more help than traditional IT management software provides Listing the contents of a single DFS 1 directory, for example, can involve a minimum of three hosts and eight network services (WINS, ICMP Echo, SMB, DFS, DNS, Kerberos, ISA key exchange, ARP) Existing management solutions focus on network elements, topology discovery, or particular services, but what is needed are tools to manage and improve the user’s end-to-end experience of networked applications In deference to Lamport, this paper defines the Leslie Graph as the graph representing the dependencies between the system components, with subgraphs representing the dependencies pertaining to a particular application or activity Nodes represent the computers, routers and services on which user activities rely, and directed edges capture their inter-dependencies Different versions of a Leslie Graph can express different granularities of dependence for an activity — for some analyses, an Leslie Graph capturing intermachine dependences at the granularity of IP addresses might be sufficient, while for others an Leslie Graph capturing inter-service dependencies at the granularity of software processes might be desirable This paper makes three contributions: (i) we define Leslie Graphs and discuss the challenges in finding them, (ii) we suggest important problems that Leslie Graphs could help
55 citations
TL;DR: In this article, a longitudinal examination of a publicly funded network of health and human services organizations that provide services to mentally ill adults is presented, where data were collected at two points in time from a single network in a large U.S. metropolitan area: when the network was completely reorganized and again when it had matured, four years later.
Abstract: This article is a longitudinal examination of a publicly funded network of health and human services organizations that provide services to mentally ill adults. Data were collected at two points in time from a single network in a large U.S. metropolitan area: when the network was completely reorganized, and again when it had matured, four years later. Analysis focuses on changes in the patterns of interaction within and across five resource-based subnetworks. The authors argue that the structure of network relationships depends on the type of resources involved—whether tangible or intangible, the stage of network evolution, and whether macro- or micro-level interactions are considered. Implications for theory and for network management, governance, and policy are discussed.
55 citations
TL;DR: This paper describes a new version of the Directory Enabled Networks next generation (DEN-ng) policy model, which is part of the FOCALE autonomic network architecture.
Abstract: The purpose of autonomic networking is to manage the business and technical complexity of networked components and systems. However, the lack of a common lingua franca makes it impossible to use vendor-specific network management data to ascertain the state of the network at any given time. Furthermore, the tools used to analyze management data, which include information and data models, ontologies, machine learning algorithms, and policy languages, are all different, and hence require different data in different formats. This paper describes a new version of the Directory Enabled Networks next generation (DEN-ng) policy model, which is part of the FOCALE autonomic network architecture. This new policy model has been built using three guiding principles: (1) the policy model is rooted in information models, so that it can govern managed entities, (2) the model is expressly constructed to facilitate the generation of ontologies, so that reasoning about policies constructed from the model may be done, and (3) the model is expressly constructed so that a policy language can be developed from it.
55 citations