RFC 2758 (rfc2758) - Page 3 of 71
Definitions of Managed Objects for Service Level Agreements Performance Monitoring
Alternative Format: Original Text Document
RFC 2758 SLAPM-MIB February 2000
operations and associated PDU formats is described in RFC 1905
[6].
o A set of fundamental applications described in RFC 2573 [9] and
the view-based access control mechanism described in RFC 2575
[11].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3.0 Structure of the MIB
The SLAPM-MIB consists of the following components:
o scalar objects
o slapmPolicyNameTable
o slapmPolicyRuleStatsTable (equivalent to the deprecated
slapmPolicyStatsTable)
o slapmPRMonTable (equivalent to the deprecated
slapmPolicyMonitorTable)
o slapmSubcomponentTable
Refer to the compliance statement defined within SLAPM-MIB for a
definition of what objects and notifications MUST be implemented by
all systems as opposed to those that MUST be implemented by end
systems only.
Initially most of the tables defined by the MIB module within this
document where directly indexed using a policy's name and a
subordinate traffic profile name. Over time the structure and
resulting naming has grown more complex and as such has exceeded the
capacity of being used as a direct MIB table index. As a result of
this the original tables (slapmPolicyStatsTable and
White Experimental