Definitions of Managed Objects for the Delegation of Management Scripts

Levi, David; Schoenwaelder, Juergen

doi:10.17487/rfc3165

Cited by 61 publications

(36 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Back in 1999 the IETF Distributed Management Working Group (DISMAN) was chartered to define a set of managed objects for specific distributed network management applications. Part of this group's work was the Definitions of Managed Objects for the Delegation of Management Scripts (Script MIB) [36] and the Distributed Management Expression MIB (Expression MIB) [37].…”

Section: Distributed Monitoring With Snmpmentioning

confidence: 99%

On the Performance and Scalability of Web Services for Monitoring MPLS-based Networks

2009

View full text Add to dashboard Cite

Web Services is an XML-based technology that has attracted significant attention for building distributed Internet services. Considerable research efforts have been trying to extend it to become a unifying management technology; initial evaluation efforts have demonstrated promising application potential in the domain of network and service management. This paper analyzes the monitoring requirements of a management system used in architectures for providing quality of service, and shows how Web Services can be used effectively to fulfill these requirements. In order to achieve this, a WS-based framework was designed and a query tool was developed to support distributed, optimized retrieval of management information exposed as Web Services. The query tool supports selective and bulk retrieval from MPLS-capable routers. Management information retrieval is demonstrated through three monitoring scenarios, and the measured performance in terms of latency and bandwidth is compared against a conventional approach based on SNMP.

show abstract

Section: Distributed Monitoring With Snmpmentioning

confidence: 99%

On the Performance and Scalability of Web Services for Monitoring MPLS-based Networks

2009

View full text Add to dashboard Cite

show abstract

“…Initially, the manager may describe some optional items to the specification (see figure 1, lines 2-7). Next, it is broken down into three sections: MessagesSection (lines 8-10), GroupsSection (lines [11][12][13] and StatesSection (lines [14][15][16], where messages to be observed, grouping and state machines that describe the trace are respectively specified. If the trace to be monitored belongs to a single application-layer protocol then the network manager may specify the TCP or UDP port number using the Port parameter (line 5).…”

Section: Organization Of a Specificationmentioning

confidence: 99%

“…When the mid-level manager sets the monitoring agent up (9,12), the former defines which protocol trace it should retrieve (it is indicated within the script that implements the task). Once retrieved (13), the trace file is loaded by the monitoring engine and the observation starts (14).…”

Section: Monitoring Agentmentioning

confidence: 99%

See 1 more Smart Citation

Distributed Management of High-Layer Protocols and Network Services through a Programmable Agent-Based Architecture

Gaspary

Balbinot

Storch

et al. 2001

Networking — ICN 2001

View full text Add to dashboard Cite

Abstract. This paper proposes an architecture for distributed management of upper layer protocols and network services called Trace. Based on the IETF Script MIB, the architecture provides mechanisms for the delegation of management tasks to mid-level managers, which interact with monitoring and action agents to have them executed. The paper introduces PTSL (Protocol Trace Specification Language), a graphical/textual language created to allow network managers to specify protocol traces. The specifications are used by mid-level managers to program the monitoring agents. Once programmed, these agents start to monitor the occurrence of the traces. The information obtained is analyzed by the mid-level managers, which may ask action agents for the execution of procedures (Perl scripts), making the automation of several management tasks possible.

show abstract

“…There are problems with potentially restricted message sizes and an overshoot effect if bulk transfer is utilized (in SNMPv2). SNMPv3 does allow data compression by adding encryption envelopes [11] and has belatedly introduced a form of management delegation [12], but the main emphasis of SNMPv3 remains security and not scalability. Nevertheless, for management applications deployed on larger networks, lack of scalability remains an issue, leading to a number of proposals for decentralized solutions including distributed object management [13], web-based management through push management [14], and Directory Enabled Networks [15].…”

Section: Introductionmentioning

confidence: 99%