Subject: snmpconf Non-numbered BCP To do item, or part 2 of #4 (fwd)

From: Jon Saperia <[email-masked]>
Date: Fri, 11 May 2001 11:23:49 -0400

Resend, I had an email problem. Sorry for any duplicates.
/jon
------- Forwarded Message

Date:    Thu, 10 May 2001 09:06:24 -0400
From:    Jon Saperia <[email-masked]>
To:      [email-masked]
Subject: Non-numbered BCP To do item, or part 2 of #4

> Reorganization of MIB design section

Done. here is a table of contents output, note that there still may be
some minor changes. 

/jon
                           Table of Contents

   1. INTRODUCTION ................................................    2
   1.1. Document Organization .....................................    3
   2. USING SNMP AS A CONFIGURATION MECHANISM .....................    3
   2.1. Transactions and SNMP .....................................    3
   2.2. Practical Requirements for Transactional Control ..........    4
   2.3. Best Practices in Configuration ...........................    5
   3. DESIGNING A MIB MODULE ......................................    8
   3.1. MIB Module Design - General Issues ........................    8
   3.2. Naming MIB modules and Managed Objects ....................    9
   3.3. Transaction Control And State Tracking ....................   10
   3.3.1. Fate sharing with multiple tables .......................   10
   3.3.2. Transaction Control MIB Objects .........................   10
   3.3.3. Usage of Row notReady Status ............................   11
   3.3.4. Summary Objects and State Tracking ......................   12
   3.3.5. Advanced Synchronization Considerations .................   14
   3.3.6. Conceptual Table Modification Practices .................   17
   3.4. Index Design Issues .......................................   18
   3.4.1. Simple Integer Indexing .................................   18
   3.4.2. Indexing with Network Addresses .........................   19
   3.4.3. Conflicting Controls ....................................   19
   3.4.4. Textual Convention Usage ................................   20
   3.4.5. Persistent Configuration ................................   21
   3.4.6. Configuration Sets and Activation .......................   22
   3.4.7. SET operation Latency ...................................   24
   3.5. Notifications and Error Reprting ..........................   26
   3.5.1. Designing Notifications .................................   26
   3.5.2. Control of Notification Subsystem .......................   27
   3.5.3. Application Error Reporting .............................   27
   3.6. Other MIB Module Design Issues ............................   29
   3.6.1. Octet String Aggregations ...............................   29
   3.6.2. Supporting multiple instances of a MIB Module ...........   30
   3.6.3. Use of special optional clauses .........................   31
   3.6.4. MIB Object and Practice Reuse ...........................   31
   4. IMPLEMENTING SNMP CONFIGURATION AGENTS ......................   31
   4.1. Operational Consistency ...................................   31
   4.2. Handling Multiple Managers ................................   32
   4.3. Designing MIB Modules for Multiple Managers ...............   33
   4.4. Specifying Row Modifiability ..............................   34
   4.5. Order of varbinds in a SET PDU ............................   34
   4.6. Implementing write-only access objects ....................   35
   5. DESIGNING CONFIGURATION MANAGEMENT SOFTWARE .................   35
   5.1. Designing Configuration Management Software ...............   36
   5.2. Protocol Operations .......................................   36
   5.3. SET Operations ............................................   37
   5.4. Configuration Transactions ................................   37
   5.5. Notifications .............................................   38
   5.6. Scale of the Management Software ..........................   38
   6. DEPLOYMENT AND SECURITY ISSUES ..............................   39
   6.1. Basic assumptions about Configuration .....................   41
   6.2. Secure Agent Considerations ...............................   41
   6.3. Authentication Traps ......................................   42
   6.4. Sensitive Information Handling ............................   42
   7. POLICY BASED MANAGEMENT .....................................   43
   7.1. Organization of Data in an SNMP-Based Policy System .......   43
   7.2. Conceptual Layering .......................................   44
   7.2.1. Conceptual Layering Diagrams ............................   48
   7.3. Information Related to Policy Based Configuration .........   49
   7.4. Policy, Mechanism/Implementation and Instance Specific
   Modules ........................................................   51
   7.5. Schedule and Time Issues ..................................   51
   7.6. Conflict Detection, Resolution and Error Reporting ........   52
   7.7. Notifications in a Policy System ..........................   53
   7.8. Using Policy to Move Less Configuration Data ..............   53
   8. EXAMPLE MIB MODULE FOR POLICY-BASED MANAGEMENT ..............   54
   8.1. NOTES ON MIB MODULE FOR POLICY-BASED MANAGEMENT ...........   65

Thanks,
/jon

- --
Jon Saperia		     [email-masked]
			     Phone: 617-744-1079
			     Fax:   617-249-0874
			     http://www.jdscons.com/
------- End of Forwarded Message