Remote Monitoring MIB Extensions for Differentiated Services
RFC 3287

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 09

Network Working Group                                         A. Bierman
Request for Comments: 3287                           Cisco Systems, Inc.
Category: Standards Track                                      July 2002

                  Remote Monitoring MIB Extensions for
                        Differentiated Services

Status of this Memo

   This 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.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects used for monitoring
   Differentiated Services (DS) Codepoint usage in packets which contain
   a DS field, utilizing the monitoring framework defined in the RMON-2
   (Remote Network Monitoring Management Version 2) MIB.

Table of Contents

   1 The SNMP Network Management Framework ........................... 2
   2 Overview ........................................................ 3
   2.1 Terms ......................................................... 4
   2.2 Relationship to Differentiated Services ....................... 4
   2.3 Relationship to the Remote Monitoring MIBs .................... 5
   3 MIB Structure ................................................... 6
   3.1 DSCP Counter Aggregation ...................................... 7
   3.1.1 Counter Aggregation Configuration ..........................  8
   3.2 MIB Group Overview ...........................................  8
   3.2.1 DSCP Counter Aggregation Control Group .....................  9
   3.2.2 DS Statistics Group ........................................ 10
   3.2.3 DS Protocol Distribution Group ............................. 10
   3.2.4 DS Host Distribution Group ................................. 11
   3.2.5 DSMON Capabilities Group ................................... 12
   3.2.6 DS Matrix Distribution Group ............................... 13
   3.3 RMON vs. DSMON Indexing Structure ............................ 13
   4 Definitions .................................................... 16

Bierman                     Standards Track                     [Page 1]
RFC 3287                       DSMON MIB                      July 2002

   5 Counter Aggregation Configuration Usage Examples .............. 108
   5.1 Step 1: Unlock the Counter Aggregation Configuration ........ 109
   5.2 Step 2: Check the  Maximum  number  of  Counter  Aggregation
        Groups ..................................................... 109
   5.3  Step  3:  Check if the counter aggregation profiles already
        exist ...................................................... 109
   5.4 Step 4: Create the Counter Aggregation Control Entries ...... 109
   5.5 Step 5: Create the Counter  Aggregation  Group  Descriptions
        ............................................................ 110
   5.6 Step 6: Create the Counter Aggregation Profile Mappings ..... 112
   5.7 Step 7: Lock the Counter Aggregation Configuration .......... 115
   6 Intellectual Property ......................................... 115
   7 Acknowledgements .............................................. 116
   8 References .................................................... 116
   9 Security Considerations ....................................... 118
   10 Author's Address ............................................. 119
   11 Full Copyright Statement ..................................... 120

1.  The SNMP Network Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [RFC2571].

   o  Mechanisms for describing and naming objects and events for the
      purpose of management.  The first version of this Structure of
      Management Information (SMI) is called SMIv1 and is described in
      STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
      1215 [RFC1215].  The second version, called SMIv2, is described in
      STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580
      [RFC2580].

   o  Message protocols for transferring management information.  The
      first version of the SNMP message protocol is called SNMPv1 and is
      described in STD 15, RFC 1157 [RFC1157].  A second version of the
      SNMP message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and is described in RFC 1901 [RFC1901]
      and RFC 1906 [RFC1906].  The third version of the message protocol
      is called SNMPv3 and is described in RFC 1906 [RFC1906], RFC 2572
      [RFC2572] and RFC 2574 [RFC2574].