A redundant file server includes at least two dual processor boards. Each physical processor has two logical processors. The first logical processor of the first physical processor of each board executes storage system code under the Microsoft NT™ operating system. The second logical processor of the first physical processor of each board executes control station code under the Linux operating system. The first logical processor of the second physical processor of each board executes data mover code. The second logical processor of the second physical processor of each board is kept in a stand-by mode for assuming data mover functions upon failure of the first logical processor of the second physical processor on the first or second board.

Redundant multi-processor and logical processor configuration for a file server

The development and maintenance of network device configurations is one of the central challenges faced by large network providers. Current network management systems fail to meet this challenge primarily because of their inability to adapt to rapidly evolving customer and provider-network needs, and because of mismatches between the conceptual models of the tools and the services they must support. In this paper, we present the Presto configuration management system that attempts to address these failings in a comprehensive and flexible way. Developed for and used during the last 5 years within a large ISP network, Presto constructs device-native configurations based on the composition of configlets representing different services or service options. Configlets are compiled by extracting and manipulating data from external systems as directed by the Presto configuration scripting and template language. We outline the configuration management needs of large-scale network providers, introduce the PRESTO system and configuration language, and reflect upon our experiences developing PRESTO configured VPN and VoIP services. In doing so, we describe how PRESTO promotes healthy configuration management practices.

/pdf/configuration-management-at-massive-scale-system-design-and-2a4fzp409n.pdf

Configuration management at massive scale: system design and experience

As the complexity of Internet of Things (IoT) systems increases, a large variety of tools and technologies for IoT management are making their way into both research setups and the market. IoT management solutions must consider the resource restrictions of embedded devices, as well as their heterogeneity and network dynamics. With these in mind, the Internet Engineering Task Force developed several standards targeting the integration and interoperation of heterogeneous devices, such as the Representational State Transfer Configuration Protocol (RESTCONF) or the Constrained Application Protocol (CoAP) Management Interface. Concurrently, the Open Mobile Alliance developed the Lightweight Machine-to-Machine protocol, for IoT device management. This paper provides a comprehensive, up-to-date overview of IoT management technologies, frameworks and protocols. Also, it proposes a taxonomy for IoT devices management. In addition to presenting the various solutions, the paper provides comparative views, standardization timeline, and market analysis. The presented analysis ranges from traditional network management protocols, such as Simple Network Management Protocol, to the newest IoT management and configuration protocols, such as CoAP Management Interface and Lightweight Machine-to-Machine protocols. Moreover, this survey identifies remaining challenges and solutions offered by recent management protocols, not covered by previous surveys.

A Survey of IoT Management Protocols and Frameworks

Recently, REpresentational State Transfer (REST) has been proposed as an alternative architecture for Web services.In the era of Cloud and Web 2.0, many complex Web service-based systems such as e-Business an de-Government applications have adopted REST. Unfortunately, the REST approach has been applied to few cases in management systems, especially for a management system for cloud computing infrastructures.In this paper, we design and implement a RESTful Cloud Management System (CMS).Managed elements can be modeled as resources in REST and operations in existing systems can be evaluated using four methods of REST or a combination of them.We also show how components of existing management systems can be realized as REST-style Web services.

A RESTful Approach to the Management of Cloud Infrastructure

Network, system and service management has evolved into an important scientific discipline over the last 20 years. While management problem solving is expected to continue ad infinitum, one would have expected that, after 20 years of research and standardization, an agreement would have been reached regarding a common management framework and protocol. But despite relevant progress and various available solutions, there seems to exist a permanent quest for the all encompassing next generation management technology. This paper looks at the evolution of management approaches, frameworks and protocols over the last 20 years, proposes a relevant taxonomy, presents the salient features of the representative tecnologies and discusses relevant issues. The purpose of this paper is to document historically this evolution, highlight important design choices and explain the how's and why's behind the various frameworks and technologies. The paper is concluded with a summary and future outlook.

/pdf/on-the-evolution-of-management-approaches-frameworks-and-6xkcmpt97p.pdf

On the Evolution of Management Approaches, Frameworks and Protocols: A Historical Perspective

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 the Internet. [STANDARDS-TRACK]

B. D. Handspicker

Papers

Common Management Information Services and Protocols for the Internet (CMOT and CMIP)