From 6ff3f7bd0d9d4ce8902963c0ed50a0f66cece10e Mon Sep 17 00:00:00 2001 From: elie Date: Wed, 28 Nov 2007 10:07:07 +0000 Subject: minor text and html fixes --- docs/pysnmp-tutorial.html | 35 ++++++++++++++++------------------- 1 file changed, 16 insertions(+), 19 deletions(-) (limited to 'docs') diff --git a/docs/pysnmp-tutorial.html b/docs/pysnmp-tutorial.html index 9e5e363..a4ad9cb 100644 --- a/docs/pysnmp-tutorial.html +++ b/docs/pysnmp-tutorial.html @@ -6,13 +6,12 @@ -

- -

PySNMP tutorial

-by Ilya Etingof, May 2006 +by Ilya Etingof, Nov 2007

Table of contents

@@ -65,9 +64,6 @@ PySNMP tutorial -

@@ -172,8 +168,8 @@ Modern SNMP standards suggest splitting Agent functionality on two parts. Such Agents may run SNMP for local processes called Subagents, which interface with managed devices internals. Communication between Master Agent and its Subagents is performed using a simplified version -of original SNMP protocol, known as AgentX, which is designed to run -only within a single system. +of original SNMP protocol, known as AgentX, which is +designed to run only within a single host.

@@ -331,11 +327,12 @@ protocol operations. SMI part of standard is inherited intact from SNMPv2.

SNMPv3 system is designed as a framework that consists of a core, known -as Message and PDU Dispatcher, and several abstract subsystems: -Message Processing Subsystem (MP), responsible -for SNMP message handling, Transport Dispatcher, used for -carrying over messages, and Security Subsystem, which deals -with message authentication and encryption issues. The framework defines +as Message and PDU Dispatcher, and several abstract +subsystems: Message Processing Subsystem +(MP), responsible for SNMP message handling, +Transport Dispatcher, used for carrying over messages, +and Security Subsystem, which deals with message +authentication and encryption issues. The framework defines subsystems interfaces to let feature-specific modules to be plugged into SNMPv3 core thus forming particular feature-set of SNMP system. Typical use of this modularity feature could be seen in multiprotocol systems -- legacy @@ -530,8 +527,8 @@ Message Processing subsystem.

Access Control subsystem uses LCD information to authorize remote access to -Managed Objects. This is used when serving Agent Applications or Trap receiver in -Manager Applications. +Managed Objects. This is used when serving Agent Applications or Trap +receiver in Manager Applications.

@@ -1435,16 +1432,16 @@ passed in as a string.

-Optional authKey parameter is a secret key used within -USM for SNMP PDU authorization. It's string type. Setting it to a non-empty +Optional authKey parameter is a secret key (string typed) +used within USM for SNMP PDU authorization. Setting it to a non-empty value implies MD5-based PDU authentication to take effect. Default hashing method may be changed by means of further authProtocol parameter.

-Optional privKey parameter is a secret key used within -USM for SNMP PDU encryption. It's string type. Setting it to a non-empty +Optional privKey parameter is a secret key (string typed) +used within USM for SNMP PDU encryption. Setting it to a non-empty value implies MD5-based PDU authentication and DES-based encryption to take effect. Default hashing and/or encryption methods may be changed by means of further authProtocol and/or -- cgit v1.2.1