2001
DOI: 10.17487/rfc3165
|View full text |Cite
|
Sign up to set email alerts
|

Definitions of Managed Objects for the Delegation of Management Scripts

Abstract: Definitions of Managed Objects for the Delegation of Management Scripts Status of this MemoThis document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
31
0
4

Year Published

2001
2001
2009
2009

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 61 publications
(36 citation statements)
references
References 22 publications
0
31
0
4
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%
“…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%
“…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
“…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%