datatracker.ietf.org
Sign in
Version 5.6.2.p5, 2014-08-04
Report a bug

Reliable Server Pooling MIB Module Definition
RFC 5525

Document type: RFC - Experimental (April 2009; No errata)
Document stream: IETF
Last updated: 2013-03-02
Other versions: plain text, pdf, html

IETF State: (None)
Consensus: Unknown
Document shepherd: No shepherd assigned

IESG State: RFC 5525 (Experimental)
Responsible AD: Magnus Westerlund
Send notices to: rserpool-chairs@tools.ietf.org

Network Working Group                                       T. Dreibholz
Request for Comments: 5525                  University of Duisburg-Essen
Category: Experimental                                          J. Mulik
                                               Delaware State University
                                                              April 2009

             Reliable Server Pooling MIB Module Definition

Status of This Memo

   This memo defines an Experimental Protocol for the Internet
   community.  It does not specify an Internet standard of any kind.
   Discussion and suggestions for improvement are requested.
   Distribution of this memo is unlimited.

Copyright Notice

   Copyright (c) 2009 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Abstract

   Reliable Server Pooling (RSerPool) is a framework to provide reliable
   server pooling.  The RSerPool framework consists of two protocols:
   ASAP (Aggregate Server Access Protocol) and ENRP (Endpoint
   Handlespace Redundancy Protocol).  This document defines an SMIv2-
   compliant (Structure of Management Information Version 2) Management
   Information Base (MIB) module providing access to managed objects in
   an RSerPool implementation.

Dreibholz & Mulik             Experimental                      [Page 1]
RFC 5525                  RSerPool MIB Module                 April 2009

Table of Contents

   1. Introduction ....................................................2
   2. The Reliable Server Pooling (RSerPool) Framework ................2
   3. Conventions .....................................................2
   4. The Internet-Standard Management Framework ......................2
   5. Structure of the MIB ............................................3
      5.1. Access to Managed Objects on ENRP Servers .................10
      5.2. Access to Managed Objects on Pool Elements ................10
      5.3. Access to Managed Objects on Pool Users ...................11
      5.4. Persistency Behavior ......................................11
   6. Definitions ....................................................11
   7. Operational Considerations .....................................42
   8. Security Considerations ........................................42
   9. IANA Considerations ............................................43
   10. Acknowledgments ...............................................43
   11. References ....................................................44
      11.1. Normative References .....................................44
      11.2. Informative References ...................................44

1.  Introduction

   This memo defines a Management Information Base (MIB) module that
   describes managed objects for RSerPool implementations.

2.  The Reliable Server Pooling (RSerPool) Framework

   For a detailed overview of the documents that describe the current
   Reliable Server Pooling (RSerPool) framework, please refer to
   [RFC3237], [RFC5351], [RFC5352], [RFC5353], [RFC5354], [RFC5355], and
   [RFC5356].  A more informal introduction can be found at
   [RSerPoolPage] as well as in [Dre2006], [LCN2005], and [IJHIT2008].

3.  Conventions

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

4.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).

Dreibholz & Mulik             Experimental                      [Page 2]
RFC 5525                  RSerPool MIB Module                 April 2009

   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580

[include full document text]